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 605, 823 and KB Article 826433

We are experiencing continuous 605/823 errors on tempdb. Having read KB
Article 826433 we want to set the trace flag for extended diags. However, it
appears we need a more recent version than SQL 2000 sp3a. The article
suggests build 847.
This being the case, please can someone explain how we go about obtaining
build 847.
Thanks
Graham,
The simple answer is to contact MS, as the KB suggests. Have you tried
moving tempdb to another, non caching local drive as the KB article
suggests. The article is also referenced by 836096. Have you tried using the
I/O Stress Simulator to see if you have hardware problems?
Chris Wood
Alberta Department of Energy
CANADA
"Graham G" <GrahamG@.discussions.microsoft.com> wrote in message
news:B7404237-5848-4C1D-A70B-FE41DB0524C6@.microsoft.com...
> We are experiencing continuous 605/823 errors on tempdb. Having read KB
> Article 826433 we want to set the trace flag for extended diags. However,
it
> appears we need a more recent version than SQL 2000 sp3a. The article
> suggests build 847.
> This being the case, please can someone explain how we go about obtaining
> build 847.
> Thanks

ErrorCode 14

I've scripted a sql trace for Sql Server 2000 and added the filename in the appropreate location andthe result is a column called ErrorCode with a value of 14. Can anyone tell me what this error code means and what could be infered about what I need to resolve it?

Thanks,
Marc

It is most probably the call to sp_trace_create that fails. You can inspect the script to find out which one of the system stored procedure call is failing. For example, error code 14 indicates the stop time is incorrect for sp_trace_create. See BOL topic below:

http://msdn2.microsoft.com/en-us/library/ms190362.aspx

Also, if you double-click on the error message in SSMS you should be positioned on the call that failed. This should give some idea as to which system SP call failed.