Node 1:
Windows 2003 Server Standar Edition SP1
SQL Server 2005 Standar Edition
Node 2:
Windows 2000 Server SP4
SQL Server 2000 Standar Edition SP3a
Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
server" too.
Both nodes use Microsoft OLE DB Provider for SQL Server.
Node 1 begins a distributed transaction vs Node 2.
Transaction KO with
"Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a]."
MS DTS is configured in Node 1 like microsoft said in
http://suppport.microsoftl.com/default.aspx?scid=kb;en-us;329332
If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
2000 SP3a, the distribution transaction run OK.
Thanks a lot.Hi
Windows 2003 has more secure defaults than Windows 2000 therefore it is
probably something that has not been configured that is causing the problem
Check out http://support.microsoft.com/kb/839279/
http://support.microsoft.com/kb/191168/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/329332
http://support.microsoft.com/kb/306212
You can use DTCPing to check it can communicate with the server
http://download.microsoft.com/download/d/0/0/d00c8f6b-135d-4441-a97b-9de16a1935c1/dtcping.exe
John
"FRF" wrote:
> Node 1:
> Windows 2003 Server Standar Edition SP1
> SQL Server 2005 Standar Edition
> Node 2:
> Windows 2000 Server SP4
> SQL Server 2000 Standar Edition SP3a
> Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
> server" too.
> Both nodes use Microsoft OLE DB Provider for SQL Server.
> Node 1 begins a distributed transaction vs Node 2.
> Transaction KO with
> "Server: Msg 7391, Level 16, State 1, Line 1
> The operation could not be performed because the OLE DB provider 'SQLOLEDB'
> was unable to begin a distributed transaction.
> OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]."
> MS DTS is configured in Node 1 like microsoft said in
> http://suppport.microsoftl.com/default.aspx?scid=kb;en-us;329332
> If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
> 2000 SP3a, the distribution transaction run OK.
> Thanks a lot.
>
Showing posts with label sp3a. Show all posts
Showing posts with label sp3a. Show all posts
Wednesday, March 21, 2012
Sunday, March 11, 2012
Error 605 - stale read
We're running SQL Server 2K sp3a on 2003 Server. Our user databases are on
an HP SAN. During heavy data warehouse ETL DTS operations we occasionally
get I/O errors such as:
DTSRun OnError: DTSStep_DTSExecuteSQLTask_2, Error = -2147467259 (80004005)
Error string: I/O error (bad page ID) detected during read at offset
0x0000020a472000 in file 'W:\SQLServer\Data\ColleagueRaw_Data.MDF'.
Running DBCC CHECKDB after a processing failure sometimes shows consistency
errors with the table associated with the I/O failure. Running DBCC again
without the REPAIR_REBUILD option will then not show any errors.
Running SQLIOStress fails with stale read errors such as:
ERROR: Stale read check failure. Page image returned does not match
previous write.
Running SQLIOStress on different boxes against the SAN results in the same
errors. Write caching is not enabled on the SAN.
Does anyone have any ideas'
Thanks much!whit wrote:
> We're running SQL Server 2K sp3a on 2003 Server. Our user databases
> are on an HP SAN. During heavy data warehouse ETL DTS operations we
> occasionally get I/O errors such as:
> DTSRun OnError: DTSStep_DTSExecuteSQLTask_2, Error = -2147467259
> (80004005) Error string: I/O error (bad page ID) detected during
> read at offset 0x0000020a472000 in file
> 'W:\SQLServer\Data\ColleagueRaw_Data.MDF'.
> Running DBCC CHECKDB after a processing failure sometimes shows
> consistency errors with the table associated with the I/O failure.
> Running DBCC again without the REPAIR_REBUILD option will then not
> show any errors.
> Running SQLIOStress fails with stale read errors such as:
> ERROR: Stale read check failure. Page image returned does not match
> previous write.
> Running SQLIOStress on different boxes against the SAN results in the
> same errors. Write caching is not enabled on the SAN.
> Does anyone have any ideas'
Looks like a MS PSS (http://support.microsoft.com) case, they should be able
to help you.
You may also want to read this:
PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
Problems
http://support.microsoft.com/defaul...kb;en-us;826433
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
an HP SAN. During heavy data warehouse ETL DTS operations we occasionally
get I/O errors such as:
DTSRun OnError: DTSStep_DTSExecuteSQLTask_2, Error = -2147467259 (80004005)
Error string: I/O error (bad page ID) detected during read at offset
0x0000020a472000 in file 'W:\SQLServer\Data\ColleagueRaw_Data.MDF'.
Running DBCC CHECKDB after a processing failure sometimes shows consistency
errors with the table associated with the I/O failure. Running DBCC again
without the REPAIR_REBUILD option will then not show any errors.
Running SQLIOStress fails with stale read errors such as:
ERROR: Stale read check failure. Page image returned does not match
previous write.
Running SQLIOStress on different boxes against the SAN results in the same
errors. Write caching is not enabled on the SAN.
Does anyone have any ideas'
Thanks much!whit wrote:
> We're running SQL Server 2K sp3a on 2003 Server. Our user databases
> are on an HP SAN. During heavy data warehouse ETL DTS operations we
> occasionally get I/O errors such as:
> DTSRun OnError: DTSStep_DTSExecuteSQLTask_2, Error = -2147467259
> (80004005) Error string: I/O error (bad page ID) detected during
> read at offset 0x0000020a472000 in file
> 'W:\SQLServer\Data\ColleagueRaw_Data.MDF'.
> Running DBCC CHECKDB after a processing failure sometimes shows
> consistency errors with the table associated with the I/O failure.
> Running DBCC again without the REPAIR_REBUILD option will then not
> show any errors.
> Running SQLIOStress fails with stale read errors such as:
> ERROR: Stale read check failure. Page image returned does not match
> previous write.
> Running SQLIOStress on different boxes against the SAN results in the
> same errors. Write caching is not enabled on the SAN.
> Does anyone have any ideas'
Looks like a MS PSS (http://support.microsoft.com) case, they should be able
to help you.
You may also want to read this:
PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
Problems
http://support.microsoft.com/defaul...kb;en-us;826433
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Error 5172
Hello,
I hava an sql server 2000 sp3a on a win2k sp4 machine running all ok. I tried to build a raid 1 using the hdd where sqlserver was and a new one, but i failed to build it and consecuently i lost all data bases.
Using some programs, i recover the mdf, ldf and ndf files from my old sql server 2000.
I reinstalled all the system exactly the same, win2k sp4 and sql server 2000 with sp3a ( i know sp4 is out ), installed all the apps and overwrites mdf,nfs and ldf files with the old data, and when i tried to put databse online i get this error:
error 5172: header not valid on file "C:\dbtest.mdf". Pageaudit property is not valid.
Any one can help me?http://www.dbforums.com/t749523.html
http://www.lazydba.com/sql/1__728.html
There's lots of stuff out there...just google it...|||well, i've tried this before post with no result. i just ask here becouse i'm very lost.|||I tried command:
exec sp_attach_db @.dbname ... with so meny variation and i get the same error. Can anyone help me?
Thanks.
I hava an sql server 2000 sp3a on a win2k sp4 machine running all ok. I tried to build a raid 1 using the hdd where sqlserver was and a new one, but i failed to build it and consecuently i lost all data bases.
Using some programs, i recover the mdf, ldf and ndf files from my old sql server 2000.
I reinstalled all the system exactly the same, win2k sp4 and sql server 2000 with sp3a ( i know sp4 is out ), installed all the apps and overwrites mdf,nfs and ldf files with the old data, and when i tried to put databse online i get this error:
error 5172: header not valid on file "C:\dbtest.mdf". Pageaudit property is not valid.
Any one can help me?http://www.dbforums.com/t749523.html
http://www.lazydba.com/sql/1__728.html
There's lots of stuff out there...just google it...|||well, i've tried this before post with no result. i just ask here becouse i'm very lost.|||I tried command:
exec sp_attach_db @.dbname ... with so meny variation and i get the same error. Can anyone help me?
Thanks.
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...
>
Wednesday, March 7, 2012
Error 3624 again!
SQL 2000 SP3a running on W2K Server SP4. Access 97 front end. Back end was
ported from Access. I get the following two errors several times a day.
Searched in the KB and the only article (827714) that comes close doesn't
seem to address my problem. Unless the hotfix it mentions is the answer...
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Has anyone else seen these problems? It is always a query - I've never seen
it on a statement.Hi Ron,
I am not sure what Service Pack level you are on or if you are running into
the same situation as mentioned in the symptom section of article 827714.
Normally you would see this type of assertion when you have corruption in a
database. As a starting point I would like you to run DBCC CHECKDB on your
database. Make sure that you have no corruption in the database by making
sure that DBCC CHECKB shows "0" allocation and "0" consistency errors.
If you do find corruption in the database, restore it from a good backup.
Hope that helps !!!
Thanks,
Fargham Butt
Microsoft - SQL Server
ported from Access. I get the following two errors several times a day.
Searched in the KB and the only article (827714) that comes close doesn't
seem to address my problem. Unless the hotfix it mentions is the answer...
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Has anyone else seen these problems? It is always a query - I've never seen
it on a statement.Hi Ron,
I am not sure what Service Pack level you are on or if you are running into
the same situation as mentioned in the symptom section of article 827714.
Normally you would see this type of assertion when you have corruption in a
database. As a starting point I would like you to run DBCC CHECKDB on your
database. Make sure that you have no corruption in the database by making
sure that DBCC CHECKB shows "0" allocation and "0" consistency errors.
If you do find corruption in the database, restore it from a good backup.
Hope that helps !!!
Thanks,
Fargham Butt
Microsoft - SQL Server
Error 3624 again!
SQL 2000 SP3a running on W2K Server SP4. Access 97 front end. Back end was
ported from Access. I get the following two errors several times a day.
Searched in the KB and the only article (827714) that comes close doesn't
seem to address my problem. Unless the hotfix it mentions is the answer...
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Has anyone else seen these problems? It is always a query - I've never seen
it on a statement.
Hi Ron,
I am not sure what Service Pack level you are on or if you are running into
the same situation as mentioned in the symptom section of article 827714.
Normally you would see this type of assertion when you have corruption in a
database. As a starting point I would like you to run DBCC CHECKDB on your
database. Make sure that you have no corruption in the database by making
sure that DBCC CHECKB shows "0" allocation and "0" consistency errors.
If you do find corruption in the database, restore it from a good backup.
Hope that helps !!!
Thanks,
Fargham Butt
Microsoft - SQL Server
ported from Access. I get the following two errors several times a day.
Searched in the KB and the only article (827714) that comes close doesn't
seem to address my problem. Unless the hotfix it mentions is the answer...
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Has anyone else seen these problems? It is always a query - I've never seen
it on a statement.
Hi Ron,
I am not sure what Service Pack level you are on or if you are running into
the same situation as mentioned in the symptom section of article 827714.
Normally you would see this type of assertion when you have corruption in a
database. As a starting point I would like you to run DBCC CHECKDB on your
database. Make sure that you have no corruption in the database by making
sure that DBCC CHECKB shows "0" allocation and "0" consistency errors.
If you do find corruption in the database, restore it from a good backup.
Hope that helps !!!
Thanks,
Fargham Butt
Microsoft - SQL Server
Error 3624 again!
SQL 2000 SP3a running on W2K Server SP4. Access 97 front end. Back end was
ported from Access. I get the following two errors several times a day.
Searched in the KB and the only article (827714) that comes close doesn't
seem to address my problem. Unless the hotfix it mentions is the answer...
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
SQL Server Assertion: File: < p:\sql\ntdbms\storeng\drs\include\record
.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Has anyone else seen these problems? It is always a query - I've never seen
it on a statement.Hi Ron,
I am not sure what Service Pack level you are on or if you are running into
the same situation as mentioned in the symptom section of article 827714.
Normally you would see this type of assertion when you have corruption in a
database. As a starting point I would like you to run DBCC CHECKDB on your
database. Make sure that you have no corruption in the database by making
sure that DBCC CHECKB shows "0" allocation and "0" consistency errors.
If you do find corruption in the database, restore it from a good backup.
Hope that helps !!!
Thanks,
Fargham Butt
Microsoft - SQL Server
ported from Access. I get the following two errors several times a day.
Searched in the KB and the only article (827714) that comes close doesn't
seem to address my problem. Unless the hotfix it mentions is the answer...
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
SQL Server Assertion: File: < p:\sql\ntdbms\storeng\drs\include\record
.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Has anyone else seen these problems? It is always a query - I've never seen
it on a statement.Hi Ron,
I am not sure what Service Pack level you are on or if you are running into
the same situation as mentioned in the symptom section of article 827714.
Normally you would see this type of assertion when you have corruption in a
database. As a starting point I would like you to run DBCC CHECKDB on your
database. Make sure that you have no corruption in the database by making
sure that DBCC CHECKB shows "0" allocation and "0" consistency errors.
If you do find corruption in the database, restore it from a good backup.
Hope that helps !!!
Thanks,
Fargham Butt
Microsoft - SQL Server
Friday, February 24, 2012
Error 2812: Could not find stored procedure and
Help! When we try to to delete a test publication on our sql server
2000 Developer Edition SP3a it returns an Error 2812: "Could not find
stored procedure"
What's weird is that we configured "Publishing, Subscribers and
Distribution" last night and after some tries we got thru the wixard
and we were able to set up a push subscription to a test database.
Now when we try to set up a new publication SQL server returns a "
server is not enabled as a Publisher on distibutor server" To enable
run "Publishing, Subscribers and Distribution and clich the Publishers
tab". When we do that we can only create a Distributor. Continuing on
that we get a new error: "21045 Cannot uninstall the Distributor
because there are databases enabled for publishing or merge
publishing". There is no way as far as we can see to disconnect any
enabled databases.
We feel like we're walking in circles. Help is greatly appreciated.
Martin,
try running these commands on each database then hopefully you'll be able to
uninstall the distributor and restart.
HTH,
Paul Ibison
exec sp_dboption 'yourdb','published',false
exec sp_dboption 'yourdb','merge publish',false
|||Thanks Paul, I was just about to write that I solved the problem by
uninstalling SQL and reinstalling. It looks like THAT did the trick.
No problems so far.
On Tue, 24 Aug 2004 19:39:33 +0100, "Paul Ibison"
<Paul.Ibison@.Pygmalion.Com> wrote:
>Martin,
>try running these commands on each database then hopefully you'll be able to
>uninstall the distributor and restart.
>HTH,
>Paul Ibison
>exec sp_dboption 'yourdb','published',false
>exec sp_dboption 'yourdb','merge publish',false
>
2000 Developer Edition SP3a it returns an Error 2812: "Could not find
stored procedure"
What's weird is that we configured "Publishing, Subscribers and
Distribution" last night and after some tries we got thru the wixard
and we were able to set up a push subscription to a test database.
Now when we try to set up a new publication SQL server returns a "
server is not enabled as a Publisher on distibutor server" To enable
run "Publishing, Subscribers and Distribution and clich the Publishers
tab". When we do that we can only create a Distributor. Continuing on
that we get a new error: "21045 Cannot uninstall the Distributor
because there are databases enabled for publishing or merge
publishing". There is no way as far as we can see to disconnect any
enabled databases.
We feel like we're walking in circles. Help is greatly appreciated.
Martin,
try running these commands on each database then hopefully you'll be able to
uninstall the distributor and restart.
HTH,
Paul Ibison
exec sp_dboption 'yourdb','published',false
exec sp_dboption 'yourdb','merge publish',false
|||Thanks Paul, I was just about to write that I solved the problem by
uninstalling SQL and reinstalling. It looks like THAT did the trick.
No problems so far.
On Tue, 24 Aug 2004 19:39:33 +0100, "Paul Ibison"
<Paul.Ibison@.Pygmalion.Com> wrote:
>Martin,
>try running these commands on each database then hopefully you'll be able to
>uninstall the distributor and restart.
>HTH,
>Paul Ibison
>exec sp_dboption 'yourdb','published',false
>exec sp_dboption 'yourdb','merge publish',false
>
Friday, February 17, 2012
error 21770 on SQL2k upgrade
We just upgraded our SQL 7 to SQL 2000 SP3a and we have the following
happening
1. running about 10000-50000 queries through ODBC blows the machine up
completely. Have to power off and on to get it back. This same code
ran fine on SQL 7 before the upgrade. It doesn't blow up at the same
number of queries or on the same data and varies widely on when it
blows up in this process.
2. when we go to properties on any of the databases we get an error
21770.
Specifically,
Error 21770 [SQL-DMO] The name 'null' was not found in the
specified collection.
Then when you hit OK on the subsequent properties screen, we get an
error 21266.
We have seen error 15457 in the logs at times as well.
DBCC checkdb on each database returns no errors. I am sure the 2
issues are related but I can find no solution to the problem(s)
anywhere.
Any help or ideas appreciated.Hi,
Prob 1:
the only prob i could think of is logging and the servers 'trunc. log. on
chkpt.' might be off or your recovery model is full and logs are not cleaned
up regularly.
cause generally people miss out the option as it appears in database
properties in sql 7 but in 2000 we have to explicitly set it to true by
sp_dboption
Prob 2:
have u checked for the object names im sure none has the name 'null'
is the database configured for replication cause the error 21266 is caused
in replication when it cannot publish the tables.
about 15457 error appears due to any configuration changes made in - Run the
RECONFIGURE
Regards,
MD
--
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
--
"Russ Cobbe" <russc@.inline.net> wrote in message
news:80e8c028.0402111950.4e4eebf9@.posting.google.com...
> We just upgraded our SQL 7 to SQL 2000 SP3a and we have the following
> happening
> 1. running about 10000-50000 queries through ODBC blows the machine up
> completely. Have to power off and on to get it back. This same code
> ran fine on SQL 7 before the upgrade. It doesn't blow up at the same
> number of queries or on the same data and varies widely on when it
> blows up in this process.
> 2. when we go to properties on any of the databases we get an error
> 21770.
> Specifically,
> Error 21770 [SQL-DMO] The name 'null' was not found in the
> specified collection.
> Then when you hit OK on the subsequent properties screen, we get an
> error 21266.
> We have seen error 15457 in the logs at times as well.
> DBCC checkdb on each database returns no errors. I am sure the 2
> issues are related but I can find no solution to the problem(s)
> anywhere.
> Any help or ideas appreciated.
happening
1. running about 10000-50000 queries through ODBC blows the machine up
completely. Have to power off and on to get it back. This same code
ran fine on SQL 7 before the upgrade. It doesn't blow up at the same
number of queries or on the same data and varies widely on when it
blows up in this process.
2. when we go to properties on any of the databases we get an error
21770.
Specifically,
Error 21770 [SQL-DMO] The name 'null' was not found in the
specified collection.
Then when you hit OK on the subsequent properties screen, we get an
error 21266.
We have seen error 15457 in the logs at times as well.
DBCC checkdb on each database returns no errors. I am sure the 2
issues are related but I can find no solution to the problem(s)
anywhere.
Any help or ideas appreciated.Hi,
Prob 1:
the only prob i could think of is logging and the servers 'trunc. log. on
chkpt.' might be off or your recovery model is full and logs are not cleaned
up regularly.
cause generally people miss out the option as it appears in database
properties in sql 7 but in 2000 we have to explicitly set it to true by
sp_dboption
Prob 2:
have u checked for the object names im sure none has the name 'null'
is the database configured for replication cause the error 21266 is caused
in replication when it cannot publish the tables.
about 15457 error appears due to any configuration changes made in - Run the
RECONFIGURE
Regards,
MD
--
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
--
"Russ Cobbe" <russc@.inline.net> wrote in message
news:80e8c028.0402111950.4e4eebf9@.posting.google.com...
> We just upgraded our SQL 7 to SQL 2000 SP3a and we have the following
> happening
> 1. running about 10000-50000 queries through ODBC blows the machine up
> completely. Have to power off and on to get it back. This same code
> ran fine on SQL 7 before the upgrade. It doesn't blow up at the same
> number of queries or on the same data and varies widely on when it
> blows up in this process.
> 2. when we go to properties on any of the databases we get an error
> 21770.
> Specifically,
> Error 21770 [SQL-DMO] The name 'null' was not found in the
> specified collection.
> Then when you hit OK on the subsequent properties screen, we get an
> error 21266.
> We have seen error 15457 in the logs at times as well.
> DBCC checkdb on each database returns no errors. I am sure the 2
> issues are related but I can find no solution to the problem(s)
> anywhere.
> Any help or ideas appreciated.
error 21770 on SQL2k upgrade
We just upgraded our SQL 7 to SQL 2000 SP3a and we have the following
happening
1. running about 10000-50000 queries through ODBC blows the machine up
completely. Have to power off and on to get it back. This same code
ran fine on SQL 7 before the upgrade. It doesn't blow up at the same
number of queries or on the same data and varies widely on when it
blows up in this process.
2. when we go to properties on any of the databases we get an error
21770.
Specifically,
Error 21770 [SQL-DMO] The name 'null' was not found in the
specified collection.
Then when you hit OK on the subsequent properties screen, we get an
error 21266.
We have seen error 15457 in the logs at times as well.
DBCC checkdb on each database returns no errors. I am sure the 2
issues are related but I can find no solution to the problem(s)
anywhere.
Any help or ideas appreciated.Hi,
Prob 1:
the only prob i could think of is logging and the servers 'trunc. log. on
chkpt.' might be off or your recovery model is full and logs are not cleaned
up regularly.
cause generally people miss out the option as it appears in database
properties in sql 7 but in 2000 we have to explicitly set it to true by
sp_dboption
Prob 2:
have u checked for the object names im sure none has the name 'null'
is the database configured for replication cause the error 21266 is caused
in replication when it cannot publish the tables.
about 15457 error appears due to any configuration changes made in - Run the
RECONFIGURE
Regards,
MD
--
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
--
"Russ Cobbe" <russc@.inline.net> wrote in message
news:80e8c028.0402111950.4e4eebf9@.posting.google.com...
> We just upgraded our SQL 7 to SQL 2000 SP3a and we have the following
> happening
> 1. running about 10000-50000 queries through ODBC blows the machine up
> completely. Have to power off and on to get it back. This same code
> ran fine on SQL 7 before the upgrade. It doesn't blow up at the same
> number of queries or on the same data and varies widely on when it
> blows up in this process.
> 2. when we go to properties on any of the databases we get an error
> 21770.
> Specifically,
> Error 21770 [SQL-DMO] The name 'null' was not found in the
> specified collection.
> Then when you hit OK on the subsequent properties screen, we get an
> error 21266.
> We have seen error 15457 in the logs at times as well.
> DBCC checkdb on each database returns no errors. I am sure the 2
> issues are related but I can find no solution to the problem(s)
> anywhere.
> Any help or ideas appreciated.
happening
1. running about 10000-50000 queries through ODBC blows the machine up
completely. Have to power off and on to get it back. This same code
ran fine on SQL 7 before the upgrade. It doesn't blow up at the same
number of queries or on the same data and varies widely on when it
blows up in this process.
2. when we go to properties on any of the databases we get an error
21770.
Specifically,
Error 21770 [SQL-DMO] The name 'null' was not found in the
specified collection.
Then when you hit OK on the subsequent properties screen, we get an
error 21266.
We have seen error 15457 in the logs at times as well.
DBCC checkdb on each database returns no errors. I am sure the 2
issues are related but I can find no solution to the problem(s)
anywhere.
Any help or ideas appreciated.Hi,
Prob 1:
the only prob i could think of is logging and the servers 'trunc. log. on
chkpt.' might be off or your recovery model is full and logs are not cleaned
up regularly.
cause generally people miss out the option as it appears in database
properties in sql 7 but in 2000 we have to explicitly set it to true by
sp_dboption
Prob 2:
have u checked for the object names im sure none has the name 'null'
is the database configured for replication cause the error 21266 is caused
in replication when it cannot publish the tables.
about 15457 error appears due to any configuration changes made in - Run the
RECONFIGURE
Regards,
MD
--
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
--
"Russ Cobbe" <russc@.inline.net> wrote in message
news:80e8c028.0402111950.4e4eebf9@.posting.google.com...
> We just upgraded our SQL 7 to SQL 2000 SP3a and we have the following
> happening
> 1. running about 10000-50000 queries through ODBC blows the machine up
> completely. Have to power off and on to get it back. This same code
> ran fine on SQL 7 before the upgrade. It doesn't blow up at the same
> number of queries or on the same data and varies widely on when it
> blows up in this process.
> 2. when we go to properties on any of the databases we get an error
> 21770.
> Specifically,
> Error 21770 [SQL-DMO] The name 'null' was not found in the
> specified collection.
> Then when you hit OK on the subsequent properties screen, we get an
> error 21266.
> We have seen error 15457 in the logs at times as well.
> DBCC checkdb on each database returns no errors. I am sure the 2
> issues are related but I can find no solution to the problem(s)
> anywhere.
> Any help or ideas appreciated.
Wednesday, February 15, 2012
Error 21002 : User already exists
Running SQL Server 2000 Enterprise SP3a ( Windows Server 2003 )
I restored several databases from one instance ( on another box ) to another
. Now I am trying to add the users
to the second box ( to duplicate those on the first ) where I restored the d
ata and I am getting this error when
trying to add the database permissions for the user.
I tried working with sp_change_users, but the report shows nothing ( no rows
returned ) .
I tried deleting user using sp_droplogin, it dropped the user, but same thin
g happened again
once I readded him. I also tried the sp_change_users_login ( autofix) to no
avail ( nothing happened )
Any help would be appreciated.
ThanksRun select * from sysusers in the database that you are trying to add the
user. If the user does exist then run the sp_granddbaccess procedure to
grant access to the user. You may then need to run sp_change_users_login
again after verifying that the login exists for this user.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||That response should hav been sp_grantdbaccess.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I restored several databases from one instance ( on another box ) to another
. Now I am trying to add the users
to the second box ( to duplicate those on the first ) where I restored the d
ata and I am getting this error when
trying to add the database permissions for the user.
I tried working with sp_change_users, but the report shows nothing ( no rows
returned ) .
I tried deleting user using sp_droplogin, it dropped the user, but same thin
g happened again
once I readded him. I also tried the sp_change_users_login ( autofix) to no
avail ( nothing happened )
Any help would be appreciated.
ThanksRun select * from sysusers in the database that you are trying to add the
user. If the user does exist then run the sp_granddbaccess procedure to
grant access to the user. You may then need to run sp_change_users_login
again after verifying that the login exists for this user.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||That response should hav been sp_grantdbaccess.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Error 1934 during index rebuild
Hi,
I have SQL Server 200 SP3a running on Windows Server
2003. During the optimization setp of my maintenance
plan, I see the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
failed because the following SET options have incorrect
settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
I saw an article in KB about creating indices on views,
which had a similar error message. The problem that I
have does not create indices on views, though. The table
being re-indexed is very simple, not many records
(thousand or so), and has only one index, which is a
clustered index on two integer values and a date. The
cluster is set to a 90% fill factor.
Other tables are re-indexed just fine in the DB, just
this one seems to be failing. The table does have null
fields, but they are not included in the index. There is
no primary key defined on the table.
Any help is greatly appreciated.
-- Jake
jwa@.beyond-ordinary.com> I have SQL Server 200 SP3a running on Windows Server
> 2003. During the optimization setp of my maintenance
> plan, I see the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
> [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
> failed because the following SET options have incorrect
> settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
Is that index set on a computed column? See if it helps:
PRB: SET OPTION Considerations When Running DBCC with Indexes On Computed
Columns
http://support.microsoft.com/default.aspx?scid=KB;en-us;q301292
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
I have SQL Server 200 SP3a running on Windows Server
2003. During the optimization setp of my maintenance
plan, I see the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
failed because the following SET options have incorrect
settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
I saw an article in KB about creating indices on views,
which had a similar error message. The problem that I
have does not create indices on views, though. The table
being re-indexed is very simple, not many records
(thousand or so), and has only one index, which is a
clustered index on two integer values and a date. The
cluster is set to a 90% fill factor.
Other tables are re-indexed just fine in the DB, just
this one seems to be failing. The table does have null
fields, but they are not included in the index. There is
no primary key defined on the table.
Any help is greatly appreciated.
-- Jake
jwa@.beyond-ordinary.com> I have SQL Server 200 SP3a running on Windows Server
> 2003. During the optimization setp of my maintenance
> plan, I see the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
> [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
> failed because the following SET options have incorrect
> settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
Is that index set on a computed column? See if it helps:
PRB: SET OPTION Considerations When Running DBCC with Indexes On Computed
Columns
http://support.microsoft.com/default.aspx?scid=KB;en-us;q301292
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Error 1934 during index rebuild
Hi,
I have SQL Server 200 SP3a running on Windows Server
2003. During the optimization setp of my maintenance
plan, I see the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
failed because the following SET options have incorrect
settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
I saw an article in KB about creating indices on views,
which had a similar error message. The problem that I
have does not create indices on views, though. The table
being re-indexed is very simple, not many records
(thousand or so), and has only one index, which is a
clustered index on two integer values and a date. The
cluster is set to a 90% fill factor.
Other tables are re-indexed just fine in the DB, just
this one seems to be failing. The table does have null
fields, but they are not included in the index. There is
no primary key defined on the table.
Any help is greatly appreciated.
-- Jake
jwa@.beyond-ordinary.com> I have SQL Server 200 SP3a running on Windows Server
> 2003. During the optimization setp of my maintenance
> plan, I see the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
> [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
> failed because the following SET options have incorrect
> settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
Is that index set on a computed column? See if it helps:
PRB: SET OPTION Considerations When Running DBCC with Indexes On Computed
Columns
http://support.microsoft.com/defaul...B;en-us;q301292
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks for your reply! That makes sense, but I can not seem to get the
ARITHABORT flag set during the maintenance plan. I tried setting it in
the job's command script, but that didn't seem to have an affect.
The table doesn't have an index on the computed columns, but it does
have an index on a column that is used in a more than one computed
column in the table. Would have an affect'
Thanks again!
=======================================
Jacob W Anderson
Beyond Ordinary Software Solutions
http://www.beyond-ordinary.com
jwa@.beyond-ordinary.com
=======================================
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||You can't use the maintenance plan for this, you must create your own
scheduled job to do it. That way you can set the settings however you wish.
This is a know problem with the MP.
Andrew J. Kelly
SQL Server MVP
"Jacob Anderson" <jwa@.beyond-ordinary.com> wrote in message
news:%23qhZxUz8DHA.1636@.TK2MSFTNGP12.phx.gbl...
> Thanks for your reply! That makes sense, but I can not seem to get the
> ARITHABORT flag set during the maintenance plan. I tried setting it in
> the job's command script, but that didn't seem to have an affect.
> The table doesn't have an index on the computed columns, but it does
> have an index on a column that is used in a more than one computed
> column in the table. Would have an affect'
> Thanks again!
> =======================================
> Jacob W Anderson
> Beyond Ordinary Software Solutions
> http://www.beyond-ordinary.com
> jwa@.beyond-ordinary.com
> =======================================
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!
I have SQL Server 200 SP3a running on Windows Server
2003. During the optimization setp of my maintenance
plan, I see the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
failed because the following SET options have incorrect
settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
I saw an article in KB about creating indices on views,
which had a similar error message. The problem that I
have does not create indices on views, though. The table
being re-indexed is very simple, not many records
(thousand or so), and has only one index, which is a
clustered index on two integer values and a date. The
cluster is set to a 90% fill factor.
Other tables are re-indexed just fine in the DB, just
this one seems to be failing. The table does have null
fields, but they are not included in the index. There is
no primary key defined on the table.
Any help is greatly appreciated.
-- Jake
jwa@.beyond-ordinary.com> I have SQL Server 200 SP3a running on Windows Server
> 2003. During the optimization setp of my maintenance
> plan, I see the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
> [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
> failed because the following SET options have incorrect
> settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
Is that index set on a computed column? See if it helps:
PRB: SET OPTION Considerations When Running DBCC with Indexes On Computed
Columns
http://support.microsoft.com/defaul...B;en-us;q301292
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks for your reply! That makes sense, but I can not seem to get the
ARITHABORT flag set during the maintenance plan. I tried setting it in
the job's command script, but that didn't seem to have an affect.
The table doesn't have an index on the computed columns, but it does
have an index on a column that is used in a more than one computed
column in the table. Would have an affect'
Thanks again!
=======================================
Jacob W Anderson
Beyond Ordinary Software Solutions
http://www.beyond-ordinary.com
jwa@.beyond-ordinary.com
=======================================
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||You can't use the maintenance plan for this, you must create your own
scheduled job to do it. That way you can set the settings however you wish.
This is a know problem with the MP.
Andrew J. Kelly
SQL Server MVP
"Jacob Anderson" <jwa@.beyond-ordinary.com> wrote in message
news:%23qhZxUz8DHA.1636@.TK2MSFTNGP12.phx.gbl...
> Thanks for your reply! That makes sense, but I can not seem to get the
> ARITHABORT flag set during the maintenance plan. I tried setting it in
> the job's command script, but that didn't seem to have an affect.
> The table doesn't have an index on the computed columns, but it does
> have an index on a column that is used in a more than one computed
> column in the table. Would have an affect'
> Thanks again!
> =======================================
> Jacob W Anderson
> Beyond Ordinary Software Solutions
> http://www.beyond-ordinary.com
> jwa@.beyond-ordinary.com
> =======================================
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!
Labels:
database,
error,
errormicrosoft,
following,
index,
maintenanceplan,
microsoft,
mysql,
optimization,
oracle,
rebuild,
running,
server,
server2003,
setp,
sp3a,
sql,
windows
Subscribe to:
Posts (Atom)