Thanks Del, I appreciate the info. I tried searching MS's site based on the SQL server error messages, but couldn't find anything useful.
Regards, Matt -----Original Message----- From: Del Hoobler [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 22, 2003 7:30 AM To: [EMAIL PROTECTED] Subject: Re: TDP for SQL errors Maria, (Matt), This may be a known Microsoft bug, BUG #: 357231 (SHILOH_BUGS). Take a look at Microsoft Knowledge Base article Q323602. http://support.microsoft.com/default.aspx?scid=kb;en-us;323602 Microsoft documents the workaround for this issue in the knowledge base article. Thanks, Del ---------------------------------------------------- Del Hoobler IBM Corporation [EMAIL PROTECTED] - Never cut what can be untied. - Commit yourself to constant improvement. ======================================================================= > . > 01/22/2003 09:00:38 ACO5422E Received the following from the MS SQL server: > 01/22/2003 09:00:38 [Microsoft][ODBC SQL Server Driver][SQL > Server]BACKUP LOG is terminating abnormally. > Microsoft SQL-DMO (ODBC SQLState: 42000) (HRESULT:0x80040bc5) > 01/22/2003 09:00:39 ACO5436E A failure occurred on stripe number (0), > rc = 428 > 01/22/2003 09:00:39 ACO5407E The SQL server aborted the operation. > 01/22/2003 09:00:39 Backup of Virgo failed. 01/22/2003 09:00:39 > ACO5422E Received the following from the MS SQL server: > 01/22/2003 09:00:39 [Microsoft][ODBC SQL Server Driver][SQL > Server]BACKUP LOG is terminating abnormally. > Microsoft SQL-DMO (ODBC SQLState: 42000) (HRESULT:0x80040bc5) > 01/22/2003 09:00:40 ACO5436E A failure occurred on stripe number (0), > rc = 428 > 01/22/2003 09:00:40 ACO5407E The SQL server aborted the operation. > 01/22/2003 09:00:41 Backup of WaitImport failed. . - 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 and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
