Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Save Password
Forgot your Password?

 All Forums
 SQL Server 2012 Forums
 Other SQL Server 2012 Topics
 SQL SERVR 2008 Ent. | Application logs missing bec
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Starting Member

1 Posts

Posted - 01/09/2013 :  13:17:15  Show Profile  Reply with Quote
In our setup we are using SQL cluster active and passive and all of our cluster drives are on the SAN.

We are using SAN "E" drive for our application logs.

Last week, we were adding new drives to the database server. During this activity, accidently drive letter had changed of the “E” drive to “Y”. Later this issue was found & fixed and drive was re-named back to “E”.

Our application logs could not get stored in the database because of drive letter was changed and next day morning, we have found that our logs database is disconnect and this was happened that drive name was changed.

We have fixed this issue with offline and online the database. After that our application logging is started on the database.
Our application logs could not get stored in the database since drive letter had changed to until we have offline and online the database. (Around 15 hour’s application logs).

Is there any chance that SQL Server would have written these logs to a temporary file elsewhere (while the E drive was “missing”)?
I have attached the application event logs message:

FCB::Open failed: Could not open file E:\DB_LOGS\DB_LOGS.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
FileMgr::StartSecondaryDataFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'E:\ DB_LOGS\DB_LOGS_xx.ndf'. Diagnose and correct the operating system error, and retry the operation.

Note: we are using MSMQ for transfer the logs from application server to DB server.

  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.02 seconds. Powered By: Snitz Forums 2000