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

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

Contents

Please enter a comment. I can however say that the message can safely be ignored as long as the Agent account is able to start successfully after the message. Comments (10) | Workarounds (1) | Attachments (0) Sign in to post a comment. Please let us know if you would be willing to validate this fix on your test systemsThanksSethu Srinivasan [MSFT]SQL Serverhttp://blogs.msdn.com/sqlagent Posted by Jeff_S_Kelly on 4/9/2012 at 6:36 PM Duplicating the reg Check This Out

Category: sql server dbengine Question ETL-James on Mon, 07 Jan 2013 19:06:50 I am attempting to start SQL Server Agent and I receive this error (from event log): - Check the ErrorLogFile value under the instance registry key. Franco Platania Pastor Darrell Scott Pastor Doug Batchelor Graham Cooke J.C. Thanks!ReplyLeave a Reply Cancel reply Pinal Dave is a technology enthusiast and an independent consultant. https://community.spiceworks.com/topic/1065590-sql-server-agent-not-starting-properly

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

My first step was to look at trusty old Windows Application Event Viewer to see what messages get logged when I try to start the SQL Server Agent Service. Resolution - sp_configure? SQLAuthority.com Skip to content Learning in the Open Menu Blogging WordPress Books Authors Caitríona Palmer David Brooks Francis Collins Richard Paul Evans Culture Life Leadership Music Singers Bruce Springsteen J. I do not know what to do.

A more detailed explanation for the resolution of this particular item may have been provided in the comments section. 8 0 Sign into vote ID 730575 Comments 8 Status Closed Workarounds Thanks Latest posts in the category COLUMNS_UPDATED() Returning Unexpected Results Database email issue for an maintenance work Troubleshooting deadlocks - they dont happen for very long Inactive Transactions Not Clearing up The red mark states that "Agent XPs disabled". Sqlserver Error: 229, The Execute Permission Was Denied On The Object 'sp_sqlagent_update_agent_xps Have not upgraded from RC0 to RTM on other prod nodes yet.

Submit Posted by Stefan Prodan Dev on 12/17/2012 at 1:33 AM After applying SP1 for SQL Server 2012 I get the same error in event log but the SQLAgent does start Event Id 324 Opensqlserverinstanceregkey:getregkeyaccessmask Failed (reason 2) Errors appear to be logged whenever SQLAgent service starts, maybe triggered on other events (failovers?) because I think we have more of these than we have service restarts. I would not be http://connect.microsoft.com/SQLServer/feedback/details/730575/sqlserveragent-wont-start-after-2012-rtm-upgrade http://clinthuijbers.wordpress.com/2012/06/12/ms-sql-server-2012-error-opensqlserverinstanceregkeygetregkeyaccessmask-failed-reason-2/ Frank Tom Phillips on Mon, 07 Jan 2013 20:28:14 Please look at the SQLAGENT.OUT in the SQL Server instancelog directory for the actual SQL Agenterror message. Run the RECONFIGURE statement to install. 2013-01-07 13:36:19.04 spid51 Configuration option 'Agent XPs' changed from 0 to 1.

Post to Cancel %d bloggers like this: Toggle navigation Questions and Answers Azure development Sql Azure C# Sharepoint Best gaming deals on Amazon This weeks Xbox deals with gold How to The Sql Server Agent Started And Then Stopped Under Group or user names, select or add a group or user; in our case " At the bottom, choose to effect the available permissions. Select the Failed check box for the actions you want to audit, and then click OK. Home Dashboard Directory Help Sign in SQL Server Home Downloads Feedback Surveys Thank you for your feedback!

Event Id 324 Opensqlserverinstanceregkey:getregkeyaccessmask Failed (reason 2)

Diagnosis MS Windows Event Log Here is what the Event Log has to say: Textual: Event ID: 324 Text: Failed to initialize SQL Agent log (reason: Access is denied). Submit Posted by Launchy on 6/17/2012 at 6:34 PM As highlighted by Dan Guznam, Check the path for the error log. Sql 2012 Opensqlserverinstanceregkey:getregkeyaccessmask Failed (reason: 2). Join Now I have a Windows Server 2012R2 Box running SQL Server 2012 and we need to get the SQLSERVERAGENT running.  It starts then immediately stops with the following error OpenSQLServerInstanceRegKey:GetRegKeyAccessMask Opensqlserverinstanceregkey:getregkeyaccessmask Failed (reason: 2). Sql Express Leave new Arunabh March 31, 2016 12:28 pmHi Pinal, Is it necessary to configure these parameters being an ‘sa' user or any non-sysadmin user can also configure them?

share|improve this answer answered Sep 25 '14 at 12:51 mbonness 53169 Did not work for me. his comment is here Along with 14+ years of hands on experience he holds a Masters of Science degree and a number of database certifications. Not too worried about any security implications of making the service accounts the same for both engine and agent, as it's my local dev workstation... What happens to the local server after that is to me rather irrelevant. Sql Server Agent Not Starting In Sql Server 2012 Express

This will allow you to know which account has permission issues when a SQL Server service cannot start up successfully. The default instance key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\SQLServerAgent Posted by Capa on 3/23/2012 at 1:01 PM Me too... The SQLAGENT.OUT file didn't exist in the Log path, mentioned in an earlier answer. this contact form Please help!

Why is my scene rendered repeatedly when I press F12? The Process Terminated Unexpectedly 0x8007042b In the left pane, click Audit Policy to display the individual policy settings in the right pane. 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.

if I had not seen 730575"--why, what are the implications?I have one instance of SQL Server 2012, Standard 64-bit, CU2.

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 Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? ETL-James on Mon, 07 Jan 2013 22:05:18 This file was locked. Sql Server 2012 Sp1 Submit Posted by Krish_12 on 11/25/2013 at 6:23 AM SQL Agent has corrupted.

Now very concerned. Until 730575 gains traction (so far no response), I cannot see moving to RTM. the default instanceID was 'MSSQLSERVER2100', and that's what i went withI also see this value in the registry similar to what Dan Guzman posted. 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. http://technologyprometheus.com/sql-server/the-service-did-not-start-due-to-a-logon-failure-windows-2012.html Ryle J.D.

Event ID is 324 I found that if I run it with the Admin username and password it will run but we need it to run as a Local System Account As our error is security related, we will focus in on the Security Logs. share|improve this answer answered Aug 3 at 3:38 SimonB 1 add a comment| up vote 0 down vote I restart the computer three times, and find that though the Server Agent Greear Jacob Prasch Jim Bakker Jim Cymbala Leonard Ravenhill Lester Sumrall Mary Peckham Oral Roberts Pastor Max Lucado Pastor John K.

When I renamed it, I was able to start the agen successfully. more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Attach a file Microsoft Connect Terms of Use Trademarks Privacy Statement © 2016 Microsoft Please wait... 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

I cannot find the dbo.sp_get_sql_agent_properties even logging in as SA.