Solved

SCOM 2012 Beta Install: SQL Instance / WMI Errors / EvtID 4656

Posted on 2011-09-23
3
1,866 Views
Last Modified: 2012-05-12
I am trying to install System Center 2012 beta on any server in our environment that will take the installation.  Thusfar all my attempts to install the software have been thwarted by the dreaded WMI error.

I have a Windows 2008 R2 Standard 64bit server SP1 (fully patched) on a VM with SQL 2008 R2 SP1.  SQL has every single feature installed that is available at installation time.  The installations are all being performed with a domain admin account.  I installed all the required options for IIS, .NET (3.5 and 4) and made all the required IIS configuration changes.  SQL server 2008 has been installed with the collation of SQL_Latin1_General_CP1_CI_AS.  All the prereq checks pass.  

When I get to the part of the install that asks for the database, I put in the name of the server or localhost and I am greeted with this error:

The version of SQL Server on this computer is either not supported or could not be validated because of an issue connecting to the WMI provider. For a complete list of the supported SQL Server versions and editions, see "Operations Manager 2012 Supported Configurations" in the TechNet library.


Whenever I change the name of the SQL server and it rechecks, I also see a failure audit pop up in the security event log:

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          9/22/2011 5:13:30 PM
Event ID:      4656
Task Category: Other Object Access Events
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      <MY SERVER NAME>.<MY DOMAIN>.com
Description:
A handle to an object was requested.

Subject:
    Security ID:        NETWORK SERVICE
    Account Name:        <MY SERVER NAME>$
    Account Domain:        <MY DOMAIN NAME>
    Logon ID:        0x3e4

Object:
    Object Server:        SC Manager
    Object Type:        SERVICE OBJECT
    Object Name:        MSSQLSERVER
    Handle ID:        0x0

Process Information:
    Process ID:        0x218
    Process Name:        C:\Windows\System32\services.exe

Access Request Information:
    Transaction ID:        {00000000-0000-0000-0000-000000000000}
    Accesses:        Query service configuration information
                Query status of service
                Query information from service
               
    Access Reasons:        -
    Access Mask:        0x85
    Privileges Used for Access Check:    -
    Restricted SID Count:    0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>4656</EventID>
    <Version>1</Version>
    <Level>0</Level>
    <Task>12804</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-23T00:13:30.896852400Z" />
    <EventRecordID>5027759</EventRecordID>
    <Correlation />
    <Execution ProcessID="544" ThreadID="576" />
    <Channel>Security</Channel>
    <Computer><MY SERVER NAME>.<MY DOMAIN>.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-5-20</Data>
    <Data Name="SubjectUserName"><MY SERVER NAME></Data>
    <Data Name="SubjectDomainName"><MY DOMAIN></Data>
    <Data Name="SubjectLogonId">0x3e4</Data>
    <Data Name="ObjectServer">SC Manager</Data>
    <Data Name="ObjectType">SERVICE OBJECT</Data>
    <Data Name="ObjectName">MSSQLSERVER</Data>
    <Data Name="HandleId">0x0</Data>
    <Data Name="TransactionId">{00000000-0000-0000-0000-000000000000}</Data>
    <Data Name="AccessList">%%7184
                %%7186
                %%7191
                </Data>
    <Data Name="AccessReason">-</Data>
    <Data Name="AccessMask">0x85</Data>
    <Data Name="PrivilegeList">-</Data>
    <Data Name="RestrictedSidCount">0</Data>
    <Data Name="ProcessId">0x218</Data>
    <Data Name="ProcessName">C:\Windows\System32\services.exe</Data>
  </EventData>
</Event>  



Here are all the things I have tried to correct this problem.

1.  mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof

2.  I tried to install the authorization hotfix mentioned in the supported configurations doc, but the patch says I don't need it.

3.  Confirmed the collation is correct, SQL_Latin1_General_CP1_CI_AS.

4.  Added the installing account to all the SQL accounts on the server.

5.  Added LC permission to the service manager for Authenticated Users.  (http://arnoutboer.nl/weblog/?p=300)

6.  Confirmed all the approriate SQL services are started. (Agent, Browser, Etc.)

7.  Firewall is off

8.  Confirmed the SQL port is listening with a netstat -an

9.  Try installing SCOM 2007 R2, it fails on the database as well with the same entry into the security log.

10. I tried doing all of the same things above on physical server, running Windows 2008 R2 Enterprise (fully patched) with with SQL 2008 R2 SP1 and received the same results, even the security log entries.

11.  Ran "%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -r"


I have extensively reviewed these links:

Operations Manager 2012 Supported Configurations
http://technet.microsoft.com/en-gb/library/hh205996.aspx

Operations Manager 2012 Supported Configurations
http://technet.microsoft.com/en-us/library/hh205990.aspx#BKMK_RBF_ManagementServer

SCOM 2012 Beta Install wizard can not find the SQL server/instance while installing
http://social.technet.microsoft.com/Forums/en-US/operationsmanagerdeployment/thread/a98dd80b-af85-4d41-b06f-20255d4bf083

SCOM 2012 beta first install
http://www.bictt.com/blogs/bictt.php/2011/07/20/scom-2012-beta-first-install


I am totally stuck, what do I need to do to fix this?
0
Comment
Question by:logicb0mb
  • 2
3 Comments
 
LVL 78

Expert Comment

by:David Johnson, CD, MVP
Comment Utility
It needs SQL Server 2008SP1 (not sp2 and not 2008R2) this is an annoyance with these beta's
0
 
LVL 1

Accepted Solution

by:
logicb0mb earned 0 total points
Comment Utility
We figured this out.

SQL Server 2008 R2 works just fine.  

The problem that we were trying to use the eval version, that didn't seem to work.  Reinstalling with a full version from MSDN did the trick for us.

--logicb0mb
0
 
LVL 1

Author Closing Comment

by:logicb0mb
Comment Utility
SCOM is working now, after installing a non eval version of SQL 2008 R2.
0

Featured Post

Are your corporate email signatures appalling?

Is it scary how unprofessional your email signatures look? Do users create their own terrible designs and give themselves stupid job titles? You can make this a lot easier for yourself by choosing an email signature management solution from Exclaimer today.

Join & Write a Comment

Sometimes drives fill up and we don't know why.  If you don't understand the best way to use the tools available, you may end up being stumped as to why your drive says it's not full when you have no space left!  Here's how you can find out...
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now