
Signature
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.
The results of the "select @@servername" query are when sql server services
are running under an administrator account. However, when I remove that
account from the administrators group, that's when the service won't start
up.
The problem is that the default sql server groups (under Manage > Local
Users and Groups ) still are called BobNEW (for example -
SQLSERVER2005MSFTEUser$BobNew) and I'm wondering if this could be why the
services won't start when the ID they are running under is removed from
administrators.
Is that a bit more clear?
> You may have this figured out by now, but some observations:
> Your first message says the SQL Server Service won't start, but the second
[quoted text clipped - 40 lines]
> >> Thanks,
> >> Karime
Rick Byham, (MSFT) - 06 May 2008 22:52 GMT
I suspect the problem is that the account that SQL Server is changed to run
under does not have access rights to the registry and file system.
Try using SQL Server Configuration Manager (SSCM) to change the account that
SQL Server is running under. SSCM is supposed to be smart enough to add the
necessary permissions for the new account.
If that works (meaning if SQL Server starts properly), then move the
original account out of the Administrators group, and then use SSCM to
change the account back to the first one.
(Always use SSCM to change the account used by SQL Server. Don't use the
Services MMC console, because it doesn't configure access to the SQL Server
registry settings and file locations.)
I hope this helps.

Signature
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.
> The results of the "select @@servername" query are when sql server
> services
[quoted text clipped - 64 lines]
>> >> Thanks,
>> >> Karime
Walter Horowitz - 30 Jul 2008 20:48 GMT
I run an SQL Server 2005 with a service account that is not a member of the
Administrators group.
It stopped working recently.
I audited file access failures for everyone in the documents and settings
and Program Files\Micorosft SQL Server directories and found that there were
indeed failures.
There are files that the service account needs to access in the CRYPTO area
and in the SQL area that were no longer accessable to that service account.
Once I found them and gave the account permissions, my server started to
work again
Perhaps this could be your problem?
Walter Horowitz
Mardovar Networking LLC
> The results of the "select @@servername" query are when sql server
> services
[quoted text clipped - 64 lines]
>> >> Thanks,
>> >> Karime