Enabling server service startup log
Is there any logging to check what the server is doing when starting the server as a service?
When starting the Tivoli Storage Manager server in the foreground using dsmserv command, there are logging information in the command windows to see what actions the server is taking. However, if the server is started using the Windows service, there is no logging information. This is especially helpful when debuging problems in regard to the service failing to start.
By default, the service logging is off. You can enable the service logging by modifying the registry. Assuming the server instance is Server1, Issue the following Windows command to update this registry value:
reg add HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\Server\Server1\Service /v LogOutputToFile /d 1 /t reg_dword /f
The location of the service log is specified in the registry HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\Server\Server1\Service\LogFile
When you are done with your debugging, disable the service logging so the log file will stop growing. To disable service logging, issue the following command (again assuming the server instance is Server1):
reg add HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\Server\Server1\Service /v LogOutputToFile /d 0 /t reg_dword
The workaround described in this article requires you to use the regedit.exe or reg.exe utilities to edit the registry. Errors in editing the registry can render the operating system unstable or unbootable. If you are not familiar or comfortable with editing the registry, then it is recommended that you ask your system administrator for assistance. It is also recommended to backup/export the current registry before making modifications.