Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter >
> 
> 
SCOM 2012 SP1 beta on Windows 2012 server with SQL 2012 SP1

Answered SCOM 2012 SP1 beta on Windows 2012 server with SQL 2012 SP1

  • Tuesday, December 04, 2012 9:28 PM
     
     
    Sign In to Vote
    0

    Hello,

    I'm trying to setup all these products on one server to meet them.

    Unfortunatly, I get this error when I setup SCOM 2012 SP1 beta management server.

    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.

    I have already done this step

    mofcomp.exe “<path>\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof”.

    What should I do more to setup Operational Database om SQL 2012 SP1 eval?

     

All Replies

  • Tuesday, December 04, 2012 9:44 PM
     
     
    Sign In to Vote
    0

    Please check the log file and see whether there's a clue there.

    As documented in this blog post: http://www.scom2k7.com/fix-scom-2012-install-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/

    Just out of curiosity which edition of SQL are you using?

    It's doing common things uncommonly well that brings succes.

     
  • Tuesday, December 04, 2012 10:33 PM
    Moderator
     
     
    Sign In to Vote
    0

    Hi

    I'm not sure the beta supports SQL 2012 SP1 as it was released prior to the SQL Service Pack. SCOM 2012 SP1 RTM will support SQL 2012 SP1.

    I'd suggest removing SQL 2012 SP1 and seeing if the install will proceed.

    SCOM 2012 SP1 isn't supported in production environments so lacking SQL 2012 SP1 shouldn't be an issue for a lab.

    Regards

    Graham

    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

     
  • Wednesday, December 05, 2012 4:38 AM
     
     
    Sign In to Vote
    0


    My full path was - mofcomp.exe “C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof” - and it didn't help me :(



     
  • Wednesday, December 05, 2012 4:42 AM
     
     
    Sign In to Vote
    0

    Hello, Graham

    On this page is said -

    http://technet.microsoft.com/en-us/library/jj656654.aspx

    Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server 2012, SQL Server 2012 SP1

    for Operational Database

    • Proposed As Answer by Alexis Yakovlev Wednesday, December 05, 2012 6:31 AM
    • Unproposed As Answer by Alexis Yakovlev Wednesday, December 05, 2012 6:31 AM
    •  
     
  • Wednesday, December 05, 2012 6:30 AM
     
     
    Sign In to Vote
    0
    Maybe it is as Graham Davies said, just try to install on SQL 2012 without SP1 and after SCOM installed.. apply SP1 for SQL 2012. 
     
  • Wednesday, December 05, 2012 6:32 AM
     
     
    Sign In to Vote
    0

    Hello, Graham

    On this page is said -

    http://technet.microsoft.com/en-us/library/jj656654.aspx

    Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server 2012, SQL Server 2012 SP1

    for Operational Database

    it's for SCOM 2012 SP1  and not for SCOM SP1 beta.
     
  • Wednesday, December 05, 2012 7:07 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi Artemiev

    SCOM 2012 SP1 beta was released nearly 2 months before SQL Server 2012 SP1 so it is very unlikely to have had any testing. SCOM 2012 SP1 will support SQL 2012 SP1 but not SCOM 2012 beta.

    Is this a problem? As SCOM 2012 SP1 beta is not supported in Production environments and should only be used in a lab, then the lack of support for SQL 2012 SP1 shouldn't really matter. The aim of the beta is to give customers a chance to look at the new release and provide feedback \ bug reports.

    Regards

    Graham

    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

     
  • Wednesday, December 05, 2012 7:52 AM
     
     
    Sign In to Vote
    0

    I've just tried to install to another server SQL.

    My colleague gets experience with SCCM 2012 + SQL 2012 (w/o SP1) on Windows Server 2012. But I can't connect to his SQL 2012 with same error.

    [11:48:19]: Always: :DatabaseConfigurationPage: Attempting to connect to database using server\instance CM12-1rc. If we need it, the port is 1433
    [11:48:19]: Debug: :MSSQLSERVER on server CM12-1rc is in a running state
    [11:48:19]: Info: :Info:Opening/Testing Sql Connection on CM12-1rc, port:
    [11:48:19]: Debug: :Connection was not open.  We will try to open it.
    [11:48:19]: Debug: :SqlConnectionReady returned True.
    [11:48:19]: Info: :GetSqlVersion: Collecting SQL Instance information for CM12-1rc
    [11:48:19]: Error: :GetSqlVersion(): Threw Exception.Type: System.Management.ManagementException, Exception Error Code: 0x80131501, Exception.Message: Invalid namespace
    [11:48:19]: Error: :StackTrace:   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
       at System.Management.ManagementScope.InitializeGuts(Object o)
       at System.Management.ManagementScope.Initialize()
       at System.Management.ManagementObjectSearcher.Initialize()
       at System.Management.ManagementObjectSearcher.Get()
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetSqlVersion(String sqlServerInstance)
    [11:48:19]: Always: :Current Version of SQL=0.0   Required Version=10.1.0.0
    [11:48:19]: Info: :Info:Using DB command timeout = 1800 seconds.
    [11:48:19]: Info: :Info:Using DB command timeout = 1800 seconds.
    [11:48:19]: Info: :The SQL Collation is valid.
    [11:48:19]: Info: :Info:DatabaseConfigurationPage: DB connection attempt completed.
    [11:48:19]: Info: :Info:DatabaseConfigurationPage: DB connection attempt completed.


    I can connect to SQL2008R2 w/o any problems
     
  • Wednesday, December 05, 2012 9:47 AM
     
     
    Sign In to Vote
    0

    The installator of SCOM 2012 (w/o SP1) can connect to the SQL 2012 SP1.

     
  • Thursday, December 06, 2012 7:21 PM
     
     
    Sign In to Vote
    0

    I've decided to begin testing the bindle - Windows server 2012 + SQL 2012 SP1 + SCOM 2012 (w/o SP1 beta)

    May be I'll get some problems. I'll see.

     
  • Monday, December 31, 2012 7:28 PM
     
      Has Code
    Sign In to Vote
    0

    Ok, with this configuration: Server 2012 + SQL 12 SP1 + SCOM 12 (No SP1), I still get the following error:

    Error:	:GetSqlVersion(): Threw Exception.Type: System.Management.ManagementException, 
    Exception Error Code: 0x80131501, Exception.Message: Invalid namespace

    
     
  • Monday, December 31, 2012 8:34 PM
    Moderator
     
     
    Sign In to Vote
    0

    Hi

    This is NOT a supported configuration. SCOM 2012 (not SP1) does not work on WINdows Server 2012 \ SQL 2012.

    Please read the documentation.

    http://technet.microsoft.com/en-us/library/jj656649.aspx

    Regards

    Graham

    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

     
  • Saturday, January 19, 2013 8:07 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hi

    I'll just update and close this thread with the SP1 RTM details now that SP1 is Generally Available. SQL Requirements:

    http://technet.microsoft.com/en-us/library/jj628198.aspx

    Cheers

    Graham

    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/