-
-
Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.
client scheduler stopping
- Thread starter pjk4
- Start date
Hi pjk4,
It happens often...You may want to do a dsmcutil updatepw /node
NODE NAME) /passwordpassword /validate:no
This way the client password is stored permanently, since I've seen this to be the cause of some of the stops. You may also want to try the MANAGEDSERVICES SCHEDULE option, or if you are using it, try it the other way.
From all of the open calls and troubleshooting the scheduler appears to fail the most because of miss communication to the server, and authentication due to error 137.
Hope this helps...
It happens often...You may want to do a dsmcutil updatepw /node
NODE NAME) /passwordpassword /validate:noThis way the client password is stored permanently, since I've seen this to be the cause of some of the stops. You may also want to try the MANAGEDSERVICES SCHEDULE option, or if you are using it, try it the other way.
From all of the open calls and troubleshooting the scheduler appears to fail the most because of miss communication to the server, and authentication due to error 137.
Hope this helps...
hakanen
ADSM.ORG Member
- Joined
- Sep 23, 2002
- Messages
- 40
- Reaction score
- 0
- Points
- 0
- Location
- Gothenburg, Sweden
- Website
- www.cristie.se
Hi all,
I'm having a problem with NT/W2k klients where TSM scheduler service stops if TSM server is down for more than 24h. (No problem with U*X, NW, Linux clients)
I have seen this on klients at 4.2 and 5.1 level and connected to TSM servers at 4.1, 4.2 and 5.1 level differnet platforms (AIX,Sun,W2k)
There must be someone else that have seen this happen but can't find any postings.
I know I can go round the problem by using managed services and letting the CAD service control the scheduler but I have an environment with hundreds of clients to update.....
/HE
I'm having a problem with NT/W2k klients where TSM scheduler service stops if TSM server is down for more than 24h. (No problem with U*X, NW, Linux clients)
I have seen this on klients at 4.2 and 5.1 level and connected to TSM servers at 4.1, 4.2 and 5.1 level differnet platforms (AIX,Sun,W2k)
There must be someone else that have seen this happen but can't find any postings.
I know I can go round the problem by using managed services and letting the CAD service control the scheduler but I have an environment with hundreds of clients to update.....
/HE
