Neil,

A few things that you didn't mention:

1.) What was the error message on the GUI screen
    or on the command-line client?

2.) What was the error in sqldsm.log (or whatever name
    you gave to the SQL Agent log)?

3.) Did you check the to see if the logs were actually
    backed up successfully?  That is, did you look
    at the "Restore" tab to see if the backups are there?
    (Maybe some post processing ADSM server logging
    failed AFTER the backup was successful.)

If things still look strange, I recommend you open
a service call with IBM support so proper
diagnostic info can be gathered.

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com



> 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.
>
> (extra deleted)
>
> 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