I am just troubleshooting a failing SCOM 2012 SP1 (System Center 2012 - Operations Manager) setup which cannot connect to database server. The setup GUI wizard doesn't let me proceed further than to specify the database server name and instance. Is there any log file of that would tell me better what's happening inside? Yes.
%LOCALAPPDATA%\SCOM\LOGS\OpsMgrSetupWizard.log
Later, you may also want to check the OMSERVER.MSI log file:
%LOCALAPPDATA%\SCOM\LOGS\OmSever.log
Ok. Now I have it resolved. So what did I learn?
The real minimum database server requirements for SCOM 2012 SP1
Not that Microsoft would like to make your work difficult intentionally, but in the world of System Center, the documentation, and especially one concerning any security related problems in a secure environments is very limited. So what you really need to install the first SCOM 2012 SP1 Management Server to a remote SQL Server?
Yes, on the SCOM MS you need to be member of local Administrators group. No problem.
The SQL server must run on a static TCP port. Go into the SQL Server Configuration Manager and fix the port number in the TCP port field which you will find on the IP Address tab of the TCP/IP protocol settings. I am happy to see that they do not rely on NamedPipes anymore.
If you preffer to configure the static port with PowerShell somewhat automatically, here comes the script:
$instanceName = 'SCOM'
$ipAll = Get-WmiObject -Namespace 'root\Microsoft\SqlServer\ComputerManagement11' -Query ('SELECT * FROM ServerNetworkProtocolProperty WHERE InstanceName = "{0}" ANd IPAddressName = "IPAll" AND PropertyName = "TcpPort" AND ProtocolName = "Tcp"' -f $instanceName)
$ipAll.SetStringValue(1433)
But on the remote SQL Server you need to be member of sysadmins SQL server role and also local Administrators of the SQL server machine as well. What a ...? Not even SharePoint needs such a permission level! SharePoint can make do with just dbcreator and securityadmin roles during its configuration database provisioning.
The SCOM Setup Wizard also needs access to the remote SQL server machine to its WMI service. Why? Because it checks OS version before it lets you proceed with the setup. Am I that stupid so that I would install the SQL Server 2012 on a Windows 2000 box?
The SCOM Setup Wizard also accesses administrative shares on the remote SQL server machine. What really? Yes, it just thinks everybody has admin shares on just to allow viruses spread. So SCOM guys went the smooth way and they are accessing the disk$ share on which you plan to have the operational database. Nice of them to check the free space before installing. I often select full disks to store big operational databases :-)
But yes, it will also create the folder which will store the SCOM database files. So the account must be able to create them in the path specified. Not that Administrators would have such a problem usually, but sometimes this may not be so easy.
Finally, what components you must have installed on the SQL server? You make do with just the database engine, management tools and full-text indexing (called also full-text search or full-text and semantic extractions).
To have it complete, we also need to know what you are NOT required to do. The service accounts, under whos identity the SQL server instance is running, does NOT need to be member of Windows Authorization Access Group (WAAG), nor it needs to have any exceptional read access to the AD user objects used by the future SCOM MS.
What are the real requirements on a SCOM 2012 SP1 Management Server?
The account, under which you install the SCOM Management Server (MS), must be member of local Administrators group on the MS.
You must have .NET Framework 4.0 installed. Prerequisite checker will check this for you before it allows to proceed. Ok. The same applies to the Report Viewer 2010 Controls package. To install both unattended, you can call:
dotNetFx40_Full_x86_x64.exe /passive /norestart
ReportViewer.exe /passive /norestart
You must also have .NET Framework 3.5.1 installed. Only the framework, you do not need the WCF Activation subfeature. Unfortunatelly, the prerequisite checker does not verify it itself. It lets you proceed, but then, the installation will fail with the following (weird enough) errors about installation of performance counters:
Source: MsiInstaller
Event Id: 10005
Message: Product: System Center Operations Manager 2012 Server -- Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.).
Source: MsiInstaller
Event Id: 11708
Message: Product: System Center Operations Manager 2012 Server -- Installation operation failed.
Source: MsiInstaller
Event Id: 1033
Message: Windows Installer installed the product. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.0.9538.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
MSI (s) (50:74) [08:28:51:780]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI644B.tmp, Entrypoint: InstallHSPerfCounters
InstallHSPerfCounters: Custom Action Data. C:\Program Files\System Center 2012\Operations Manager\Server\
InstallHSPerfCounters: Installing agent perf counters.
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\System Center 2012\Operations Manager\Server\HealthServiceCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\System Center 2012\Operations Manager\Server\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\System Center 2012\Operations Manager\Server\HealthServiceCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\System Center 2012\Operations Manager\Server\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\System Center 2012\Operations Manager\Server\HealthServiceCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\System Center 2012\Operations Manager\Server\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\System Center 2012\Operations Manager\Server\HealthServiceCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\System Center 2012\Operations Manager\Server\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\System Center 2012\Operations Manager\Server\HealthServiceCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\System Center 2012\Operations Manager\Server\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\System Center 2012\Operations Manager\Server\HealthServiceCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\System Center 2012\Operations Manager\Server\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallHSPerfCounters: Failed to install agent perf counters. Error Code: 0x80070057.
MSI (s) (50:08) [08:29:21:835]: I/O on thread 1732 could not be cancelled. Error: 1168
MSI (s) (50:08) [08:29:21:835]: I/O on thread 2252 could not be cancelled. Error: 1168
MSI (s) (50:08) [08:29:21:835]: I/O on thread 2532 could not be cancelled. Error: 1168
MSI (s) (50:08) [08:29:21:835]: I/O on thread 2904 could not be cancelled. Error: 1168
MSI (s) (50:08) [08:29:21:835]: I/O on thread 1904 could not be cancelled. Error: 1168
MSI (s) (50:08) [08:29:21:835]: I/O on thread 2128 could not be cancelled. Error: 1168
MSI (s) (50:08) [08:29:21:836]: I/O on thread 2328 could not be cancelled. Error: 1168
MSI (s) (50:08) [08:29:21:836]: I/O on thread 2248 could not be cancelled. Error: 1168
MSI (s) (50:08) [08:29:21:836]: I/O on thread 2260 could not be cancelled. Error: 1168
MSI (s) (50:08) [08:29:21:836]: I/O on thread 2612 could not be cancelled. Error: 1168
MSI (s) (50:08) [08:29:21:836]: I/O on thread 2616 could not be cancelled. Error: 1168
MSI (s) (50:08) [08:29:21:836]: I/O on thread 2164 could not be cancelled. Error: 1168
MSI (s) (50!6C) [08:29:21:837]: Product: System Center Operations Manager 2012 Server -- Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.).
Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.).
CustomAction _RollBack_UninstallHealthServicePerfCountersForUpgrade.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 returned actual error code 1603 but will be translated to success due to continue marking
Although the log says that it cannot install the performance counters, it is just a matter of .NET Framework 3.5.1 missing. Go and install it. If you like, you can do it from PowerShell (this way it works both on Windows 2008 R2 as well as on Windows 2012)
Import-Module ServerManager
Add-WindowsFeature NET-Framework-Core
Another fine feature of the setup is, that it sometimes cannot accept account logon names in the format of UPN (user principal name, userPrincipalName attribute). UPN is the "email-like" login with an ampersand (@). If the UPN prefix differs from the pre-Windows 2000 compatible login name (SAM account name, sAMAccountName attribute), the wizard is not able to validate it.
What this means, is that you should always specify the account login names in the form of the SAM account name - that is domain\login. If you went the modern way - login@upnsuffix, it may not validate the account.
The SCOM guys in Microsoft have probably never heard about the fact that some organizations do not use SAM account names at all. Tha fact is, SAM login is limited to 20 characters while UPN can be up to 64 characters long. There is a feature since Windows 2003 DFL (domain functinal level) which enables user accounts to be created "without SAM login". Because the SAM login must always be present on all user accounts, AD automatically generates random SAM login. Random of a form of $xxxxxx-yyyyyyyyyyyy. In that case, you will have to manually determine the weird SAM login and use it instead of the nice user's UPN.
If you have the problem with different UPN and SAM login, you will see the follogin error messages either in the GUI or in the log:
One of the accounts provided cannot be validated. Please provide valid user names and passwords
[10:00:10]: Info: :Info:AccountsInformationPage: In OnNextFinalValidationsDoWork to validate account access.
[10:00:10]: Error: :GetCrackNameResult() DS_NAME_RESULT_ITEM crack failed with error = DS_NAME_ERROR_NOT_FOUND
[10:00:10]: Error: :ValidateEssentialsAdministratorAccount() failed to crack NT4 format.
[10:00:10]: Info: :ValidateEssentialsAdministratorAccount() Try to crack account with directory searcher.
Another funny feature of the SCOM 2012 SP1 installation is already offically documented: File names for the Data Warehouse database and log are .mdf and .ldf (really?, I thought "Service Packs" receive a lot of testing). Very funny until you want to install to data warehouses into the same folder. So a good advice is - after installation, go and change the names of the OperationsManagerDW database data and log files. To rename the database files, follow procedure from this guide: http://support.microsoft.com/kb/814576
And lastly, one nice issue on the SCOM 2012 Management Server in conjunction with sysprep
The server operating system has been built using Sysprep from a base Windows 2008 R2 machine. It is related to PowerShell on the server. As it seems, sysprep, or more specifically the PowerShell's sysprep provider has a small bug on every Windows I have tested (Windows 2003, Windows 2008, Windows 2008 R2, Windows 2012 and Windows 7 and Windows 8 as well).
When you generalize the source machine with sysprep, it removes one particular registry value from PowerShell registry key - the Path value. Its normal value points to PowerShell installation folder. But this may change after you duplicate the image, so sysprep correctly removes the path:
HKLM\Software\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell
Path = REG_SZ = C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
The problem comes after you distribute the image. It does not reconstruct the value. And accidentally, SCOM 2012 setup tries to read it and store it into its MSI property called MONAD_SHELL_PATH. I have received the following error messages:
MSI (s) (60:28) [18:45:51:807]: Hello, I'm your 64bit Impersonated custom action server.
Action start 18:45:51: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0.
GetRegistyStringValue: RegQueryValueEx failed.. Error Code: 0x80070002.
SetMonadFilePath: Failed to find Key. Error Code: 0x80070002. SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell
CustomAction _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 18:45:51: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0. Return value 3.
Action ended 18:45:51: INSTALL. Return value 3.
Log file: Application
Source: MsiInstaller
Event Id: 1033
Message: Windows Installer installed the product. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.0.9538.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
Log file: Appliation
Source: MsiInstaller
Event Id: 11708
Message: Product: System Center Operations Manager 2012 Server -- Installation operation failed.