Link to home
Start Free TrialLog in
Avatar of John Porter
John PorterFlag for United States of America

asked on

SQL Server 2005 service will not Start on Windows 7 computer

Hello Experts,

I have an issue with the SQL Server 2005 service not starting on a Windows 7 computer.

When trying to start the service, it times out with a code 3417. A message then comes up saying that Administrative privileges are needed to start the Service. The current user is an Administrator. (This computer is in a remote location on a computer that I did not configure) I believe the user logged on has Administrator rights.

In Event Windows logs/System, there is not much info.

The description for Event ID from source Service Manager cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
SQL Server (MyInstance)
%%3417
The locale specific resource for the desired message is not present


The service is set to start using "Local System" so it should start regardless of the user right?

Can anyone see what is going on here?

Thanks!
Avatar of Qlemo
Qlemo
Flag of Germany image

The usual culprits are missing privileges in the folder the (system) DBs are stored, or the DB files being compressed.
Since the default account is Network Services, you should try if changing the service to use that user will work.
Avatar of John Porter

ASKER

Thanks for the comment Qlemo...

I can't see how to change the Service Account to "Network Services".

I know you can select this when SQL Server is being installed but there is not an option I can see to do this in the control panel applet Administrator Tools\Services or SQL Surface Area Configurations.

Any Ideas?

Thanks!
ASKER CERTIFIED SOLUTION
Avatar of Qlemo
Qlemo
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It didn't appear to be privileges - I ended up uninstalling and re-installing the instance to fix it