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

Similar Messages

  • Upgrade to SCOM 2012 Agent - 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameters is incorrect)

    I have seen this behavior on multiple servers. I receive this error when upgrading from a 2007 Agent to SCOM 2012.
    Event ID: 10005
    Product: System Center 2012 - Operations Manager Agent -- Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.).
    Event ID: 1008
    The Open Procedure for service "HealthService" in DLL "C:\Program Files\System Center Operations Manager 2007\HealthServicePerformance.dll" failed. Performance data for this service will not be available. The Status code returned is the
    first DWORD in the attached data.
    Any idea why I receive this error?
    Thanks
    Mike

    Hi,
    Please refer to this article:
    SCOM 2012 – Unable to upgrade agent after upgrade from SCOM 2007
    http://www.phits.nl/wordpress/2013/02/01/scom-2012-unable-to-update-agent-after-upgrade-from-scom-2007/
    Alex Zhao
    TechNet Community Support

  • WSUS SP2; SCCM 2012 SP1; Sync failed: WSUS update source not found

    Hi,
    I have installed the Fresh SCCM 2012 SP1 and WSUS 3.0 SP2 + KB2720211 + KB2734608. However, still the Sync is getting failed. This is what I am getting in the wsyncmgr and WCM logs:
    wsyncmgr:
    Sync failed: WSUS update source not found on site PR1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
    SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
    3668 (0x0E54)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=3668 GMTDATE=Fri Jan 09 18:00:00.537 2015 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found
    on site PR1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
    3668 (0x0E54)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
    1/9/2015 12:00:00 PM 3668 (0x0E54)
    WCM:
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
    1/9/2015 11:19:03 AM 4176 (0x1050)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
    1/9/2015 11:19:03 AM 4176 (0x1050)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
    1/9/2015 11:19:03 AM 4176 (0x1050)
    STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.489 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
    ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    Remote configuration failed on WSUS Server.
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.515 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
    ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    I have used the default port numbers 80 and 443 still the sync is failing. Please provide your advise to fix this issue.
    Regards,
    Malwinder

    WCM:
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    It's not only a matter of installing the console, but also those hotfixes on a remote server ...
    Torsten Meringer | http://www.mssccmfaq.de

  • 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?

  • Question on upgrading to SCOM 2012 R2 form SCOM 2012 SP1

    Hello!
    I planned upgrade to SCOM 2012 R2 form SCOM 2012 SP1.
    Should I install any or last update rollup package to my SCOM 2012 SP1, before upgrading to SCOM 2012 R2 ?

    It is highly recommend that you has install most updated CU before upgrade SCOM 2012 sp1 1 to SCOm 2012 R2 but it is not necessary.  You should view NEPA PFE Team blog that demostrate how to upgrade SCOM 2012 SP1 with CU4 to SCOM 2012 R2.
    http://blogs.technet.com/b/nepapfe/archive/2013/11/26/upgrading-scom-2012-sp1-to-scom-2012-r2.aspx
    Roger

  • 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.

  • 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

  • SCOM 2012 SP1 SQL Server 2008 R2 Clustering Monitoring?

    We have a new print management system that was setup using SQL server 2008 R2 clustering.  Right now we have SQL MP (monitoring)(discover) 6.3.173.1.  They had a failover occur a week ago and SCOM didnt throw any alerts.  As a temporary
    fix, I found some correlated events and setup a monitor for those events on the servers.  However, the system owner wants to know if there is a MP that will monitor for a SQL cluster failover event.  I have looked and looked and cant seem to find
    anything that gives a whole lot of detail on this.
    Thanks
    EFD
    Warm Fuzzies!

    Yes, you can monitor SQL Cluster 2008 using SCOM 2012 SP1. but you need to install SQL MP and Windows Cluster MP and Enable proxy Agent on physical nodes.
    You can refer below link {it's same for SCOM 2012}
    http://blogs.technet.com/b/birojitn/archive/2010/04/14/sql-server-2008-cluster-monitoring.aspx
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • 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.

  • 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

  • How SCOM Agent will get degraded which is installed on the monitored server while reverting Back from CU6 to CU3 of SCOM 2012 SP1?

    Hi,
    I have SCOM 2012 SP1 (CU3) inatalled on base server 2012 Standard which is a VM.
    Now I am planning to Go for CU6 and thinking to take snapshot of complete  SCOM server instead of taking Data Base Backup. Which should I prefer?
    If i am going for the Snapshot for complete SCOM server and run the CU6 complete setup. And some thing went wrong and not able to fix the issue.
    And I need to reverted back to CU3 using Snspshot.
    Now, how can I revert the Agent Version to CU3 level which is already upgraded to CU6?
    Thanks
    Amit Raj

    Hi,
    all agents with CU6 will be work fine with SCOM CU6.
    But if you decide back to the CU3 you need to backup your OPsDB and DWH (if CU6 contains sql scripts).
    In regard agents you can use repair from OPsMGR console.

  • SCOM 2012 SP1 Update Rollup 5 - DB and DW SQL script and the Management Packs

    Hi,
    I am applying SCOM 2012 SP1 update rollup 5 from KB article : 2904680.
    Step#  4 and 5 from the "Installation Information" sections says to run the SQL queries(UR_Datawarehouse.sql and Update_rollup_mom_db.sql) located at "%SystemDrive%\Program Files\System Center 2012 SP1\Operations
    Manager\Server \SQL Script for Update Rollups\."
    But I do not have "System Center 2012 SP1\Operations Manager\Server \SQL Script for Update Rollups\." folder location on  my SCOM Management Servers. Similarly I do not have the MPs given in Step #6.
    Can someone please let me know from where else can I get these SQL scripts and the MPs. What if I don't run these SQL scripts. Is that OK?

    You will find it on below path%SystemDrive%\Program Files\System Center 2012\Operations Manager\Server \SQL Script for Update Rollups\.
    inside system center 2012 folder> search to Server folder and inside it you will find SQL Script
    Please remember, if you see a post that helped you please click (Vote As Helpful" and if it answered your question, please click (Mark As Answer).

  • Upgrading from SCOM 2012 SP1 to SCOM 2012 R2 what CU do i install? CU5?

    Hi,
    I just upgraded from SCOM 2012 SP1 to SCOM 2012 R2. What CU version should I install? CU5?
    Thanks
    K

    The most current CU version os SCOM 2012R2 is CU4
    You can download it from
    https://support.microsoft.com/kb/2906925?wa=wsignin1.0
    For detail description of SCOM 2012 R2 CU4, you may refer to
    http://support.microsoft.com/kb/2992020
    and
    http://syscentercldman.blogspot.hk/2014/12/update-of-scom-2012-r2-ur4.html
    Roger

  • 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

  • Stop SCOM services before installing UR5 for SCOM 2012 SP1?

    Hello,
    Shall I stop SCOM services on management server before upgrade to UR5?
    ENV: 3 SCOM 2012 SP1 management servers without UR.

    You didn't need to stop services within upgrade.
    To upgrade to UR5, you can refer below link
    http://www.ms-opsmgr.eu/?p=488
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical

Maybe you are looking for