Home Dashboard Directory Help
Search

Reloading Agent Settings appears in SQL Agent Logs every 90 seconds by AndrewTuerk


Status: 

Closed
 as Fixed Help for as Fixed


22
0
Sign in
to vote
Type: Bug
ID: 729700
Opened: 3/8/2012 6:20:25 AM
Access Restriction: Public
0
Workaround(s)
view
11
User(s) can reproduce this bug

Description

While this does not appear to be impacting things currently, this message shows up every 90 seconds in the sql agent log. I have discussed this with many people, and everyone agrees that this is an issue of some sort. If this is to be expected, the reason should be documented somewhere so IT doesnt spend weeks trying to figure out what the issue is. example:

Date                     1/25/2012 8:41:21 AM
Log                         SQL Server Agent (Current - 1/25/2012 8:29:00 AM)

Message
Reloading agent settings


Date                     1/25/2012 8:39:51 AM
Log                         SQL Server Agent (Current - 1/25/2012 8:29:00 AM)

Message
Reloading agent settings

Date                     1/25/2012 8:38:21 AM
Log                         SQL Server Agent (Current - 1/25/2012 8:29:00 AM)
Details
Sign in to post a comment.
Posted by Ulysses B Brown Jr on 10/20/2012 at 10:13 PM
I followed the instructions and made the registry change from 1 to 0. Now I can't restart the SQL Agent. So I rebooted the server and now none of my SQL Services are working. NONE. So I went back in and changed it back to 1 and rebooted. SQL still broken. From the event log I see the following:

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-1758556770-2135383126-751859383-17768:
Process 960 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-1758556770-2135383126-751859383-17768\Printers\DevModePerUser
Posted by Microsoft on 4/4/2012 at 10:33 AM
Hello,
We have fixed this issue in next Service pack for SQL 2012.

If you need this fix in earlier CU, please contact our product support team. http://support.microsoft.com/ph/1044

Thanks
Sethu Srinivasan [MSFT]
SQL Server
Posted by akelly on 3/21/2012 at 11:07 AM
I don't think this is something that should wait for a Service Pack. I think the first CU should include this. Making everyone edit their registry to avoid somethhing that should have never been in there to begin with is not a good solution.
Posted by AaronBertrand on 3/21/2012 at 7:58 AM
This is extremely painful as you can quickly fill up the agent log to the 1 MB limit unless you proactively cycle the agent log often. Not many users are going to suddenly know to do this until they realize that they're no longer capturing important information because it's filled up with this useless status. Please fix this - I think these messages should be suppressed by default but at the very least there should be an easier way to suppress them than telling everybody to update the registry key.
Posted by Microsoft on 3/14/2012 at 10:22 AM
Hello and thank you for reporting this issue,

We investigated this issue and it's indeed painful behavior from the user perspectives, we will address this issue in nearest Service Pack.

For now I can suggest you the the following workaround:

Go to registry on your SQL Server machine and navigate to corresponding SQL Instance registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\ MSSQL11.YOUR_INSTANCE_NAME\SQLServerAgent

Change registry settings called “AutoRegistryRefresh” from 1 to 0.

The side impact of this: if you change any default settings behavior for SQL Agent, you may need to restart SQL Agent to get it.

Thank you
Alex Grach [MSFT]
Posted by JHunter on 3/14/2012 at 5:00 AM
This also makes using tools such as SQL Sentry's Event Manager very painful. Every calendar view is simply filled with the event.
Posted by Sethu Srinivasan on 3/9/2012 at 2:11 PM
Thanks for your feedback. We shall look into this issue

Thanks
Sethu Srinivasan [MSFT]
SQL Server
Sign in to post a workaround.