Re: SQLServerAgent will not start - "Event ID: 103" - URGENT HELP

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 08/15/04


Date: Sun, 15 Aug 2004 12:39:03 -0600

Check the start up account that you are using for SQL Agent.
Make sure it has a SQL Server login and appropriate
permissions. You may also want to try having it start using
Local System and see if SQL Agent starts up correctly under
that account. Additionally, make sure you are configuring
the start up account and password using Enterprise Manager
rather than the services applet. If you configure the start
up accounts via Enterprise Manager, the permissions and
rights needed for the accounts will be setup correctly.
In terms of the second error with Query Analyzer, it depends
on what the message is that you are getting with that error.
The error 18456 usually has a message along the lines of
"Login failed for user <whatever user> " - often followed
by more text which will lead you to the problem. If the
server is using Windows Authentication only, then your
Windows login needs access to SQL Server. If you are using
mixed authentication, then you should check the login and
password you are using to connect to SQL Server.

-Sue

On Wed, 11 Aug 2004 04:49:01 -0700, "badri"
<badri@discussions.microsoft.com> wrote:

>Dear Support Team,
>
>I had installed sqlserver 2000 with sp3 on windows 2003 server. Navision ERP
>client software 3.70 installed in this server. Sql server service is running
>as local system account and sql agent service is configured to run as local
>system account. sql agent service is not starting. It throws following error
>in the event log.
>SQLServerAgent will not start, automatically or manual. The message
>in the event log is:"Event ID: 103
>SQLServerAgent could not be started (reason: Unable to connect to
>server '(local)'; SQLServerAgent cannot start)
>
>I tried to connect the Query analyzer: It throws following error:
>ODBC: MSG 18456, Level 16, State 1
>I able to connect the server from the remote system and able to take the
>navision backup from the front end.
>
>When I look in the ODBC Data source administrator on the server under the
>Drivers tab the version information for the SQL Server driver is blank??
>
>To overcome this i checked the ODBC component checker and i found that mdac
>2.8 was installed. Found that some dll are corrupted. I reinstalled the mdac
>and reexecuted teh mdac checker and now all dll's are intact. Still sql
>server driver is blank.
>
>Following registry entry is available
>HKLM\Software\ODBC\ODBCINST.IN\sql server. Apart from this no entry is
>available. Pls tell me whether sql server name to be mentioned here.
>
>
>
>Also checked the service startup dependencies. No dependencies are
>configured for both services(bother server service and agent service)
>
>Pls help me to overcome this.
>
>



Relevant Pages

  • Re: Compromise?
    ... Yes, if you don't provide a password on your SA account, anybody able to run ... and connect now has complete control over your SQL Server. ... Server has. ...
    (microsoft.public.sqlserver.security)
  • Re: Windows Auth to SQL Server from ATL Web Service not working...
    ... account I'm logged on as. ... SQL on a different box from my web service in an Atl Server web ... impersonation token is not passed on to the SQL Server. ... Event Category: Account Logon ...
    (microsoft.public.vc.atl)
  • Re: Discussing 3 different strategies for deleting from multiple tables
    ... I will be using SQL Server but I am riding on top of a third party ... FYI, Account contains around 20K ... >>> This results in one parameterized query followed by two more trips to ...
    (microsoft.public.data.ado)
  • RE: connection problems in secondary site and SQL server
    ... Do you have a Windows 2003 server anywhere in your environment? ... i can't add this account to this group. ... SMS Management Point encountered an error when connecting to its Database ... SMS on SQL Server My_Primary_SMS_Server. ...
    (microsoft.public.sms.admin)
  • RE: MP Install issue
    ... Will setting the SPN on the domain account fix the communication issue ... >> MPDB ERROR - CONNECTION PARAMETERS ... >> with a trusted SQL Server connection. ...
    (microsoft.public.sms.setup)