Try following (Do not forget to replace service names like "TSM Scheduler" ). 
You may first remove all services. Then install them like in 2. paragraph or 
update like in 3. or 4. 


regards, 
Burak 



dsmcutil remove /name:"TSM Scheduler" /password:mypassword 
dsmcutil remove /name:"TSM Acceptor" /password:mypassword 
dsmcutil remove /name:"TSM Agent" /password:mypassword 


dsmcutil install /name:"TSM Scheduler" /node:KT_FILESRV1 /password:mypassword 
/autostart:yes 
dsmcutil install CAD /name:"TSM Acceptor" /node:KT_FILESRV1 /autostart:yes 
/password:mypassword 
dsmcutil install REMOTE /name:"TSM Agent" /node:KT_FILESRV1 /partnername:"TSM 
Acceptor" /password:mypassword 


dsmcutil updatepw /node:KT_FILESRV1 /name:"TSM Scheduler" /password:mypassword 


dsmcutil update /node:KT_FILESRV1 /name:"TSM Scheduler" /password:mypassword 
dsmcutil update /node:KT_FILESRV1 /name:"TSM Acceptor" /password:mypassword 
dsmcutil update /node:KT_FILESRV1 /name:"TSM Agent" /password:mypassword 



        bkamp AT MHS DOT NET 
        Sent by: ADSM-L AT VM.MARIST DOT EDU 
        
        12.02.2002 14:39 
        Please respond to ADSM-L 
                        
                        To:        ADSM-L AT VM.MARIST DOT EDU 
                        cc:         
                        Subject:        NT 4.1.2.20 Client

I'm having problems upgrading my NT/2000 clients. 

Environment TSM ver 4.1.3.2 on AIX 4.3.3 

Clients NT SP6a & Win2k SP1 & 2. 

In the app event logs I keep getting the following error: 

ID 4099 Scheduler exited unexpectedly with a result code of 0. 

In the error log I see this: 

02/12/2002 06:07:29 sessOpen: Error 137 from signon authentication. 

This is the contents of my dsmsched.log: 



02/12/2002 06:07:30 Scheduler has been started by Dsmcad. 

02/12/2002 06:07:30 Querying server for next scheduled event. 

02/12/2002 06:07:30 Node Name: PATHOLOGY-SQL 

02/12/2002 06:07:30 Session established with server TSMSERV: AIX-RS/6000 

02/12/2002 06:07:30   Server Version 4, Release 1, Level 3.2 

02/12/2002 06:07:30   Server date/time: 02/12/2002 06:09:09  Last access:
02/12/2002 06:09:09 



02/12/2002 06:07:30 --- SCHEDULEREC QUERY BEGIN 

02/12/2002 06:07:30 --- SCHEDULEREC QUERY END 

02/12/2002 06:07:30 Next operation scheduled: 

02/12/2002 06:07:30
------------------------------------------------------------ 
02/12/2002 06:07:30 Schedule Name:         PATHOLOGY-SQL 
02/12/2002 06:07:30 Schedule Name:         PATHOLOGY-SQL 

02/12/2002 06:07:30 Action:                Incremental 

02/12/2002 06:07:30 Objects: 

02/12/2002 06:07:30 Options:
-preschedulecmd=D:\wins\1\backup\bkuppre.cmd
-postschedulecmd=D:\wins\1\backup\bkuppost.cmd 
-postschedulecmd=D:\wins\1\backup\bkuppost.cmd 
02/12/2002 06:07:30 Server Window Start:   01:00:00 on 02/13/2002 
02/12/2002 06:07:30 Server Window Start:   01:00:00 on 02/13/2002 

02/12/2002 06:07:30
------------------------------------------------------------ 
02/12/2002 06:07:30 Scheduler has been stopped. 
02/12/2002 06:07:30 Scheduler has been stopped. 



I have tried updating the node password on TSM then on the client. 



I have tried taking out the password generate option & updating then but
nothing seems to be working...... 

Also on my Citrix farm the nodes keep contacting my TSM server about every
10min all day long (open incident with Tivoli)!!! 



Any help will be greatly appreciated!!! 



Thanks, 

------------------------------------ 
Bruce Kamp 
Bruce Kamp 

Network Analyst II 

Memorial Healthcare System 

P: (954) 987-2020 x6008 

E: bkamp AT mhs DOT net <mailto:bkamp AT mhs DOT net> 

------------------------------------