When i checked EVENT VIEWER

i got the following error

FCB::Open failed: Could not open file D:\PROD\MSSQL.3\MSSQL\DATA\model.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).

Here PROD instance name

in SQl log :

SQL Server is now ready for client connections. This is an informational message; no user action is required.

2009-08-03 23:48:26.18 spid9s Clearing tempdb database.

2009-08-03 23:48:27.53 spid24s Starting up database 'DB_DBA'.

2009-08-03 23:48:27.53 spid19s Starting up database 'ECOMMERCE'.

2009-08-03 23:48:27.53 spid26s Starting up database 'TEMP_TABLE_DB1'.

2009-08-03 23:48:27.53 spid18s Starting up database 'DB_SURVEY'.

2009-08-03 23:48:27.53 spid25s Starting up database 'AspState'.

2009-08-03 23:48:27.53 spid27s Starting up database 'TEMP_TABLE_DB2'.

2009-08-03 23:48:27.53 spid16s Starting up database 'DB_RESPONDENT'.

2009-08-03 23:48:27.53 spid20s Starting up database 'ESS'.

2009-08-03 23:48:28.15 spid25s Error: 17207, Severity: 16, State: 1.

2009-08-03 23:48:28.15 spid25s FCB::Open: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\PROD\MSSQL.3\MSSQL\DATA\AspState.mdf'. Diagnose and correct the operating system error, and retry the operation.

2009-08-03 23:48:28.21 spid25s Error: 17204, Severity: 16, State: 1.

2009-08-03 23:48:28.21 spid25s FCB::Open failed: Could not open file D:\PROD\MSSQL.3\MSSQL\DATA\AspState.mdf for file number 1. OS error: 2(The system cannot find the file specified.).

2009-08-03 23:48:28.26 spid25s Error: 5120, Severity: 16, State: 101.

2009-08-03 23:48:28.26 spid25s Unable to open the physical file "D:\PROD\MSSQL.3\MSSQL\DATA\AspState.mdf". Operating system error 2: "2(The system cannot find the file specified.)".

2009-08-03 23:48:28.74 spid25s Error: 17207, Severity: 16, State: 1.

2009-08-03 23:48:28.74 spid25s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\PROD\MSSQL.3\MSSQL\DATA\AspState_1.LDF'. Diagnose and correct the operating system error, and retry the operation.

2009-08-03 23:48:28.74 spid25s File activation failure. The physical file name "D:\PROD\MSSQL.3\MSSQL\DATA\AspState_1.LDF" may be incorrect.

2009-08-03 23:48:28.74 spid25s Starting up database 'ESS_ARCHIVE'.

2009-08-03 23:48:28.74 spid25s Error: 17207, Severity: 16, State: 1.

2009-08-03 23:48:28.74 spid25s FCB::Open: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\PROD\MSSQL.3\MSSQL\DATA\ESS_ARCHIVE.mdf'. Diagnose and correct the operating system error, and retry the operation.

2009-08-03 23:48:28.74 spid25s Error: 17204, Severity: 16, State: 1.

2009-08-03 23:48:28.74 spid25s FCB::Open failed: Could not open file D:\PROD\MSSQL.3\MSSQL\DATA\ESS_ARCHIVE.mdf for file number 1. OS error: 2(The system cannot find the file specified.).

2009-08-03 23:48:28.74 spid25s Error: 5120, Severity: 16, State: 101.

2009-08-03 23:48:28.74 spid25s Unable to open the physical file "D:\PROD\MSSQL.3\MSSQL\DATA\ESS_ARCHIVE.mdf". Operating system error 2: "2(The system cannot find the file specified.)".

2009-08-03 23:48:28.76 spid25s Error: 17207, Severity: 16, State: 1.

2009-08-03 23:48:28.76 spid25s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\PROD\MSSQL.3\MSSQL\Data\ESS_ARCHIVE_7.ldf'. Diagnose and correct the operating system error, and retry the operation.

2009-08-03 23:48:28.76 spid25s File activation failure. The physical file name "D:\PROD\MSSQL.3\MSSQL\Data\ESS_ARCHIVE_7.ldf" may be incorrect.

2009-08-03 23:48:28.87 spid24s Analysis of database 'DB_DBA' (16) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.

2009-08-03 23:48:33.07 spid9s Starting up database 'tempdb'.

2009-08-03 23:48:34.00 spid14s CHECKDB for database 'DB_PROD' finished without errors on 2007-12-27 05:21:09.400 (local time). This is an informational message only; no user action is required.

2009-08-03 23:48:44.18 spid5s Error: 8355, Severity: 16, State: 1.

2009-08-03 23:48:44.18 spid5s Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdsb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker.

2009-08-03 23:48:44.21 spid5s Recovery is complete. This is an informational message only. No user action is required.

2009-08-03 23:48:44.80 spid12s The Service Broker protocol transport is disabled or not configured.

2009-08-03 23:48:44.80 spid12s The Database Mirroring protocol transport is disabled or not configured.

2009-08-03 23:48:45.03 spid12s Service Broker manager has started.

2009-08-03 23:48:48.09 spid51 Using 'xpsqlbot.dll' version '2005.90.3042' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.

2009-08-03 23:48:50.44 spid51 Using 'xpstar90.dll' version '2005.90.3310' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.

2009-08-03 23:48:51.96 spid51 Using 'xplog70.dll' version '2005.90.3042' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.

2009-08-04 00:00:06.18 spid16s This instance of SQL Server has been using a process ID of 1792 since 8/3/2009 11:48:44 PM (local) 8/3/2009 6:18:44 PM (UTC). This is an informational message only; no user action is required.

2009-08-04 10:36:49.37 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.

2009-08-04 10:36:52.99 spid12s Service Broker manager has shut down.

2009-08-04 10:36:52.99 spid12s Error: 17054, Severity: 16, State: 1.

2009-08-04 10:36:52.99 spid12s The current event was not reported to the Windows Events log. Operating system error = 31(A device attached to the system is not functioning.). You may need to clear the Windows Events log if it is full.

2009-08-04 10:36:53.73 Server The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established. This is an informational message only. No user action is required.

2009-08-04 10:37:04.24 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

2009-08-04 10:37:04.56 Server The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x45b, state: 4. Administrator should deregister this SPN manually to avoid client authentication errors.