Re: SQL2005 non-administrator Service Account

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.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"SQLDudette" <SQLDudette@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B329BD41-8E93-4C83-A9DC-A1CD6424FAED@xxxxxxxxxxxxxxxx
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?

"Rick Byham, (MSFT)" wrote:

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
message has the results of queries, so it must have started.
Your second message says the queries return bob as the name of the server.
Since you say "we renamed BOBnew to BOB" you sound like you don't have a
problem.
Do you only have a problem with the name in Registered Servers? Drop the
server registration and re-register it.
I probably don't understand something. If you still have a problem, please
clarify.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"SQLDudette" <SQLDudette@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:49784645-A3F4-4FA7-B898-7A2433B0A155@xxxxxxxxxxxxxxxx
> Also, i have run both of these and they both give the results "bob"
> SELECT @@SERVERNAME
> SELECT SERVERPROPERTY('MachineName'), SERVERPROPERTY ('InstanceName')
>
> When I right click on the server in Managment Studio, and hit register, > it
> also has bob as the server name.
>
> Any assistance would be appreciated!!
>
> "SQLDudette" wrote:
>
>> On server BOB, the SQL Services are running under an ID that by >> default
>> was
>> added to the SQL server groups
>> SQLServer2005MSFTEUser$-ServerName-$MSSQLSERVER etc. However, the ID >> is
>> also
>> under the administrators group and I would like to remove it from >> there.
>> I
>> used a test 2005 box to test this, however, when I removed the id from
>> the
>> administrators, the SQL Server Service would not start up. We did
>> however
>> change the name of this box as it was a replacement for an existing
>> server,
>> the initial name was BOBnew because it was replacing a server named >> BOB,
>> then
>> when we shut down BOB, we renamed BOBnew to BOB. In the SQL server >> group,
>> the
>> –ServerName- is still BOBnew – it didn’t change when we changed the >> name
>> of
>> the box.
>>
>> Could this have something to do with the SQL service not starting up?
>>
>> Thanks,
>> Karime
>>


.

Relevant Pages

  • Re: Error 15401 using sp_grantlogin (not addressed by current KB articles)
    ... Restarting Windows 2000 resolved the problem for this particular account, ... confused when it sees a duplicate SID. ... > One way to get SQL Server to agree with the renamed NT ... > Preview (to ensure the script was created), ...
    (microsoft.public.sqlserver.security)
  • Re: SharePoint V3 Install Error
    ... But it our case it had to do with Group Policies that forbid the account of ... WSS FAQ:www.wssv3faq.com/wss.collutions.com ... Event Source: WindowsSharePointServices3Search ... whatever you are installing WSS as sufficient rights to the SQL Server ...
    (microsoft.public.sharepoint.windowsservices)
  • Deleting BUILTINAdministrators
    ... when the EM tries to write it to the registry, ... Make sure that the sql server account ... >the SQL Server Agent wouldn't restart. ...
    (microsoft.public.sqlserver.security)
  • RE: Problems with WebParts
    ... to a database called aspnetdb. ... > The connection string specifies a local SQL Server Express instance using a ... > server account must have read and write access to the applications directory. ... > This is necessary because the web server account will automatically create ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Cannot connect to Query Analyzer
    ... For Query Analyzer, I tried replacing the file as you suggested but had the ... same results (Enterprise Manager starts up fine, ... I created an account on my laptop and changed SQL ... Try replacing the MMC app for SQL Server from the original ...
    (microsoft.public.sqlserver.connect)