c.j.hund
ADSM.ORG Senior Member
Greetings,
I recently bumped into an issue installing a scheduler service on a Windows Server 2003. This server is currently using the 5.3.5.3 client (old, yes). The TSM server is version 5.5. It's also an Oracle server, and recently the 6.3 Oracle TDP was installed, which required a reboot of the box. The Oracle version installed was the 32bit 6.3.0.0 package.
After the Oracle install/reboot, we came to notice that the existing scheduler service was having an issue with its password and connecting to the TSM server. The old TSM service was uninstalled and an attempt was made to reinstall the service. Using the TSM GUI wizard, a new scheduler service was attempted to be installed, but at the end of the wizard walk-through we got the message:
"Error 0 occurred c the 'S' registry key."
The new service name shows up in the list of services, but it errors when you try to start it up. Also, I noticed that when I run a dsmcutil list from the command line, nothing shows up. dsmcutil does not recognize the service name and nothing is listed.
So this service did seem to be working before the 6.3 Oracle TDP code was installed. I'm not sure if that has something to do with this or not. Any ideas?
Sincere thanks,
C.J.
I recently bumped into an issue installing a scheduler service on a Windows Server 2003. This server is currently using the 5.3.5.3 client (old, yes). The TSM server is version 5.5. It's also an Oracle server, and recently the 6.3 Oracle TDP was installed, which required a reboot of the box. The Oracle version installed was the 32bit 6.3.0.0 package.
After the Oracle install/reboot, we came to notice that the existing scheduler service was having an issue with its password and connecting to the TSM server. The old TSM service was uninstalled and an attempt was made to reinstall the service. Using the TSM GUI wizard, a new scheduler service was attempted to be installed, but at the end of the wizard walk-through we got the message:
"Error 0 occurred c the 'S' registry key."
The new service name shows up in the list of services, but it errors when you try to start it up. Also, I noticed that when I run a dsmcutil list from the command line, nothing shows up. dsmcutil does not recognize the service name and nothing is listed.
So this service did seem to be working before the 6.3 Oracle TDP code was installed. I'm not sure if that has something to do with this or not. Any ideas?
Sincere thanks,
C.J.