We had no problems with Win2K and the 4.2.0 client, until we started rolling
out SP3.  Ever since we have gotten errors on just "some" servers.  Same
with SP4.  We upgraded all the clients to 5.1.6.2, and that eliminated all
the problems with the System Object.  (DO NOT use 5.1.6.0, known bug in
registry restore.)





-----Original Message-----
From: Chang, Calvin [mailto:Calvin.Chang AT MOODYS DOT COM]
Sent: Thursday, February 26, 2004 2:03 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: FW: Reference Memory Error ##Help## on TSM client 4.2.3


Has anyone experienced this problem when backing up system objects on Win2k
Server SP4?? This error only appears on some servers and I can't seem to pin
point out the problem since other servers are backing up fine.



FYI



(managedservices Schedule Webclient) is set in my dsm.opt.

                      Platform: WinNT

               Client OS Level: 5.00

                Client Version: Version 4, Release 2, Level 3.0

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Error



Windows POPUP Icon:

Dsmcsvc.exe - Application Error

The instruction at "0x77fcb032" referenced memory at "0x000000" The memory
could not be "written"



XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX



This message seems to appear right after the local domain backup
successfully and then tries to backup the system object. If I exclude the
system object the client would backup successfully.



Hangs at this entry below in the dsmsched.log:



02/25/2004 19:07:42 Preparing System Object -> System and Boot FilesANS1898I
***** Processed    72,500 files *****

02/25/2004 19:07:46 ANS1898I ***** Processed    73,000 files *****

02/25/2004 19:07:50 ANS1898I ***** Processed    73,500 files *****



>From here on the scheduler would just hang there.



Any help would be deeply appreciated.



Thank you





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

The information contained in this e-mail message, and any attachment
thereto, is confidential and may not be disclosed without our express
permission.  If you are not the intended recipient or an employee or agent
responsible for delivering this message to the intended recipient, you are
hereby notified that you have received this message in error and that any
review, dissemination, distribution or copying of this message, or any
attachment thereto, in whole or in part, is strictly prohibited.  If you
have received this message in error, please immediately notify us by
telephone, fax or e-mail and delete the message and all of its attachments.
Thank you.

Every effort is made to keep our network free from viruses.  You should,
however, review this e-mail message, as well as any attachment thereto, for
viruses.  We take no responsibility and have no liability for any computer
virus which may be transferred via this e-mail message.