Really would appreciate some advice on this problem. I have a cluster, CORPUSGA and a stand alone server CORPUSAPP22. CORPUSAPP22 has a linked server set up to CORPUSGA using 'sa' as the security context. Within a stored procedure I am running a SELECT to CORPUSGA.msdb.dbo.sysjobs.
When this is run from Query Analyzer it is fine and runs under the 'dbo' security context, but when is is run under xp_sendmail that uses the SQL Agent's security context (a domain account called
IntServiceGA) it fails with this message:
ODBC error 7410 (42000) Remote access not allowed for Windows NT user activated by SETUSER.
For the following command:
exec master.dbo.xp_sendmail
@.recipients = 'stelzner_eve@.emc.com;dabas_ravi@.emc.com;bergin_gi llian@.emc.com;lynch_eoin@.e
mc.com;sherman_ nancy@.emc.com',
@.message = @.email,
@.query = @.query_text,
@.no_header = 'true',
@.width=80,
@.subject = 'Job Failed on CORPUSGA ',
@.attach_results = 'true',
@.set_user = 'dbo'
Where @.query_text is something like "select * from CORPUSGA.msdb.dbo.sysjobs"
The IntServiceGA account is identical on both servers and is in the local administrators group on both servers and is in the system administrators role within SQL Server, has access to the database and sysjobs has granted permissions to IntServiceGA (SELECT, INSERT,UPDATE,DELETE).
When I run profiler against this, it tries to execute under IntServiceGA (an Windows authentication account) and then tries to SETUSER to sa . This is what it objects to the switching. I have tried to set up the IntServiceGA as the security context for the linked server too and this does not work, same error.
Any help would be great,
Thanks,
EveWhy do you need @.set_user if SQLAgent service account is already in sysadmin server role?|||I have another stored procedure that uses this and it works with the
@.set_user on this one. However, whether I leave it in or take out the
@.set_user parameter it still fails. Any ideas?
Thanks,
Eve|||Try to run your xp_sendmail after doing SETUSER 'DOMAIN_NAME\IntServiceGA' and see what you get.|||no go, using the SETUSER prior to the xp_sendmail still netted the
same results? Do you know what generates this message- NT or SQL?|||It's NT. It just proved that your SQLAgent account is lacking some rights. Was mail profile setup using SQLAgent service account?|||Yes, the profile was set up on both servers from the
corp\IntServiceGA account that is a local admin on
the both servers. Are there additional policies that need
to be put on for this account that are not in the default?
Showing posts with label cluster. Show all posts
Showing posts with label cluster. Show all posts
Wednesday, March 21, 2012
Friday, March 9, 2012
Error 435 bringing resource online?
Hi All,
I hope this is not a FAQ. I have a 2-node Windows Server 2003 cluster, with
SQL Server 2000 SP3a. This is a development system, and is actually
implemented using VMware (though I don't think that is relevant).
Occasionally when moving the SQL Server group, I get random failures of SQL
Server, Agent, or Fulltext. Going through cluster.log, I find entries like
the following:
000002d4.0000020c::2005/03/10-05:56:37.490 ERR SQL Server <SQL Server>:
[sqsrvres] StartResourceService: Failed to start MSSQLSERVER service.
CurrentState: 1
000002d4.0000020c::2005/03/10-05:56:37.490 ERR SQL Server <SQL Server>:
[sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status 435)
000002d4.0000020c::2005/03/10-05:56:37.505 ERR SQL Server <SQL Server>:
[sqsrvres] OnlineThread: Error 435 bringing resource online.
and
000002d4.00000cf0::2005/03/10-06:09:52.281 ERR <Unknown Resource>:
[sqsrvres] StartResourceService: Failed to start SQLSERVERAGENT service.
CurrentState: 1
000002d4.00000cf0::2005/03/10-06:09:52.281 ERR SQL Server Agent <SQL Server
Agent>: [sqagtres] OnlineThread: ResUtilsStartResourceService failed (status
435)
000002d4.00000cf0::2005/03/10-06:09:52.281 ERR SQL Server Agent <SQL Server
Agent>: [sqagtres] OnlineThread: Error 435 bringing resource online.
Any ideas as to what is going wrong? Could this be network-related?
Many thanks,
John.
John wrote:
> Hi All,
> I hope this is not a FAQ. I have a 2-node Windows Server 2003 cluster, with
> SQL Server 2000 SP3a. This is a development system, and is actually
> implemented using VMware (though I don't think that is relevant).
It could be relevant. Workstation 4.x does too much disk caching so disk
corruption will occur, on the quorum disk for example. VMWare GSX 3 is
fine a long as you add disk.locking="FALSE" and scsi0.sharedBus="virtual"
Hans
|||Thanks for the response. Yes, I am using VMware Workstation 4.5 - that may
be an issue.
Is there a way of finding out exactly what error 435 means? It does not
seem to be a standard error code; "net helpmsg" does not help.
Thanks,
John.
"Hans de Bruin" wrote:
> John wrote:
> It could be relevant. Workstation 4.x does too much disk caching so disk
> corruption will occur, on the quorum disk for example. VMWare GSX 3 is
> fine a long as you add disk.locking="FALSE" and scsi0.sharedBus="virtual"
> --
> Hans
>
|||John wrote:
> Thanks for the response. Yes, I am using VMware Workstation 4.5 - that may
> be an issue.
> Is there a way of finding out exactly what error 435 means? It does not
> seem to be a standard error code; "net helpmsg" does not help.
>
Cluster service can't bring the resources online. Check the windows event
log and the sql log files to find out why. When that does not help, run a
dos box as the sql service account an start sql from the command line (not
net start but the sqlserver.exe).
If you really want to cluster with vmware either use a single node cluster
or use iscsi drives. I have got an out of date site which describes this:
http://eratosthenes.xs4all.nl/wmwarecluster/ .
Hans
|||What was the fix for this? I am having the same exact issue.
Originally posted by Hansde Bruin
John wrote:
> Thanks for the response. Yes, I am using VMware Workstation 4.5 - that may
> be an issue.
> Is there a way of finding out exactly what error 435 means? It does not
> seem to be a standard error code; "net helpmsg" does not help.
>
Cluster service can't bring the resources online. Check the windows event
log and the sql log files to find out why. When that does not help, run a
dos box as the sql service account an start sql from the command line (not
net start but the sqlserver.exe).
If you really want to cluster with vmware either use a single node cluster
or use iscsi drives. I have got an out of date site which describes this:
http://eratosthenes.xs4all.nl/wmwarecluster/ .
Hans
I hope this is not a FAQ. I have a 2-node Windows Server 2003 cluster, with
SQL Server 2000 SP3a. This is a development system, and is actually
implemented using VMware (though I don't think that is relevant).
Occasionally when moving the SQL Server group, I get random failures of SQL
Server, Agent, or Fulltext. Going through cluster.log, I find entries like
the following:
000002d4.0000020c::2005/03/10-05:56:37.490 ERR SQL Server <SQL Server>:
[sqsrvres] StartResourceService: Failed to start MSSQLSERVER service.
CurrentState: 1
000002d4.0000020c::2005/03/10-05:56:37.490 ERR SQL Server <SQL Server>:
[sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status 435)
000002d4.0000020c::2005/03/10-05:56:37.505 ERR SQL Server <SQL Server>:
[sqsrvres] OnlineThread: Error 435 bringing resource online.
and
000002d4.00000cf0::2005/03/10-06:09:52.281 ERR <Unknown Resource>:
[sqsrvres] StartResourceService: Failed to start SQLSERVERAGENT service.
CurrentState: 1
000002d4.00000cf0::2005/03/10-06:09:52.281 ERR SQL Server Agent <SQL Server
Agent>: [sqagtres] OnlineThread: ResUtilsStartResourceService failed (status
435)
000002d4.00000cf0::2005/03/10-06:09:52.281 ERR SQL Server Agent <SQL Server
Agent>: [sqagtres] OnlineThread: Error 435 bringing resource online.
Any ideas as to what is going wrong? Could this be network-related?
Many thanks,
John.
John wrote:
> Hi All,
> I hope this is not a FAQ. I have a 2-node Windows Server 2003 cluster, with
> SQL Server 2000 SP3a. This is a development system, and is actually
> implemented using VMware (though I don't think that is relevant).
It could be relevant. Workstation 4.x does too much disk caching so disk
corruption will occur, on the quorum disk for example. VMWare GSX 3 is
fine a long as you add disk.locking="FALSE" and scsi0.sharedBus="virtual"
Hans
|||Thanks for the response. Yes, I am using VMware Workstation 4.5 - that may
be an issue.
Is there a way of finding out exactly what error 435 means? It does not
seem to be a standard error code; "net helpmsg" does not help.
Thanks,
John.
"Hans de Bruin" wrote:
> John wrote:
> It could be relevant. Workstation 4.x does too much disk caching so disk
> corruption will occur, on the quorum disk for example. VMWare GSX 3 is
> fine a long as you add disk.locking="FALSE" and scsi0.sharedBus="virtual"
> --
> Hans
>
|||John wrote:
> Thanks for the response. Yes, I am using VMware Workstation 4.5 - that may
> be an issue.
> Is there a way of finding out exactly what error 435 means? It does not
> seem to be a standard error code; "net helpmsg" does not help.
>
Cluster service can't bring the resources online. Check the windows event
log and the sql log files to find out why. When that does not help, run a
dos box as the sql service account an start sql from the command line (not
net start but the sqlserver.exe).
If you really want to cluster with vmware either use a single node cluster
or use iscsi drives. I have got an out of date site which describes this:
http://eratosthenes.xs4all.nl/wmwarecluster/ .
Hans
|||What was the fix for this? I am having the same exact issue.
Quote:
John wrote:
> Thanks for the response. Yes, I am using VMware Workstation 4.5 - that may
> be an issue.
> Is there a way of finding out exactly what error 435 means? It does not
> seem to be a standard error code; "net helpmsg" does not help.
>
Cluster service can't bring the resources online. Check the windows event
log and the sql log files to find out why. When that does not help, run a
dos box as the sql service account an start sql from the command line (not
net start but the sqlserver.exe).
If you really want to cluster with vmware either use a single node cluster
or use iscsi drives. I have got an out of date site which describes this:
http://eratosthenes.xs4all.nl/wmwarecluster/ .
Hans
Error 42d during Fail Over SQL 2000 Enterprise in a Server 2003 Ent. Cluster
Hi All,
I've been struggling with this issue for a few days now.
We have 2node Server 2003 Entprise cluster with a fresh install of
MSSQL 2000 SP3a. Everything works great until I attempt to simluate a
node failure. Node 2 starts every service fine with the exception of
the 3 SQL services:
SQL Server
SQL Server Agent
SQL Server Fulltext
When I check the event log I see the following twice:
Event ID : 17052 [sqsrvres] StartResourceService: StartService
(MSSQLSERVER) failed. Error: 42d
Event ID : 17052 [sqsrvres] OnlineThread: ResUtilsStartResourceService
failed (status 42d)
Event ID : 17052 [sqsrvres] OnlineThread: Error 42d bringing resource
online.
Now I've read prior posts and have found that the 42d when converted
from HEX means that it's a logon failure. However I'm using the
Administrator account, have re-entered the username and password 3+
times and have checked all the domain security policies against this
account. I've even added Administrator to the "logon as service" and
three other priv's that Microsoft recommends.
I have rebooted the server numerous times now after each change and I
am still experiencing the same problem. What could I be missing?
I appreciate your time in this matter.
~Chris
Christopher,
Are you using the local "administrator" account to startup the services? If
so you should create a special domain account to startup your sql server
servcies on both servers and add this account to the Administrators local
group or to any other group with the restricted privileges you want.
Try from the working node, on the Enterprise manager to change the startup
account to the one which is currently working, doing from the EM should
change the account on all the nodes on the cluster.
Hope this helps.
Regards.
FR
|||On May 16, 5:26 pm, Frivas <Fri...@.discussions.microsoft.com> wrote:
> Christopher,
> Are you using the local "administrator" account to startup the services? If
> so you should create a special domain account to startup your sql server
> servcies on both servers and add this account to the Administrators local
> group or to any other group with the restricted privileges you want.
> Try from the working node, on the Enterprise manager to change the startup
> account to the one which is currently working, doing from the EM should
> change the account on all the nodes on the cluster.
> Hope this helps.
> Regards.
> FR
Greetings Frivas,
Thanks for your response. I am using the "Domain Administrator"
account. The software vendor the cluster is assembled for required
that we use that account unfortunately. However I will give your
recommendation a try and let you know my findings.
Thanks again.
~Chris
|||Look for the location of the SQL agent log file and make sure it is a
clustered resource in the SQL group. There is a bug in the
install/configure routines that allows the log file to be placed in an
incorrect cluster location.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<christophercnewton@.gmail.com> wrote in message
news:1179350437.951320.310920@.p77g2000hsh.googlegr oups.com...
> Hi All,
> I've been struggling with this issue for a few days now.
> We have 2node Server 2003 Entprise cluster with a fresh install of
> MSSQL 2000 SP3a. Everything works great until I attempt to simluate a
> node failure. Node 2 starts every service fine with the exception of
> the 3 SQL services:
> SQL Server
> SQL Server Agent
> SQL Server Fulltext
> When I check the event log I see the following twice:
> Event ID : 17052 [sqsrvres] StartResourceService: StartService
> (MSSQLSERVER) failed. Error: 42d
> Event ID : 17052 [sqsrvres] OnlineThread: ResUtilsStartResourceService
> failed (status 42d)
> Event ID : 17052 [sqsrvres] OnlineThread: Error 42d bringing resource
> online.
> Now I've read prior posts and have found that the 42d when converted
> from HEX means that it's a logon failure. However I'm using the
> Administrator account, have re-entered the username and password 3+
> times and have checked all the domain security policies against this
> account. I've even added Administrator to the "logon as service" and
> three other priv's that Microsoft recommends.
> I have rebooted the server numerous times now after each change and I
> am still experiencing the same problem. What could I be missing?
> I appreciate your time in this matter.
> ~Chris
>
|||Chris you should know that there is no technical reason to a domain admin
account. Usually people want a domain account so that they can run things
against an other machine. If you do create a service account and make is
local admin on the system and other systems that is needs to talk to you will
be fine. We run all our servers with service accounts that are just normal
users on the domain and the network, in some special cases that account in
local admin.
Good Luck
John Vandervliet
"christophercnewton@.gmail.com" wrote:
> On May 16, 5:26 pm, Frivas <Fri...@.discussions.microsoft.com> wrote:
>
> Greetings Frivas,
> Thanks for your response. I am using the "Domain Administrator"
> account. The software vendor the cluster is assembled for required
> that we use that account unfortunately. However I will give your
> recommendation a try and let you know my findings.
> Thanks again.
> ~Chris
>
|||Also make sure that if you have removed the BUILTIN\Administrators group as
a valid login that you add back the service account that operates the
Cluster service.
It does not need any special rights, but it will need to log into the
server.
On both cluster nodes, make sure that the SQL Server service account is a
domain account and has the following User Rights assignments:
Act as part of the OS
Bypass Traverse Checking
Lock Pages in Memory
Log on as a Batch Job
Log on as a Service
Replace a Process Level Token
http://support.microsoft.com/kb/283811
Anthony Thomas
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:utHVUXImHHA.4752@.TK2MSFTNGP04.phx.gbl...
> Look for the location of the SQL agent log file and make sure it is a
> clustered resource in the SQL group. There is a bug in the
> install/configure routines that allows the log file to be placed in an
> incorrect cluster location.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> <christophercnewton@.gmail.com> wrote in message
> news:1179350437.951320.310920@.p77g2000hsh.googlegr oups.com...
>
I've been struggling with this issue for a few days now.
We have 2node Server 2003 Entprise cluster with a fresh install of
MSSQL 2000 SP3a. Everything works great until I attempt to simluate a
node failure. Node 2 starts every service fine with the exception of
the 3 SQL services:
SQL Server
SQL Server Agent
SQL Server Fulltext
When I check the event log I see the following twice:
Event ID : 17052 [sqsrvres] StartResourceService: StartService
(MSSQLSERVER) failed. Error: 42d
Event ID : 17052 [sqsrvres] OnlineThread: ResUtilsStartResourceService
failed (status 42d)
Event ID : 17052 [sqsrvres] OnlineThread: Error 42d bringing resource
online.
Now I've read prior posts and have found that the 42d when converted
from HEX means that it's a logon failure. However I'm using the
Administrator account, have re-entered the username and password 3+
times and have checked all the domain security policies against this
account. I've even added Administrator to the "logon as service" and
three other priv's that Microsoft recommends.
I have rebooted the server numerous times now after each change and I
am still experiencing the same problem. What could I be missing?
I appreciate your time in this matter.
~Chris
Christopher,
Are you using the local "administrator" account to startup the services? If
so you should create a special domain account to startup your sql server
servcies on both servers and add this account to the Administrators local
group or to any other group with the restricted privileges you want.
Try from the working node, on the Enterprise manager to change the startup
account to the one which is currently working, doing from the EM should
change the account on all the nodes on the cluster.
Hope this helps.
Regards.
FR
|||On May 16, 5:26 pm, Frivas <Fri...@.discussions.microsoft.com> wrote:
> Christopher,
> Are you using the local "administrator" account to startup the services? If
> so you should create a special domain account to startup your sql server
> servcies on both servers and add this account to the Administrators local
> group or to any other group with the restricted privileges you want.
> Try from the working node, on the Enterprise manager to change the startup
> account to the one which is currently working, doing from the EM should
> change the account on all the nodes on the cluster.
> Hope this helps.
> Regards.
> FR
Greetings Frivas,
Thanks for your response. I am using the "Domain Administrator"
account. The software vendor the cluster is assembled for required
that we use that account unfortunately. However I will give your
recommendation a try and let you know my findings.
Thanks again.
~Chris
|||Look for the location of the SQL agent log file and make sure it is a
clustered resource in the SQL group. There is a bug in the
install/configure routines that allows the log file to be placed in an
incorrect cluster location.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<christophercnewton@.gmail.com> wrote in message
news:1179350437.951320.310920@.p77g2000hsh.googlegr oups.com...
> Hi All,
> I've been struggling with this issue for a few days now.
> We have 2node Server 2003 Entprise cluster with a fresh install of
> MSSQL 2000 SP3a. Everything works great until I attempt to simluate a
> node failure. Node 2 starts every service fine with the exception of
> the 3 SQL services:
> SQL Server
> SQL Server Agent
> SQL Server Fulltext
> When I check the event log I see the following twice:
> Event ID : 17052 [sqsrvres] StartResourceService: StartService
> (MSSQLSERVER) failed. Error: 42d
> Event ID : 17052 [sqsrvres] OnlineThread: ResUtilsStartResourceService
> failed (status 42d)
> Event ID : 17052 [sqsrvres] OnlineThread: Error 42d bringing resource
> online.
> Now I've read prior posts and have found that the 42d when converted
> from HEX means that it's a logon failure. However I'm using the
> Administrator account, have re-entered the username and password 3+
> times and have checked all the domain security policies against this
> account. I've even added Administrator to the "logon as service" and
> three other priv's that Microsoft recommends.
> I have rebooted the server numerous times now after each change and I
> am still experiencing the same problem. What could I be missing?
> I appreciate your time in this matter.
> ~Chris
>
|||Chris you should know that there is no technical reason to a domain admin
account. Usually people want a domain account so that they can run things
against an other machine. If you do create a service account and make is
local admin on the system and other systems that is needs to talk to you will
be fine. We run all our servers with service accounts that are just normal
users on the domain and the network, in some special cases that account in
local admin.
Good Luck
John Vandervliet
"christophercnewton@.gmail.com" wrote:
> On May 16, 5:26 pm, Frivas <Fri...@.discussions.microsoft.com> wrote:
>
> Greetings Frivas,
> Thanks for your response. I am using the "Domain Administrator"
> account. The software vendor the cluster is assembled for required
> that we use that account unfortunately. However I will give your
> recommendation a try and let you know my findings.
> Thanks again.
> ~Chris
>
|||Also make sure that if you have removed the BUILTIN\Administrators group as
a valid login that you add back the service account that operates the
Cluster service.
It does not need any special rights, but it will need to log into the
server.
On both cluster nodes, make sure that the SQL Server service account is a
domain account and has the following User Rights assignments:
Act as part of the OS
Bypass Traverse Checking
Lock Pages in Memory
Log on as a Batch Job
Log on as a Service
Replace a Process Level Token
http://support.microsoft.com/kb/283811
Anthony Thomas
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:utHVUXImHHA.4752@.TK2MSFTNGP04.phx.gbl...
> Look for the location of the SQL agent log file and make sure it is a
> clustered resource in the SQL group. There is a bug in the
> install/configure routines that allows the log file to be placed in an
> incorrect cluster location.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> <christophercnewton@.gmail.com> wrote in message
> news:1179350437.951320.310920@.p77g2000hsh.googlegr oups.com...
>
Friday, February 24, 2012
Error 2809
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
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
>
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
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
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]
>
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
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
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
> >>
> >>
> >>
> >>
> >
>
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 -2147217900: failed to create SQL database
Geoff,
On a different note, we rebuilt the SQL cluster network today. However when
I run the MSI, I am seeing the below given error this time:
Event Type:Error
Event Source:MsiInstaller
Event Category:None
Event ID:10005
Date:10/16/2006
Time:4:06:34 PM
User:myDomain\SQLServerAccount
Computer:SQLServer
Description:
Product: Database -- Error 26201. Error -2147217900: failed to create SQL
database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
names listed could not be created. Check previous errors..
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Any thoughts on what this error is, and what could be causing this?
--Mehul
"Geoff N. Hiten" wrote:
> Use the cluster.exe command-line utility to stop and restart instances from
> within a script.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:39DD3469-5CEE-49DC-9755-681B5701D0EF@.microsoft.com...
>
>
When you rebuilt the cluster, did you add disk resources as dependencies for
SQL Server? If not, then SOL Server cannot see the disks.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"Mehul" <Mehul@.discussions.microsoft.com> wrote in message
news:CCA03ACA-2B83-488C-B479-11406C9E2D1C@.microsoft.com...
Geoff,
On a different note, we rebuilt the SQL cluster network today. However when
I run the MSI, I am seeing the below given error this time:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 10/16/2006
Time: 4:06:34 PM
User: myDomain\SQLServerAccount
Computer: SQLServer
Description:
Product: Database -- Error 26201. Error -2147217900: failed to create SQL
database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
names listed could not be created. Check previous errors..
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Any thoughts on what this error is, and what could be causing this?
--Mehul
"Geoff N. Hiten" wrote:
> Use the cluster.exe command-line utility to stop and restart instances
> from
> within a script.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:39DD3469-5CEE-49DC-9755-681B5701D0EF@.microsoft.com...
>
>
|||Try creating the databases maually so you get the SQL error message, not the
installer error message. That should tell you exactly why it failed.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:u4pJE2X8GHA.4708@.TK2MSFTNGP05.phx.gbl...
> When you rebuilt the cluster, did you add disk resources as dependencies
> for
> SQL Server? If not, then SOL Server cannot see the disks.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> .
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:CCA03ACA-2B83-488C-B479-11406C9E2D1C@.microsoft.com...
> Geoff,
> On a different note, we rebuilt the SQL cluster network today. However
> when
> I run the MSI, I am seeing the below given error this time:
> Event Type: Error
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 10005
> Date: 10/16/2006
> Time: 4:06:34 PM
> User: myDomain\SQLServerAccount
> Computer: SQLServer
> Description:
> Product: Database -- Error 26201. Error -2147217900: failed to create SQL
> database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
> names listed could not be created. Check previous errors..
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Any thoughts on what this error is, and what could be causing this?
> --Mehul
> "Geoff N. Hiten" wrote:
>
|||You are right on. This is exactly the cause for the below given error log.
We ran profiler to see what commands is the MSI passing to create the DB.
Then we manually tried to run that command in Query analyzer, that throwed
reference to the disk dependency.
Thanks Tom/Geoff for your quick response.
--Mehul
"Tom Moreau" wrote:
> When you rebuilt the cluster, did you add disk resources as dependencies for
> SQL Server? If not, then SOL Server cannot see the disks.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:CCA03ACA-2B83-488C-B479-11406C9E2D1C@.microsoft.com...
> Geoff,
> On a different note, we rebuilt the SQL cluster network today. However when
> I run the MSI, I am seeing the below given error this time:
> Event Type: Error
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 10005
> Date: 10/16/2006
> Time: 4:06:34 PM
> User: myDomain\SQLServerAccount
> Computer: SQLServer
> Description:
> Product: Database -- Error 26201. Error -2147217900: failed to create SQL
> database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
> names listed could not be created. Check previous errors..
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Any thoughts on what this error is, and what could be causing this?
> --Mehul
> "Geoff N. Hiten" wrote:
>
>
On a different note, we rebuilt the SQL cluster network today. However when
I run the MSI, I am seeing the below given error this time:
Event Type:Error
Event Source:MsiInstaller
Event Category:None
Event ID:10005
Date:10/16/2006
Time:4:06:34 PM
User:myDomain\SQLServerAccount
Computer:SQLServer
Description:
Product: Database -- Error 26201. Error -2147217900: failed to create SQL
database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
names listed could not be created. Check previous errors..
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Any thoughts on what this error is, and what could be causing this?
--Mehul
"Geoff N. Hiten" wrote:
> Use the cluster.exe command-line utility to stop and restart instances from
> within a script.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:39DD3469-5CEE-49DC-9755-681B5701D0EF@.microsoft.com...
>
>
When you rebuilt the cluster, did you add disk resources as dependencies for
SQL Server? If not, then SOL Server cannot see the disks.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"Mehul" <Mehul@.discussions.microsoft.com> wrote in message
news:CCA03ACA-2B83-488C-B479-11406C9E2D1C@.microsoft.com...
Geoff,
On a different note, we rebuilt the SQL cluster network today. However when
I run the MSI, I am seeing the below given error this time:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 10/16/2006
Time: 4:06:34 PM
User: myDomain\SQLServerAccount
Computer: SQLServer
Description:
Product: Database -- Error 26201. Error -2147217900: failed to create SQL
database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
names listed could not be created. Check previous errors..
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Any thoughts on what this error is, and what could be causing this?
--Mehul
"Geoff N. Hiten" wrote:
> Use the cluster.exe command-line utility to stop and restart instances
> from
> within a script.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:39DD3469-5CEE-49DC-9755-681B5701D0EF@.microsoft.com...
>
>
|||Try creating the databases maually so you get the SQL error message, not the
installer error message. That should tell you exactly why it failed.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:u4pJE2X8GHA.4708@.TK2MSFTNGP05.phx.gbl...
> When you rebuilt the cluster, did you add disk resources as dependencies
> for
> SQL Server? If not, then SOL Server cannot see the disks.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> .
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:CCA03ACA-2B83-488C-B479-11406C9E2D1C@.microsoft.com...
> Geoff,
> On a different note, we rebuilt the SQL cluster network today. However
> when
> I run the MSI, I am seeing the below given error this time:
> Event Type: Error
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 10005
> Date: 10/16/2006
> Time: 4:06:34 PM
> User: myDomain\SQLServerAccount
> Computer: SQLServer
> Description:
> Product: Database -- Error 26201. Error -2147217900: failed to create SQL
> database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
> names listed could not be created. Check previous errors..
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Any thoughts on what this error is, and what could be causing this?
> --Mehul
> "Geoff N. Hiten" wrote:
>
|||You are right on. This is exactly the cause for the below given error log.
We ran profiler to see what commands is the MSI passing to create the DB.
Then we manually tried to run that command in Query analyzer, that throwed
reference to the disk dependency.
Thanks Tom/Geoff for your quick response.
--Mehul
"Tom Moreau" wrote:
> When you rebuilt the cluster, did you add disk resources as dependencies for
> SQL Server? If not, then SOL Server cannot see the disks.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:CCA03ACA-2B83-488C-B479-11406C9E2D1C@.microsoft.com...
> Geoff,
> On a different note, we rebuilt the SQL cluster network today. However when
> I run the MSI, I am seeing the below given error this time:
> Event Type: Error
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 10005
> Date: 10/16/2006
> Time: 4:06:34 PM
> User: myDomain\SQLServerAccount
> Computer: SQLServer
> Description:
> Product: Database -- Error 26201. Error -2147217900: failed to create SQL
> database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
> names listed could not be created. Check previous errors..
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Any thoughts on what this error is, and what could be causing this?
> --Mehul
> "Geoff N. Hiten" wrote:
>
>
Subscribe to:
Posts (Atom)