TSM Scheduler does not start

[clscmmd]

Event Type: Error
Event Source: AdsmClientService
Event Category: None
Event ID: 4099
Date: 7/3/2007
Time: 8:29:33 AM
User: NT AUTHORITY\SYSTEM
Computer: SERVERNAME
Description:
Scheduler exited with a result code of 8.



Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 7/3/2007
Time: 8:19:50 AM
User: N/A
Computer: SERVERNAME
Description:
The TSM Scheduler service terminated with service-specific error 8 (0x8).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Any idea guys! thanks in advance

 

[may]

can you post here what does the dsmerror says

 

[noodles]

Hi,

Return Code 8 means warning.
What does your 'dsmerror.log' and 'dsmsched.log' say?

I suppose this error is generated because of that include/exclude problem with the DRM reg key.

Regards
/noodles

 

[clscmmd]

DSM Error log

Here is the dsmerror.log file from yesterday.

07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\...\ntuser.dat' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\...\Usrclass.dat' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\WINNT\csc\...\*' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\WINNT\REGISTARTION\*.CLB\...\*.CRMLOG' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\DOCUMENTS\...\INDEX.DAT' found while processing the client options file.

 

[clscmmd]

Part 2 of the log continued

Part 2 of the log continued

This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\WINNT\SYSTEM32\DTCLOG\MSDTC.LOG' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\WINNT\NETLOGON.CHG' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\WINNT\SCHEDLGU.TXT' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\WINNT\DEBUG\*.*' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\...\EA DATA. SF' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\WINNT\...\PERFLIB*.DAT' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\...\SYSTEM32\CONFIG\...\*' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\...\NTFRS\JET\...\*' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\...\NTDS\*' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\SYSTEM VOLUME INFORMATION' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE \...\Temporary Intenet Files\...\*' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE \...\cache\...\*' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *.dmp' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\winnt\symbols\...\*' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE \temp\...\*' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\...\*.mp3' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\...\*.avi' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:19:48 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
07/03/2007 08:19:48 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
07/03/2007 08:19:48 sessOpen: Error 137 from signon authentication.
07/03/2007 08:19:48 sessOpen: Error 137 from signon authentication.
07/03/2007 08:19:48 ANS1029E Communications have been dropped.
07/03/2007 08:20:11 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\...\ntuser.dat' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:20:11 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\...\Usrclass.dat' found while processing the client options file.
This might produce unexpected results.
07/03/2007 08:20:11 ANS1496W Duplicate include/exclude option 'EXCLUDE *:\WINNT\csc\...\*' found while processing the client options file.

 

[may]

in ffact you have some exclude statment on your node dsm.opt file wich are already present and exclude on the TSM server level via the Clientopset

just remove them from you dsm.opt and that should be good

which version of TSM client you have?

 

[Jeroen]

this is the error
07/03/2007 08:19:48 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
07/03/2007 08:19:48 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
07/03/2007 08:19:48 sessOpen: Error 137 from signon authentication.
07/03/2007 08:19:48 sessOpen: Error 137 from signon authentication.

Looks like the scheduler cannot find the password in the Windows registry.
Try setting the password via the GUI or via the dsmcutil program

 

[clscmmd]

Thanks!

Thanks guys! let me try and get back with the resolution.

 

[clscmmd]

Tried but still the backup shows MISSED

Tried changing the password via webadmin and also going onto the server and logging onto the backup GUI and entering the password. It looks that it did not help either. I did check the event logs and I could not find anything that was related to TSM. So, I am kind of wondering what else that needs to be done in order to fix this.

I tried running a manual backup on one of the server and the backup did run.

 

[cheffern]

Have you tried a simple uninstall - reboot - reinstall of the client software?
Before you uninstall - use dsmcutil to remove all services & give it a 'clean slate'

 

[sgabriel62]

run the correct dsmcutil command to load the password into the registry

 

[jharris]

The password is probably the issue.... you should be seeing on a successful scheduler service stop:
----------------------------------
Event Type: Information
Event Source: AdsmClientService
Event Category: None
Event ID: 4097
Date: 2/08/2007
Time: 4:06:38 PM
User: NT AUTHORITY\SYSTEM
Computer: NBK1477
Description:
TSM Client Scheduler halted.
----------------------------------

Are you running a Microsoft Cluster ? As my current cluster checkpoint file is out of sync and it is constantly clearing my passwords stored in registry when it fails back and forth (there is a current IBM KB on this http://www-1.ibm.com/support/docview.wss?rs=663&uid=swg21243061)

I've been haunted by various Windows machines that report this error off and on over the years from Windows NT (TSM 5.2 version) through to WIN2k3 SP2 (TSM 5.4.2.0) client.

Essentially if you use dsmcutil to uninstall and correctly install all of the services with a currently known password, I think I've manage to rectify all but a handful of my 400 windows clients:
1. Stop client services (CAD/Scheduler/Remote Access) on affected node
2. Stop any client command sessions (check task manager for rogue dsmc.exe processes and end them)
3. SET the client Password on the TSM Server
4. Rewrite password into registry
....\BACLIENT\DSMC set password %currentpassword% %newpassword% -optfile=dsm.opt
or
....\BACLIENT\dsmcutil updatepw /node:%nodename% /password:%currentpassword% /oldpassword:%newpassword%
5. Remove old scheduler service
....\BACLIENT\DSMCUTIL rem /name:"TSM Client Scheduler"
6. Install new scheduler with correct password
....\BACLIENT\DSMCUTIL install scheduler /name:"TSM Client Scheduler" /node:%nodename% /password:%newpassword% /optfile:%dsm.opt%
7. And if Managing the client scheduler from the Client Acceptor Daemon:
....\BACLIENT\DSMCUTIL update cad /name:"TSM Client Acceptor" /cadschedname:"TSM Client Scheduler"
8. Start Client Acceptor Daemon



From memory this can also occur if the following registry key is missing or unpopulated:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TSM Client Scheduler\Parameters]
"ADSMClientKey"="Client Scheduler Service"