Error: 208, Severity: 16, State: 0

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Locked
thomas62j5
Posts: 71
Joined: Tue Aug 17, 2004 7:59 pm
Location: West Coast, USA

Error: 208, Severity: 16, State: 0

Post by thomas62j5 » Fri Jul 29, 2005 2:14 pm

We are running sql profiler to audit security and exceptions in sql server, and we are seeing a lot of these errors:

Error: 208, Severity: 16, State: 0

A lot of them are originating from the sourcegear client, and I was wondering if you might know why?

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

SQL Server Error 208

Post by ian_sg » Fri Jul 29, 2005 2:25 pm

This error indicates a reference to an object that SQL Server can't find.

Is there any text associated with the error within profiler? Are you doing anything in particular when you see these? Does the Vault client report an error when this occurs on the server?

It would also help if you could provide the version of Vault that you're running.

Thanks.
Ian Olsen
SourceGear

thomas62j5
Posts: 71
Joined: Tue Aug 17, 2004 7:59 pm
Location: West Coast, USA

Re: SQL Server Error 208

Post by thomas62j5 » Fri Jul 29, 2005 5:26 pm

ian_sg wrote:Is there any text associated with the error within profiler?
Nope. :-(
ian_sg wrote:Are you doing anything in particular when you see these?
It is hard to tell, because we are constantly tracing, and then the next day I go in and check the data, and that is when I see a lot of these.
ian_sg wrote:Does the Vault client report an error when this occurs on the server?
I have not seen any errors from vault, at least not any that would correlate to the # of times this error is showing up.
ian_sg wrote:It would also help if you could provide the version of Vault that you're running.
We are currently running 3.0.4 and 3.0.5 clients against a 3.0.4 server. I will upgrade the server and clients to the latest version today though.

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Mon Aug 01, 2005 11:57 am

With the profiler client, are you connecting to SQL Server using an administrative account? It sounds like it may actually be that profiler itself is unable to find certain SQL Server objects, and that's where the errors are coming from.
Ian Olsen
SourceGear

thomas62j5
Posts: 71
Joined: Tue Aug 17, 2004 7:59 pm
Location: West Coast, USA

Post by thomas62j5 » Mon Aug 01, 2005 12:18 pm

The profiler is actually created from the sa account, so I think it should work ok. I will check on that aspect.

Locked