June 3, 2009 at 5:06 pm
I would greatly appreciate if someone could please advise regarding the following:
We have a non-critical database (I'd like to drop) on a SQL 7 production server.
The event log is flooded with messages such as those below.
I cannot drop (the referenced) claims_backup database, I cannot drop logins (from the master db) (get i/o error 59).
In Enterprise Manager, I right-click on a mission critical table (different database) I get communication link failure error. Our backups started to fail about the same time these errors began to appear in the event log.
The claims_backup.mdf is physically located on the sql server but the path referenced in the messages is a unc path. I don't know how to look at the database config to see if the referenced path is physical or logical (I suspect this might have to do with the problem). When I try to run sp_helpdb I get the i/o error 59 shown below.
Error: 823, Severity: 24, State: 1
I/O error 64(The specified network name is no longer available.) detected during read of BUF pointer = 0x125e5880, page ptr = 0x71a24000, pageid = (0x1:0x2c), dbid = 11, status = 0x801, file = \\claimssql\d$\MSSQL7\Data\claims_backup.mdf.
Error: 823, Severity: 24, State: 4
I/O error 64(The specified network name is no longer available.) detected during write of BUF pointer = 0x125cba00, page ptr = 0x1ed30000, pageid = (0x1:0x7e86c), dbid = 11, status = 0xb, file = \\claimssql\d$\MSSQL7\Data\claims_backup.mdf.
Error: 9001, Severity: 21, State: 1
The log for database 'claims_backup' is not available.
Error: 823, Severity: 24, State: 1
I/O error 59(An unexpected network error occurred.) detected during read of BUF pointer = 0x126a4c80, page ptr = 0x76fa4000, pageid = (0x1:0xe), dbid = 11, status = 0x801, file = \\claimssql\d$\MSSQL7\Data\claims_backup.mdf.
Error: 823, Severity: 24, State: 4
I/O error 59(An unexpected network error occurred.) detected during write of BUF pointer = 0x12397980, page ptr = 0x3fb7c000, pageid = (0x1:0xabca8), dbid = 11, status = 0xb, file = \\claimssql\d$\MSSQL7\Data\claims_backup.mdf.
Thank you for any assistance you can provide.
June 3, 2009 at 6:32 pm
This was resolve by rebooting the server.
Sorry guys - i should have tried the reboot before posting.
By the way, the "faulting" database was setup w/ a unc path to the data and log files.
All others had a physical path.
I was able to drop the db after the restart and the sql server behavior has returned to normal.
Thank you
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply