SQL Server Version issue with SCOM 2012 SP1 upgrade?
-
Friday, January 18, 2013 6:01 PM
Hello,
I was running both SCCM 2012 RTM and SCOM 2012 RTM with a SQL 2008 R2 server. I upgraded SQL 2008 R2 to SQL 2012 CU5, and upgraded SCCM 2012 to SP1. Today I tried to upgrade SCOM 2012 to SP1 but when the prerequisite checker came up I was told that The Installed version of SQL Server is not supported for the operational and data wharehouse databases.
SCOM 2012 RTM is still functioning properly and is connecting to the updated SQL 2012 server. Per the System Requirements guide for SCOM SP1 it does state that SQL Server 2012 is supported so I am not sure where the problem lies. The SQL server does not live on the same server as my SCOM servers; whereas it does reside on the SCCM server. Does something additional need to be done for the installer to connect and verify requirements from the SQL server that differed from SQL 2008 R2?
Any help on this would be appreciated.
All Replies
-
Friday, January 18, 2013 6:06 PMModerator
Hi
SCOM 2012 RTM does not support SQL 2012 - the problem you might be facing is that the SCOM 2012 upgrade to SCOM 2012 SP1 doesn't recognise an existing supported SQL version.
Do you have the log file for the pre-install check? Can you post it up.
Thanks
Graham
Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/- Edited by Graham DaviesMVP, Moderator Friday, January 18, 2013 6:06 PM
-
Friday, January 18, 2013 7:12 PM
Hello Graham,
Thank you for the information. I am unable to post the log directly to the thread as my account isn't verified yet. I have uploaded the logs to my dropbox though. You can take a look at them here:
https://www.dropbox.com/s/k463sr9jqpb1o6u/SCOMPrereqCheck.log
Looking for things regarding SQL it doesn't seem to even really know where SQL is located but maybe I am reading the log wrong. Any assistance you can provide after review would be appeciated!
- Edited by xoit Friday, January 18, 2013 7:18 PM
-
Friday, January 18, 2013 7:23 PMModerator
Hi
The failures in the pre-req log are:
<Result StatusCode="2">
<Id>52E3A4CC-9A5A-4663-B2BE-BE8F4830938A</Id>
<Status>Failed</Status>
<Check>OMDBSqlVersionCheckTitle</Check>
<Components>
<Component>OMSERVER</Component>
</Components>
<Description>OMDBSqlVersionCheckFailed</Description>
<Resolution>OMDBSqlVersionCheckResolution</Resolution>
<LogInformation><![CDATA[CheckPrerequisites: Logic Type:and IsValidOMDBSQLVersionCheck: 2]]></LogInformation>
</Result>
<Result StatusCode="2">
<Id>2B781195-DA11-4F39-8899-4D1B2A4A926F</Id>
<Status>Failed</Status>
<Check>OMDWSqlVersionCheckTitle</Check>
<Components>
<Component>OMSERVER</Component>
</Components>
<Description>OMDWSqlVersionCheckFailed</Description>
<Resolution>OMDWSqlVersionCheckResolution</Resolution>
<LogInformation><![CDATA[CheckPrerequisites: Logic Type:and IsValidOMDWSQLVersionCheck: 2]]></LogInformation>
</Result>At this stage it is checking existing infrastructure and I suspect that because SQL 2012 is not supported for SCOM 2012, it is throwing an invalid SQL version error. If that is the case then there won't be a supported way that we can help - even with a MSFT support engineer there might not be a way other than restoring a backup to a SQL 2008 R2 server which is going to be a lot of administrative work. You might want to wait to see if anyone else has seen this and found a workaround or you might want to look for MSFT support sooner rather than later.
Sorry I can't be of more help.
Regards
Graham
Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/ -
Friday, January 18, 2013 9:26 PM
Hi Graham,
I reverted back to my previous SCCM RTM with SQL 2008 R2 SP1 on it. I attempted to re-run through the OM 2012 SP1 installer and I am getting the same error message as before. Looking at the log file it is failing with the same output. I even tried upgrading SQL to 2008 R2 SP2 with no luck. I will attempt to open a case with Microsoft and see if they can assist.
- Proposed As Answer by Dancing Ferret Monday, January 21, 2013 12:41 PM
- Unproposed As Answer by Dancing Ferret Monday, January 21, 2013 12:41 PM
-
Saturday, January 19, 2013 6:50 AMModerator
Hi
It isn't something I have seen before and as no-one else has posted I guess this isn't common.
It would be useful if you could update when the issue is resolved to help anyone who has this in the future.
Cheers
Graham
Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/ -
Monday, January 21, 2013 12:44 PM
Hi Graham,
I reverted back to my previous SCCM RTM with SQL 2008 R2 SP1 on it. I attempted to re-run through the OM 2012 SP1 installer and I am getting the same error message as before. Looking at the log file it is failing with the same output. I even tried upgrading SQL to 2008 R2 SP2 with no luck. I will attempt to open a case with Microsoft and see if they can assist.
I just had the same issue (SCOM 2012 SP1 upgrade) and it wasn't anything to do with SQL. My Win 2008 R2 Ent. installation hadn't upgraded to SP1. Once SP1 was installed the 2 SQL error checks disappeared. My fault for not checking it, but MS once again throwing up errors not related to what the actual issue is.
Hope this helps.
-
Monday, January 21, 2013 4:34 PM
Dancing Ferret, thank you for posting your fix. I should have stuck with a more established server when I did my SCOM 2012 installation...I went with Server 2012 as I figured it would be a good test to see if I could learn the new OS while installing a new product in our environment. Doesn't seem like any kind of SP exists for 2012 at this point but I will ensure that everything is patched on the server and see if it helps. Still waiting for Microsoft to get back to me via the email case I opened. Will update once I know how to move forward.
-
Monday, January 21, 2013 5:30 PM
SCxx SP1 (where xx is all the system centre products) supports Windows Server 2012 and 2012 Core, I suspect what you will need is the Product with SP1 intergrated and not a seperate service pack, to do the install. Not checked if it's available as a download yet, but i don't think it will be to long from now.
While i've not tried it and it will be long winded, i'm sure with some pitfalls, you could always do a win 2008 R2 Sp1 build, then install your product with SP1 (say SCOM) and then upgrade your server to Win 2012, if server 2012 is what you want to play with. Bare in mind that the idea of server 2012 going forward is not to log onto the server to do your work like previous versions. MS are pushing remote support eg: Win 8 with RSAT tools or SCOM admin console etc installed, then doing all your support from the Win 8 wrkstation.
If server 2012 is what you want to play with I would suggest just building a 2012 server\ environment and playing, you wouldn't get much learning benefit from using SCOM etc on a 2012 server. If hardware etc is an issue build a Win 8 workstation, install Hyper V (built into Win 8 now) and build a 2012 DC and single 2012 server.
http://technet.microsoft.com/en-gb/library/jj656654.aspx
-
Monday, January 21, 2013 5:37 PMModerator
Hi
There is no seperate "just service pack" download and won't be. The iso is the full SCOM 2012 SP1 product. Running that will detect if an install already exists and try to upgrade it.
As this is an upgrade there isn't the option to go the windows 2008 R2 and then upgrade in place to Windows Server 2012 ...
To the original poster - you mention - " I should have stuck with a more established server when I did my SCOM 2012 installation...I went with Server 2012 - do you have SCOM 2012 running on Windows Server 2012? If so, this isn't a supported. SCOM 2012 requires Windows Server 2008 (or 2008 R2).
It might help to list your exact SCOM architecture with OS \ SQL versions.
Cheers
Graham
Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/ -
Monday, January 21, 2013 5:50 PM
I'm intrigued why you wouldn't be able to do an OS upgrade at some point later down the line, if your installation is Win 2008 R2 and you later move to Server 2012.
When I get a little free time, I'm going to test it :) . Joys of a virtual lab environment.....
-
Monday, January 21, 2013 6:01 PMModerator
My understanding from their comment - " I should have stuck with a more established server when I did my SCOM 2012 installation...I went with Server 2012" is that the current install is already deployed and is on Windows Server 2012 ... so it isn't an option to use Windows 2008 R2 .. the Windows Server 2012 environment is already there. Sadly SCOM 2012 was not supported on Windows Server 2012 which might cause problems with MSFT support.
An in place upgrade of the OS is certainly (in general) an option as is an in place upgrade of SQL, though be aware of a gotcha with SQL RS:
http://thoughtsonopsmgr.blogspot.co.uk/2013/01/om12-sp1-upgrading-sql-server-2008-sp1.html
Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/ -
Monday, January 21, 2013 6:13 PM
My understanding from their comment - " I should have stuck with a more established server when I did my SCOM 2012 installation...I went with Server 2012" is that the current install is already deployed and is on Windows Server 2012 ... so it isn't an option to use Windows 2008 R2 .. the Windows Server 2012 environment is already there. Sadly SCOM 2012 was not supported on Windows Server 2012 which might cause problems with MSFT support.
An in place upgrade of the OS is certainly (in general) an option as is an in place upgrade of SQL, though be aware of a gotcha with SQL RS:
http://thoughtsonopsmgr.blogspot.co.uk/2013/01/om12-sp1-upgrading-sql-server-2008-sp1.html
Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/ahh ok, with you... :)
My comments were also a just " you could try this as a new installation" as i assumed he didn't have a working setup yet....
Just kicking the OS upgrade off now, purely to see what breaks more than anything ( upgrade not on the SQL server, as I want to test upgrade to both SQL 2012 then Server 2012)
Update: OS upgrade complete and SCOM looking good...no up grade errors in SCOM or OS...- Edited by Dancing Ferret Monday, January 21, 2013 7:22 PM
-
Monday, January 21, 2013 6:55 PM
Hi xoit,
Firstly, what is the OS of the SQL server? It has to be a minimum of 2008 R2 SP1 to support SCOM 2012 SP1 and the installer will block if it detects an OS below this.
Assuming this is not the issue, are you able to create or do you already have access to another SQL 2008 R2 server?
As long as the collation is supported, you could follow the procedure to move the Ops and DW databases to this server (http://technet.microsoft.com/en-us/library/hh278848.aspx and http://technet.microsoft.com/en-us/library/hh268492.aspx), perform the upgrade and then move the DBs back to the SQL 2012 server on completion.
Quite a bit of work but should do the trick.
Regards
Steve
- Marked As Answer by xoit Tuesday, January 22, 2013 10:55 PM
-
Tuesday, January 22, 2013 10:57 PM
Hi Steve,
I spoke with Microsoft regarding this issue today and they narrowed it down to the OS that SQL 2008 R2 was running on. We are running our SQL server on Windows 2008 SP2 which is supported for SCOM RTM but not for SP1. Really sucks that this is what is preventing the upgrade as I don't think doing an upgrade from 2008 SP2 with SQL and SCOM installed on a server would go very well trying to upgrade inplace to 2008 R2.
- Edited by xoit Tuesday, January 22, 2013 10:59 PM
.png)
