As with the previous post where I upgraded SCCM SQL from 2008 to 2014, I did the same with System Center Operations Manager.
You need to make sure that SQL 2008 is on SP2 and that SQL 2012 is on SP1 or the upgrade will fail on the checks.
After I upgraded these I proceeded to do the upgrade and received an error about custom security settings within SSRS.
I made a copy of the reportserver.config file and then removed all the authentication and security info in the config file. I then ran the checks again and it passed.
SQL 2008 was upgraded to SQL 2014. After the reboot SCOM opened but I received an error on reporting.
I ran the setup for SCOM, removed the reporting feature and then rebooted. After the reboot I went into SQL Reporting and configured it again, pointing to the correct report DB’s for SCOM.
I then re-ran the SCOM setup and installed the Reporting Feature, after the last reboot I was able to login to SCOM and run reports.
I don’t think that SQL 2014 with SCOM 2012 R2 is really supported yet but I wanted to write about this for anyone who wants to test it.
Hope it helps
Installing of SCOM 2012 has some requirements and one of them being SQL. I ran the install for SQL and when I tried to install SP1 for SQL 2008 R2 it failed with the following error:
- ” A failure was detected for a previous installation, patch, or repair for instance ‘MSSQLSERVER’. In order to apply this patch package, you must resolve any issues with the previous operation that failed. View the summary.txt log to determine why the previous operation failed.”
So I went to Programs and Features and ran a repair on SQL. Upon getting to 80% of the repair it gave this error:
- “The following error has occurred: The process cannot access the file ‘C:\Windows\system32\perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll’ because it is being used by another process.
- Click ‘Retry’ to retry the failed action, or click ‘Cancel’ to cancel this action and continue setup.”
So I checked and all services were stopped. The fix is to stop the Windows Management Intrumentation Service and all the dependencies. After that the repair will go through successfully and you will now be able to install SP1 for SQL.
Hope it helps
Yesterday I downloaded System Center Data Protection Manager 2012 R2. I extracted the ISO file and started the splash screen.
Upon clicking the link to install DPM another screen similar to the earlier versions appears and you click next. With this install you have the option to install using SQL local or clustered.
If you choose local it defaults to the SQL instance created by DPM 2012 (unless you changed it)
When I clicked Check and Install the checks run through and then DPM 2012 R2 fails with an error that the SQL instance is not valid.
When I checked the logs I noticed it was complaining about the protocol TCP. I went to SQL Configuration Manager and I got the same WMI error saying it couldnt open. I then opened up and elevated prompt and ran the following:
mofcomp.exe “C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof”
After that I could open up SQL Configuration Manager, I enabled TCP for the SQL instance and then restarted all the services. I then went back to the DPM 2012 R2 install and clicked the Check Again button and voila, DPM 2012 R2 upgraded my existing DPM installation and completed successfully.
Hope it helps.