DB Suspect error

hi,
my db went into suspect,,got the following error messages from log files..can anyone help me to sort out the problem
1) FCB::Open failed: Could not open device e:\disbursement\disbdata\ICICI_Disb_log.ldf for virtual device number (VDN) 2.
2) udopen: Operating system error 32(The process cannot access the file because it is being used by another process.) during the creation/opening of physical device e:\disbursement\disbdata\ICICI_Disb_log.ldf.
thanks
sanjayNeed some more information regarding the version of SQL
Server that you are running on your server.
This posting is provided "AS IS" with no warranties, and
confers no rights.
http://www.microsoft.com/info/cpyright.htm
>--Original Message--
>hi,
> my db went into suspect,,got the following error
messages from log files..can anyone help me to sort out
the problem
>1) FCB::Open failed: Could not open device
e:\disbursement\disbdata\ICICI_Disb_log.ldf for virtual
device number (VDN) 2.
>2) udopen: Operating system error 32(The process cannot
access the file because it is being used by another
process.) during the creation/opening of physical device
e:\disbursement\disbdata\ICICI_Disb_log.ldf.
>thanks
>sanjay
>.
>|||Seems like some other program is using one of your database files, resulting in SQL Server not being
able to open the file. Could be an anti-virus software, for instance.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"samkau" <anonymous@.discussions.microsoft.com> wrote in message
news:F09AA7EC-7161-412A-AE29-83635DCC9753@.microsoft.com...
> hi,
> my db went into suspect,,got the following error messages from log files..can anyone help me to
sort out the problem
> 1) FCB::Open failed: Could not open device e:\disbursement\disbdata\ICICI_Disb_log.ldf for virtual
device number (VDN) 2.
> 2) udopen: Operating system error 32(The process cannot access the file because it is being used
by another process.) during the creation/opening of physical device
e:\disbursement\disbdata\ICICI_Disb_log.ldf.
> thanks
> sanjay|||its sqlserver 2000,
wot can be the reasons of db going suspect.|||One such reason is another piece of software opening the file so that SQL Server then cannot open
the file for exclusive use. This is more likely to happen if you have autoclose for the database.
Other obvious reasons are hardware problems.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"sanjay" <anonymous@.discussions.microsoft.com> wrote in message
news:72A8470C-34EB-4BD6-88F0-26A67C13146E@.microsoft.com...
> its sqlserver 2000,
> wot can be the reasons of db going suspect.