Friday, February 24, 2012
Error 2809
We are running SQL Server 2000 Enterprise on a W2K cluster.
I have been seeing Error 1203 in a profile trace. I successfully applied
service pack 3a and Error 1203 has stopped, but I still see error 2809
periodically.
Also, when I run "select @.@.version", the response says '...build 2195:
Service Pack 2' and doesn't mention service pack 3a. Is this normal?
Thanks
Bill
Hi
Build 2195 is Windows 2000. The SP2 reference is Windows 2000 SP2. That is
the Os information.
When running select @.@.version, the values after 8.00.xxxx are what determine
the SQL Server version
SP3a = 8.00.760
If I were you, get onto Windows 2000 SP4 asap.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"bill" <belgie@.datamti.com> wrote in message
news:OnTnOd#yEHA.3548@.TK2MSFTNGP09.phx.gbl...
> What is error 2809?
> We are running SQL Server 2000 Enterprise on a W2K cluster.
> I have been seeing Error 1203 in a profile trace. I successfully applied
> service pack 3a and Error 1203 has stopped, but I still see error 2809
> periodically.
> Also, when I run "select @.@.version", the response says '...build 2195:
> Service Pack 2' and doesn't mention service pack 3a. Is this normal?
> Thanks
> Bill
>
>
|||I see. Thanks.
Do you know what the Error 2809 is? I can't find much about it.
"bill" <belgie@.datamti.com> wrote in message
news:OnTnOd%23yEHA.3548@.TK2MSFTNGP09.phx.gbl...
> What is error 2809?
> We are running SQL Server 2000 Enterprise on a W2K cluster.
> I have been seeing Error 1203 in a profile trace. I successfully applied
> service pack 3a and Error 1203 has stopped, but I still see error 2809
> periodically.
> Also, when I run "select @.@.version", the response says '...build 2195:
> Service Pack 2' and doesn't mention service pack 3a. Is this normal?
> Thanks
> Bill
>
>
|||Hi
Not see that one around. Do you always get it on a specific query?
2809, Sev 16.
The request for %S_MSG '%.*ls' failed because '%.*ls' is a %S_MSG object.
Not much out there about it. If you can figure out in what scenarios you get
it, PSS might be able to help
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"bill" <belgie@.datamti.com> wrote in message
news:eHAkDB$yEHA.3844@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> I see. Thanks.
> Do you know what the Error 2809 is? I can't find much about it.
>
> "bill" <belgie@.datamti.com> wrote in message
> news:OnTnOd%23yEHA.3548@.TK2MSFTNGP09.phx.gbl...
applied
>
|||It is what pretty much what you see in the full description:
A request for an object of the wrong type - such as trying
to execute a view or a table instead of a stored procedures.
I've generally seen it with ADO apps that have some problems
with OpenReecordset commands - usually when table names are
used for the data source instead of a select statement.
-Sue
On Tue, 16 Nov 2004 10:23:41 -0500, "bill"
<belgie@.datamti.com> wrote:
>I see. Thanks.
>Do you know what the Error 2809 is? I can't find much about it.
>
>"bill" <belgie@.datamti.com> wrote in message
>news:OnTnOd%23yEHA.3548@.TK2MSFTNGP09.phx.gbl...
>
|||OK, I think you're right - the database is sometimes used by some MSAccess
ADPs and when the code uses a DLOOKUP function on a table, it looks like it
tries to execute the table as if it was a stored procedure, and I see the
error.
Thanks for your help.
-Bill
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:nh7kp05nnnh65v81qbit3iae04sa9dtd38@.4ax.com... [vbcol=seagreen]
> It is what pretty much what you see in the full description:
> A request for an object of the wrong type - such as trying
> to execute a view or a table instead of a stored procedures.
> I've generally seen it with ADO apps that have some problems
> with OpenReecordset commands - usually when table names are
> used for the data source instead of a select statement.
> -Sue
> On Tue, 16 Nov 2004 10:23:41 -0500, "bill"
> <belgie@.datamti.com> wrote:
applied
>
Error 2809
We are running SQL Server 2000 Enterprise on a W2K cluster.
I have been seeing Error 1203 in a profile trace. I successfully applied
service pack 3a and Error 1203 has stopped, but I still see error 2809
periodically.
Also, when I run "select @.@.version", the response says '...build 2195:
Service Pack 2' and doesn't mention service pack 3a. Is this normal?
Thanks
BillHi
Build 2195 is Windows 2000. The SP2 reference is Windows 2000 SP2. That is
the Os information.
When running select @.@.version, the values after 8.00.xxxx are what determine
the SQL Server version
SP3a = 8.00.760
If I were you, get onto Windows 2000 SP4 asap.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"bill" <belgie@.datamti.com> wrote in message
news:OnTnOd#yEHA.3548@.TK2MSFTNGP09.phx.gbl...
> What is error 2809?
> We are running SQL Server 2000 Enterprise on a W2K cluster.
> I have been seeing Error 1203 in a profile trace. I successfully applied
> service pack 3a and Error 1203 has stopped, but I still see error 2809
> periodically.
> Also, when I run "select @.@.version", the response says '...build 2195:
> Service Pack 2' and doesn't mention service pack 3a. Is this normal?
> Thanks
> Bill
>
>|||I see. Thanks.
Do you know what the Error 2809 is? I can't find much about it.
"bill" <belgie@.datamti.com> wrote in message
news:OnTnOd%23yEHA.3548@.TK2MSFTNGP09.phx.gbl...
> What is error 2809?
> We are running SQL Server 2000 Enterprise on a W2K cluster.
> I have been seeing Error 1203 in a profile trace. I successfully applied
> service pack 3a and Error 1203 has stopped, but I still see error 2809
> periodically.
> Also, when I run "select @.@.version", the response says '...build 2195:
> Service Pack 2' and doesn't mention service pack 3a. Is this normal?
> Thanks
> Bill
>
>|||Hi
Not see that one around. Do you always get it on a specific query?
2809, Sev 16.
The request for %S_MSG '%.*ls' failed because '%.*ls' is a %S_MSG object.
Not much out there about it. If you can figure out in what scenarios you get
it, PSS might be able to help
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"bill" <belgie@.datamti.com> wrote in message
news:eHAkDB$yEHA.3844@.TK2MSFTNGP12.phx.gbl...
> I see. Thanks.
> Do you know what the Error 2809 is? I can't find much about it.
>
> "bill" <belgie@.datamti.com> wrote in message
> news:OnTnOd%23yEHA.3548@.TK2MSFTNGP09.phx.gbl...
applied[vbcol=seagreen]
>|||It is what pretty much what you see in the full description:
A request for an object of the wrong type - such as trying
to execute a view or a table instead of a stored procedures.
I've generally seen it with ADO apps that have some problems
with OpenReecordset commands - usually when table names are
used for the data source instead of a select statement.
-Sue
On Tue, 16 Nov 2004 10:23:41 -0500, "bill"
<belgie@.datamti.com> wrote:
>I see. Thanks.
>Do you know what the Error 2809 is? I can't find much about it.
>
>"bill" <belgie@.datamti.com> wrote in message
>news:OnTnOd%23yEHA.3548@.TK2MSFTNGP09.phx.gbl...
>|||OK, I think you're right - the database is sometimes used by some MSAccess
ADPs and when the code uses a DLOOKUP function on a table, it looks like it
tries to execute the table as if it was a stored procedure, and I see the
error.
Thanks for your help.
-Bill
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:nh7kp05nnnh65v81qbit3iae04sa9dtd38@.
4ax.com...
> It is what pretty much what you see in the full description:
> A request for an object of the wrong type - such as trying
> to execute a view or a table instead of a stored procedures.
> I've generally seen it with ADO apps that have some problems
> with OpenReecordset commands - usually when table names are
> used for the data source instead of a select statement.
> -Sue
> On Tue, 16 Nov 2004 10:23:41 -0500, "bill"
> <belgie@.datamti.com> wrote:
>
applied[vbcol=seagreen]
>
Error 2809
We are running SQL Server 2000 Enterprise on a W2K cluster.
I have been seeing Error 1203 in a profile trace. I successfully applied
service pack 3a and Error 1203 has stopped, but I still see error 2809
periodically.
Also, when I run "select @.@.version", the response says '...build 2195:
Service Pack 2' and doesn't mention service pack 3a. Is this normal?
Thanks
BillHi
Build 2195 is Windows 2000. The SP2 reference is Windows 2000 SP2. That is
the Os information.
When running select @.@.version, the values after 8.00.xxxx are what determine
the SQL Server version
SP3a = 8.00.760
If I were you, get onto Windows 2000 SP4 asap.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"bill" <belgie@.datamti.com> wrote in message
news:OnTnOd#yEHA.3548@.TK2MSFTNGP09.phx.gbl...
> What is error 2809?
> We are running SQL Server 2000 Enterprise on a W2K cluster.
> I have been seeing Error 1203 in a profile trace. I successfully applied
> service pack 3a and Error 1203 has stopped, but I still see error 2809
> periodically.
> Also, when I run "select @.@.version", the response says '...build 2195:
> Service Pack 2' and doesn't mention service pack 3a. Is this normal?
> Thanks
> Bill
>
>|||I see. Thanks.
Do you know what the Error 2809 is? I can't find much about it.
"bill" <belgie@.datamti.com> wrote in message
news:OnTnOd%23yEHA.3548@.TK2MSFTNGP09.phx.gbl...
> What is error 2809?
> We are running SQL Server 2000 Enterprise on a W2K cluster.
> I have been seeing Error 1203 in a profile trace. I successfully applied
> service pack 3a and Error 1203 has stopped, but I still see error 2809
> periodically.
> Also, when I run "select @.@.version", the response says '...build 2195:
> Service Pack 2' and doesn't mention service pack 3a. Is this normal?
> Thanks
> Bill
>
>|||Hi
Not see that one around. Do you always get it on a specific query?
2809, Sev 16.
The request for %S_MSG '%.*ls' failed because '%.*ls' is a %S_MSG object.
Not much out there about it. If you can figure out in what scenarios you get
it, PSS might be able to help
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"bill" <belgie@.datamti.com> wrote in message
news:eHAkDB$yEHA.3844@.TK2MSFTNGP12.phx.gbl...
> I see. Thanks.
> Do you know what the Error 2809 is? I can't find much about it.
>
> "bill" <belgie@.datamti.com> wrote in message
> news:OnTnOd%23yEHA.3548@.TK2MSFTNGP09.phx.gbl...
> > What is error 2809?
> >
> > We are running SQL Server 2000 Enterprise on a W2K cluster.
> >
> > I have been seeing Error 1203 in a profile trace. I successfully
applied
> > service pack 3a and Error 1203 has stopped, but I still see error 2809
> > periodically.
> >
> > Also, when I run "select @.@.version", the response says '...build 2195:
> > Service Pack 2' and doesn't mention service pack 3a. Is this normal?
> >
> > Thanks
> > Bill
> >
> >
> >
> >
>|||It is what pretty much what you see in the full description:
A request for an object of the wrong type - such as trying
to execute a view or a table instead of a stored procedures.
I've generally seen it with ADO apps that have some problems
with OpenReecordset commands - usually when table names are
used for the data source instead of a select statement.
-Sue
On Tue, 16 Nov 2004 10:23:41 -0500, "bill"
<belgie@.datamti.com> wrote:
>I see. Thanks.
>Do you know what the Error 2809 is? I can't find much about it.
>
>"bill" <belgie@.datamti.com> wrote in message
>news:OnTnOd%23yEHA.3548@.TK2MSFTNGP09.phx.gbl...
>> What is error 2809?
>> We are running SQL Server 2000 Enterprise on a W2K cluster.
>> I have been seeing Error 1203 in a profile trace. I successfully applied
>> service pack 3a and Error 1203 has stopped, but I still see error 2809
>> periodically.
>> Also, when I run "select @.@.version", the response says '...build 2195:
>> Service Pack 2' and doesn't mention service pack 3a. Is this normal?
>> Thanks
>> Bill
>>
>>
>|||OK, I think you're right - the database is sometimes used by some MSAccess
ADPs and when the code uses a DLOOKUP function on a table, it looks like it
tries to execute the table as if it was a stored procedure, and I see the
error.
Thanks for your help.
-Bill
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:nh7kp05nnnh65v81qbit3iae04sa9dtd38@.4ax.com...
> It is what pretty much what you see in the full description:
> A request for an object of the wrong type - such as trying
> to execute a view or a table instead of a stored procedures.
> I've generally seen it with ADO apps that have some problems
> with OpenReecordset commands - usually when table names are
> used for the data source instead of a select statement.
> -Sue
> On Tue, 16 Nov 2004 10:23:41 -0500, "bill"
> <belgie@.datamti.com> wrote:
> >I see. Thanks.
> >Do you know what the Error 2809 is? I can't find much about it.
> >
> >
> >
> >"bill" <belgie@.datamti.com> wrote in message
> >news:OnTnOd%23yEHA.3548@.TK2MSFTNGP09.phx.gbl...
> >> What is error 2809?
> >>
> >> We are running SQL Server 2000 Enterprise on a W2K cluster.
> >>
> >> I have been seeing Error 1203 in a profile trace. I successfully
applied
> >> service pack 3a and Error 1203 has stopped, but I still see error 2809
> >> periodically.
> >>
> >> Also, when I run "select @.@.version", the response says '...build 2195:
> >> Service Pack 2' and doesn't mention service pack 3a. Is this normal?
> >>
> >> Thanks
> >> Bill
> >>
> >>
> >>
> >>
> >
>
Friday, February 17, 2012
Error -2147217887
my query.
Platform detail
Windows 98
SQL 2000
error 2147217887 - ODBC driver does not support the
requested properties
Please suggestHi Nishant
There maybe problem with your MDAC. I suggest to apply latest MDAC on the
machine where you try to launch SQL profiler.
Sincerely,
Yih-Yoon Lee [Microsoft]
Microsoft SQL Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Wednesday, February 15, 2012
Error 208, Missing Stats
Just been having my head messed with...
I was running a trace capturing all errors and SQL. Had a bucket of
error 208's (invalid object name). Found the SQL that caused it - an
SP.
Ran the sp by hand, no messages come up - error 208 logged in the
trace.
Couldn't work it out. Then noticed stats missing on one column.
Created the stats manually - and suddenly the 208 error stops. Wtf?
Is this predicted/expected behaviour? Just me being a noob?
Thought I'd just share that. ta ;)
SQL2k, sp3a, w2k server.WangKhar (Wangkhar@.yahoo.com) writes:
> I was running a trace capturing all errors and SQL. Had a bucket of
> error 208's (invalid object name). Found the SQL that caused it - an
> SP.
Yes, this to be expected. This is because of deferred name resolution.
If the procedure creates temp tables, you'll get a lot of 208s. It could
be missing stastistics too. These are just signaled internally and inter-
cepted by some other module.
They are possibly of interest if they are causing recompiles for missing
tables, but then you should look for SP:Recompile instead.
And, true, missing statistics is another thing you could find. Then
again, with auto-statistics on, the statistics should come by time anyway.
--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <sommar@.algonet.se> wrote in message
> Yes, this to be expected. This is because of deferred name resolution.
Ta.
Error 208 while executing procedure
Here is a piece of code which i execute while running a stored procedure,
when i trace the procedure i get error 208 , the inner proc which i execute
is there in the database but still i get error 208 when i execute the outer
procedure, here is the code for outer proc which executes the inner proc
IF @.Reserves <> 0 AND @.cDeathFundEventStatus = 'DA' -- @.NonPIA = 1
BEGIN
SET @.cResult = NULL
EXEC dbo.ap_Dth_Settle_Trans_HandleAssets
@.cDeathBenefitOptionID,
'NONPIASR',
NULL,
@.cResult OUTPUT
---
-- Error Handler
---
-- Check system error
SET @.nError = @.@.ERROR
IF @.nError <> 0
BEGIN
SET @.cOutput = @.cProcessName + '~(' + CAST(@.nError AS VARCHAR(10))+
')5:System error calling sp ap_Dth_Settle_Trans_HandleAssets'
GOTO errHandler
END -- (@.nError <> 0)
-- Check for logic error
IF @.cResult IS NOT NULL -- Success = NULL
BEGIN
SET @.cOutput = @.cResult -- Logic failure in called sp
GOTO errHandler
END -- @.cResult IS NOT NULL (Success = NULL)
ENDRodger,
Is 'dbo' the owner of the inner procedure?
See "Error 208" in BOL.
AMB
"Rodger" wrote:
> HI
> Here is a piece of code which i execute while running a stored procedure,
> when i trace the procedure i get error 208 , the inner proc which i execut
e
> is there in the database but still i get error 208 when i execute the oute
r
> procedure, here is the code for outer proc which executes the inner proc
> IF @.Reserves <> 0 AND @.cDeathFundEventStatus = 'DA' -- @.NonPIA = 1
> BEGIN
> SET @.cResult = NULL
> EXEC dbo.ap_Dth_Settle_Trans_HandleAssets
> @.cDeathBenefitOptionID,
> 'NONPIASR',
> NULL,
> @.cResult OUTPUT
> ---
> -- Error Handler
> ---
> -- Check system error
> SET @.nError = @.@.ERROR
> IF @.nError <> 0
> BEGIN
> SET @.cOutput = @.cProcessName + '~(' + CAST(@.nError AS VARCHAR(10))+
> ')5:System error calling sp ap_Dth_Settle_Trans_HandleAssets'
> GOTO errHandler
> END -- (@.nError <> 0)
> -- Check for logic error
> IF @.cResult IS NOT NULL -- Success = NULL
> BEGIN
> SET @.cOutput = @.cResult -- Logic failure in called sp
> GOTO errHandler
> END -- @.cResult IS NOT NULL (Success = NULL)
> END|||Hi
If you can script the DDL, example data and the procedures so that the
problem is re-creatable in another database, then you may solve it, otherwis
e
they could be posted!
My only guess is that there is some spurious character(s) in there.
John
"Rodger" wrote:
> HI
> Here is a piece of code which i execute while running a stored procedure,
> when i trace the procedure i get error 208 , the inner proc which i execut
e
> is there in the database but still i get error 208 when i execute the oute
r
> procedure, here is the code for outer proc which executes the inner proc
> IF @.Reserves <> 0 AND @.cDeathFundEventStatus = 'DA' -- @.NonPIA = 1
> BEGIN
> SET @.cResult = NULL
> EXEC dbo.ap_Dth_Settle_Trans_HandleAssets
> @.cDeathBenefitOptionID,
> 'NONPIASR',
> NULL,
> @.cResult OUTPUT
> ---
> -- Error Handler
> ---
> -- Check system error
> SET @.nError = @.@.ERROR
> IF @.nError <> 0
> BEGIN
> SET @.cOutput = @.cProcessName + '~(' + CAST(@.nError AS VARCHAR(10))+
> ')5:System error calling sp ap_Dth_Settle_Trans_HandleAssets'
> GOTO errHandler
> END -- (@.nError <> 0)
> -- Check for logic error
> IF @.cResult IS NOT NULL -- Success = NULL
> BEGIN
> SET @.cOutput = @.cResult -- Logic failure in called sp
> GOTO errHandler
> END -- @.cResult IS NOT NULL (Success = NULL)
> END|||Thanks Guys .. I found out the problem my stored procedure had lot of
temporary tables so it gave me a error while executing this piece of code
which executes a inner stored procedure, when i try global temporary table i
t
works
Thanks
"John Bell" wrote:
> Hi
> If you can script the DDL, example data and the procedures so that the
> problem is re-creatable in another database, then you may solve it, otherw
ise
> they could be posted!
> My only guess is that there is some spurious character(s) in there.
> John
> "Rodger" wrote:
>|||Rodger,
If you're only seeing the 208 errors when monitoring the exception event in
Profiler, you likely haven't got an issue at all with the original code.
Exception events reported in Profiler may or may not actually get reported t
o
the application calling SQL Server. There are cases in which SQL Server
internally raises and then handles the 208 exception. As a result, it gets
captured by Profiler, but the client application never encounters an error.
The time when this is most often encountered is with exception event 208
(basically, object not found). This often happens with deferred name
resolution in SQL Server. Basically, whenever SQL Server is parsing a query
,
it attempts to resolve the names of all tables referenced in the query. In
some cases, such a temp tables, these might not exist yet. Internally, this
raises the 208 exception event. However, SQL Server looks at the situation
and determines that the issue can be addressed by deferred name resolution
(i.e. it doesn't worry about it until someone actually executes the query).
As a result of this handling, processing proceeds normally and no error is
reported to the client application despite being reported within Profiler.
To see this behavior, create and then run the following stored procedure in
Query Analyzer. If you monitor the exception event in Profiler, you should
see exception 208 pop up, but execution is reported as successful within
Query Analyzer.
CREATE PROCEDURE proc_test_deferred_name_resolution
AS
CREATE TABLE #test(c1 int)
SELECT * FROM #test
DROP TABLE #test
GO
EXEC proc_test_deferred_name_resolution
GO
For additional information on deferred name resolution in SQL Server, please
see the Books Online topic "Deferred Name Resolution and Compilation"
(http://msdn.microsoft.com/library/d...
s_07_5wa6.asp)
- Chris Cubley
"Rodger" wrote:
> Thanks Guys .. I found out the problem my stored procedure had lot of
> temporary tables so it gave me a error while executing this piece of code
> which executes a inner stored procedure, when i try global temporary table
it
> works
> Thanks
> "John Bell" wrote:
>
Error 208
anything to health and performance of the box? Is this
something developers have to fix? Thnx.Hi,
Are you talking about the appearance of the message ' DBCC TRACEON 208,
server process ID (SPID)' in the SQL Server log file ?If so, this is the
logging of the 'MS Query Quoted Identifier' trace flag .This is for the DBA
to fix by using the start up parameter -T2505 with SQL Server.
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"BH" <hubrian@.hotmail.com> wrote in message
news:027a01c37d4b$d2a36a50$a401280a@.phx.gbl...
> Getting a lot of error 208 in trace. Does this mean
> anything to health and performance of the box? Is this
> something developers have to fix? Thnx.