I understand from Microsoft that a SQL Server 2000 Cluster on Windows
2003 Enterprise can be run with a non-administrative service account
but I have not been able to get this to work- the SQL installation
fails with "This operation returned because the timeout period expired"
and, while sqlstp.log and sqlstpN.log files look OK, the following
appears in sqlclstr.log:
CreateClusterVirtualSQLSvrGroup2: 1381
[sqlclusterSetup.cpp:2549] : 1460 (0x5b4): This operation returned
because the timeout period expired.
Watching the cluster during the install indicates that it never brings
the SQL Cluster IP address online.
Running the installation in exactly the same way but with the SQL
Server service account in the local administrators group on both nodes
works fine.
My hunch is that this has something to do with registering IP, DNS or
SPN resources in Active Directory but I have found nothing specific in
Technet or in the news groups to back this up.
Has anybody got this to work and can offer me any advice?
Thanks.
I have seen similar error a long time ago. When you get the error, do not press OK. Open SQL Server Errorlog and see the messages in it. That may be helpful.
Also, make sure that you do not have any networking/name resolution issues.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Thanks for your comments but I eventually cracked it with the help of
this article:
http://www.sqlservercentral.com/colu...intversion.asp
I simply followed the steps in here for assigning file and registry
permissions on both nodes and removed the service account from the
local Adminstrators group when I'd finished. Works a treat.
Note that the service account needs read permissions to the whole of
the drive with the master and TempDB devices not just the folder they
are in and full control on the folders containing the data devices.
Tuesday, March 20, 2012
Requirements for non-administrative service account for clustered SQL 2000
Labels:
accountbut,
cluster,
clustered,
database,
enterprise,
microsoft,
mysql,
non-administrative,
oracle,
requirements,
run,
server,
service,
sql,
windows2003
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment