What version of the TSM Client are you using? Is this Windows 2000 with service pack 4?
Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981 -----Original Message----- From: Chris Hund [mailto:[EMAIL PROTECTED] Sent: Thursday, August 12, 2004 3:24 PM To: [EMAIL PROTECTED] Subject: Tivoli locking up a Win2k system? Hi all, Has anyone ever come across an issue where the Tivoli client locks up a Win2k system? This is happening fairly regularly with one of the Win2k boxes in our environment. Here are a few small excerpts from the dsmsched.log file during the times the system locks up: ------------------------------------------------------------------- 07/22/2004 07:06:58 Normal File--> 259,384 \\harr-facet-app\c$\WINNT\Fonts\micross.ttf 07/22/2004 09:16:06 Querying server for next scheduled event. 07/25/2004 02:56:02 Directory--> 0 \\harr-facet-app\c$\Program Files\TriZetto\Facets\311\Customer\Output\Backup-ELIG\ERISCO_8920\log 07/25/2004 23:34:33 Querying server for next scheduled event. 07/26/2004 07:09:48 Normal File--> 13,072 \\harr-facet-app\c$\WINNT\system32\dmintf.dll [Sent] 07/26/2004 07:09:48 Normal File--> 07/26/2004 09:00:16 Querying server for next scheduled event. 08/12/2004 17:08:20 Normal File--> 105,232 \\harr-facet-app\c$\WINNT\system32\dfssetup.dll [Sent] 08/12/2004 17:38:34 Querying server for next scheduled event. ------------------------------------------------------------------- Those excerpts from the dsmsched.log file come from four different days ... four different days where the system locked up during a backup. As you can see, there's nothing consistent about where or when the backup is when the system locks up (which is why I'm leaning towards thinking this isn't really a TSM problem). I've talked to IBM Tivoli support. They didn't know what the problem was. I'm hoping someone here has come across this before. Many thanks, Chris Hund IBM Tivoli Administrator, Fiserv Health
