Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Why i am getting SQL Agent error.

Posted on 2014-12-11
8
Medium Priority
?
562 Views
Last Modified: 2014-12-25
Dear EE,

In my SQL Server i am getting below information in EVENT ID. Please see attached picture.

There are two types of information.
SQL SERVER AGENT :-
The description for Event ID 53 from source SQLSERVERAGENT 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:
[sqagtres] CheckServiceAlive: returning TRUE (success)


MSSQLSERVER
The description for Event ID 18454 from source MSSQLSERVER 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:
AGRALAPP
 [CLIENT: 130.0.14.100]


I received information from client that there is a network issue from CLIENT TO DB SERVER.

Thanks
EE-Error.jpg
0
Comment
Question by:Netsol-NOS
  • 5
  • 3
8 Comments
 
LVL 29

Accepted Solution

by:
Dan McFadden earned 2000 total points
ID: 40493602
This seems to indicate that the SQL Agent cannot contact or connect with the database.  If you received information from your client that there is a potential network issue between the client and server, then this is the reason for the event log entries.

Dan
0
 

Author Comment

by:Netsol-NOS
ID: 40493611
Hi Dan ,

Thank you for your quick reply.

Please see that why it is not showing any network disconnectivity or you can say why log are not reporting any NETWORK issue.

Even in Client machine or in DB Server machine.

Thanks
0
 

Author Comment

by:Netsol-NOS
ID: 40493616
Client Logs has nothing with respect to DB side i think it is not complete logs.

The only information i am getting is from DB Server side.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
LVL 29

Expert Comment

by:Dan McFadden
ID: 40493618
Event ID 18454 references logon audit events.  I would verify that the username and password for the account that is being used to connect to the database, is correct.

- Can you ping the database server from the client server?
- can you connect to the database using SQL Server Management Studio?

Dan
0
 

Author Comment

by:Netsol-NOS
ID: 40493633
All is going well right now.
0
 

Author Comment

by:Netsol-NOS
ID: 40493645
Issue is we need to find out why this happends.
0
 
LVL 29

Expert Comment

by:Dan McFadden
ID: 40493657
Then you need to post more information:

- what version of OS on the client
- what version of OS on the server
- what version of SQL drivers on client
- what version of SQL Server on server
- how are the computers connected?  on internal network, same subnet?  over a routed network thru the internet?
- how is the SQL Server Agent configured for authentication?  does it use a service account or SYSTEM, etc.
- what time did these errors occur?
- what events are in the SQL Server logs?
- what additional entries are in the event logs at this time?
- post the contents on the entries in from the events above
- can you manually connect to the SQL Server using the credentials of the SQL Server Agent?

Event ID 53 indicates that the SQL Server Agent is in a failed state.
Event ID 18454 indicates that there was a login issue on the sql server.
0
 

Author Closing Comment

by:Netsol-NOS
ID: 40517502
We have forwarded the case to Network team and they have resolved the issue .

As the client machine is not communicating with DB Server.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Use this article to create a batch file to backup a Microsoft SQL Server database to a Windows folder.  The folder can be on the local hard drive or on a network share.  This batch file will query the SQL server to get the current date & time and wi…
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

886 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question