Running SQL Server on a Limited Account

[RITE1]

I am having problems getting MSDE to operate properly when the user account is switched to limited.

It startups with the computer but the little picture at the bottom stays blank until I manually enter the name of the computer in the server blank and click refresh services, then it’s fine. All the information like "SQL Server" under Services and the check box under auto-start service when OS starts repopulate to their normal settings.

For security purposes, I have to have this computer a limited account.

Is there anyway to make sql server start normally with a limited account? Thanks!

 

[RITE1]

This may be note-worthy. When Im an loged on to an administrator account, then log off, log back on to the limited user account, sql server starts fine. Strange.

 

[SQLRickster]

If I understand the scenario correctly:
The login at OS startup does not have the proper security settings, therefore the startup of SQL Server fails. Set the service to use a specified account when it starts in place of the users login. This is administered in Administrative Tools under services under SQLServerAgent. This will provide SQL Server Services the authority to start regardless of who is logged in. Also make sure that the account specified for the SQL Server Agent has a local Administrative account.

Hope this Helps,
Rick

 

[RITE1]

Tried it, no go.

SQL Server is starting when logging into a limited account, the problem is it seems to forget all its default settings. All the feilds like server, services, the check box for auto-start service when OS start are all blank. Theres no green arrow, no red square inside the little pic, just a white circle.

As soon as I enter in the name of the server, all the information is repopulated and the green arrow shows up.

Anymore thoughts??? Thanks for the try Rick

 

[RITE1]

Anymore suggestions????

 

[theoxyde]

Okay, you are referring to the Service Manager app that runs in the system tray / notification area. FYI: The service manager isn't required for the SQL Server service to run. That is governed by the MSSQLSERVER service (I'm assuming since you mention restricted accounts that you are running a NT/2k/XP/2k3 system).

What is probably happening is that the service manager isn't "seeing" the sql server instance. I imagine this is probably a unique configuration of the user the service is running under, the user you are logged in as, and the permissions assigned to each.

The Service Manager doesn't appear to use any settings to save what servers are being managed (either in its own directory, or in the registry), but appears to discover them dynamically (i.e., it can't lose its settings, because there are no settings). Even running it in a restricted user account, I can't seem to duplicate your problem, so there is probably something unique to your setup causing the issue. Like I said, only the MSSQLSERVER service must be running; the Service Mananger is just a notification app.