SQL 6.5 backup log error | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

SQL 6.5 backup log error


I get the following error message from a scheduled task that is meant to run every 15mins, any ideas. Can’t open dump device ‘E:myBackupsmyData.DAT’, device error or device off line. Please consult the SQL Server error log for more details. (Message 3201). SQL error logs show:
kernel error: dbswritecheck: Read of first trailer failed : (null) and also ods error Unable to write to ListenOn connection ‘2220’, loginname ‘mylogin’, hostname ". I’m having all this errors from this server and i’m sorry that i’m not much of a SQL 6.5 fanatic!!
Ensure there is enough space on E: drive of server and no other application is using the file.
Check SQL error log for other errors. If an Open Data Services (ODS) application, such as SQL Server, is processing a large number of client disconnection events, you may receive a handled access violation (AV) within Open Data Services. Open Data Services is designed to shut down upon encountering an access violation. Therefore, when this problem occurs, the ODS application (such as SQL Server) will also be stopped. Take help of following KBAs:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;166967 – proper SQL configuration settings.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;169521 – troubleshoot 17832 errors, if any.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;109787 – about SQL communication errors. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
would it do any good to stop and restart SQL services?
i’ve just deleted old files because i realised that the drive had no space left. One more question is do i need to stop and restart SQL before doing a manual dump?
Check if there aren’t any errors in SQL SErver error log for ODS, if so then restarting services will overcome those issues otherwise leave them as it is. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
apparently the drive used for backup ran out of space so i had to clear out and ran stuff manually, and everything looks good now. thanks for your help
Glad its resolved, the first time when I look at the error I thought its a space issue.
As you’ve mentioned entry about ODS error, listed the articles for your reference. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>