Have you installed this version on any windows platforms?

Melinda Cooper 
Senior Information Center Analyst 
Work - 425.783.4467 
Pager - 425.438.5981 


-----Original Message-----
From: Bos, Karel [mailto:Karel.Bos AT ATOSORIGIN DOT COM] 
Sent: Tuesday, July 20, 2004 8:05 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003

Hi,

There is a 5.2.3 windows client available on the ftp site (maintenance
dir). Maybe these problems are solved in that version?

Regards,

Karel

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Cooper, Melinda
Sent: dinsdag 20 juli 2004 17:00
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003


This has been very frustrating for us since when you review the log
files it says that the system objects and files have successfully been
backed up.

This is the error code:
ANS1026E Session rejected: Communications protocol error. 
Explanation: Communications protocol error. An unexpected communications
message was received by the client. 
System Action: ADSM canceled the current operation. 
User Response: Verify that your communication path is functioning
properly. If the problem continues, have your service representative
check for a possible program error.

So at this point I don't know if it's in the dsm.opt file for with the
Unix server that has the TSM software.


Melinda Cooper 
Senior Information Center Analyst 
Work - 425.783.4467 
Pager - 425.438.5981 


-----Original Message-----
From: Kamp, Bruce [mailto:bkamp AT MHS DOT NET] 
Sent: Tuesday, July 20, 2004 7:54 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003

I just started to notice this also on one of my Win2k3 servers.....
I never heard about splitting the backups before now....

Also noticed these errors:

07/20/2004 02:34:44 ANS1512E Scheduled event 'WIN_SYS_4' failed.  Return
code = 12.
07/20/2004 06:44:26 VssQuerySystemWriters(): pAsync->QueryStatus()
returns
hr=E_UNEXPECTED
07/20/2004 06:44:34 VssQuerySystemWriters(): pAsync->QueryStatus()
returns
hr=E_UNEXPECTED
07/20/2004 06:44:41 GetDfsEnum(): Server=\\xxxyyyy01, NetDfsEnum()
returns
RC=259.
07/20/2004 06:44:52 VssQuerySystemWriters(): pAsync->QueryStatus()
returns
hr=E_UNEXPECTED
07/20/2004 06:47:46 VssQuerySystemWriters(): pAsync->QueryStatus()
returns
hr=E_UNEXPECTED
07/20/2004 06:47:46 VssQuerySystemWriters(): pAsync->QueryStatus()
returns
hr=E_UNEXPECTED



-----------------------------------------------------
Bruce Kamp
Senior Server Analyst
Memorial Healthcare System
E-Mail: bkamp AT mhs DOT net
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: 9542869441 AT archwireless DOT net
Fax: (954) 985-1404
-----------------------------------------------------

-----Original Message-----
From: Cooper, Melinda [mailto:MHCooper AT SNOPUD DOT COM]
Sent: Tuesday, July 20, 2004 10:48 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TSM Client V5.2.2.10 for Windows 2000/2003

We've been working with IBM Support on various issues we've had with
this version of the client V5.2.2.10.



We are reviewing this newer version and wonder if anyone has had any
issues?



Currently the majority of our Windows servers have TSM Client V5.1
installed.  We realized a few months ago that our system objects were
not being backed up and updated our dsm.opt file to 'domain all-local'.
In doing this we ran into some issues of getting RC=12 - failure
notifications that the backups failed.  In reviewing the event log,
dsmerror log and adsmsched log file it says that in fact the files were
backed up.  IBM said that this was resolved with TSM Client V5.2.2.10.
I have since been installing mainly Windows 2003 operating systems with
this newer version.  Periodically we run into the same issue of RC=12 -
failure notification that the backup failed, but in fact the files were
backed up.



IBM has said that the 'best practice' is to have two separate backups
one for system objects and the other for files.  I have over 80 windows
servers and I'd rather upgrade to the newer client than change all the
dsm.opt files and install a batch file.





Melinda Cooper
Senior Information Center Analyst
Work - 425.783.4467
Pager - 425.438.5981