SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
Windows server patches screw things up (I know....what else
Author Message
Post Windows server patches screw things up (I know....what else 
I suspect this might be a variation of a well-known MS bug.

Open the registry entry


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesN
otToBackup\DRM

Now close the window with the "OK" button (not the "Cancel" button).
Stop and restart the TSM client and see if that fixes the problem.

--
Mark Stapleton (mark.stapleton < at > cdw.com)
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf
Of Zoltan Forray/AC/VCU
Sent: Monday, August 18, 2008 10:37 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] Windows server patches screw things up (I
know....what else is new....)

We are seeing new errors on various Windows 2003 servers, which we
think
are related to recent M$ patches (so, what else is new). The client
confirms that updates were applied on the same day the first failures
started.

The symptoms/error messages are:

08/15/2008 05:57:38 ANS1009W An error occurred processing the
operating
system include/exclude statements.
The error was detected while processing:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\Files
NotToBackup\DRM.
RC = 13.
08/18/2008 02:04:34 ANS5250E An unexpected error was encountered.
TSM function name : isVolumeSupported
TSM function : IsVolumeSupported() returned
'VSS_E_UNEXPECTED_PROVIDER_ERROR' for volume 'c:\'
TSM return code : 4353
TSM file : vssreq.cpp (5491)
08/18/2008 02:04:35 ANS5250E An unexpected error was encountered.
TSM function name : vssCheckVolumeSupport
TSM function : isVolumeSupported() returned unexpected error
for
volume '\\den3print\c$'
TSM return code : 4353
TSM file : vssback.cpp (3075)
08/18/2008 02:04:35 ANS5258E An error occurred initializing a VSS
request.
For more information, see the TSM client error log.

Going back in the log for 2+ weeks does not show any of these errors.

This client is a 5.5.0.2 and I suggested upgrading to 5.5.1.1 as a
minimum. I haven't been able to find anything definitive when
searching
IBM.COM.


Any thoughts?

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB