Tag: troubleshoot

Installation of SCOM 2012 fails with Error: :LaunchMSI: MSI D:\Setup\AMD64\Server\OMServer.msi returned error 1618

I’ve ran into a strange error during recent installation of OpsMgr 2012 SP1. I’ve started the installation as usual and I’ve entered the configuration installation. Somewhere in the middle of the installation after the importing of the management packs in OperationsManager database I’ve received this screen:

image

I’ve opened the logs and I’ve found the error listed:

[XX:XX:XX]: Error: :LaunchMSI: MSI D:\Setup\AMD64\Server\OMServer.msi returned error 1618

I’ve tried to search for this error with installation of SCOM but couldn’t find results. Than I’ve realized that this is a MSI error and I’ve found this article:

http://support.microsoft.com/kb/229683

Cause was so simple:

image

Without trying to search which installation was running in the background I’ve restarted the server and after the restart OspMgr 2012 server was installed without issues.

Keep in mind that in your situation may be it is better to find what is being installed on the background and wait till it finishes if it is possible.

Such general error could happen even if you are installing SCOM console or an agent.

Re-install SCOM 2012 SP1 Agent on your SCSM SP1 Management Servers – Updated

As most of you probably know SCSM 2012 SP1 comes with built-in SCOM 2012 SP1 agent. You juts install your SCSM SP1 management server and late you can configure your SCOM 2012 SP1 agent from the control panel. So far seems good but there could be situation where your SCSM management server is working normal and your SCOM agent is failing for some reason. So one of the solution would probably be to re-install the SCOM agent right? But how to do that as SCSM management server and the SCOM agent are connected tightly? The solution is to reinstall the SCSM management server. Heavy task but at least there is a solution. So here are the general steps you need to follow to do that:

1. Backup your SCSM management server.

2. Backup the encryption key of the SCSM management server.

3. Uninstall the SCSM management server from Control Panel.

4. Remove any registry keys left from the installation. Examples:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MOMConnector
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OpsMgr Config Service
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OMCFG
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OMSDK
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OpsMgr Config Service Per Agent
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OpsMgr SDK Service
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\System Center Management APM

5. Install SCSM 2012 SP1 management server again with the encryption key you’ve backed up.

6. Configure SCOM SP1 agent from the Control Panel.

This information was provided by Travis Wright – PM @ Microsoft. Thanks Travis for the support. I haven’t tested this but if you are in such situation and you have backup do not be afraid to try it.

————————–UPDATE———————————————–

After some discussions with community members we discovered that SCSM 2012 Self Service Portal SP1 role does not install builtin SCOM agent. The only way to install SCOM agent is to do it prior installing SSP role. Of course to re-install the agent will mean that you have to remove SSP role, re-install the SCOM agent and install SSP role. But be careful with that approach because you may loose some portal customizations you have done. Also I am not sure if MSFT will support such approach of installing the SCOM agent prior SSP role. I would recommend to monitor that server agentless.

I’ve also spoke to Travis Wright and he stated that SCSM team does not have plans to add bultin SCOM agent on the SSP role in any of the future URs.

System Center 2012 SP1 Configuration Analyzer

There is a new troubleshooting tool on the System Center horizon. This tool combines Best Practice Analyzers for the different System Center components. Keep in mind that the tool troubleshoots only server-side issues. In order to use it you have to install Microsoft Baseline Configuration Analyzer 2.1 also. Download the tool from here.

Fixing non-compliant virtual switches in System Center 2012 Virtual Machine Manager

This article in SCVMM Team blog shows how much Virtual Machine Manager evolved from 2008 R2 to 2012. In past versions any errors appearing on virtual machines or hosts couldn’t be repaired trough VMM. Now with 2012 there are errors that can be fixed with just one click. Read this useful article here.

KB: How to increase the timeout for Migration Jobs in System Center 2012 Virtual Machine Manager

Sometimes live migration job can take longer than 30 minutes depending on the virtual machine you migrate and the network. If the job passes 30 min limit that job is terminated. Of course if you have such long jobs you can actually increase that time out value. To find out how look here.