Prev: SQL Server Edition
Next: I want full open katrina kaif.
From: david on 19 May 2010 01:59
After a major system failure, and restoration from dodgy backups,
I can't get SQLAgent to run. I'm getting event 103,

SQLServerAgent could not be started
(reason: Unable to connect to server

Well, the server is running, and the website is running, and I can
connect using OSQL, so I figure perhaps it is an authentication issue.
The SQLServerAgent service is trying to run using
"local system account". I can connect (osql) using the windows
administrator account.

I'd like to check that the "local system account" known by the
SQL Server is valid (I have reason to suppose it might not be),
but checking is not really important: if it makes sense, I'd like
to reset SQL Server accounts so that the "local system account"
has correct permissions.

Does this make sense? How do I go about it?

(david)


From: millin on 19 May 2010 07:45
what version of SQL server?

"david" wrote:

> After a major system failure, and restoration from dodgy backups,
> I can't get SQLAgent to run. I'm getting event 103,
>
> SQLServerAgent could not be started
> (reason: Unable to connect to server
>
> Well, the server is running, and the website is running, and I can
> connect using OSQL, so I figure perhaps it is an authentication issue.
> The SQLServerAgent service is trying to run using
> "local system account". I can connect (osql) using the windows
> administrator account.
>
> I'd like to check that the "local system account" known by the
> SQL Server is valid (I have reason to suppose it might not be),
> but checking is not really important: if it makes sense, I'd like
> to reset SQL Server accounts so that the "local system account"
> has correct permissions.
>
> Does this make sense? How do I go about it?
>
> (david)
>
>
> .
>
From: millin on 19 May 2010 07:48

The first thing to verify for this event is that the SQL Server service is
running as the SQLSERVERAGENT service depends on it. If the SQL Server
service is not started, troubleshoot that problem first.

From a newsgroup post: "Please check the following registry key.
HKLM\Software\ODBC\ODBCINST.INI\SQL Server\Driver
It should be pointing to c:\winnt\system32\SQLSRV32.dll. When the above
registry key is not present or if the value is not pointing to the SQL server
driver, you will see the error message. If the registry key is not present,
please add a new String Key with the name 'Driver' and the value
'c:\winnt\system32\sqlsrv32.dll' or the appropriate location. If the value is
pointing to a wrong location, update it correctly and make sure the driver
exists at the location you have specified for the value.

please let me know.
mill



"david" wrote:

> After a major system failure, and restoration from dodgy backups,
> I can't get SQLAgent to run. I'm getting event 103,
>
> SQLServerAgent could not be started
> (reason: Unable to connect to server
>
> Well, the server is running, and the website is running, and I can
> connect using OSQL, so I figure perhaps it is an authentication issue.
> The SQLServerAgent service is trying to run using
> "local system account". I can connect (osql) using the windows
> administrator account.
>
> I'd like to check that the "local system account" known by the
> SQL Server is valid (I have reason to suppose it might not be),
> but checking is not really important: if it makes sense, I'd like
> to reset SQL Server accounts so that the "local system account"
> has correct permissions.
>
> Does this make sense? How do I go about it?
>
> (david)
>
>
> .
>
 | 
Pages: 1
Prev: SQL Server Edition
Next: I want full open katrina kaif.