Thanks Del and Matt for your inputs. It turned out to be a password problem that would only be resolved using "dsmcutil updatepw".
Larry McNutt Timken Company -----Original Message----- From: Adams, Matt (US - Hermitage) [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 09, 2003 5:05 PM To: [EMAIL PROTECTED] Subject: Re: Version compatibility with baclient and SQL TDP? Check to make sure your dsm.opt for the SQL client doesn't have any unsupported communication protocols listed. (IPX/SPX, etc) 4.2.x clients ignored them. 5.1.x clients does not. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Tuesday, December 09, 2003 4:03 PM To: [EMAIL PROTECTED] Subject: Re: Version compatibility with baclient and SQL TDP? Larry, Data Protection for SQL 1.1.2 is quite old and out of support. Normally, upward compatibility should work fine, but... Without seeing the error messages that you are receiving, it is hard to know what problem you are encountering. Can you append the error messages that you see in the Data Protection for SQL log file and the TSM API error file? Thanks, Del ---------------------------------------------------- > Client is W2K, MSSQL 6.5 > TDP 1.1.2 > > We upgraded the baclient from 4.2.2.0 to 5.1.5.9. > Now the SQL backups no longer work. > Is there possibly a compatibility problem with the newer api and the > TDP? This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. ********************************************************************** PLEASE NOTE: The above email address has recently changed from a previous naming standard -- if this does not match your records, please update them to use this new name in future email addressed to this individual. This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company **********************************************************************
