SQL Server Agent Trouble inside the IPIVR

I'm face a problem with my SQL server agent inside CRS the version is 7.0, I have already repair the IPIVR software and restart this one, but it continue with alert inside the CRS.
Does somebody know if have some patch to apply or some extra configuration that can I set?

Hi,
when ever i am trying to executing the sql server agent job's through manual that time  i am getting the below error.
I searched  net for this type of error and found that Latest SP can fix this issue.See below link
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/12181324-bc51-41a5-a8a5-608bfe2725e9/could-not-load-type-smoagentjobbasecollection?forum=sqlsmoanddmo
Can you also refer to this link 
http://www.sqldbadiaries.com/2010/12/20/could-not-load-file-or-assembly-error-while-using-tdp-makes-a-come-back/
Also please see this connect also
http://connect.microsoft.com/SQLServer/feedback/details/280907/sql-agent-job-actions-fail-from-job-activity-monitor
hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Similar Messages

  • While i am trying to start the sql server agent job getting the error

    Hi,
    when ever i am trying to executing the sql server agent job's through manual that time  i am getting the below error.

    Hi,
    when ever i am trying to executing the sql server agent job's through manual that time  i am getting the below error.
    I searched  net for this type of error and found that Latest SP can fix this issue.See below link
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/12181324-bc51-41a5-a8a5-608bfe2725e9/could-not-load-type-smoagentjobbasecollection?forum=sqlsmoanddmo
    Can you also refer to this link 
    http://www.sqldbadiaries.com/2010/12/20/could-not-load-file-or-assembly-error-while-using-tdp-makes-a-come-back/
    Also please see this connect also
    http://connect.microsoft.com/SQLServer/feedback/details/280907/sql-agent-job-actions-fail-from-job-activity-monitor
    hope this helps
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • SQL Server Agent running SSIS package fails Unable to determine if the owner of job has server access

    I have a web application developed through VS 2012 which has a button on a form that when operated starts a SQL Server agent job on the server that runs an SSIS package.  The website and the instance of SQL Server with the agent and SSIS package are
    on the same windows 2008 r2 server.  When the button is operated no exceptions are raised but the SSIS package did not execute.
    When I look in the logfileviewer at the job history of the sql server agent job I see that the job failed with message...
    The job failed.  Unable to determine if the owner (DOMAINNAME\userid) of job runWebDevSmall has server access (reason: Could not obtain information about Windows NT group/user 'DOMAINNAME\userid'<c/> error code 0x6e. [SQLSTATE 42000] (Error 15404)).,00:00:00,0,0,,,,0
    ...even though DOMAINNAME\userid is in the logins for the sql server and has admin authorities.
    Could someone show me what I need to do to get this to run?  Thanks tonnes in advance for any help, Roscoe

    This can happen when the network is too slow to allow a timely completion of the verification. Or the account running has no such right.
    I suggest you try using the SA account for the job as it does not require to poll the AD.
    Arthur My Blog

  • SQL server agent send email

    I set up email notification for a job completes. I configured database mail profile and mail account. This works fine and I can send out test email.
    However, the SQL agent couldn't send out email and when I tried to restart the SQL server agent, I got the following errors:
    Message
    [260] Unable to start mail session (reason: Microsoft.SqlServer.Management.SqlIMail.Server.Common.BaseException: Mail configuration information could not be read from the database. ---> System.InvalidCastException: Unable to cast object of type 'System.DBNull'
    to type 'System.Byte[]'.
       at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.DataAccessAdapter.GetAccount(Int32 accountID)
       --- End of inner exception stack trace ---
       at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.DataAccessAdapter.GetAccount(Int32 accountID)
    My SQL server is SQL 2008 with service pack 3.
    Anybody has any idea what's the problem is?
    Thanks

    Hi Ying,
    You could try below suggestions.And restart SQL Server Agent.
    Please refer:
    http://www.developerjoint.com/kb/9363-trouble-with-sql-2005-database-mail.aspx.
    Thanks,
    Maggie
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

  • Error when execute a package from SQL Server Agent

    We have the next problem:
    When we execute a package from a Job of SQL Server agent, it shows the success messege, but reviewing the results, the package didnt do all the tasks.
    When we run it mannually by MSIS the package, it shows the success message and it works fine.
    The workflow of the package is :
    1) Shrink the databases (executing a sql file)
    2) Backup the databases (Back up Database task of MSIS)
    3) Rename the files to .BAK extension (by the Foreach loop container and fyle system task)
    4) Execute command to compress the it (by a .bat)
    5) Move the compress file to another location  (by another Foreach loop)
    Manually run correct, but when is a a SQL AGent Job that execute the package it does only the first 2 steps.
    we are ussing Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (coffee) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) 
    We are using a user with administrator privilegies
    Cheers 

    Can you check if account running package has proper access. You may need to define a proxy account for that.
    See
    http://www.databasejournal.com/features/mssql/article.php/3789881/Proxy-Accounts-in-SQL-Server.htm
    http://gqbi.wordpress.com/2014/01/30/setting-up-a-proxy-account-to-run-sql-server-integration-services-ssis-2012-packages/
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Error: Failed to acquire connection while exporting a file using SSIS package through SQl Server Agent job.

    Hi Team,
    I am running a sql server job which is loading data to a sharepoint document library.File is an excel format and is getting loaded
    when executed through SSDT solution .But when i am using an SQL Agent job to pick up the file it doesnt get the path and agent job fails with the error "Failed to acquire connection".I have deployed the SSIS Package through SQL Server 2012 deployment
    methodologies.
    I am not able to trace the error of loading data from a sharepoint library.library. Sql agent jobs works fine when i give local path.The
    account which is running the sql agent job is the same who has access to document library.I also tried to run the job through proxy account. I am using a xml configuraion to store my credentials.I am able to palce the same file to a network drive in the same
    server through sql server agent job. The only problem is when I am trying to load the file to a sharepoint folder.
    Thanks,
    Arsa..

    Is that the WebDAV method that you are suggesting here to map the n/w drive?
    Its kind of webdav but you will be using windows nw drive to store data
    yes, I am able to create the file to D: , but didn't check with the C:.
    Try with c:, as c: require special permisssions
    If this helped you resolve your issue, please mark it Answered

  • SSIS fails to load files from network when executed via SQL server Agent (SQL server 2008 R2 SP 2)

    Hi All,
    I have a simple SSIS package that reads a flat file and copies it into a SQL Server table.
    When the flat fiel is on the C drive I have no problem runnign this package from SQL Server Agent, but as soon as I update the path to a network location the package only works when I run it manually, but fails when is executed via the SQL Server agent job.
    The error says "cannot open the datafile", while the datafile location is valid.
    Is this a kind of limitation of a SQL Server Agent that only local files are allowed to be processed?
    Thanks,
    Andrei
    SSIS question

    Hi All,
    Thanks for your responses.
    I configured the SQL agent service to use my domain account with which I have no porblems accessing the folder. However the issue persisted.
    Thanks,
    Andrei
    SSIS question

  • SSIS package is failing when using SQL server agent

    I am trying to execute an SSIS package through an SQL server agent and receiving the following error:
    Message
    Executed as user: serv-syst\SYSTEM. Microsoft (R) SQL Server Execute Package Utility  Version 10.50.1600.1 for 32-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started:  1:56:53 PM  Error: 2014-04-21
    13:56:54.81     Code: 0xC0202009     Source: PACKAGEWMG Connection manager "DestinationConnectionOLEDB"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred.
    Error code: 0x80040E4D.  An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80040E4D  Description: "Login failed for user 'hsnzha'.".  End Error  Error: 2014-04-21
    13:56:54.82     Code: 0xC00291EC     Source: Drop table(s) SQL Task 1 Execute SQL Task     Description: Failed to acquire connection "DestinationConnectionOLEDB". Connection may not be configured
    correctly or you may not have the right permissions on this connection.  End Error  Error: 2014-04-21 13:56:54.82     Code: 0xC0202009     Source: PACKAGEWMG Connection manager "DestinationConnectionOLEDB"    
    Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E4D.  An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80040E4D  Description: "Login
    failed for user 'hsnzha'.".  End Error  Error: 2014-04-21 13:56:54.82     Code: 0xC00291EC     Source: Preparation SQL Task 1 Execute SQL Task     Description: Failed to acquire connection
    "DestinationConnectionOLEDB". Connection may not be configured correctly or you may not have the right permissions on this connection.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  1:56:53 PM 
    Finished: 1:56:54 PM  Elapsed:  0.844 seconds.  The package execution failed.  The step failed.
    My SSIS package retrieves a excel file and saves the vales into an SQL table. When I run the package by itself in my server it works fine but when it's called from a SQL agent, it fails with the above error. Please help me resolve it.

    That's the issue. If it's a SQL login the password cannot be retrieved by account executing the package from the job which is why login fails. In that case best thing would be set password in job properties or pass it using configuration created in the package
    See
     HTTP://blogs.msdn.com/b/runeetv/archive/2011/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspx
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs
    My package is saved with ServerStorage which appears under \\server\Stored Packages\MSDB\PACKAGE and when I run it, it works fine.
    There is a new error message that I get now after following the steps from the link...
    Message
    Microsoft (R) SQL Server Execute Package Utility
    Version 10.50.1600.1 for 32-bit
    Copyright (C) Microsoft Corporation 2010. All rights reserved.
    Started:  3:34:22 PM
    Error: 2014-04-21 15:34:23.82
       Code: 0xC0202009
       Source: PACKAGEWMG Connection manager "SourceConnectionExcel"
       Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft Office Access Database Engine"  Hresult: 0x80004005  Description: "Unexpected error from external database driver (????????).".
    End Error
    Error: 2014-04-21 15:34:23.82
       Code: 0xC020801C
       Source: Data Flow Task 1 Source - 'Contact Center$' [1]
       Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "SourceConnectionExcel" failed with error code 0xC0202009.  There may be error
    messages posted before this with more information on why the AcquireConnection method call failed.
    End Error
    Error: 2014-04-21 15:34:23.82
       Code: 0xC0047017
       Source: Data Flow Task 1 SSIS.Pipeline
       Description: component "Source - 'Contact Center$'" (1) failed validation and returned error code 0xC020801C.
    End Error
    Error: 2014-04-21 15:34:23.82
       Code: 0xC004700C
       Source: Data Flow Task 1 SSIS.Pipeline
       Description: One or more component failed validation.
    End Error
    Error: 2014-04-21 15:34:23.82
       Code: 0xC0024107
       Source: Data Flow Task 1
       Description: There were errors during task validation.
    End Error
    DTExec: The package execution returned DTSER_FAILURE (1).
    Started:  3:34:22 PM
    Finished: 3:34:23 PM
    Elapsed:  1.25 seconds

  • SSIS package fails in sql server agent wirh 'Process exit code "-532459699" runs fine when run independantly

    I have a SSIS package that fails when running via sql server agent.  I can successfully run it from BIDS.    I have created a proxy account that is in the local server administrators group and is sysadmin.  SQL Server Agent and SQL
    Server Integration Services  are running under the same account,
    following the the error message:
    Error: 2014-02-07 10:29:12.59
       Code: 0xC0029151
       Source: Execute De-linking Execute Process Task
       Description: In Executing "d:\cie\files\working\9426\PowerpointConsole.exe" " 60.ppt" at "d:\cie\files\working\9426", The process exit code was "-532459699" while the expected was "0".
    End Error
    This package ran successfully on a different server running windows 2003 and sql server 2008 r2.  The new environment is windows 7 with sql server 2008 r2.

    Hi Gaileg,
    As Abhinav said, to check whether it is a 32-bit/64-bit issue, please check whether the package runs in 32-bit runtime mode or 64-bit runtime mode in BIDS by checking the Run64bitRuntime property of the project. Then, make sure the package runs in the same
    runtime mode in the SQL Server Agent job by checking or unchecking the “Use 32 bit runtime” option for the Execution options of the job step.
    If it is not the issue, please create another job that uses a CmdExec type job step to call the executable “D:\cie\files\working\9426\PowerpointConsole.exe”. If this job also fails, the issue is actually occurs because of the issue between executable and
    SQL Server Agent rather than the SSIS package itself.
    Regards,
    Mike Yin
    TechNet Community Support

  • SSIS Package Fails when Scheduled as a SQL Server Agent Job

    I have an SSIS package that runs without any problems when executed through BIDS.
    However, when I schedule the SSIS as an Agent job, it fails completely or part way through. When it partially runs, the part that it is failing on is a Script Task that moves the source data file to an archive folder (on the same server).
    I have tried using my domain account as the owner of the job, then the job fails straight off and I get an error:
    Unable to determine if the owner (Domain\MyID) of job JobName has server access (reason: Could not obtain information about Windows NT group/user 'Domain\MyID'
    If I change the owner to the 'sa' account , then the job partially runs, but then fails because 'sa' is a SQL account and does not have access to the filesystem.
    I have managed to get it to work by using the SQL2008_Local account and granting modify permissions to the affected folders.
    My question is - what is the advised way of doing this?
    Thanks
    Gary

    Hi Garyv.King,
    When you see a SSIS package fails running in a SQL Agent job, you need to first consider the following conditions:
    1. The user account that is used to run the package under SQL Server Agent differs from the original package author.
    2. The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
    For more detailed information about the issue, please following this KB article:
    An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step
    http://support.microsoft.com/kb/918760 
    You can check SQL Server Agent’s activity logs, Windows Event logs and SSIS logs to get more clues. Also the tool Process Monitor is helpful to track the cause of registry or file access related issues.
    The following 4 issues are common encountered in the SSIS forum.
    1. The package's Protection Level is set to EncryptSensitiveWithUserKey but your SQL Server Agent service account is different from the SSIS package creator.
    2. Data source connection issue.
    3. File or registry access permission issue.
    4. No 64-bit driver issue.
    For more information about it, please see:
    How do I troubleshoot SSIS packages failed execution in a SQL Agent job:
    http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e13c137c-1535-4475-8c2f-c7e6e7d125fc 
    Thanks,
    Eileen

  • SSIS package give an error if execute through SQL server agent

    I have created a SSIS package in BIDS 2012. If i execute this package through sql server agent it gives the below error:
    Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility  Version 11.0.2100.60 for 64-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  11:19:47 AM  Error: 2015-01-20
    11:19:47.83     Code: 0xC0016016     Source: Sub_Hadoop_aggregation      Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.".
    You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.  End Error  Error: 2015-01-20 11:19:47.94     Code: 0xC0016016     Source:
    Sub_Hadoop_aggregation      Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error
    occurs when there is a cryptographic error. Verify that the correct key is available.  End Error  Error: 2015-01-20 11:19:48.04     Code: 0xC0016016     Source: Sub_Hadoop_aggregation      Description: Failed to
    decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct
    key is available.  End Error  Error: 2015-01-20 11:19:48.92     Code: 0xC00291EC     Source: alter_keys Execute SQL Task     Description: Failed to acquire connection "mstr_warehouse". Connection may not be
    configured correctly or you may not have the right permissions on this connection.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  11:19:47 AM  Finished: 11:19:48 AM  Elapsed:  1.42 seconds.
     The package execution failed.  The step failed.
    so i have change some properties in our package like protectionlevel change from encrypted to dontsavesensitive. After that i have created configuration file for the package and use that configuration file. It executes the package through sql server agent
    smoothly.
    Thanks
    Azhar Khan

    Hi selfdestruct80,
    According to your description, you created SSIS package and it works fine. But you got the error message when the SSIS package was called from a SQL Server Agent job.
    According to my knowledge, the package may not run in the following scenarios:
    The current user cannot decrypt secrets from the package.
    A SQL Server connection that uses integrated security fails because the current user does not have the required permissions.
    File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses.
    A registry-based SSIS package configuration uses the HKEY_CURRENT_USER registry keys. The HKEY_CURRENT_USER registry keys are user-specific.
    A task or a connection manager requires that the current user account has correct permissions.
    According to the error message, the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword as ArthurZ mentioned. To solve the problem, you need to go to Command Line tab, manually specify the paassword in SQL Agent Job with the command like below:
    /FILE "\"C:\Users\xxxx\Documents\SQL Server Management Studio\SSIS\Package.dtsx\"" /DECRYPT somepassword /CHECKPOINTING OFF /REPORTING E
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu
    Wendy Fu
    TechNet Community Support

  • SQL Procedure working when run manually, not running from sql server agent

    I have a procedure that runs fine using the execute command in SSMS, however putting the same command in a job gives the following error.
    line 9, character 9, unexpected end of input
    The code takes a very long XML string in UTF-8 encoding and puts it into a single nvarchar(max) cell. Then puts this string into a XML cell in a different table, allowing me to query the individual parts of the XML code using the nodes function. I cannot put
    the data directly into a nvarchar cell due to encoding differences.
    I can't reproduce the string here as it is very very long.
    I'm just looking for ideas really as to where it might be going wrong.
    Here is what I know so far:
    The procedure runs without issue when executed manually
    I have checked permission issues, and that doesn't seem to be the problem. The agent runs under my own account and I am a sysadmin on the database
    I split the procedure into seperate parts to locate exactly where the problem is occuring. Once again the seperate procedures run fine when executed manually but an error occurs when run through SQL Server agent.
    When the query is run seperately through SQL Server Agent it gives a slightly different error. This leads me to believe it is an encoding issue. However I am getting the XML from a webpage and I can't change the encoding on the webpage.
    line 1, character 38, unable to switch the encoding
    I know this is a long shot since you can't replicate the issue but if anyone could give an idea as to where to start looking for an answer, it would be greatly appreciated.

    Here's how I'm taking the XML data and putting it into an nvarchar(max) column (Column Name TEXT):
    Select @url = 'http://....'
    EXEC @hr=sp_OACreate 'WinHttp.WinHttpRequest.5.1',@win OUT
    IF @hr <> 0 EXEC sp_OAGetErrorInfo @win
    EXEC @hr=sp_OAMethod @win, 'Open',NULL,'GET',@url,'false'
    IF @hr <> 0 EXEC sp_OAGetErrorInfo @win
    EXEC @hr=sp_OAMethod @win,'Send'
    IF @hr <> 0 EXEC sp_OAGetErrorInfo @win
    INSERT #TextData(TEXT)
    EXEC @hr=sp_OAGetProperty @win,'ResponseText'
    IF @hr <> 0 EXEC sp_OAGetErrorInfo @win
    EXEC @hr=sp_OADestroy @win
    IF @hr <> 0 EXEC sp_OAGetErrorInfo @win

  • SQL Server Agent available on Azure?

    I would like to delete records from an database table on Azure when the table reaches a certain size.
    I would normally do this by scheduling a stored procedure job using SQL Server Agent.
    Is the SQL Server Agent available on databases held on Azure?
    Should I use an alternative approach?
    Thanks
    Stew

    Hello ,
    Please take look on :
    Scheduling job on SQL Azure
    We can execute sql procedures on Azure based on our need (schedule configuration).
    Create a mobile service.
    Create a scheduler. Mention the database to be used for this.
    Configure the scheduler for the frequency.
    Click on tab Script. The script can be written in java script or .net. The script should have the code to run a proc.
     I used below code to run dbo.ExecuteDataRequest procedure Azure database.
     function Execute_Process_Request() {
          console.log("Executing ExecuteDataRequest...");
          mssql.query('Exec dbo.ExecuteDataRequest',{
             success: function(results){
             console.log("Finished the Process Request job.");
              error: function(err) {
                console.log("error is: " + err);
    Find the new user added which will run the scheduler (Under Login folder of Security of Azure db server). Need to grant execute permission to the new user on the database where we need to execute the job.
    Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

  • SQL Server Agent ... Relation with BizTalk.

    Hi All,
    I know that there are jobs in SQL Server Agent which are used to perform some activity on scheduled basis like Purging,backup etc...
    what happens if SQL server agent service is in Stop mode(is it mandatory to have it started) and does it have any relation with BizTalk BAM.
    Praj Dixit

    Yes, you have to make sure the SQL Server Agent is running on the SQL Server. When the SQL Server
    Agent is stopped, the built-in BizTalk SQL Server Agent jobs that are responsible for database maintenance cannot run. This behaviour causes database growth, and this growth may cause performance issues. 
    SQL Server Agent jobs except the MessageBox_Message_Cleanup_BizTalkMsgBoxDb job should be enabled and running successfully. 
    You can learn about the SQL Server Agent jobs at Description of the SQL
    Server Agent jobs in BizTalk Server
    Regarding BizTalk BAM,
    Yes Backup BizTalk Server Job takes the backup of BAM Primary Import, SQL NS as
    well as other BizTalk databases. The BAM Analysis database, BAM Star Schema Database and Tracking Analysis Server database store content in SQL Server Analysis Services cubes. The Backup BizTalk Server job does not back up these databases. Instead, to
    backup these databases, it uses SQL Server Analysis Manager.
    I found this utility (BizTalk Monitoring
    Automation Utility) very useful to automate the monitoring of
    your BizTalk environment. If you have liberty to go with a paid tool,
    BizTalk360 a monitoring and support tool is the one for you.
    Rachit

  • SQL Server Agent Stopped

    Received an error in SQL Server Agent and none of the Job executed as per schedules and attaching a screen shot of the Error Message while expanding the Job Folder under SQL Server Agent. Additionally, need to find the RCA for this issue to avoid the re-occurrence.
    Pls share your experience if any such issue which you have faced earlier.
    As usual, after re-starting the Windows Server the issue got fixed and no RCA captured. Please let me know how to drill down and find out the RCA for this issue.

    Hi,
    the exact issue what i had is as in below URL.
    https://connect.microsoft.com/SQLServer/feedback/details/243790/sql-server-agent-exception-in-the-tsql-subsystem-agent-hangs-unresponsive
    And in the another reference URL i can feel that could be the solution but not able to identify the exact Root Cause.
    http://mssqlwiki.com/sqlwiki/sql-server-agent/sql-agent-maxworkerthreads-and-agent-subsystem/
    Additionally, attaching the Application Log event details for further Analysis in HTML format.
    [sqagtres] CheckServiceAlive: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:22:09.000000000Z" />
        <EventRecordID>10509692</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:52:09 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:22:09.000000000Z" />
        <EventRecordID>10509690</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:52:00 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:22:00.000000000Z" />
        <EventRecordID>10509678</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:52:00 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:22:00.000000000Z" />
        <EventRecordID>10509676</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:52:00 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:22:00.000000000Z" />
        <EventRecordID>10509674</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:51:13 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:21:13.000000000Z" />
        <EventRecordID>10509652</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:51:13 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:21:13.000000000Z" />
        <EventRecordID>10509650</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:51:13 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:21:13.000000000Z" />
        <EventRecordID>10509648</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:46:09 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:16:09.000000000Z" />
        <EventRecordID>10509545</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:46:09 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:16:09.000000000Z" />
        <EventRecordID>10509543</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:46:09 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:16:09.000000000Z" />
        <EventRecordID>10509541</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:46:03 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:16:03.000000000Z" />
        <EventRecordID>10509529</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:46:03 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:16:03.000000000Z" />
        <EventRecordID>10509527</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:46:03 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:16:03.000000000Z" />
        <EventRecordID>10509525</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:44:46 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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: Service is dead
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:14:46.000000000Z" />
        <EventRecordID>10509513</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: Service is dead
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-26 4:44:46 AM
    Event ID:      53
    Task Category: (5)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    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] SvcStop: service did not stop; giving up.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T23:14:46.000000000Z" />
        <EventRecordID>10509511</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] SvcStop: service did not stop; giving up.
    </Data>
        <Binary>35000040010000000A00000042004C005500530051004C00410043004300000000000000</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        Microsoft-Windows-User Profiles Service
    Date:          2014-10-26 4:01:10 AM
    Event ID:      1530
    Task Category: None
    Level:         Warning
    Keywords:      
    User:          SYSTEM
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  
     DETAIL - 
     1 user registry handles leaked from \Registry\User\S-1-5-21-771433644-1862610895-1113058290-1216:
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-1216\Printers\DevModePerUser
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-User Profiles Service" Guid="{89B1E9F0-5AFF-44A6-9B44-0A07A7CE5845}" />
        <EventID>1530</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T22:31:10.210213900Z" />
        <EventRecordID>10508265</EventRecordID>
        <Correlation />
        <Execution ProcessID="924" ThreadID="12052" />
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData Name="EVENT_HIVE_LEAK">
        <Data Name="Detail">1 user registry handles leaked from \Registry\User\S-1-5-21-771433644-1862610895-1113058290-1216:
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-1216\Printers\DevModePerUser
    </Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        Microsoft-Windows-User Profiles Service
    Date:          2014-10-26 3:37:38 AM
    Event ID:      1530
    Task Category: None
    Level:         Warning
    Keywords:      
    User:          SYSTEM
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  
     DETAIL - 
     1 user registry handles leaked from \Registry\User\S-1-5-21-771433644-1862610895-1113058290-1434:
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-1434\Printers\DevModePerUser
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-User Profiles Service" Guid="{89B1E9F0-5AFF-44A6-9B44-0A07A7CE5845}" />
        <EventID>1530</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T22:07:38.056728700Z" />
        <EventRecordID>10507688</EventRecordID>
        <Correlation />
        <Execution ProcessID="924" ThreadID="12052" />
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData Name="EVENT_HIVE_LEAK">
        <Data Name="Detail">1 user registry handles leaked from \Registry\User\S-1-5-21-771433644-1862610895-1113058290-1434:
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-1434\Printers\DevModePerUser
    </Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        Microsoft-Windows-User Profiles Service
    Date:          2014-10-26 3:12:07 AM
    Event ID:      1530
    Task Category: None
    Level:         Warning
    Keywords:      
    User:          SYSTEM
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  
     DETAIL - 
     1 user registry handles leaked from \Registry\User\S-1-5-21-771433644-1862610895-1113058290-1434:
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-1434\Printers\DevModePerUser
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-User Profiles Service" Guid="{89B1E9F0-5AFF-44A6-9B44-0A07A7CE5845}" />
        <EventID>1530</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T21:42:07.367675100Z" />
        <EventRecordID>10507058</EventRecordID>
        <Correlation />
        <Execution ProcessID="924" ThreadID="18292" />
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData Name="EVENT_HIVE_LEAK">
        <Data Name="Detail">1 user registry handles leaked from \Registry\User\S-1-5-21-771433644-1862610895-1113058290-1434:
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-1434\Printers\DevModePerUser
    </Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        Microsoft-Windows-User Profiles Service
    Date:          2014-10-26 12:59:12 AM
    Event ID:      1530
    Task Category: None
    Level:         Warning
    Keywords:      
    User:          SYSTEM
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  
     DETAIL - 
     3 user registry handles leaked from \Registry\User\S-1-5-21-771433644-1862610895-1113058290-500:
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-500
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-500\Printers\DevModePerUser
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-500\Software\Microsoft\Windows NT\CurrentVersion\Windows
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-User Profiles Service" Guid="{89B1E9F0-5AFF-44A6-9B44-0A07A7CE5845}" />
        <EventID>1530</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T19:29:12.118229900Z" />
        <EventRecordID>10503856</EventRecordID>
        <Correlation />
        <Execution ProcessID="924" ThreadID="17644" />
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData Name="EVENT_HIVE_LEAK">
        <Data Name="Detail">3 user registry handles leaked from \Registry\User\S-1-5-21-771433644-1862610895-1113058290-500:
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-500
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-500\Printers\DevModePerUser
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-500\Software\Microsoft\Windows NT\CurrentVersion\Windows
    </Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        Application Error
    Date:          2014-10-25 11:10:49 PM
    Event ID:      1000
    Task Category: Application Crashing Events
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc808
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x0000000000000000
    Faulting process id: 0x%9
    Faulting application start time: 0x%10
    Faulting application path: %11
    Faulting module path: %12
    Report Id: %13
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T17:40:49.000000000Z" />
        <EventRecordID>10501239</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>mmc.exe</Data>
        <Data>6.1.7600.16385</Data>
        <Data>4a5bc808</Data>
        <Data>unknown</Data>
        <Data>0.0.0.0</Data>
        <Data>00000000</Data>
        <Data>c0000005</Data>
        <Data>0000000000000000</Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        Microsoft-Windows-User Profiles Service
    Date:          2014-10-25 11:09:59 PM
    Event ID:      1530
    Task Category: None
    Level:         Warning
    Keywords:      
    User:          SYSTEM
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  
     DETAIL - 
     1 user registry handles leaked from \Registry\User\S-1-5-21-771433644-1862610895-1113058290-1434:
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-1434\Printers\DevModePerUser
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-User Profiles Service" Guid="{89B1E9F0-5AFF-44A6-9B44-0A07A7CE5845}" />
        <EventID>1530</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T17:39:59.818023100Z" />
        <EventRecordID>10501214</EventRecordID>
        <Correlation />
        <Execution ProcessID="924" ThreadID="6232" />
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData Name="EVENT_HIVE_LEAK">
        <Data Name="Detail">1 user registry handles leaked from \Registry\User\S-1-5-21-771433644-1862610895-1113058290-1434:
    Process 1004 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-771433644-1862610895-1113058290-1434\Printers\DevModePerUser
    </Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          2014-10-25 7:15:00 PM
    Event ID:      209
    Task Category: (3)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      GSGLOBAL-CN07.GSGLOBAL.local
    Description:
    The description for Event ID 209 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: 
    1
    Copy_ESHOP_GBR_GT
    0x4644461009F9A840BEC1F3FE774C400A
    TSQL
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="49152">209</EventID>
        <Level>2</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-25T13:45:00.000000000Z" />
        <EventRecordID>10495566</EventRecordID>
        <Channel>Application</Channel>
        <Computer>GSGLOBAL-CN07.GSGLOBAL.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>1</Data>
        <Data>Copy_ESHOP_GBR_GT</Data>
        <Data>0x4644461009F9A840BEC1F3FE774C400A</Data>
        <Data>TSQL</Data>
      </EventData>
    </Event>
    I could not able to attach as Application Event Log file instead just pasted the detailed content of the log details otherwise that would be easier to analyse.
    Thanks,
    Mohanraj

Maybe you are looking for