Home > Event Id > Sql 2012 Opensqlserverinstanceregkey:getregkeyaccessmask Failed (reason: 2).

Sql 2012 Opensqlserverinstanceregkey:getregkeyaccessmask Failed (reason: 2).


When you use the SQL Server Management Studio tool to start the SQL Server Agent service, these extended stored procedures are enabled automatically. Assign this account to the SQL Agent Service via SQL Server Configuration Manager. Marked as answer by ETL-James Monday, January 07, 2013 10:02 PM Unmarked as answer by ETL-James Monday, January 07, 2013 10:02 PM Monday, January 07, 2013 8:28 PM Reply | Quote Image: Causation The error is sourced to the Replication Wizard inability to submit jobs to SQL Server Agent. this contact form

Post navigation ← SQL Monitor on CodePlex (free standalonetool) Windows Azure Reporting nowavailable! → 12 thoughts on “MS SQL Server 2012 Error – OpenSQLServerInstanceRegKey:GetRegKeyAccessMask failed (reason:2).” Manoj says: on April 26, perhaps this would updated the proper registry keys and this never would of happened.For now, i'll likely just un-install and re-do everything as this our first 2012 test cluster. For any SQL Server Performance Tuning Issue send email at pinal @ . This worked perfectly.

Sql 2012 Opensqlserverinstanceregkey:getregkeyaccessmask Failed (reason: 2).

Via sp_configure, Enable "Agent XP" exec sp_configure 'show advanced options', 1 go reconfigure with override go exec sp_configure 'Agent XPs', 1 go reconfigure with override go But, no help. Double-click Local Security Policy. To audit unsuccessful access to these objects, select the Failure check box.

Double-click Audit object access. All rights reserved. Here is the TSQL to enable Agent XPs manually:sp_configure 'show advanced options', 1;GORECONFIGURE;GOsp_configure 'Agent XPs', 1;GORECONFIGUREGOSummaryIn summary you should define dedicated accounts for each SQL Server Service up front before you Sql Server Agent Not Starting In Sql Server 2012 Express Be sure to backup your registry before you attempt this.

You should enable it to make sure the SQL Agent Service work correctly. Event Id 324 Opensqlserverinstanceregkey:getregkeyaccessmask Failed (reason 2) About Me Cecil Du Toit View my complete profile Popular Posts SQL Server 2012-SQL Agent Service Cannot Start After Setup Upload Documents to SharePoint 2010 with Web Services Lessons Learned using Home Dashboard Directory Help Sign in SQL Server Home Downloads Feedback Surveys Thank you for your feedback! SQL Server > SQL Server Database Engine Question 0 Sign in to vote I am attempting to start SQL Server Agent and I receive this error (from event log): -

You may have already seen these links but see if there is anything that can help you troubleshoot until an MVP replies. Sqlserver Error: 229, The Execute Permission Was Denied On The Object 'sp_sqlagent_update_agent_xps When this option is not enabled, the SQL Server Agent node is not available in SQL Server Management Studio Object Explorer. In the Enter the object name to select box, type the name of the user or group whose access you want to audit. All rights reserved.Terms of Use|Trademarks|Privacy Statement|Site Feedback Home SQL Server Agent Not Starting Properly by whaaah on Jul 14, 2015 at 1:05 UTC | Microsoft SQL Server 1 Next: Add columns

Event Id 324 Opensqlserverinstanceregkey:getregkeyaccessmask Failed (reason 2)

MSSQL12 is for SQL Server 2014 and so on.Once we change the path to a valid location, SQL Server Agent was started.Reference: Pinal Dave ( Tags: SQL Error Messages, SQL Scripts, I have found though, that granting the permissions causes far less trouble in a clustered environment than not doing so. Sql 2012 Opensqlserverinstanceregkey:getregkeyaccessmask Failed (reason: 2). A system administrator can enable the use of ‘Agent XPs' by using sp_configure. (Microsoft SQL Server, Error 15281 Image: SQL Server blocked access  to procedure ‘dbo.sp_set_sqlagent_properties' of component ‘Agent XPs' Textual: Event Id 324 Failover Thanks dude.

Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your account. (LogOut/Change) You are weblink Always keep your eye on the Windows Application Event Viewer for SQL Server errors!Cheerio!

Categories: SQL Agent Service, SQL Server Disqus Blee Blah of .Net My opinion on Microsoft .Net I am running SQL Server 2012, attempting to setup CDC jobs. TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and workstation via the Splunk Universal Forwarder. Opensqlserverinstanceregkey:getregkeyaccessmask Failed (reason: 2). Sql Express

He has authored 11 SQL Server database books, 21 Pluralsight courses and have written over 3800 articles on the database technology on his blog at a Keywords Thank goodness, we can use Keyword equal to "Audit Failure" Event ID 4656 4656: A handle to an object was requested 

When you enable auditing on an object (e.g. Resolution - sp_configure? navigate here Search for: Recent Posts SQL Server - Integration Services - Network Flow andRules Dissociative Identity Disorder SQL Server - Integration Services – Connectivity – Issue – “Class Not Registered” / Address

Posted by Jeff_S_Kelly on 4/9/2012 at 5:48 PM I also have this issue with an upgrade from RC0 to RTM.I'm wondering if it has anything to do with the instanceID on I have the same message: Log Name: ApplicationSource:SQLSERVERAGENTDate: 23/03/2012 02:58:18 p.m.Event ID: 324Task Category: FailoverLevel: ErrorKeywords: ClassicUser: N/AComputer: S04.dissantamaria.locDescription:OpenSQLServerInstanceRegKey:GetRegKeyAccessMask failed (reason: 2).Event Xml: 324250x800000000000003106ApplicationS04.dissantamaria.loc Login here!

Run SQL Server Configuration Manager (SSCM) and change the account there.

Please let us know if you would be willing to validate this fix on your test systemsThanksSethu Srinivasan [MSFT]SQL Server Posted by Jeff_S_Kelly on 4/9/2012 at 6:36 PM Duplicating the reg I have experience on wide range of products such as MySQL, Oracle Essbase, Agile, SAP Basis, SharePoint, Linux and Business Apps admin. Further analysis of the Application log shows that recovery isn’t done at the time. Do NOT grant the runas accounts Domain Admin permissions.

Also could not get SQLAgent to start, but I don't know know that it's related to these events. Thus, the issue could be related to lack of permissions. I think I missed checking to see if I had supplanted the fact that SQL Express does not support SQL Agent, but the Enterprise does. One odd thing is that all other groups (sorry not sure the correct term) have keys in both and I can see the following which makes me believe it's using the

Posted on June 12, 2012 by Clint Huijbers I've encountered this annoying error which causes the SQL Agent Service to immediately stop after it is started. Join the community Back I agree Powerful tools you need, all for free. I have the 2 following entries:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\SQLServerAgentand this one:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER2100\SQLServerAgentHowever, only the first SQLServerAgent (non 2100) has any keys associated under it. Using SQL Server Management Studio, Review Settings Via SQL Server Management Studio, review SQL Server Agent Settings: We can clearly see the red mark by the Agent's icon.