.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
MarieAdela
Imran Ghani
Post New Web Links

SQLServerAgent initiating self-termination

Posted By:      Posted Date: October 15, 2010    Points: 0   Category :Sql Server
 

Hi,

 

I recently had the SQL Server Agent service stop itself on a SQL 2005 SP2 x64 Server with the following error:

 

"Exception 253 caught at line 446 of file e:\sql9_sp2_t\sql\komodo\src\core\sqlagent\src\job.cpp. SQLServerAgent initiating self-termination"

 

I've seen some other posts saying that this can be caused by SQL Agent jobs that are set to run when the CPU is idle but I don't have any jobs configured in this way.

 <


View Complete Post


More Related Resource Links

SQLServerAgent could not be started (reason: Startup error: The 'msdb' database does not exist)

  
After installing Service pack 3 for Microsoft SQL Server 2005 the SQLServerAgent wont start: From SQLAGENT.OUT: 2010-08-30 17:10:08 - ! [298] SQLServer Error: 208, Invalid object name 'sys.configurations'. [SQLSTATE 42S02] (DisableAgentXPs) 2010-08-30 17:10:08 - ! [298] SQLServer Error: 208, Invalid object name 'master.dbo.sysdatabases'. [SQLSTATE 42S02] 2010-08-30 17:10:08 - ! [000] Startup error: The 'msdb' database does not exist 2010-08-30 17:10:08 - ! [298] SQLServer Error: 208, Invalid object name 'sys.configurations'. [SQLSTATE 42S02] (DisableAgentXPs) 2010-08-30 17:10:08 - ? [098] SQLServerAgent terminated (normally)

SQL Server Event ID 17052: SQLServerAgent has terminated unexpectedly.

  
Hello All,       We are getting EventID17052 in one of our production server from last 3 months. SQL Server Agent is restarting on its own. As per threads about same issue I dig into the Jobs and processes running at that time in Server and I have found one job is causing this issue and Agent crash is happening same time that job is scheduled but not everyday. Server is running with SQL Server 2005 SP2 (Microsoft SQL Server 2005 - 9.00.3042.00 (X64)   Feb 10 2007 00:59:02   Copyright (c) 1988-2005 Microsoft Corporation  Standard Edition (64-bit) on Windows NT 6.0 (Build 6001: Service Pack 1) ).  Please let me  know is there any fix for this error and also let me know SP3 upgrade to SQL Server 2005 will help for it or not? I am also providing full error details from event viewer. The description for Event ID 17052 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: SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly. the message resource is present but the message is not found in t

Error 14258: Cannot perform this operation while SQLServerAgent is starting. Try again later.

  
I'm getting the following error on two of my SQL Servers - Error 14258: Cannot perform this operation while SQLServerAgent is starting. Try again later. The only solution that I have seen is the same solution that Microsoft has published in the following article - KB303287 [http://support.microsoft.com/?scid=http%3a%2f%2fwww.support.microsoft.com%2fkb%2f303287%2fen-us%2f] The solution is to unflag the use of NT Fibers.  However, our software application provider is advising us against doing this.  Is there another fix anywhere that I could get my hands on - another solution? Thanks in advance.

Background Thread + Impersonation + Termination

  

I have an ASP.NET 2.0 web application that is running in Windows Impersonation Mode...

Where the web site is configured as:

- Disable anonymous access

- and web.config

<authentication mode="Windows"/>
<identity impersonate="true"/>
    <authorization>
      <allow users="DOMX\USER1"/>
      <allow users="DOMX\USER2"/>
      <allow users="DOMX\USER3"/>
      <allow users="DOMX\USER4"/>
      <deny users="?"/>
      <deny users="*"/>
    </authorization>

This application needs to execute a potentially time consuming set of actions.  I had a couple of questions about using a background thread...

Question 1:   If I launch a background thread in the code behind... will that thread be terminated when the web application timesout?

Question 2:  If I decide to utilize a separate process (i.e. using System.Diagnostics.

StartResourceService: Failed to start SQLSERVERAGENT service

  

Dear all,

We have problem with SQL Server Agent service running on Fail-Over Cluster at Windows Server 2003 R2 Enterprise Edition. Agent service won't started. These error founded in Event Viewer :


System Event Log
================
Event Type: Error
Event Source: ClusSvc
Event Category: Failover Mgr
Event ID: 1069
Date:  1/11/1990
Time:  5:48:55 PM
User:  N/A
Computer: JSXDBET1
Description:
Cluster resource 'SQL Server Agent' in Resource Group 'MSDTC Group' failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Application Event Log
=====================
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Failover
Event ID: 53
Date:  1/11/1990
Time:  5:48:55 PM
User:  N/A
Computer: JSXDBET1
Description:
[sqagtres] StartResourceService: Failed to start SQLSERVERAGENT service.  CurrentState: 1


For more information, see Help and Support Center at

Question about Workflow Termination

  

I have read that if an user terminate a workflow, all the tasks associated with that workflow will be deleted. But, I think it is important to keep all the task details for future reference.

How do i prevent deleting tasks? Or atleast how can I prevent users terminating workflows?

Thanks,

Nith

 

 


Clean termination of socket connections.

  

I'm finding the MSDN docs confusing for socket closure.

On a Socket we have:

1. Shutdown

2. Disconnect

3. Close

I am far from clear on what order to call these or whether each of them need to be called.

Consider a server Socket that is connected and has been receiving data async, all working fine.

Now one of the messages sent by client is a "disconnect" message (meaning client is telling server it will soon close it's own client socket, with a reason code etc).

When server gets this message it calls:

 client.Shutdown(SocketShutdown.Both);



 client.Disconnect(true);



 client.Close();







At the time this code runs in server, the client has not yet closed or shutdown it's own socket.

The server's call to Shutdown returns right away, but the next call to Disconnect hangs for several minutes.

It eventually comes back and the Close gets called and returns right away too.

Why does Disconnect hang?

Is it perhaps because the Socket was created by Accept and "only" the original client app can initiate this?

If the client sends the disconnect message and then immediately closes it's socket, this might trigger the network exception handler in the server that

Close DB Connection upon application termination?

  

The reason this question came up, is because if I run my website application with a SQL Server data store, and I terminate the browser (terminating the session), I try to open up SSMS to edit the DB.  But I can't access the database because I believe there is still an open connection, even after application termination.

Is it recommended to close the database connection upon session/application closing?  Or am I way off on what I'm thinking could be the problem?

Thanks in advance. :)


Avoid initiating an app by double clicking exe

  
Hi,

I have a windows app (APP-A) which will be initiated from another windows app (APP-B). I don't want users to directly 
browser to that folder where exe resides (APP-A) and double click that..

If user did that, I want to show a message "you must open this by clicking some button on main app".
How can I do this? At the same time I don't want to give trouble to other developers on team who is working
on that app (APP-A. maybe in debug mode or release mode).

Thanks

Initiating A Workflow Programmatically

  

I want to initiate a workflow by using SPWorkflowManager.StartWorkflow method with the user with no privileges to do so; I was using RunWithElevatedPrivileges but this causes a problem, it makes System Account the initiator of the workflow but I want the current user to be the initiator of the workflow, kindly suggest what needs to be done.


Initiating A Workflow Programmatically

  

I want to initiate a workflow by using SPWorkflowManager.StartWorkflow method with the user with no privileges to do so; I was using RunWithElevatedPrivileges but this causes a problem, it makes System Account the initiator of the workflow but I want the current user to be the initiator of the workflow, kindly suggest what needs to be done.


Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend