Mssql collation conflict while update scom 2012 sp1 to r2

hi all
i have scom 2012 sp1 (windows server2008 r2), mssql 2012 sp1 (windows server2008 r2)
while updating scom 2012 sp1 to r2 error is appears:
"DB operations failed with SQL error 468: Cannot resolve the collation conflict between "Cyrillic_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation."
how can i change collation of db "OperationsManager" from "Cyrillic_General_CI_AS" to "SQL_Latin1_General_CP1_CI_AS"?
thanks in advance

For Failed to store data in the Data Warehouse. Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation, you can refer below link
http://thoughtsonopsmgr.blogspot.com/2010/04/failed-to-store-data-in-data-warehouse.html
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

Similar Messages

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 Update Rollups

Hi All,
I am planning to deploy patches on SCOM server. We are on SCOM 2012 SP1 as of now. As you know Microsoft has been released UR1, UR2, UR3, UR4, UR5 and UR6 for SCOM 2012 SP1.
Do I need to deploy each UR one by one on SCOM server or UR6 will have all fixes?
If I go for directly UR6 then does this patch contains all fixes which are available till UR5?

http://blogs.technet.com/b/server-cloud/archive/2014/04/23/system-center-2012-sp1-ur6-and-system-center-2012-r2-ur2-now-available.aspx
Customers can now download the latest update rollups for both System Center 2012 SP1 and System
Center 2012 R2. Update rollups provide a cumulative package of fixes for each System Center component and are available from Microsoft Update. Alternatively, they can be manually downloaded from the Microsoft Update Catalog.

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

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.

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 Cu4 Web Console issue logging

Hi I am having an Issue with the SCOM 2012 sp1 Cu4 Web console,
When logon to the web console its Says Singing IN,
And the loops on Initializing....
after a while I get this error,
Please provide the following information to the support engineer if you have to contact Microsoft Help and Support :
System.TimeoutException: [HttpRequestTimedOutWithoutDetail]
Arguments:
http://localhost/OperationsManager/Services/DataAccessService.svc
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem.
See
http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20913.00&File=System.ServiceModel.dll&Key=HttpRequestTimedOutWithoutDetail ---> System.Net.WebException ---> System.Net.WebException
   at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult)
   at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClassa.<EndGetResponse>b__9(Object sendState)
   at System.Net.Browser.AsyncHelper.<>c__DisplayClass4.<BeginOnUI>b__0(Object sendState)
   --- End of inner exception stack trace ---
   at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state)
   at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)
   --- End of inner exception stack trace ---
   at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args, IAsyncResult result)
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.Proxy.ServiceReference.DataAccessServiceClient.DataAccessServiceClientChannel.EndExecute(IAsyncResult result)
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.Proxy.ServiceReference.DataAccessServiceClient.Microsoft.EnterpriseManagement.Presentation.DataAccess.Proxy.ServiceReference.IDataAccessService.EndExecute(IAsyncResult result)
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.Proxy.ServiceReference.DataAccessServiceClient.OnEndExecute(IAsyncResult result)
   at System.ServiceModel.ClientBase`1.OnAsyncCallCompleted(IAsyncResult result)
I found that the only way to fix it previously was to completely remove IIS from the server and reinstall everything connecting to the Web Console, so far its not the best way to go as I keep getting this error after 2 days,
Can anyone tell me how I would even go about diagnosing this?
Kind Regards

Got the same issue again with Update Release 2 for R2,
then found this blog, but it did not help me, only guided me in a direction
http://thoughtsonopsmgr.blogspot.com/2013/12/quick-fix-register-aspnet-40-with-iis.html
What help me was to re-add the svc-integrated-4.0 by copying and pasting the info it, same with the ScriptModule-4.0.
Don't know why that worked for me but this is a funny issue,
I also don't recommend doing this, as it only worked for me.

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

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 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 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 2012 SP1 - SCVMM 2012 SP1 Integration

Hi All,
I need to integrate SCOM 2012 SP1 (without UR)with SCVMM 2012 SP1(without UR).
Is Update Rollup required for this integration as a prerequisites? or We can directly proceed with Integration without update Rollup. Please advice.
Can we get performance date of virtual machine by integration scom with scvmm?
Thanks and Regards
Karthick M

Hi,
To monitor virtual machines in VMM, we should integrate VMM with SCOM, please go through the article below:
How to Connect VMM with Operations Manager
https://technet.microsoft.com/en-us/library/hh882396.aspx
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

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

SCOM 2012 SP1 UR4 management servers grey state

Hi,
My SCOM environment is made up of the below :-
SCOM 2012 SP1 UR4.
3 SCOM Management Servers all on Windows 2008 R2 SP1.
Shared SQL 2008 cluster with 2 Windows nodes also on same OS.
Just recently all our SCOM management servers have been flipping in and out from grey to green state. Gateways/agents all look ok as showing green. Alerting from agents appears normal as can see lots of them in console.
Have flushed the health state cache folder on all 3 SCOM MS's and still the same issue.
Appreciate any help on this one.

Event id: 7011 - Was your server recently patched (Installed by any automatic updates) ?
IS SCCM Configured in your MS? If Yes disable and check?
Is Windows update service running ? Stop if for one or two days and check if this issue still appears
Reference threads:
http://social.technet.microsoft.com/Forums/en-US/b86e5a3d-0c2e-4d5e-9d3d-905da91fc982/scom-2012-event-id-7011-service-control-manager-error-when-fep-definition-updates-apply?forum=configmanagersecurity
http://stefanroth.net/2012/09/26/scom-2012-event-id-7011-service-control-manager-error/
Solution also available in: http://technet.microsoft.com/en-us/library/cc756319(v=ws.10).aspx
===========================================
For Event id 20026 -
1. Does your Operationsmanager database have enough space ? Check that first.
What is you DB size ?
How much is the free space left ?
2. Was there any resent change in the SCOM Action accoutn password ? Or has the password expired. Try re entering the SCOM Action password by re directing your self to Administration tab --> Run as Config -- > Accounts --> SCOM Action account.
The description would be - This is the user account under which all rules run by default on the agent.
Right click and go to properties and re enter the account name and password there and check.
Refer the below screen shot
Check this article as well:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/102d443c-db0e-4bf2-b0d6-31d7f9328537/all-agents-greyed-out-multiple-event-errors-with-ids-20026-20028?forum=operationsmanagergeneral
============================================
Event id : 11904 - As per my knowledge appears due to incorrect Alrting string display name selected in any Rule or monitor.
Also the description what you pasted in Event id : 11904 says Microsoft.SystemCenter.HealthService.ActionAccountConfigured.Error as highlighted below.
Suggest to re enter the action account password and tell the results.
Also is the Healthservice on the MS running using System account or Domain account ?
=================================================================
Description : The Microsoft Operations Manager Expression filter Module failed to query the delivered item, item was dropped.
Property Expression: Reachability/State
Error : 0XC00EE22
One or more workflows were affected by this. Workflow
name: Microsoft.SystemCenter.HealthService.ActionAccountConfigured.Error
Gautam.75801

Mssql collation conflict while update scom 2012 sp1 to r2

Similar Messages

Maybe you are looking for