Robert...Thanks for your reply! The SP level for most of the clients are SP2.
Thanks Tim Clark, Robert A wrote:
You don't mention the SP level for the W2K3. People working with outdated docs (here) installed 5.2.x.x level TSM clients on W2K3. Ironically, the older clients (5.2.x.x) work OK doing legacy type system state backups. If you put on a newer client (say 5.5.1.0) and W2K3 is at less than SP2, WMI and system state backups are a complete mess. So the short answer is: If its W2K3, get it to SP2 or later. The memory issue (code 12) typically points to JBB and/or memoryefficientbackup=diskcachemethod. YMMV [RC] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Timothy Hughes Sent: Friday, January 16, 2009 7:59 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Windows 2003 Clients failing all of sudden after TSM server upgrade Hi all, For the past few days an abnormal number of Windows Clients have been failing with the following error (s). I have noticed that most if not all are windows 2003 clients with TSM client 5.5. It has been happening on some clients every day and others off and on. Also, these errors seemed to start after we upgraded our TSM Servers to 5.5.2. However it's only occurring on two TSM Servers with Windows clients we have 2 other servers that have a bunch of Windows 2003 clients and they do not have this issue? I am not sure which error is the problem or is it a combination? Why would these occur suddenly after and upgrade to 5.5.2 TSM server? ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51 DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.