Tuesday, January 29, 2013 6:38 PM
I am attempting to install SCOM 2012 SP1 on Server 2012 using SQL Server 2012. SQL and SCOM are on the same machine SYSTEMCENTER. This machine also has WSUS installed. I used the default SQL instance name. This is a fresh SQL install. In the setup wizard I enter in SYSTEMCENTER\MSSQLSERVER when prompting for DB locations. I have setup up an account on our domain controller for Data Reader/Write account. I am using Local System accounts for both Managment server action account and service/access account. I setup up SQL Server 2012 to be Windows Authentication rather than mixed mode because someone else had sucess with this. Can this confriguration be done? SCOM SP1 now supports Server 2012. All prerequisites have been applied and the wizard passes this test.
My install fails in the same way as this below post.
Key error messages: if you want to see the full log I can attach
No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
ProcessInstalls: Running the PostProcessDelegate for OMDATABASE failed.... This is a fatal item. Setting rollback.
Tuesday, January 29, 2013 6:46 PMModerator
If you are using the default SCOM instance then just type in the server name - do not append \MSSQLServer.
Personally, I'd always set up with domain accounts:
Tuesday, January 29, 2013 9:39 PM
Thanks for the response.
Removed \MSSQLServer from DB names.
Used all domain accounts for all services.
When doing the install and reviewing the TechNet Article with the installation guide. I did not install the 'Reporting' role on SCOM. When I selected this and attempted to select a DB instance from the drop down box nothing showed up. (Step 15) Otherwise I have followed the steps as outlined in the guide.
Same error messages in the log file as before. Stills seems to be getting stuck at the same thing. My guess it is something with SQL. Turn off windows firewall even through it is on the same machine?
- Edited by OctopusTwo Tuesday, January 29, 2013 9:40 PM
Wednesday, January 30, 2013 7:00 AM
Make sure that the SQL reporting service is installed before you select Reporting role in SCOM installation
Wednesday, January 30, 2013 7:23 PMI did not select this role to be installed and I still get errors.
Wednesday, January 30, 2013 7:28 PMModerator
Make sure the SQL Server Agent service is running - it is manual by default but is required for the install.
I understand that the SQL Server is remote from the Management Server? Make sure you have SQL SysAdmin rights (as it will be your account that creates the databases) and local windows admin rights on the SQL Server.
Thursday, January 31, 2013 5:04 AMModerator
Please try again with the command method:
Installing Operations Manager by Using the Command Prompt Window
Please check the log file; if there are any other related errors, please let us know.
TechNet Community Support
Thursday, January 31, 2013 6:11 PM
SQL Server is installed on the same machine as planned Operations Manager. Nothing is remote.
jjbadmin is a domain admin account
Log file in: C:\Users\jjbadmin\AppData\Local\SCOM\LOGS
OpsMgrSetupWizard.log (only displayed errors)
[12:28:06]: Always: :ImportManagementPack: Loading management pack G:\Setup\AMD64\MPLP\Microsoft.SystemCenter.WebApplicationSolutions.Library.Resources.enu.mpb. 12:28:06
[12:28:06]: Error: :ImportManagementPack: Unknown Error. Microsoft.Deployment.WindowsInstaller.InstallerException : The system cannot open the device or file specified. Database="G:\Setup\AMD64\MPLP\Microsoft.SystemCenter.WebApplicationSolutions.Library.Resources.enu.mpb"
[12:28:06]: Error: :Error:FirstManagementServer: Failed to load MP G:\Setup\AMD64\MPLP\Microsoft.SystemCenter.WebApplicationSolutions.Library.Resources.enu.mpb on retry number 3
[12:28:06]: Error: :Error:FirstManagementServer: Gave up trying to load the MP G:\Setup\AMD64\MPLP\Microsoft.SystemCenter.WebApplicationSolutions.Library.Resources.enu.mpb
[12:28:06]: Error: :Error:failed to import Server management packs. This is a fatal error
[12:28:06]: Error: :FATAL ACTION: ImportManagementPacks
[12:28:06]: Error: :FATAL ACTION: DatabaseActions
[12:28:06]: Error: :ProcessInstalls: Running the PostProcessDelegate returned false.
[12:28:06]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Database Configuration
[12:28:06]: Error: :ProcessInstalls: Running the PostProcessDelegate for OMDATABASE failed.... This is a fatal item. Setting rollback.
[12:28:06]: Always: :!***** Installing: OMSERVER ***
[12:28:06]: Info: :ProcessInstalls: Rollback is set and we are not doing an uninstall so we will stop processing installs
Looks like it could not find: Microsoft.SystemCenter.WebApplicationSolutions.Library.Resources.enu.mpb It tried this 3 times.
Script being used:
setup.exe /silent /install /components:OMServer,OMConsole,OMWebConsole /ManagementGroupName: "GS_Production" /AcceptEndUserLicenseAgreement:1 /SqlServerInstance: SYSTEMCENTER /DatabaseName: OperationManager /DWSqlServerInstance: SYSTEMCENTER /DWDatabaseName: DWDatabaseName /UseLocalSystemActionAccount /UseLocalSystemDASAccount /DatareaderUser: newberlin\operations /DatareaderPassword: operations /DataWriterUser: newberlin\operations /DataWriterPassword: operations /WebSiteName: "Default Web Site" /WebConsoleAuthorizationMode: Mixed /SendODRReports: 0 /EnableErrorReporting: Never /SendCEIPReports: 0 /UseMicrosoftUpdate: 0
File does exist on installation media?
Monday, February 04, 2013 7:27 PM
Had a chance to look at this more. My above install was from TechNet as a mounted in ISO in 2012. I then logged into Action Pack/Microsoft Partner Network and downloaded this same file again. Same exact size down to the byte. Again mounted this as an ISO. Ran the installer again using this new media and it ran with success on the first try. So always ensure the installation media is not corrupt. Usually when this happens the installer does not work at all, never have it seen it where only 1 file was at fault/corrupt. Learn something new everyday.
Thanks again for anyone who responded.