We have 2- node Windows Enterprise 2003 x64 servers clustered in
active/active configuration with SQL 2005 x64 installed on it. Both servers
are domain controllers.
Now we try to add another node to the cluster. This third server is not
domain controller. We added new node to cluster and this work fine. Cluster
disk and other resource (IP address, network name) can be transformed to
third server. Then we changed SQL instance configuration and added third
server to possible owners of instance. Installations pass OK.
Problem is that we cannot move SQL instance to third server when user that
starts SQL and Agent services is normal user. When user is part of
administrators everything starts normally.
All HF and SP are installed.
User have privilege granted with GP – Log on as a services.
Logged error is:
Event ID: 17053
UpdateUptimeRegKey: Operating system error 5 (error not found) encountered.
Event ID: 17113
Error 3(error not found) occurred while opening file 'U:\Microsoft SQL
Server\MSSQL.5\MSSQL\DATA\master.mdf' to obtain configuration information at
startup. An invalid startup option might have caused the error. Verify your
startup options, and correct or remove them if necessary.
Event ID: 17053
UpdateUptimeRegKey: Operating system error 5(error not found) encountered.
Event ID: 17049
Unable to cycle error log file from 'U:\Microsoft SQL
Server\MSSQL.5\MSSQL\LOG\ERRORLOG.5' to 'U:\Microsoft SQL
Server\MSSQL.5\MSSQL\LOG\ERRORLOG.6' due to OS error '5(error not found)'. A
process outside of SQL Server may be preventing SQL Server from reading the
files. As a result, errorlog entries may be lost and it may not be possible
to view some SQL Server errorlogs. Make sure no other processes have locked
the file with write-only access.
Event ID: 19019
[sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status 435),

Best guess is that the file system permissions on the DCs do not allow SQL
access to the data files when the disk is moved to a non-DC host. SQL
cannot access the file and therefore does not start. SQL Agent requires
that SQL Server be started first in order to set up a shared memory buffer
so it is not starting either.

One more reason why Domain Controllers are not supported SQL server
clustered hosts. You either get a non-functioning system or have to
implement worst practices security on your data host AND your domain
controllers.


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP



"Dovla" <Dovla (AT) discussions (DOT) microsoft.com> wrote

We found the solution for this problem. We were trying with setting the
permissions from
http://msdn.microsoft.com/en-us/libr...4(SQL.90).aspx and this was
not helpfull. Then we checked and found that domain level was Windows 2000.
When we updated domain level to Windows 2003 everything started to work.

"Dovla" wrote: