nicolajsb
asked on
Can't start the SQL Server Agent
Hi all
I have just installed SQL Server 2008 on a new server. After installation I have created new local users for each service of the SQL Server (sql server, sql server agent, Integration Service, OLAP and so on) and each user is member of the corresponding group created by the installation.
The user for the sql server agent for example is member of the group SQLServerSQLAgentUser$MSSQ
This works fine for all services except for the agent which fails when I try to start the service. The event log shows the following messages:
Login failed for user 'MSSQL2008-A\SQLServerAgen
and
SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).
Additional info: the server is not on an AD network&.. all the users I created for the services are local users
Please.... does someone have an idea.....
/Nicolaj
I have just installed SQL Server 2008 on a new server. After installation I have created new local users for each service of the SQL Server (sql server, sql server agent, Integration Service, OLAP and so on) and each user is member of the corresponding group created by the installation.
The user for the sql server agent for example is member of the group SQLServerSQLAgentUser$MSSQ
This works fine for all services except for the agent which fails when I try to start the service. The event log shows the following messages:
Login failed for user 'MSSQL2008-A\SQLServerAgen
and
SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).
Additional info: the server is not on an AD network&.. all the users I created for the services are local users
Please.... does someone have an idea.....
/Nicolaj
can you do a runas in cmd prompt? i e:
c:\runas /u:SQLServiceAccount cmd
ENTER
CMD will prompt for password. If it works it will open another CMD prompt. Just to see that the account works.
Try put it in local admin group, if the service starts, then you know its related to permissions somehow.
Come back with results.
Regards Marten
c:\runas /u:SQLServiceAccount cmd
ENTER
CMD will prompt for password. If it works it will open another CMD prompt. Just to see that the account works.
Try put it in local admin group, if the service starts, then you know its related to permissions somehow.
Come back with results.
Regards Marten
ASKER
just checked.... "log on as service" is grandet by default to the group that is created when the SQL Server is installed and the "runas" thing works fine too.
I have tried to add the user to the Administrators group byt that didn't help either.
If I change the service account for the agent to "Local System" everything works.... but i guess it is best practice to create diticated user accounts for every service and use the groups created during the installation....
I have tried to add the user to the Administrators group byt that didn't help either.
If I change the service account for the agent to "Local System" everything works.... but i guess it is best practice to create diticated user accounts for every service and use the groups created during the installation....
You could try to use the browse button when assigning the account.
If this doesn't work, try creating a new account and see if it will work with this account!
/Marten
If this doesn't work, try creating a new account and see if it will work with this account!
/Marten
ASKER
hmmm tried everything now.... recreating the account, reinstalling the SQL Server.... nothing helps. going back to "Network Service" as the service account for the Agent
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
/Marten