Errors in the trace from Enterprise manager

Hi,
I was running a trace for few hours and noticed bunch of
exception events. I cannot find descriptions for most of
these exceptions. One was especially frequent, coming
from enterprise manager:
Error: 208, Severity: 16, State: 1.
What was that about?
By the way, in the BOL I read that for exception events,
severity, error, and state columns should be included in
the trace, for getting meaningful result. However, I
found that including these columns has no significance,
because text column contains everything that is contained
in these 3 columns anyway.
Thanks
OJ
OJ wrote:
> Hi,
> I was running a trace for few hours and noticed bunch of
> exception events. I cannot find descriptions for most of
> these exceptions. One was especially frequent, coming
> from enterprise manager:
> Error: 208, Severity: 16, State: 1.
> What was that about?
> By the way, in the BOL I read that for exception events,
> severity, error, and state columns should be included in
> the trace, for getting meaningful result. However, I
> found that including these columns has no significance,
> because text column contains everything that is contained
> in these 3 columns anyway.
> Thanks
> OJ
You can ignore most of them. They are "object not found" errors which
are often raised when a procedure accesses a temp table. The error is
important, but in order to figure out if it's relevant, you need to
examine the SQL statement running prior to the error.
David Gugick
Imceda Software
www.imceda.com

Errors after startup

Only over the last couple of days has this been an issue. We do a daily reboot. After the reboot we get several events from MSSQLSERVER ending with an event in the event viewer:

17126 :
SQL Server is ready for client connections

Then almost exactly 50 minutes (50' 1") later we get:

17207 :
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 C:\Program Files\MSSQL\Data\VTSystem.mdf.

and

17204 :
FCB::Open failed: Could not open device C:\Program Files\MSSQL\Data\VTSystem.mdf for virtual device number (VDN) 1.

This is one of our data files. From this point on we cannot connect to the database until we restart the service..

I have just recently been receiving the same error every night immediately following the backup job at 2AM. The application has 6 individual databases, 1 of which goes into a suspect state and returns this error. Each night it has been a different database, but the same aplpication. Any help is greatly appreciated|||

Check whether autoclose is set on the database, and if so turn it off. SQL Server opens data and log files exclusively at startup, and does not release those locks unless the database is closed such as by auto-close.

When data files are closed it's possible that a backup, virus scan or other process may come along and open the files,thus preventing sql server from re-opening the database.