SCOM 2012 SP1 Installation failed

Hello,
I´m experiencing problems installing operations manager and I need some help. I´m trying to do this type of installation:
Two servers: One for bbdd and reporting and the other one for Management Server and Web Console server.
2 server have windows 2012 std installed full patched one of them with sql server 2012.
When doing management and web console server installation I get an error and cannot continue, i paste some of the show on the OpsMgrSetupWizard.log:
Error:    :Error:User did not accept EULA.
Error:    :Error:IsReportingValidToInstall failed SRS instance not provided
Error:    :No Management Server property was provided and Setup could not find a valid Management Server.  Please rerun setup with a valid management server.
Error:    :The management server specified would lead to an invalid scenario. Setup will attempt to find a valid scenario mgt server.
Error:    :CheckForConflictingSqlDatabases: Found a database with the name ReportServer$OPERATIONS in this instance.
Error:    :Error:Failed to log in with account GES-SIEMSA\.....
Error:    :ImportManagementPack: MP already imported so skip : E:\Setup\AMD64\..\..\ManagementPacks\Microsoft.SystemCenter.ApplicationMonitoring.360.Template.Library.mp
Warn:    :Warning:Failed to connect to local SDK in attempt number: 1. Error Message while connecting to SDK: The Data Access service is either not running or not yet initialized. Check the event log for more information. InnerException Details:
No se pudo conectar a net.tcp://......-domain:5724/DispatcherService. La duración del intento de conexión fue de 00:00:02.1159125. Código de error TCP 10061: No se puede establecer una conexión ya que el equipo de destino denegó expresamente dicha conexión
192.168.69.116:5724.
Error:    :Exception running sql string
Error de CREATE DATABASE. No se pueden crear algunos de los archivos de la lista. Consulte los errores relacionados.
Error:    :FATAL ACTION: CreateDataWarehouse
Error:    :FATAL ACTION: DWInstallActionsPostProcessor
Error:    :ProcessInstalls: Running the PostProcessDelegate returned false.
THANKS IN ADVANCE !!!!

Ok and I suppose that you check the box to accept the license?
The communication with the SQL Server is ok? Firewall port are opened?

Similar Messages

  • SCOM 2012 SP1 is failing to install - SQL not compatible

    I'm getting an error when installing SCOM 2012 SP1 stating the SQL is not supported. I have seen a few posts on the forum about this error message but so far none of the resolutions resolved my issue.
    Using named instance on port 2433.  Entering SQL\instance and port 2433 yields same message as seen in another post:
    "The installed version of SQL server is not supported.  Verify that the computer and installed version of SQL Server meet the minimum requirements for installation.  Please see the Supported Configurations document for further information."
    I noticed I get this in my OpsMgrSetupWizard.log
    [15:03:28]: Error: :StackTrace:   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at System.Management.ManagementScope.InitializeGuts(Object o)
       at System.Management.ManagementScope.Initialize()
       at System.Management.ManagementObjectSearcher.Initialize()
       at System.Management.ManagementObjectSearcher.Get()
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
    [15:03:28]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
    Notice the last line - IsSQLOnAValidComputer is null/empty.  The solutions I found are to open the ports between these servers but the SQL server and SCOM server are on the same network - no firewall between them.  The registry key for domain firewall
    policy to 'EnableFirewall' is 0.  The firewall service is disabled on both machines.
    I am running the installation as a domain service account - for the DAA.  It has local admin on the SQL and SCOM server.  It has sysadmin DB access to the instance.
    SCOM Server:
    Server 2008 R2 Standard SP1
    SQL Server:
    Server 2008 R2 Enterprise SP1 | SQL 2012 RM 64-bit version 11.0.2100.60
    Any help is greatly appreciated.

    Glad to hear the issue has been resolved. Thanks for the update.
    Niki Han
    TechNet Community Support

  • System Center Virtual Machine Manager SC VMM 2012 SP1 Installation fails: Unable to assign the name NO_PARAM to this host because this name is already in use.

    I'm trying to install VMM 2012 SP1 on a Windows Server 2012 machine and it fails with this error,
    the scenario is as follows,
    Old database (from 2012 RTM) exists on remote SQL 2012 SP1 server
    Server was 2008 R2 SP1 so I decided to make a fresh installation of 2012 with the same name
    installed ADK
    specific error: 01:42:13:VMMPostinstallProcessor threw an exception: Threw Exception.Type: Microsoft.VirtualManager.Setup.Exceptions.BackEndErrorException, Exception.Message: Unable to assign the name NO_PARAM to this host because this name is already in
    use.
    please help

    I had a similar problem today when upgrading from SCVMM 2012 RTM to SCVMM 2012 SP1 RTM. To re-create the issue you describe originally you can actually just uninstall SCVMM 2012 SP1 RTM with "retain data" option and re-install the software on the same
    computer (with the same name of course), attaching it to the retained DB. If you change the SCVMM server name I believe it will make some things go wrong after your install, like missing VM template passwords for example as the data gets encrypted in
    the DB. Maybe it didn't but I didn't risk it. I definitely know if you change service accounts on a scenario like this you will be without the encrypted DB data which isn't much fun. To avoid changing the computer name, if you look in the setup log
    files in %systemdrive%\ProgramData\VMMLogs\, specifically the SetupWizard.log file. You will see details on it failing because the same computer name is in the DB table "dbo.tbl_ADHC_AgentServer" and until it is removed from that table I wasn't able to get
    the install to complete at all. The error in my logs looked something like this "InnerException.Type: System.Data.SqlClient.SqlException, InnerException.Message: Violation of UNIQUE KEY constraint 'unique_ADHC_AgentServer_ComputerName'. Cannot insert duplicate
    key in object 'dbo.tbl_ADHC_AgentServer'. The duplicate key value is (computername.is.writtenhere). The statement has been terminated." In the row data in the DB it also seems to suggest that the computer name had "Virtual Machine Manager Library Files" on
    it which is strange since I always remove the local SCVMM server as a library server after I install it and use an off box library server.

  • Reinstalling SCSM 2012 SP1 -- installation fails on Finalize step "while executing a custom action:RollbackCleanup" -- absolutely stumped!

    I uninstalled a previous installation of SCSM 2012 in our lab environment because the person who installed it is didn't give anyone else permissions and they weren't available to make the change.  Since then, I've tried to install SCSM 2012 multiple
    times and it fails every time during the Finalize step with the error shown in the picture below.
    Things I've tried and double checked:
    I am running the install with a domain admin account
    I'm specifying a domain user service account during install which is local administrator on the machine
    I rebuilt the performance counters
    I'm running SQL 2k8 R2 SP2
    .Net 3.5.1 is installed
    I see the following message in the System Event Log during setup:
    Event 7036 - The System Center Data Access Service service entered the running state.
    Event 7031 - The System Center Data Access Service service terminated unexpectedly. 
    It has done this 1 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.
    It appears as though this happens 18 times before the service is no longer restarted and is left terminated.
    Any thoughts or help on how to get this to work would be greatly appreciated!  Log excerpts are below as well as a link to the full log file at the end.
    Chris
    Errors in the log that make me go "hmm…" 
    I changed my domain and username in the logs to "DOMAIN" and "user" respectively. 
    MSI (s) (74!94) [10:29:06:718]: Note: 1: 2711 2: MOMServer
    Action start 10:29:06: _SetHealthServiceConfig.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.
    GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMServer
    MSI (s) (74!94) [10:29:06:719]: Note: 1: 2711 2: MOMGateway
    SetHealthServiceConfig: Failed to get Feature State.. Error Code: 0x80070646. MOMServer
    GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMGateway
    MSI (s) (74:04) [10:49:58:011]: Executing op: ActionStart(Name=_ExecuteSqlScripts,Description=Configuring Database,Template=[1])
    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769. The arguments are: _MPProcessorDeferred, 9923,
    Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.RegisterSdkSCP
    RegisterSdkSCP: Old serviceConnectionPoint found
    RegisterSdkSCP: Deleting existing serviceConnectionPoint
    RegisterSdkSCP: Warning: Dont have access to delete existing serviceConnectionPoint
    RegisterSdkSCP: Creating New serviceConnectionPoint
    RegisterSdkSCP: Adding ACL for current user: DOMAIN\account
    RegisterSdkSCP: Adding ACL for SM Admini: DOMAIN\SCSM Admins
    RegisterSdkSCP: Error: The object already exists.
    Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart
    WaitForSDKServiceStart:Entering
    WaitForSDKServiceStart:Sleeping for SDK to start 0 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 10 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 20 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 30 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 40 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 50 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 60 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 70 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 80 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 90 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 100 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 110 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 120 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 130 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 140 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 150 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 160 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 170 seconds
    WaitForSDKServiceStart: SDK Service connect error, after 3 mins, fail this function
    MSI (s) (74:40) [10:56:20:397]: NOTE: custom action _WaitForSDKServiceStart unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that
    handle.
    CustomAction _WaitForSDKServiceStart returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (74:04) [10:56:40:799]: Executing op: CustomActionRollback(Action=_RollBack_UninstallHealthServicePerfCountersForUpgrade.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,ActionType=3393,Source=BinaryData,Target=InstallHSPerfCounters,CustomActionData=C:\Program
    Files\Microsoft System Center 2012\Service Manager\)
    MSI (s) (74:38) [10:56:40:801]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI62BF.tmp, Entrypoint: InstallHSPerfCounters
    InstallHSPerfCounters: Custom Action Data. C:\Program Files\Microsoft System Center 2012\Service Manager\
    InstallHSPerfCounters: Installing agent perf counters.
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\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\Microsoft System Center 2012\Service Manager\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\Microsoft System Center 2012\Service Manager\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\Microsoft System Center 2012\Service Manager\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\Microsoft System Center 2012\Service Manager\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\Microsoft System Center 2012\Service Manager\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\Microsoft System Center 2012\Service Manager\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\Microsoft System Center 2012\Service Manager\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\Microsoft System Center 2012\Service Manager\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\Microsoft System Center 2012\Service Manager\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\Microsoft System Center 2012\Service Manager\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\Microsoft System Center 2012\Service Manager\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) (74:04) [10:57:10:844]: I/O on thread 2752 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:844]: I/O on thread 4796 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:844]: I/O on thread 4928 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 4612 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 884 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 2600 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 1884 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 4872 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 3084 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 4920 could not be cancelled. Error: 1168
    MSI (s) (74!E0) [10:57:10:846]: Product: Microsoft System Center 2012 - Service Manager -- The installer has encountered an unexpected error installing this package. This may indicate a problem with
    this package. The error code is 25211. The arguments are: -2147024809, The parameter is incorrect.,
    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25211. The arguments are: -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
    MSI (s) (74:04) [10:57:17:154]: Note: 1: 1708
    MSI (s) (74:04) [10:57:17:154]: Product: Microsoft System Center 2012 - Service Manager -- Installation failed.
    MSI (s) (74:04) [10:57:17:155]: Windows Installer installed the product. Product Name: Microsoft System Center 2012 - Service Manager. Product Version: 7.5.2905.0. Product Language: 0. Manufacturer:
    Microsoft Corporation. Installation success or error status: 1603.
    Full log file:
    https://skydrive.live.com/redir?resid=F723C571E9E6D51F!1414&authkey=!ACisfvqIpGO_i7A

    Hello Christopher,
    I have recently worked in a case that had mostly the same errors:
    InstallHSPerfCounters: Installing agent perf counters.
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\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\Microsoft System Center\Service Manager\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\Microsoft System Center\Service Manager\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\Microsoft System Center\Service Manager\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\Microsoft System Center\Service Manager\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\Microsoft System Center\Service Manager\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\Microsoft System Center\Service Manager\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\Microsoft System Center\Service Manager\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\Microsoft System Center\Service Manager\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\Microsoft System Center\Service Manager\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\Microsoft System Center\Service Manager\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\Microsoft System Center\Service Manager\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) (A8:D4) [10:29:51:586]: I/O on thread 8152 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 9580 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 6008 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 2112 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 8252 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 12504 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 9548 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 11464 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:587]: I/O on thread 10616 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:587]: I/O on thread 8120 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:587]: I/O on thread 2424 could not be cancelled. Error: 1168
    MSI (s) (A8!D4) [10:29:51:587]: Product: Microsoft System Center 2012 R2 Service Manager -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25211. The arguments are:
    -2147024809, The parameter is incorrect.,
    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25211. The arguments are: -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
    MSI (s) (A8:3C) [10:29:51:599]: Executing op: ActionStart(Name=_StopNamedServices_HealthService.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,Description=Stopping Health services,)
    MSI (s) (A8:3C) [10:29:51:603]: Executing op: ActionStart(Name=StopServices,Description=Stopping services,Template=[1])
    MSI (s) (A8:3C) [10:29:51:605]: Executing op: ServiceControl(,Name=W3SVC,Action=1,,)
    MSI (s) (A8:3C) [10:29:52:621]: Executing op: ActionStart(Name=ProcessComponents,Description=Updating component registration,).
    - I was able to resolve it using the command  line LOTCTR /R
    - And restarting the IIS service using the command line tool IISRESET
    - After this command was successfully applied I have tried to install the Service Manager Portal without any errors.
    http://technet.microsoft.com/en-us/library/bb490926.aspx
    http://technet.microsoft.com/en-us/library/hh875560.aspx
    http://support.microsoft.com/kb/300956
    https://blogs.technet.com/b/yongrhee/archive/2009/10/06/how-to-rebuild-performance-counters-on-windows-vista-server2008-7-server2008r2.aspx
    Thank you very much
    Renato Pacheco

  • Exchange Server 2012 SP1 installation fails

    I am not an expert in Exchange. I did set up and administer an Exchange server for a customer years ago, and I just persuaded another customer to purchase and install Exchange Server 2013 SP1.
    I downloaded the ISO file and extracted it and then did the install. It told me some Hotfixes needed to be installed, so I installed all that were required. It's worth noting at this point that the link to the KB974405 was wrong and I had to search for the
    hotfix. But eventually all prerequisites were installed and installation began. Apart from taking a long time, it appeared to work.
    After installation completed I clicked to allow administration to open and I was unable to administer anything. The link to Exchange Administrative Center failed with a 404. I opened IIS and noticed that Exchange Back End was installed on port 444. Subsequently
    I observed that the Exchange website appeared to be installed twice, once as Exchange Back End and once under Default Web Site. The first problem was a complaint that a module, which name now escapes me, but which was installed locally had been compiled with
    a later version of .Net than the website is using. The website is using .Net 4.5.1. In case it matters I had installed Exchange with both the mailbox and client access roles.
    After messing around with it for a long time and finding no relevant help on Google, I decided to uninstall and start over. The uninstalled failed because there are mailboxes. Heaven knows where the mailboxes came from since I had never managed to administer
    Exchange. I attempted to use Get-Mailbox cmdlet but got a response the Get-Mailbox was an unknown cmdlet.
    I am considering reverting the server back to a backup prior to the install and starting over, but I am not sure it would be any different the second time around. Does Microsoft have any suggestions. I suppose I could ask for a refund, but then I am left
    with a dissatisfied customer. 
    Please help, I am desperate!

    At the risk of stating the obvious, if I could recover the current installation, I wouldn't need to uninstall it. There was no prior Exchange Server on this computer or even in the domain. SO this was a clean install but I can't administer it.
    If it helps at all, the module that it complained about was Microsoft.Exchange.OwaUrlModule. Is there any kind of "FixIt" uninstall - I don't it just deleting the database because there is nothing of use in it. Or can I manual delete it? Do you have
    any clue why the Get-Maiolbox says it is an unknown cmdlet?

  • SCOM 2012 SP1 : Update rollup installation failed

    Hello,
    I'm trying to update SCOM 2012 SP1 with UR7 but the installation rollback automatically.
    Same error with others UR.
    LOG MSP :
    MSI (c) (08:1C) [14:49:24:772]: Product: System Center Operations Manager 2012 Server - Update 'System Center 2012 - Operations Manager SP1 UR7 Update Patch' could not be installed. Error code 1603. Additional information is available in the log file c:\logs3.log.
    MSI (c) (08:1C) [14:49:24:772]: Windows Installer installed an update. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.0.9538.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: System Center 2012 - Operations
    Manager SP1 UR7 Update Patch. Installation success or error status: 1603.
    MSI (c) (08:1C) [14:49:24:772]: Note: 1: 1729 
    MSI (c) (08:1C) [14:49:24:772]: Product: System Center Operations Manager 2012 Server -- Configuration failed.
    MSI (c) (08:1C) [14:49:24:772]: Windows Installer reconfigured the product. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.0.9538.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error
    status: 1603.
    MSI (c) (08:1C) [14:49:24:772]: Attempting to delete file C:\Users\ADMINJ~1\AppData\Local\Temp\10c36d.msp
    MSI (c) (08:1C) [14:49:24:772]: Unable to delete the file. LastError = 32
    MSI (c) (08:1C) [14:49:24:772]: Grabbed execution mutex.
    MSI (c) (08:1C) [14:49:24:772]: Cleaning up uninstalled install packages, if any exist
    MSI (c) (08:1C) [14:49:24:772]: Attempting to delete file C:\Users\ADMINJ~1\AppData\Local\Temp\10c36d.msp
    MSI (c) (08:1C) [14:49:24:772]: MainEngineThread is returning 1603
    === Verbose logging stopped: 15/10/2014  14:49:24 ===
    MOMPerfCtrsInstall.log
    The uninstall is beginning.
    See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.dll assembly's progress.
    The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.InstallLog.
    The uninstall has completed.
    The uninstall is beginning.
    See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.dll assembly's progress.
    The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.InstallLog.
    See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.dll assembly's progress.
    The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.InstallLog.
    The uninstall has completed.
    Running a transacted installation.
    Beginning the Install phase of the installation.
    See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.dll assembly's progress.
    The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.InstallLog.
    An exception occurred during the Install phase.
    System.FormatException: Input string was not in a correct format.
    The Rollback phase of the installation is beginning.
    See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.dll assembly's progress.
    The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.InstallLog.
    The Rollback phase completed successfully.
    The transacted install has completed.
    Running a transacted installation.
    Beginning the Install phase of the installation.
    See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.dll assembly's progress.
    The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.InstallLog.
    An exception occurred during the Install phase.
    System.FormatException: Input string was not in a correct format.
    The Rollback phase of the installation is beginning.
    See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.dll assembly's progress.
    The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.InstallLog.
    The Rollback phase completed successfully.
    The transacted install has completed.
    Maybe someone have a idea about that ?
    Thank you !
    Jérémy

    Hi,
    Have your tried to review the c:\logs3.log for any potential error or indication of cause?
    For more information, please review the link below:
    Update Rollup 7 for System Center 2012 Operations Manager Service Pack 1
    http://support.microsoft.com/kb/2965420
    Update rollup packages for System Center 2012 Operations Manager
    http://support.microsoft.com/kb/2906925
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SCOM 2012 SP1 - PowerShell Script failed to run - 3 alerts appear after every reboot of the SCOM Server

    Brand new SCOM 2012 SP1 install with Update Rollup 1 applied
    Single server, local SQL install, SQL Server 2012 SP1
    Hyper-V VM running on Server 2012.  VM has 8GB Ram, single vCPU
    Going through initial management pack importing and configuration, at this point I have the Windows Server 2012 and SQL 2012 MP's installed.
    See screenshot
    http://i.imgur.com/l0Molh1.png
    I am getting the following alerts in my SCOM console and cannot find a resolution to fix the issue.  I don't want to set an override, as an override will prevent the PowerShell alert in other instances, where I might want to receive an alert.
    Looking at the alert description, it states "The Data Access service is either not running or not yet initialized"
    The SCOM Console launches and responds fine, and I get no other errors.  I check the Data Access service and it is online.  I have left the system alone for a couple of hours and no other errors.  I then closed those alerts and restarted the
    server, and they came right back in, so I know that this is something that is happening at either server startup of during the start of the SCOM services.
    Is it possible that SCOM is trying to execute these scripts and the Data Access service has not come online yet?
    Has anyone else come across this before?

    Please try the method in the following thread:
    Note: As there is operations related to Registry, please perform a backup before doing this.
    OpsMgr 2012 - Power Shell Script failed to run 
    http://social.technet.microsoft.com/Forums/de-DE/systemcenterde/thread/4be37f8d-1e7b-450c-8cb9-f1e95f3b2bd0/
    Thanks.
    Nicholas Li
    TechNet Community Support

  • VMM 2012 SP1 Console Fail Installation With Error 1603

    Dear Sir,
    I am trying to install VMM 2012 SP1 console on my management Windows 8 Enterprise machine, but it's failing:
    [Installing C:\Users\XXXXX\Desktop\VMM 2012 SP1\amd64\setup\msi\Client\AdminConsole.msi failed with Windows Installer error 1603.
    See C:\ProgramData\VMMLogs\AdminConsole.log for more information. After resolving the problem, retry setup.]
    I am admin with full permission, and the machine is joined to the domain.
    Please find below VMMlogs for more information:
    Property(S): CountComponentClients = DAFEE2F2-CF16-47f5-94A7-725D0795BCB9
    Property(S): RegisterCmdlets = "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\installUtil.exe" /LogFile= /LogToConsole=false "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Microsoft.SystemCenter.VirtualMachineManager.dll"
    Property(S): RollbackCmdlets = "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\installUtil.exe" /u /LogFile= /LogToConsole=false "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Microsoft.SystemCenter.VirtualMachineManager.dll"
    Property(S): TRANSLATE_SID = S-1-5-11
    Property(S): TRANSLATE_SID_PROPERTYNAME = AUTHENTICATEDUSERS
    Property(S): AUTHENTICATEDUSERS = Authenticated Users
    Property(S): DeleteAddInsOldFolder = "C:\Windows\SysWOW64\cmd.exe" /C rmdir "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\AddInPipeline\AddIns.old" /S /Q
    Property(S): RenameAddInsFolder = "C:\Windows\SysWOW64\cmd.exe" /Q /C ren "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\AddInPipeline\AddIns" "AddIns.old"
    Property(S): ProgramFiles64Folder = C:\Program Files\
    Property(S): TARGETDIR = F:\
    Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
    Property(S): SourceDir = C:\Users\supercharo\Desktop\VMM 2012 SP1\amd64\setup\msi\Client\
    Property(S): HelpDir = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\help\
    Property(S): psModulesDir = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\psModules\
    Property(S): INDIGOPORT = 8100
    Property(S): Manufacturer = Microsoft Corporation
    Property(S): ProductCode = {CDFB453F-5FA4-4884-B282-F46BDFC06051}
    Property(S): ProductLanguage = 1033
    Property(S): ProductName = Microsoft System Center Virtual Machine Manager Administrator Console (x64)
    Property(S): ProductVersion = 3.1.6011.0
    Property(S): INSTALLLEVEL = 100
    Property(S): ARPSYSTEMCOMPONENT = 1
    Property(S): ALLUSERS = 1
    Property(S): BOOTSTRAPPED = 0
    Property(S): REREGBINDIR = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\wwwroot\bin\
    Property(S): SecureCustomProperties = ANYVERSION
    Property(S): Trace.3812768D_658A_4BB6_9A68_F288BE3E9CF5 = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\
    Property(S): RegisterEventManifest = "wevtutil.exe" im "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\VmmEtwEvents.Man"
    Property(S): RollbackRegisterEventManifest = "wevtutil.exe" um "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\VmmEtwEvents.Man"
    Property(S): ExecXmlFile = 2€0€C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\VmmEtwEvents.Man€7€1€/*/*/*/*[@messageFileName]€messageFileName€C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\Microsoft.VirtualManager.EtwResources.dll€2€0€C:\Program
    Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\VmmEtwEvents.Man€7€1€/*/*/*/*[@resourceFileName]€resourceFileName€C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\Microsoft.VirtualManager.EtwResources.dll
    Property(S): MsiLogFileLocation = C:\ProgramData\VMMLogs\AdminConsole.log
    Property(S): PackageCode = {A96E8FEC-A027-4FF8-A395-1ECC0C460677}
    Property(S): ProductState = -1
    Property(S): PackagecodeChanging = 1
    Property(S): INSTALLINGLANGUAGE = 1033
    Property(S): REBOOT = ReallySuppress
    Property(S): CURRENTDIRECTORY = C:\Users\supercharo\AppData\Local\Temp\VMB790.tmp\Setup
    Property(S): CLIENTUILEVEL = 3
    Property(S): MSICLIENTUSESEXTERNALUI = 1
    Property(S): CLIENTPROCESSID = 968
    Property(S): VersionDatabase = 301
    Property(S): VersionMsi = 5.00
    Property(S): VersionNT = 602
    Property(S): VersionNT64 = 602
    Property(S): WindowsBuild = 9200
    Property(S): ServicePackLevel = 0
    Property(S): ServicePackLevelMinor = 0
    Property(S): MsiNTProductType = 1
    Property(S): WindowsFolder = C:\Windows\
    Property(S): WindowsVolume = C:\
    Property(S): System64Folder = C:\Windows\system32\
    Property(S): SystemFolder = C:\Windows\SysWOW64\
    Property(S): RemoteAdminTS = 1
    Property(S): TempFolder = C:\Users\SUPERC~1\AppData\Local\Temp\
    Property(S): ProgramFilesFolder = C:\Program Files (x86)\
    Property(S): CommonFilesFolder = C:\Program Files (x86)\Common Files\
    Property(S): CommonFiles64Folder = C:\Program Files\Common Files\
    Property(S): AppDataFolder = C:\Users\supercharo\AppData\Roaming\
    Property(S): FavoritesFolder = C:\Users\supercharo\Favorites\
    Property(S): NetHoodFolder = C:\Users\supercharo\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
    Property(S): PersonalFolder = C:\Users\supercharo\Documents\
    Property(S): PrintHoodFolder = C:\Users\supercharo\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
    Property(S): RecentFolder = C:\Users\supercharo\AppData\Roaming\Microsoft\Windows\Recent\
    Property(S): SendToFolder = C:\Users\supercharo\AppData\Roaming\Microsoft\Windows\SendTo\
    Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
    Property(S): CommonAppDataFolder = C:\ProgramData\
    Property(S): LocalAppDataFolder = C:\Users\supercharo\AppData\Local\
    Property(S): MyPicturesFolder = C:\Users\supercharo\Pictures\
    Property(S): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
    Property(S): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
    Property(S): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
    Property(S): DesktopFolder = C:\Users\Public\Desktop\
    Property(S): FontsFolder = C:\Windows\Fonts\
    Property(S): GPTSupport = 1
    Property(S): OLEAdvtSupport = 1
    Property(S): ShellAdvtSupport = 1
    Property(S): MsiAMD64 = 6
    Property(S): Msix64 = 6
    Property(S): Intel = 6
    Property(S): PhysicalMemory = 32695
    Property(S): VirtualMemory = 58675
    Property(S): AdminUser = 1
    Property(S): MsiTrueAdminUser = 1
    Property(S): LogonUser = supercharo
    Property(S): UserSID = S-1-5-21-3202008507-3906799607-3053210984-500
    Property(S): UserLanguageID = 1033
    Property(S): ComputerName = CHARO-Z1
    Property(S): SystemLanguageID = 1033
    Property(S): ScreenX = 1024
    Property(S): ScreenY = 768
    Property(S): CaptionHeight = 23
    Property(S): BorderTop = 1
    Property(S): BorderSide = 1
    Property(S): TextHeight = 16
    Property(S): TextInternalLeading = 3
    Property(S): ColorBits = 32
    Property(S): TTCSupport = 1
    Property(S): Time = 23:20:44
    Property(S): Date = 2/17/2013
    Property(S): MsiNetAssemblySupport = 4.0.30319.17929
    Property(S): MsiWin32AssemblySupport = 6.2.9200.16384
    Property(S): RedirectedDllSupport = 2
    Property(S): MsiRunningElevated = 1
    Property(S): Privileged = 1
    Property(S): USERNAME = CHARO
    Property(S): DATABASE = C:\Windows\Installer\113cc0a.msi
    Property(S): OriginalDatabase = C:\Users\supercharo\Desktop\VMM 2012 SP1\amd64\setup\msi\Client\AdminConsole.msi
    Property(S): UILevel = 2
    Property(S): ACTION = INSTALL
    Property(S): ComponentCount = 0
    Property(S): ROOTDRIVE = F:\
    Property(S): CostingComplete = 1
    Property(S): OutOfDiskSpace = 0
    Property(S): OutOfNoRbDiskSpace = 0
    Property(S): PrimaryVolumeSpaceAvailable = 0
    Property(S): PrimaryVolumeSpaceRequired = 0
    Property(S): PrimaryVolumeSpaceRemaining = 0
    Property(S): SOURCEDIR = C:\Users\supercharo\Desktop\VMM 2012 SP1\amd64\setup\msi\Client\
    Property(S): SourcedirProduct = {CDFB453F-5FA4-4884-B282-F46BDFC06051}
    Property(S): ProductToBeRegistered = 1
    MSI (s) (DC:2C) [23:20:44:051]: Note: 1: 1708 
    MSI (s) (DC:2C) [23:20:44:051]: Product: Microsoft System Center Virtual Machine Manager Administrator Console (x64) -- Installation failed.
    MSI (s) (DC:2C) [23:20:44:052]: Windows Installer installed the product. Product Name: Microsoft System Center Virtual Machine Manager Administrator Console (x64). Product Version: 3.1.6011.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation
    success or error status: 1603.
    MSI (s) (DC:2C) [23:20:44:067]: Deferring clean up of packages/files, if any exist
    MSI (s) (DC:2C) [23:20:44:068]: MainEngineThread is returning 1603
    MSI (s) (DC:A4) [23:20:44:072]: RESTART MANAGER: Session closed.
    MSI (s) (DC:A4) [23:20:44:072]: No System Restore sequence number for this installation.
    === Logging stopped: 02/17/2013  23:20:44 ===
    MSI (s) (DC:A4) [23:20:44:076]: User policy value 'DisableRollback' is 0
    MSI (s) (DC:A4) [23:20:44:076]: Machine policy value 'DisableRollback' is 0
    MSI (s) (DC:A4) [23:20:44:076]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (DC:A4) [23:20:44:076]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (DC:A4) [23:20:44:077]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (DC:A4) [23:20:44:078]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (DC:A4) [23:20:44:084]: Destroying RemoteAPI object.
    MSI (s) (DC:A4) [23:20:44:084]: Custom Action Manager thread ending.
    MSI (c) (C8:18) [23:20:44:086]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (C8:18) [23:20:44:086]: MainEngineThread is returning 1603
    === Verbose logging stopped: 02/17/2013  23:20:44 ===
    Your help is highly appreciated.
    Thank you.
    Regards,

    Mine is solved.
    Was because I removed VMM 2012 R2 on the same host (again, because R2 doesn't do P2V conversions) but the uninstall failed to remove "Microsoft Web Deploy 3.5". When VMM 2012 SP1 installs uses Web Deploy 3.0 and was blocked by the newer version. uninstalled
    3.5 and then the console install worked.
    hopes this helps someone out there.
    Jae

  • SCOM 2012 SP1 failed to send notifications by IM Channel

    Hello, I have a problem with my SCOM 2012 SP1. When it tries to send notification by IM Channel I get the following alert in SCOM:
    Notification subsystem failed to send notification using
    device/server 'live.august.ru:5060' over 'sip' protocol to
    'sip:[email protected]'.
    Microsoft.Rtc.Signaling.OperationFailureException: The GetInbandDataAsyncResult
    operation has failed with message: "The data session subscription to server
    failed.". See the InnerException and FailureReason properties as well as the
    logs for additional information. . Rule id:
    Subscription077dc311_59c0_4ba5_a432_072b486cd287
    At the same time the following event in the Application Event Log generates on the server with IM service:
    Event Type: Warning
    Event Source: Live Communications Server Authentication
    Event Category: (1003)
    Event ID: 16435
    User:  N/A
    Computer: LCS
    Description:
    At least one invalid authentication signature was detected.
    There were 2 messages with invalid signatures in the last 7112 minutes. The last one had the FROM header: sip:[email protected]
    Cause: This could be due to a client or server which is not handling authentication correctly, or it could be due to an attacker.
    Resolution:
    None needed unless the failure count is high (>100). Check your network for any rogue clients. Restart the server if problem persists.
    Notifications sent by the SMTP channel work fine!
    I Have the following Servers:
    LCS (live.august.ru) - Win 2003 EE SP2 + Live Communication Server 2005 SP1
    SCOM - Win 2012 + SCOM 2012 SP1
    Also I have a third server (Win 2003 + SCOM 2007 R2) and it sends notifications to the same VMLCS server successfully. The configurations of IM Channels are identical on both servers:
    IM server: live.august.ru
    Return address: sip:[email protected]
    Protocol option: TCP
    Authentication method: Kerberos
    IM port: 5060
    I tried to change the Authentication method to NTLM, and the port to 5061, but it doesn't help...

    Hi,
    Please refer to these following articles to configure IM channel correctly:
    How to Create and Configure the Notification Action Account
    http://technet.microsoft.com/en-us/library/hh212835.aspx
    How to Enable an Instant Message Notification Channel
    http://technet.microsoft.com/en-us/library/hh212690.aspx
    Enabling Instant Messaging Notifications in System Center 2012 Operations Manager
    http://opsmgrunleashed.wordpress.com/2012/02/24/enabling-instant-messaging-notifications-in-system-center-2012-operations-manager/
    Alex Zhao
    TechNet Community Support

  • Issue upgrading SCOM 2012 SP1 to SCOM 2012 R2

    I have been having a really fun time trying to get my test SCOM 2012 SP1 environment upgraded to SCOM 2012 R2.  I initially had an issue with the DB server not accepting connections to SMB which was causing the upgrade to fail stating database permission
    issues (that was a fun one to troubleshoot).  Once I figured out that problem I am now getting an error in the OpsMgrSetupWizard log that is stating the following:
    [14:46:47]: Always:
    :LaunchMsiSetup: Complete: 2 seconds
    [14:46:47]: Error:
    :LaunchMsiSetup: Failed, return code: 1612
    [14:46:47]: Error:
    :Error:Failed to uninstall previous MOM product on this machine, cannot proceed with upgrade
    [14:46:47]: Error:
    :Error:Failed to uninstall Operations Manager Agent on this machine. This is fatal error, we cannot proceed with upgrade
    [14:46:50]: Error:
    :LaunchMSI: MSI E:\Setup\AMD64\Server\OMServer.msi returned error 1603
    [14:46:50]: Error:
    :ProcessInstalls: Install Item Management Server failed to install.  We did not launch the post process delegate.
    In the application log I am getting the following error:
    "Product: System Center Operations Manager 2012 Server -- The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service
    Manager is already installed. These must be uninstalled to proceed."
    I have verified that I don't have any of these installed and have even gone so far as to remove my Config man agent and System Center Endpoint Protection just in case it was getting confused with System Center Essentials.
    I am at a loss as to what to try next.  Any suggestions?

    Hi,
    Check if you have the following registry. If so, please back it up first, then delete for a test.
     HKEY_CLASSES_ROOT\Installer\UpgradeCodes\C96403E8AD6025B4F9E1FE9C574E34AE
    Also, please uninstall MOM product and Operations Manager Agent manually to check the result.
    Upgrading System Center 2012 SP1 - Operations Manager to System Center 2012 R2
    http://technet.microsoft.com/en-us/library/dn249707.aspx
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Manage DPM servers, running DPM jobs, etc from SCOM 2012 SP1

    Hi,
    Little background about our systems.
    We have a dedicated SCOM 2012.
    We have 22 DPM servers, DPM 2010 and DPM 2012 (we are upgrading to 2012 SP1, we have customers that still using Windows 2003 servers) to be managed by SCOM
    We have a few DPM servers that are not located on the same domain as the SCOM server (untrusted domain).
    Some problem we have
    1. When we try to manage the DPM servers from the SCOM server.
    From SCOM 2012 server I can “Manage DPM server” that are located in our domain but I cannot manage DPM servers located on untrusted domains (customer’s domains). I receive the below error message
    "Unable to connect to <untrusted domain DPM SERVER> ID: 948
    Verify that the DPM service is running on this computer"
    I guess it’s because the account that I’m using to run SCOM server located in our domain and does not have the permission to open the DPM console on the untrusted domain. So I wonder if it is possible to use “RUN AS profiles/accounts”
    to solve this issue, and how?
    2. I have installed SCOM 2012 Operations Manager Console on my computer and then installed DPM Central Console.
    When I select one dpm server (from my computer), that is on our domain, and then click “Manage DPM server” I got this error message
    "Unable to connect to <our domain DPM SERVER> ID: 33333
    1. Verify that the DPM service is running on this computer (YES)
    2. Verify that the current user has been added to at least one of the roles in Operations Manager. (YES)
    3. Open Operations Manage console and then try launching the DPM Console (THAT IS WHAT I AM TRYING TO DO)
    4. If you have re-imported the management pack recently, the role configuration may be corrupt. Open the DPM-specific roles and check if the roles have task assigned to them. If not, delete the roles and recreate the...."
    When I click on “Get more information” I get this error message.
    "You don´t have access permission to connect to the System Center Data Access service on <SCOM SERVER>. Please check if it is a permission issue".....
    Do you know why I cannot connect to any DPM server on our own domain?
    Why do I get access permission error on my computer but not on the SCOM server (using the same account)?
    What should we do to be able to connect to DPM servers that are on untrusted domain?
    3. Is it possible to see Last Recovery Point date/time in SCOM alerts?
    For me it is the first thing I look at. If it has failed 10 min ago it is not critical.
    But if it is a date and time more than 1 day old, then it is critical.
    I hope someone can help us with this
    Br
    SvBoho

    Hi,
    To manager DPM, I think we may need to add the account to local admin group of the DPM server.
    In addition, to connect to DPM the user needs permissions to DPM/SQL Server DPMDB.
    For your DCs, have your enabled agent proxy option? If not, please enable that option for all DCs.
    To monitor DPM with SCOM, please also go through the below links:
    http://kevingreeneitblog.blogspot.com/2011/10/managing-and-monitoring-system-center.html
    http://damatisystemcenter.com/2013/10/14/monitor-data-protection-manager-2012-using-scom-2012-sp1/
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Regards,
    Yan Li
    Regards, Yan Li

  • Problem upgrading from SCOM 2012 SP1 to R2 (near impossible to uninstall SCOM agent from Management Server)

    I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
    We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
    installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
    I have to remove the management installation first. And that's not gonna happen.
    I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
    In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
    Control Panel. And this can NOT be the most healthy way of getting through the setup.
    I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
    Any of you have tips as to how I can get rid of the agents more gracefully?

    Hi
    Thanks for the replay guys!
    None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
    I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
    days.
    Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
    agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
    So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
    but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment.

  • Three agent UR versions gets installed from gateway - SCOM 2012 SP1 UR4

    Hi,
    We have a SCOM 2012 SP1 UR4 installation with several gateways that servers connect to and get installation from.
    We noticed that when the agent get installed on a client server it gets first the agent itself, then UR1, UR2 and last UR4.
    From the XML-section in the task that has installed the agent one can read the following:
    SoftwareUpdateInstalled KB2784734-amd64-Agent.msp;KB2826664-amd64-Agent.msp;KB2880799-amd64-Agent.msp; SoftwareUpdateInstalled
    Below is from the application log of a newly installed server that got the agent installed.
    The question I have is if this is correct? Why are all three UR installed?
    Shouldn't it be enough with the latest version of UR? Are they not cumulative?
    Can I simply delete the older versions in the agent directory of the Gateway?
    Regards S-E
    Windows Installer installed the product. Product Name: System Center 2012 - Operations Manager Agent.
    Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
    Installation success or error status: 0.
    Windows Installer installed an update. Product Name: System Center 2012 - Operations Manager Agent.
    Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
    Update Name: System Center 2012 - Operations Manager SP1 UR1 Update Patch.
    Installation success or error status: 0.
    Windows Installer installed an update. Product Name: System Center 2012 - Operations Manager Agent.
    Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
    Update Name: System Center 2012 - Operations Manager SP1 UR2 Update Patch.
    Installation success or error status: 0.
    Windows Installer installed an update. Product Name: System Center 2012 - Operations Manager Agent.
    Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
    Update Name: System Center 2012 - Operations Manager SP1 UR4 Update Patch.
    Installation success or error status: 0.
    Windows Installer installed the product. Product Name: Active Directory Management Pack Helper Object.
    Product Version: 1.1.0. Product Language: 1033. Manufacturer: Microsoft Corporation.
    Installation success or error status: 0.

    Hi,
    This should be normal, as we can see in the below two articles. When applying Update Rollup 2, UR1 is listed there, and when applying Update Rollup 3, UR1 and UR2 is listed there also.
    http://blogs.technet.com/b/kevinholman/archive/2013/04/11/applying-update-rollup-2-ur2-to-opsmgr-2012-sp1.aspx
    http://blogs.technet.com/b/kevinholman/archive/2013/09/27/applying-update-rollup-3-ur3-to-opsmgr-2012-sp1.aspx
    For example, UR3 can be applied to System Center Operations Manager 2012 SP1 (as released) or a SCOM 2012 SP1 deployment that has had UR1 or UR2 already applied.
    Regards,
    Yan Li
    Regards, Yan Li

  • Non supported version of SQL with new install of SCOM 2012 SP1

    I have SQL 2012 SP1 running on Server 2012.  I have tried the SCOM installation with and without CU2 (to fix the 1618 installation error)
    SC VMM installed cleanly and appears to work.
    The install for SCOM produces an error that says, "The installed version of SQL Server is not supported".  I have not been able to find any log from the install that has that error in it.
    Also, I have not been able to determine the true requirements of the SQL server for SCOM.  (I found dock SCOM 2012 RTM and SQL 2008 R2, but noting for 2012 SP1.
    Can someone point me to the correct place for the install log with (hopefully more information) and/or the requrements for the SQL installation?
    Roy

    The log is not created yet because it has not started the install.
    The firewall is the most common issue indeed. Temporarily Disable the firewall and see whether you can continue.
    Are you using a developers edition? The only 2 editions supported are standard and Enterprise.
    The true requirements for SCOM 2012 sp1:
    We recommend that you check for updates and hotfixes for SQL Server. Note the following database considerations for Operations Manager:
    SQL Server 2008 R2 and SQL Server 2012 are available in both Standard and Enterprise editions. Operations Manager will function with both editions.
    Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.
    Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features.
    SQL Server collation settings for all databases must be one of the following: SQL_Latin1_General_CP1_CI_AS, French_CI_AS, Cyrillic_General_CI_AS, Chinese_PRC_CI_AS, Japanese_CI_AS, Traditional_Spanish_CI_AS, or Latin1_General_CI_AS.  No other collation
    settings are supported.
    The SQL Server Agent service must be started, and the startup type must be set to automatic.
    Side-by-side installation of System Center Operations Manager 2007 R2 reporting and System Center 2012 Service Pack 1 (SP1), Operations Manager reporting on the same server is not supported.
    The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start.
    For information about how to resolve the issue, see System Center Data Access Service Start Up Failure Due to SQL Configuration Change
    If you plan to use the Network Monitoring features of System Center 2012 – Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles. For more information, see
    tempdb Database.
    Found here:
    http://technet.microsoft.com/en-us/library/jj656654.aspx#BKMK_RBF_OperationsDatabase
    It's doing common things uncommonly well that brings succes.

  • System center data access service crashes with event id 26339 ad 26380 in SCOM 2012 Sp1 RTM

    hi all,
    I have deployed scom 2012 sp1 rtm on Os 2012 std and database is on another VM Machine having SQL 2012 sp1 with OS 2008 R2 SP1 std, suddenly sql vm get stopped and unable to start , so I have delete it from hyper-v 2012 console and imported the VM again
    in Hyper-0S 2012 cluster.
    Now, System centre data access service get crashed again and again with mentioned events
    event 26339, OpsMgr SDKService
    event 26380, opsmgr SDkService
    An exception was thrown while initializing the service container.
    Exception message: Initialize
    Full exception: HTTP could not register URL
    http://+:51905/ConnectorFramework/ because TCP port 51905 is being used by another application.
    The System Center Data Access service failed due to an unhandled exception. 
    The service will attempt to restart.
    Exception:
    System.ServiceModel.AddressAlreadyInUseException: HTTP could not register URL http://+:51905/ConnectorFramework/ because TCP port 51905 is being used by another application. ---> System.Net.HttpListenerException: The process cannot access the file
    because it is being used by another process
       at System.Net.HttpListener.AddAllPrefixes()
       at System.Net.HttpListener.Start()
       at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
       --- End of inner exception stack trace ---
       at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
       at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
       at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
       at System.ServiceModel.Channels.HttpChannelListener`1.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at Microsoft.EnterpriseManagement.ConnectorFramework.ServiceDataLayer.ConnectorFrameworkDataAccessChannel.Initialize()
       at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.Initialize(InProcEnterpriseManagementConnectionSettings configuration)
       at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.InitializeRunner(Object state)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    Kirpal Singh

    Hi Kirpal
    Can you try this it might help as its an known issue of getting event id 's 26361,26380 try out & lets see if it helps.
    The manifest files are located on the RMS at the \Program Files\System Center Operations Manager 2007\ root directory. The manifest files will need to be edited for the config and sdk service on affected RMS. The file names are:
    Microsoft.Mom.Sdk.ServiceHost.exe.config
    Microsoft.Mom.ConfigServiceHost.exe.config
    In between the EXISTING <runtime> and </runtime> lines – you need to ADD a NEW LINE with the following:
    <generatePublisherEvidence enabled="false"/>
    This solution disables CRL checking for the specified execute-ables, permanently.

Maybe you are looking for