Re: Error 42d during Fail Over SQL 2000 Enterprise in a Server 2003 Ent. Cluster
- From: "Anthony Thomas" <ALThomas@xxxxxxxxx>
- Date: Tue, 19 Jun 2007 15:57:25 -0500
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@xxxxxxxxx> wrote in message
news:utHVUXImHHA.4752@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxx> wrote in message
news:1179350437.951320.310920@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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
.
- Prev by Date: Re: Unable to use DTC when on another node
- Next by Date: Re: SQL Server pulls incorrect instance data from the registry?
- Previous by thread: Re: Unable to use DTC when on another node
- Next by thread: Re: SQL Server pulls incorrect instance data from the registry?
- Index(es):
Relevant Pages
|