asked on

SQL 2012 Error 823

Hello - we are seeing an error on our SQL Server 2012 that is puzzling us. It's an Error 823 and its occurring every minute of the day, for as far back as the event log goes. the strange thing is ity does not seem to impact the DB itself - but its causing our Arcserve SQL backup job to fail when backing up ANY of the many DB's on the server. We called Arcserve, and they tell us "fix this SQL error, and the backup job should work". So we have tried restoring the DB from the last good backup, and also ran a DBCC checkDB on the DB in question, to no avail. Here is the error:

"The operating system returned error 64(The specified network name is no longer available.) to SQL Server during a read at offset 0x0000000016a000 in file '\\lacosql2\X\AX2012R3BaselineDEV10.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online."

We have also confirmed the UNC path to the DB file (on another server - "lacosql2") that the path works and is good. We also checked the free space on the drive, and there is 132GB free. Also checked and verified that the MDB file is actually there.

Out of ideas now..

Thanks for your help.

ASKER CERTIFIED SOLUTION

Pavel Celba

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Damian Gardner

ASKER

it is a temporary DB that was created, and there is not enough space on the local drives. If we do not have enough space, should we just give up?

SOLUTION

Scott Pletcher

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Damian Gardner

ASKER

Ok let me try that. thanks and standby Scott.

Pavel Celba

No, you should not give up but you should add new disk to the computer where the SQL Server resides. Or install SQL Server on the computer having enough disk space.

Damian Gardner

ASKER

welp - so far, it doesn't seem to be helping. After executing the two commands, and also opening up the permissions for the user account being used, the event viewer is still showing the error as of the last minute. I also ran a test backup job and there's no change. But - I hadn't noticed this before, but out of about 8 DB's I have in the backup job, only one is showing an error related to not being able to reach the DB file - wheras the others are failing with something different:

(Microsoft SQL Server Error 0 (ODBC State = "08S01"): [Microsoft][ODBC SQL Server Driver]Communication link failure).

The rest of the DB's are LOCAL to the machine. So - on the SQL server itself, there is only the Error 823 with the one DB. But on the Arcserve backup server, it's getting these other errors.

This is a weird one.

SOLUTION

Vitor Montalvão

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Damian Gardner

ASKER

Ahh - yes I am, and good point. I need to add that user....

SOLUTION

Bharat Bhushan

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Pavel Celba

Both the "specified network name is no longer available" and "Communication link failure" means unstable network. When you solve this problem then even the database on a network share should work for you.

BTW, you were talking about the "temporary database". So if you have database on a network share for some temporary or test purposes then you could exclude it from AcrServe backups and do these backups manually.

Damian Gardner

ASKER

Thank you for your help gentlemen. It was a bad database, as it turned out. we deleted the database and the error went away.