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.

Don't let the ODBC errors get you thrown off. They are used for ODBC Data
Sources, not Query Analyzer. When you are able to connect with SQL Query
Analyzer, an entry gets written to SQL Client Network Utility (cliconfg.exe)
under Aliases. Have you tried running client network utility and SQL server
network utility on the server to make sure both programs are communicating
on the same protocol.

--
************************************************** *****************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@NOMORESPAM.yahoo.com

Please remove NOMORESPAM before replying.

Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.

This posting is provided "as is" with no warranties
and confers no rights.

************************************************** *****************
"badri" <badri@discussions.microsoft.com> wrote in message
news:5177EAC7-42CA-4D4C-BF59-4C95778822C8@microsoft.com...
> 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.
>
>
>

You can get ODBC errors using Query Analyzer - Query
Analyzer connects to SQL Server using ODBC. Plenty of apps
can connect via ODBC and without any ODBC data sources set
up (i.e. DSN-less connections).

-Sue

On Fri, 13 Aug 2004 15:06:46 -0400, "Andy Svendsen"
<andymcdba1@NOMORESPAM.yahoo.com> wrote:

>Don't let the ODBC errors get you thrown off. They are used for ODBC Data
>Sources, not Query Analyzer. When you are able to connect with SQL Query
>Analyzer, an entry gets written to SQL Client Network Utility (cliconfg.exe)
>under Aliases. Have you tried running client network utility and SQL server
>network utility on the server to make sure both programs are communicating
>on the same protocol.

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.
>
>

Dear All,

I solved this issue in a crooked method. I have another windows 2003 server
in my DC. I made registry export of odbc entry alone and imported in another
server and made working now.

Thanks

badri

"Sue Hoegemeier" wrote:

> 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.
> >
> >
>
>