Operation on handle \\\\server\\HKEY_LOCAL_MACHINE failed

Monitor, diagnose and receive alerts to problems across your SQL Servers.

Operation on handle \\\\server\\HKEY_LOCAL_MACHINE failed

Postby hespinoza » Tue Jan 29, 2013 10:58 pm

We recently change the account our sql red gate service is running under and after that change we are having problems starting the monitoring of our servers. Below is the entry of our log file that gets written when we try to reestablish the connection to the servers

2013-01-29 22:46:01,822 [ 5] WARN RedGate.Response - Getting Log file
2013-01-29 22:47:07,601 [ 21] WARN RedGate.Response.Engine.Monitoring.Core.Licensing.LicenceAllocator - Licence level for uldbprod (1) changing from #a to #b
2013-01-29 22:47:07,625 [ 21] WARN RedGate.Response.Engine.Monitoring.Core.New.DataCollectionScheduler - Overriding schedule for [Cluster].[SqlServer].[Database].[Table].[Index] with WeeklyJobSchedule(Sunday, 1, 0)
2013-01-29 22:47:07,716 [ 5] WARN RedGate.Response.Engine.Monitoring.Core.Communicators.Machines.Registry.Unmanaged.Handles.AutoRegistryHandle - Operation on handle \\\\server\\HKEY_LOCAL_MACHINE failed with error 5. Closing handle.

Any ideas of what this would possible be?

Posts: 4
Joined: Tue Jan 29, 2013 10:55 pm

Postby stanori » Thu Jan 31, 2013 12:13 am

Hi hespinoza,

Thanks for your post. It looks like there could be some issues with remote registry access. From the machine that is running the SQL Monitor Base Monitor service you can log in with the new account you changed to, and run through the following data collection tests:

http://www.red-gate.com/supportcenter/c ... collection

It could be this account does not have proper rights to the remote registry. Hope this helps.

Best Regards,
Steve Tanori
Product Support
Red Gate Software Ltd.
Posts: 84
Joined: Mon Apr 23, 2012 12:13 pm

Return to SQL Monitor Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests