Does anybody have any thoughts on the following:

Up until this week we were successfully backing up a SQL Server v7.0
database using v1.1.2 of the ADSM SQL Agent. Then one day this week it
broke in a very strange way. We can still perform full database backups but
transaction log backups from either the command line or the SQL Agent GUI
always fail.

The messages in the server (v3.7.1) activity logs look like this:

06-02-2000 15:01:16   ANR0406I Session 722 started for node SAPB2BP1_SQL
(WinNT)
                       (Tcp/Ip 10.1.16.147(4238)).

06-02-2000 15:01:16   ANR0406I Session 723 started for node SAPB2BP1_SQL
(TDP
                       MSSQL NT) (Tcp/Ip 10.1.16.147(4239)).

06-02-2000 15:01:17   ANE4991I (Session: 723, Node: SAPB2BP1_SQL)  TDP
MSSQL NT
                       ACO3507 Sql Application Client: Starting INCR backup
of
                       database BBP from server SAPB2BP1.

06-02-2000 15:01:17   ANR0444W Protocol error on session 723 for node

                       SAPB2BP1_SQL (TDP MSSQL NT) - out-of-sequence verb
(type
                       Data) received.

06-02-2000 15:01:17   ANR0484W Session 723 for node SAPB2BP1_SQL (TDP MSSQL
NT)
                       terminated - protocol violation detected.

06-02-2000 15:01:18   ANR0406I Session 724 started for node SAPB2BP1_SQL
(TDP
                       MSSQL NT) (Tcp/Ip 10.1.16.147(4241)).

06-02-2000 15:01:18   ANE4991I (Session: 724, Node: SAPB2BP1_SQL)  TDP
MSSQL NT
                       ACO3508 Sql Application Client: Backup from server

                       SAPB2BP1 complete: 0 of 1 objects backed up
successfully.
                       0 bytes backed up in 0.00 seconds.

06-02-2000 15:01:18   ANR0403I Session 724 ended for node SAPB2BP1_SQL (TDP

                       MSSQL NT).

06-02-2000 15:01:18   ANR0403I Session 722 ended for node SAPB2BP1_SQL
(WinNT).
06-02-2000 15:01:18   ANR0406I Session 725 started for node SAPB2BP1_SQL
(WinNT)
                       (Tcp/Ip 10.1.16.147(4242)).

06-02-2000 15:01:18   ANR0403I Session 725 ended for node SAPB2BP1_SQL
(WinNT).

The protocol errors led me to believe initially that it was a problem with
the stored password. I reset it both on the client and server but the
problem persisted. Also, I *am* able to do full database backups of the
same database using the ADSM SQL Agent.

To eliminate the server, I made the SQL Server a client of a different ADSM
server - this time running 3.1.2.13 - and got the same errors.

The DSMERROR.LOG on the client shows the following errors:

02/06/2000 15:01:18 TcpFlush: Error 10054 sending data on Tcp/Ip socket 68.
02/06/2000 15:01:18 sessSendVerb: Error sending Verb, rc: -50
02/06/2000 15:01:18 TcpFlush: Error 10054 sending data on Tcp/Ip socket 68.
02/06/2000 15:01:18 TcpFlush: Error 10038 sending data on Tcp/Ip socket
4294967295.
02/06/2000 15:01:18 sessSendVerb: Error sending Verb, rc: -50

The SQL server database has no options enabled except auto-create
statistics and auto-update statistics. Truncate on checkpoint is definitely
disabled. I suspected a database integrity problem but DBCC checks showed
no problems and in all other respects it seems fine.

I can successfully dump the transaction log of the database to file from
Enterprise Manager. Worryingly, when the transaction log backup is
performed using the SQL Agent, the SQL Server logs indicate that the log
has been backed up successfully.

I have rebooted both the client and the server to no effect. On the server
we have CommTimeOut set to 600 and IdleTimeOut set to 15. The client is
running NT v4.0 SP5 and SQL Server v7.0 SP1.

Any help would be much appreciated.

Neil Schofield


The information in this e-mail is confidential and may also be legally
privileged. The contents are intended for recipient only and are subject
to the legal notice available at http://www.keldagroup.com/email.htm
Kelda Group plc and its subsidiaries, UK
Registered in England and Wales No 2366627