TSM Server service does not start in the Windows 2003 Server environment

shahzeb

ADSM.ORG Member
Joined
Nov 5, 2002
Messages
34
Reaction score
0
Points
0
Website
Visit site
I have installed a TSM Server in the Windows 2003 Standard Edition Server environment. After rebooting the server I find out, that TSM Server service does not start. I get message - The TSM Server1 Service on Local Computer Started, and then stopped. Some service stop automatically if they have no work to do for an example the performance logs and alert service.



Anybody had this kind problem with Windows 2003, that the TSM Server service does not start. Please advise. Thanks.
 
The best way to see exactly what is the problem, start TSM at the command line ( ..\program files\tivoli\tsm\server\dsmsrv.exe) that should give you a good idea.



YT
 
Thanks for the response. I did use dsmserv command, and is complaining, that it cannot recognize the language. I did update the dsmserv.opt file, but still it is picking up the language problem. Event viewer is showing, that the TSM Service started, and stopped.
 
Can You please privide us the language of the Win2k3 Server.



I myself experienced problems installing TSL in the "Program Files" Folder and decided to install on "C:\" to avoid these problems!
 
Hello Shahzeb,



i had the same problem. I think there is a bug in the installprogram.

After the installation you have to copy the file :



CDROM:\TSM32\SERVER\PROGRAM FILES\TIVOLI\TSM\SERVER\DSMAMENG.TXT



to:



C:\PROGRAM FILES\TSM\SERVER
 
Hello Shahzeb,



i had the same problem. I think there is a bug in the installprogram.

After the installation you have to copy the file :



CDROM:\TSM32\SERVER\PROGRAM FILES\TIVOLI\TSM\SERVER\DSMAMENG.TXT



to:



C:\PROGRAM FILES\TSM\SERVER
 
Hello Shahzeb,



i had the same problem. I think there is a bug in the installprogram.

After the installation you have to copy the file :



CDROM:\TSM32\SERVER\PROGRAM FILES\TIVOLI\TSM\SERVER\DSMAMENG.TXT



to:



C:\PROGRAM FILES\TSM\SERVER
 
resolution: I rebooted the server (backup server) to resolve the issue.
 
Back
Top