SCOM 2007 R2 to SCOM 2012 SP1 upgrade issues.

We have SCOM 2007 R2 on one of our development Environment.
The plan was to upgrade to SCOM 2012 R2 so we installed the SCOM 2007 R2 CU5.
We are having issues to upgrade now from SCOM 2007 R2 CU5 to SCOM 2012 SP1.
While upgrading we received the below message:
Unable to Proceed
Setup is unable to proceed with installation for the following reason:
At least one of the following application is installed on the computer.Due to incompatibility with system center 2012 - operations manager,these applications must be uninstalled.
-System Center 2012 - operations manager beta
-system center operations manager 2007
-system center operations manager 2007 sp1
--system center operations manager 2007 r2
-system center service manager agent
--system center essentials agent

Hi,
You cannot upgrade from SCOM2007R2 to SCOM2012SP1, you must upgrade to SCOM2012 and the upgrade to SCOM2012SP1
Cameron Fuller has a blog:
http://blogs.catapultsystems.com/cfuller/archive/2013/02/11/can-you-upgrade-from-opsmgr-2007-r2-to-opsmgr-2012-sp1-scom-sysctr.aspx
Upgrading System Center 2012 – Operations Manager to System Center 2012 SP1
http://technet.microsoft.com/en-us/library/jj899854.aspx
"The only supported upgrade path to System Center 2012 Service Pack 1 (SP1), Operations Manager is from System Center 2012 – Operations Manager. If you are upgrading from System Center Operations Manager 2007 R2, you must first upgrade to System Center 2012
– Operations Manager"
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

SCOM 2012 SP1 Upgrade

Hello,
I have a SCOM 2007 R2 CU7 server that I upgraded to SCOM 2012. I am running Windows Server 2008 R2 SP1 and SQL Server 2008 R2 SP2. I tried twice to upgrade it to SCOM 2012 SP1 and it failed both times. In the OpsMgrSetupWizard.log file,
I see this error:
: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Incorrect syntax near 'MERGE'. You may need to set the compatibility level of the current database to a higher value to enable this feature.
See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE.
Incorrect syntax near the keyword 'AND'.
Incorrect syntax near the keyword 'THEN'.
[10:58:04]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
[10:58:04]: Error: :RunStandardScripts failed with the following exception: : Threw Exception.Type: System.Reflection.TargetInvocationException, Exception Error Code: 0x80131604, Exception.Message: Exception has been thrown by the target of an invocation.
[10:58:04]: Error: :StackTrace:   at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Microsoft.EnterpriseManagement.SetupFramework.ActionEngine.Action.Run(String displayStringNamespace, ProgressData progressData, Func`2 progressDelegate)
   at Microsoft.EnterpriseManagement.SetupFramework.ActionEngine.InstallStep.Run(String displayStringNamespace, ProgressData progressData, Func`2 progressDelegate)
[10:58:04]: Error: :Inner Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131604, Exception.Message: Incorrect syntax near 'MERGE'. You may need to set the compatibility level of the current database to a higher value
to enable this feature. See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE.
Incorrect syntax near the keyword 'AND'.
Incorrect syntax near the keyword 'THEN'.
After both failed upgrades, I had to re-install SCOM 2007. How can I get the upgrade to complete? The prerequisites have been installed.

So try to change the SQL database Compatibility Level to SQL 2008 (100):
1. Open SQL Server Management Studio
2. Connect to the SQL server hosting the Operations Manager Databases
3. Expand Databases, Right Click on OperationsManager and click properties
4. Click Options, Change the Compatibility level: drop down to SQL Server 2008 (100), Click OK
5. Right Click on OperationsManagerDW and click properties, Click Options
6. Change the Compatibility level: drop down to SQL Server 2008 (100), Click OK
Niki Han
TechNet Community Support

SCOM 2012 SP1 Upgrade - RMS fine but can't upgrade reporting or web console

Hi,
We've just upgraded our RMS to SCOM 2012 SP1 and everything went smoothly as per the documentation. However when I next try to upgrade the Reporting or Web Consoles (located on separate servers) to SP1 I am presented with a message saying:
"The management server to which this component reports has not been upgraded".
At that point we cannot proceed past the prerequisite checker.
I am totally confident that the SP1 upgrade went through on the RMS and all file versions are at SP1.
Can anyone help please?
Thanks,
Tim

Hi Retee,
I was not able to find a fix for this but I did find a workaround.
1. I copied the installation files from the SCOM 2012 SP1 DVD/ISO to a folder, SCOM_2012_INSTALL on the reporting server.
2. Browsed to the following folder ..\SCOM_2012_INSTALL\setup\AMD64\ and commented out the following section of the IntermilestoneUpgradePrereqs.xml file:

3. Ran ..\SCOM_2012_INSTALL\setup.exe and the upgrade was successful.
Our SCOM infrastructure has now been at 2012 R2 for a couple of months and I have not seen any issues caused by commenting out this section. But as always, use at your own risk.
Hope this helps.
Thanks,
Iain

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.

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.

Windows 2012 upgrade plan to R2 hosted with SCOM 2012 SP1

Dear Experts,
Currently we are hosting SCOM 2012 SP1 on Windows 2012 Operating System and the Server team plan to upgrade Windows server OS 2012 to Windows OS 2012 R2.
So, Is there any Potential road blocks and things to take care for SCOM 2012 SP1 if we want to upgrade the Windows 2012 R2 OS.
Thanks,
Saravana
Saravana Raja

Hi,
I have seen this a couple of times without any issues.
Just make sure you backup all SCOM related (databases if local, management packs etc).
www.coretech.dk - blog.coretech.dk

Scom 2012 sp1 to Scom R2 upgrade?

Dear all,
We are running with scom 2012 sp1 , is it mandatory to upgrade to scom 2012 r2 ? Since we heard scom 2012 sp1 has some bugs.

Hi,
It is highly recommend upgrade SCOM 2012 SP1 to SCOM 2012 R2 but it is not necessary. You could view NEPA PFE Team blog that demostrate how to upgrade SCOM 2012 SP1 to SCOM 2012 R2.
http://blogs.technet.com/b/nepapfe/archive/2013/11/26/upgrading-scom-2012-sp1-to-scom-2012-r2.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.

Upgrading SCOM 2012 SP1 agent to SCOM 2012 R2

Hello All
We have created a new SCOM 2012 R2 environment and now planning to upgrade our agents which are in SCOM 2012 SP1 environment . We want to keep the agents dual homed for some time . I would like to know if there is any kind of automation/script that someone
has already made to upgrade SCOM agent from SP1 to R2 ,and at the same time have it dual homed (pointing to 2 MG)

You may try
1) upgrade the SCOM agent by
msiexec /i MOMAgent.msi /qn /l*v D:\logs\AgentUpgrade.log AcceptEndUserLicenseAgreement=1
2) Add additional management group y using following vb script
Option Explicit
Dim objMSConfig
Set objMSConfig = CreateObject("AgentConfigManager.MgmtSvcCfg")
‘Add a management group
Call objMSConfig.AddManagementGroup ("MyManagementGroupToAdd", "company.sm.net",5723)
For detail, pls. refer to
http://technet.microsoft.com/en-us/library/jj899848.aspx
http://msdn.microsoft.com/en-us/library/hh329017.aspx
Roger

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

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 R2 Upgrade Plan Discussion

Dear Experts,
Currently I have a RMS and one MS Server with SCOM 2007 R2 in my Test Environment (Windows 2008 R2).
Now, The Upgradation plan is below and please correct me if I am wrong.
SCOM 2007 R2 CU4 --> SCOM 2012
SCOM 2012 --> SCOM 2012 SP1
SCOM 2012 SP1 --> SCOM 2012 R2.
So we need to purchase of three types of SCOM 2012 versions S/W or else we can simply download those versions from Microsoft ?
Please provide me the complete process of this Migration cycle.
Saravana Raja

Hi Saravana:
Upgrading to System Center 2012 – Operations Manager is supported from Operations Manager 2007 R2 CU4, or from the latest available CU. See
http://technet.microsoft.com/en-us/library/hh476934.aspx.
As for upgrading from SCOM 2012 to SCOM 2012 SP1 to SCOM 2012 R2, MVP Marnix Wolf is clear that you need to perform each upgrade step separately:
http://thoughtsonopsmgr.blogspot.com/2013/07/upgrade-paths-to-system-center-2012-r2.html. The "complete process" would consists of performing the upgrade for each version one after the other, again, just as you put in your plan.
You do not need to purchase any additional software, but you will need to download the 3 versions as you described from Microsoft volume license site or other media source.
John Joyner MVP-SC-CDM

SCOM 2012 SP1 Web Console not filtering "Items by Text Search"

I have the weirdest issue with not one, but two installations of SCOM 2012 (SP1) specific to the Web-based Console. I have to think that it's something that I've messed up since each installation (separate domains, separate environments) is exhibiting
the exact same behavior and that I cannot find a single mention by anyone else experiencing this problem anywhere on the 'net.
The problem I'm encountering is that when I try to filter the list of objects using the "Look for: Items by text Search" option, the list doesn't filter! It's just the *weirdest* thing!
For example, I go into "Microsoft Windows Server; Performance" and select "Disk Capacity". The view loads just fine with two panes up top, and the object list down below. I select a pane to display the list of objects which
gives me all the servers discovered/managed by SCOM. I changed the "Look for:" drop-down from "All Items" to "Items by Text Search" which makes the text field (to the right) active. I enter my text string and........
nothing happens. When I hit "Enter" the pane simply refreshes. The "Reset" button doesn't become active further reinforcing the fact that something just ain't right.
I have a installation of SCOM 2007 R2 and this feature works flawlessly.
Anyone have any idea as to what I may have missed or what I might do to resolve this issue? Again, I've found absolutely nothing on the Internet specific to this issue (unless my search criteria is woefully flawed) which suggests that I've messed something
up.
Thank you in advance for your time!
-Todd
PS - this feature works just fine in the installed/thick client/console.

Unfortunately, I never did receive an answer to this issue/post, and I never found a solution with this version of SCOM.
I did, however, just test this functionality on the SCOM 2012 R2 installation and discovered that the "Items by text search" filter in the web console *does* work as one would expect. So, if you're able, upgrade to SCOM 2012 R2 and you should
be much happier with the result. (I think I'm running Cumulative Update #2, if that helps.)
Hope this helps!
-Todd

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

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.

SCOM 2007 R2 to SCOM 2012 SP1 upgrade issues.

Similar Messages

Maybe you are looking for