Operations Manager 2007 R2 Failed RMS Promotion

Forum,
I am moving our RMS to a 64-bit computer in preparation to upgrade to Operations Manager 2012. I have followed the directions found in the How to Promote a Root Management Server and it seemed successful. After reviewing the event logs, I have found repeating
21042 and 29106 events. There appears be a problem with my Secure Storage Key. I have tried creating a new key but that doesn't help. I have tried reinstalling my RMS server but I always end up at the same place. The agents are getting the 20070 error and
are unable to communicate with the server. Is there a way to rebuild the secure storage key?
RMS OS - Windows 2012R2
RMS - Ops Manager 2007R2 CU7
21042 Event
Operations Manager has discarded 1 items in management group LCC, which came from $$ROOT$$. These items have been discarded because no valid route exists at this time. This can happen when new devices are added to the topology but the complete
topology has not been distributed yet. The discarded items will be regenerated.
29106 Event
The request to synchronize state for OpsMgr Health Service identified by "00745302-047f-944b-0542-544eb4314c22" failed due to the following exception "System.Security.Cryptography.CryptographicException: Error occurred during a cryptographic
operation.
Server stack trace:
   at Microsoft.EnterpriseManagement.Mom.Internal.AesNativeTransform.DepadBlock(Byte[] block, Int32 offset, Int32 count)
   at Microsoft.EnterpriseManagement.Mom.Internal.AesNativeTransform.TransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount)
   at Microsoft.EnterpriseManagement.Security.SecureStorageManager.Decrypt(Byte[] value)
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.CredentialDocumentHelper.CreateCredentialSectionsForGivenCredentialType(XmlWriter& writer, Result dbRow)
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.CredentialDocumentHelper.InsertCredentialInfo(XmlWriter& writer, ReadOnlyCollection`1 requestedGuids, List`1 dbList, TypeOfCredentialDocumentElement elementType)
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.CredentialDocumentHelper.GenerateCredentialAndCredentialReferenceDocument()
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.RootConnectorMethods.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1
modifiedSecureStorageReferences, ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
   at Microsoft.EnterpriseManagement.Mom.Sdk.Service.SDKReceiver.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences,
ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.EnterpriseManagement.Mom.Internal.ISdkService.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences,
ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
   at Microsoft.Mom.ConfigService.Networking.ConnectionFactory.Connection.Sender.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1
modifiedSecureStorageReferences, ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
   at Microsoft.Mom.ConfigService.Networking.ConnectionFactory.Connection.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences,
ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.SecureDataWriter.Write(StateSyncResponseMessage response)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.WriteState(StateSyncResponseMessage response)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.Write(StateSyncResponseMessage response)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.Write(StateContext stateContext, ConfigurationItems configurationItems, StateSyncResponseMessage response, IConnection connection)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.CreateResponse(Managers managers)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.Managers.Synchronize(OnDoSynchronizedWork onDoSynchronizedWork)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Execute(Managers managers)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Run(Guid source, String cookie, Managers managers, IConfigurationDataAccessor dataAccessor, Stream stream, IConnection connection)".
Agent Event Error 20070
The OpsMgr Connector connected to RMS ServerName, but the connection was closed immediately after authentication occurred. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server
has not received configuration. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.
Thanks,
Warren

Hi Warren,
May be it helps you:
http://blogs.technet.com/b/kevinholman/archive/2009/11/10/29106-event-on-rms-index-was-out-of-range-wait-what.aspx
http://scug.be/christopher/2012/08/31/scom-2007-r2-configuration-not-loaded/
http://anandthearchitect.com/2009/12/02/scom-2007-r2-%E2%80%93-rms-server-not-seeing-the-agents-or-agents-are-not-talking-to-the-server/
Natalya

Similar Messages

Upgrade System Center Operations Manager 2007 R2 CU6 -- 2012 RTM issues (Assembly related exception in log)

Hi guys
I am currently performing a distributed, complex upgrade with a customer:
4 management servers (1 being RMS), both databases (OM & DW) on a single SQL Server (2008 R2 SP2)
We moved over the RMS role to another server and decomissioned the old one due to it being a 2003 server.
Then we upgraded all non-RMS management servers.
We had some issues with them as well (same error in the log), but when we reinstalled the 2007 R2 binaries & patches and redid the upgrade it came through fine.
The RMS however keeps throwing the same error. Things I tried:
- Full clean of the server including momclean and msizap, then reinstall the RMS and retry the upgrade
- Reregister of the msiexec server
I am suspecting some issues with assemblies and / or GAC, but no clear proof on that, only that it crashes after performing assembly operations.
Below an extract from the RemoveMOMServer.log (the error occurs when uninstalling SCOM 2007 R2)
Can anyone help out or give me some pointers on possible causes?
Many thanks in advance!
MSI (s) (F4:CC) [15:43:55:259]: Executing op: UpdateEstimatedSize(EstimatedSize=0)
MSI (s) (F4:CC) [15:43:55:261]: Executing op: ProductCPDisplayInfoRegister()
MSI (s) (F4:CC) [15:43:55:263]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommit,,)
MSI (s) (F4:CC) [15:43:55:264]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommit,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (F4:CC) [15:43:55:266]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitUninstall,,)
MSI (s) (F4:CC) [15:43:55:266]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitUninstall,ActionType=3649,Source=BinaryData,Target=ExecNetFx,CustomActionData=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe uninstall "Microsoft.EnterpriseManagement.OperationsManager,
Version=6.0.4900.00, Culture=neutral, PublicKeyToken=31BF3856AD364E35"€500€C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe uninstall "Microsoft.EnterpriseManagement.OperationsManager.Common, Version=6.0.4900.00, Culture=neutral, PublicKeyToken=31BF3856AD364E35"€500€C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe
uninstall "C:\Program Files\System Center Operations Manager 2007\Microsoft.EnterpriseManagement.UI.Foundation.dll"€500€C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe uninstall "C:\Program Files\System Center Operations Manager 2007\Microsoft.EnterpriseManagement.UI.ConsoleFramework.dll"€500€C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe
update /queue€500€C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe update /queue€500)
MSI (s) (F4:CC) [15:43:55:268]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitInstall,,)
MSI (s) (F4:CC) [15:43:55:268]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitInstall,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (F4:CC) [15:43:55:270]: Executing op: ActionStart(Name=PublishFeatures,Description=Publishing product features,Template=Feature: [1])
MSI (s) (F4:CC) [15:43:55:270]: Executing op: FeaturePublish(Feature=MOMServer,,Absent=3,Component=@+h863e0NAgaZ7OoE1)HM[lp(tNC_AUZ$SF(D`%aFTE9fFyfs=F=$JG3?U4%Jg+a[OgIJ9l,ltBUJ6}nEPr^ulwB]8CeSrDJOg^Dv6-5{b^j}@^?vz.j7,3M6C%7,*@eo93k8pr6&&N9$znhtI3,f=ds,sbkr{FsK5s,aat+W9Luq^c2T)%]NK-`Nh95Q?1j(Dg@M-ujVqmWklfnQ9{a+G7w.5xHY-FhkL+vZAB~5y'c@}'jr8WIsm`xe=5orHD{+mjmr3jr^W2UX?7PmxUa@v*Z]~U%@4u.j?-mBUeMsh74(}?767KRj@A72,VR{&Ndp=1kRf[ZQAWW2Vmir6O-EYNi`aVy0=sY*I`g=~^zgj-K41CWIAn3+(O4}ZvX8=hVDIvD^A&7iGA]RjL$JKo'QVT)b@Y@NcD-awAKEm,xN7,?,Ad7cW2b8}K?@`XVc]R`h8k*+PKa=CULr]CV`GY24=J**5wT+^.,Yw,vNCs'_A95dR?W8yIC[JXIm!nzq@5?Enk}PZewbi(r&t1H!94?5m0NzSd96@yq+0'^.?}G.RFEU^J@e`)a-_.e4@W?a@,yfmDTR]^+cbWf.=hV2Lk`!5yfUciqXO0JF?wIvuYFC{LBr*ENyKNMv9@3O~EdzJ!$jxy*dl]uq8{j_GLM1aC_g[-UdCQiC90o{ZS=lW(WUciqXme3eSKW@5fYZQ*R{[[yk0@XZAwJAUIK=yaPrb5j3zZII9*^7LD'L6,,V{p7-suLJ?`v(5R1a5&ko,1X$zkt~8Ic75fYZQ*RaE1v.2pOX8dqQ4PWI)'Vx5^d6cT~W@m1M]xA+z~*JWKX5swUG9JO-4h}&rH2H%obQfhOk?@2$kky4Qx]3yC3vPpLx@bP%U&2$(719F%lc[~}z8HzR.HDHZ)c]{SAz-boA9DSkLX$,eI5Tm1KmpVu+AzEhUp4Ka@(9k~3kSgQX@N@a@gaH@B-,TlvgYR`J9ET02Ay.r4F*v&OktBzm?8g^(@8)Udj
MSI (s) (F4:CC) [15:43:55:273]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (F4:CC) [15:43:55:273]: Executing op: CleanupConfigData()
MSI (s) (F4:CC) [15:43:55:273]: Executing op: RegisterPatchOrder(Continue=0,SequenceType=0,Remove=0)
MSI (s) (F4:CC) [15:43:55:276]: Executing op: RegisterPatchOrder(Continue=0,SequenceType=1,Remove=0)
MSI (s) (F4:CC) [15:43:55:280]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=80035200)
MSI (s) (F4:CC) [15:43:55:280]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager,fileVersion="6.1.7221.99",version="6.0.4900.00",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",
AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:280]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:281]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:55:289]: Verifying accessibility of file: Microsoft.EnterpriseManagement.OperationsManager.dll
MSI (s) (F4:CC) [15:43:55:291]: Using source file security for destination.
MSI (s) (F4:CC) [15:43:55:304]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL, AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:304]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:305]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:55:306]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL, AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:306]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:307]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:55:308]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL, AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:308]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:310]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:55:310]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL, AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:310]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:312]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:59:483]: Internal Exception during install operation: 0xc00000fd at 0x0000000077C24EDC.
MSI (s) (F4:CC) [15:43:59:483]: WER report disabled for silent install.
MSI (s) (F4:CC) [15:43:59:483]: WER report disabled for non-console install.
MSI (s) (F4:CC) [15:43:59:483]: Internal MSI error. Installer terminated prematurely.

Thanks for you updating! For SQL related issue, please post on the following forum:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?category=sqlserver
Regards,
Yan Li
Regards, Yan Li

System center operations manager 2007 R2

HI All,
Can some one share the information , if we can find at what time an rule is generated, or if we can find how many rules are generated at a particular given time.
Rgs,

Hello,
What do you mean by rule is generated? do you mean Generated Alerts? or Created Rules?
For generated alerts, you can see the time on the alert details. or you can generate Alerts Report to show the common alerts or alerts in a specific timeframe.
Also you can use some useful SQL Queries to get the required info from this blog post:
http://blogs.technet.com/b/kevinholman/archive/2007/10/18/useful-operations-manager-2007-sql-queries.aspx
Regards,
Mazen
Regards, Mazen Ahmed

System Center Operations Manager 2007

Hi,
Is there anyone who is monitoring their IronPort C-series with System Center Operations Manager 2007?
If so, is there anything I should look out for implementing it?
/Fredrik

Hi
If scom supports SNMP, then we can monitor Ironport devices. We can monitor Ironport via Solarwinds and Hp openview.

Can we deploy Antimalware Policy Operations Manager 2007 to Operations Manager 2012?

Can we deploy Antimalware Policy Operations Manager 2007 to Operations Manager 2012?

Hi,
Yes, you can check, you can update it to match the informaton here:
http://blogs.technet.com/b/manageabilityguys/archive/2013/11/26/system-center-2012-r2-operations-manager-anti-virus-exclusions.aspx
Reagrds,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Team Foundation Server 2010 and System Center 2012 SP1 Operations Manager WorkItem Synchronization fail

Hello,
We are currently implementing a Devops solution with SCOM 2012 SP1 and TFS 2010 SP1 and we would like to synchronize APM alerts with TFS and the Operational Issue WorkItem. However we are not
able to sync anything.
Here is our environments :
Products :
SCOM
System Center Operations Manager 2012 SP1
French
OS: Windows 2012 SP1 Std x64
French
DB: SCOM SQL Server 2012 SP1 x64
Management Pack
MP Operations Manager TFS Work Item Synchronisation 7.0.9538.0
MP Alert Attachement 7.0.9538.0 (We have also try the version in the VM DEVOPSALL : 7.0.9538.1005)
TFS
Team Foundation Server 2010 SP1
French 10.0.40219.1
OS: Windows 2008 R2 SP1 Std x64
French
DB: TFS SQL Server 2008 x64
TFS 2012 Object Model Installer (We have also try the version 2010)
Here is our configuration :
TFS Platform
This a French platform with a project based on the Process Template SCRUM 1.0 alone in a Team Project collection. The Operational Issue import completed successfully. It’s possible to manipulate
Operational Issue for all of its states from TFS.
SCOM Platform
We followed the documentation at :
http://technet.microsoft.com/en-us/library/jj883936.aspx
to configure SCOM Alert Attachment and Operation Manager Tfs Work Item Synchronization. Everything seems to be ok. All configurations succeed. We did not configure Intellitrace collector.
The problem occurs when we are trying to push an APM alert to TFS. When we assigned an alert to the Engineering nothing is synchronized in TFS. There is no error in the event viewer on the TFS
server. But, on the SCOM server we get 2 exceptions raised by Microsoft.EnterpriseManagement.Modules.Apm.TfsWISync.OMModules. We provide you the log of the SCOM Server in this mail.
Detailed exceptions :
Exception message are in French. In English it could be : OEF expected. The followed elements are not closed : Source, Link.
Microsoft.SystemCenter.TfsWISync.SyncAttachments.Rule
TFS Work Item Synchronisation ServerName
{EC924637-2725-7C94-8F37-013B657F4530}
Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadOpenAlertsModule
System.Xml.XmlException: Fin de fichier inattendue. Les éléments suivants ne sont pas fermés : Source, Link. Ligne 1, position 65537.
   à System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
   à System.Xml.XmlTextReaderImpl.ParseElementContent()
   à System.Xml.XmlReader.ReadString()
   à System.Xml.XmlReader.ReadElementString(String name)
   à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.Common.DataItems.Links.DeserializeInternal(XmlReader reader)
   à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.Common.DataItems.Links.Deserialize(String mappings)
   à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadOpenAlertsModule.InitializeConfiguration(XmlReader reader)
   à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadOpenAlertsModule..ctor(ModuleHost`1 moduleHost, XmlReader configurationReader, Byte[] previousState)
Microsoft.SystemCenter.TfsWISync.SyncWorkItems.Rule
TFS Work Item Synchronisation ServerName
{EC924637-2725-7C94-8F37-013B657F4530}
Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadAlertsSyncModule
System.Xml.XmlException: Fin de fichier inattendue. Les éléments suivants ne sont pas fermés : Source, Link. Ligne 1, position 65537.
   à System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
   à System.Xml.XmlTextReaderImpl.ParseElementContent()
   à System.Xml.XmlReader.ReadString()
   à System.Xml.XmlReader.ReadElementString(String name)
   à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.Common.DataItems.Links.DeserializeInternal(XmlReader reader)
   à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.Common.DataItems.Links.Deserialize(String mappings)
   à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadAlertsSyncModule.InitializeConfiguration(XmlReader reader)
   à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadAlertsSyncModule..ctor(ModuleHost`1 moduleHost, XmlReader configurationReader, Byte[] previousState)
According to you, is there a possible incompatibility of the synchronization system with French environments?
Thanks for your help.
Gregory OTT => http://twitter.com/gregory_ott
ALM Engineer at Tekigo => www.tekigo.com

Hi,
To monitor the complete TFS infrastructure, you need additional monitoring packs that alert you about a wide range of problems with TFS components. When you import the TFS Work Item Synchronization management pack, it is a best practice to
also import and configure these monitoring packs, you can double check these:
Monitoring Integration between Operations Manager and TFS in System Center 2012 SP1
http://technet.microsoft.com/en-us/library/jj899893.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.

Cisco UCS Management Pack for System Center Operations Manager 2007 R2 Login Error

I have Cisco UCS 1.4 (3q) and just installed the MP v2.1 for Cisco UCS, however when I click on the "Management Pack Events" alert view in the SCOM console, there are error for event number 19900. The description of the error is as follows:
Description:
CISCO UCS R2 MP (https://10.x.x.x/nuova) [CISCO.UCS.R2.Proxy.LoadCache.ProbeAction.vbs] : CISCO UCS Login Error: Authentication failed (Code: 551)
I noticed that it's looking for the /nuova directory, but in order to login to our UCS environment, we usually just go to the IP address - so I'm wondering if that has something to do with it? I've verified that when going directly to the IP from Internet Explorer I can login using the opsmgr credentials we specifically created for this account. I've also gone through the process of creating a run-as account on the SCOM side and associated it with the correct profiles.
Any help is greatly appreciated.

Troubleshooting has found out its user error, wrong password configured.

Microsoft Operations Manager Condolidator Module processing thread failed

Hello,
I got the error: The Microsoft Operations Manager Condolidator Module processing thread failed with an internal error and must be unload.
with event ID 11105 & 11108 but not the one in the article is it the same issue or more ...
I could not find any WMI issue as stated in http://thoughtsonopsmgr.blogspot.com/2011/01/error-consolidator-module-failed.html
Any idea?
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

try clearing the health service cache on the agents and restart the health service to reload that workflow.
Juke Chou
TechNet Community Support
I did already twice and this did not fix the issue.
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Operations Manager 2012 R2 Management Pack importing issue

Hi
I seem to be having an issue importing certain management packs, when i do i get the below error:
Windows Server 2008 Operating System (Monitoring) could not be imported.
If any management packs in the Import list are dependent on this management pack, the installation of the dependent management packs will fail.
Verification failed with 2 errors:
Error 1:
Found error in 2|Microsoft.Windows.Server.2008.Monitoring|6.0.7296.0|Microsoft.Windows.Server.2008.Monitoring|| with message:
Could not load management pack [ID=Microsoft.Windows.Server.2008.Discovery, KeyToken=31bf3856ad364e35, Version=6.0.7296.0]. The management pack was not found in the store.
: An error occurred while loading management pack b4bda654-49bd-6e04-ca24-e152fc227001 from the database
Error 2:
Found error in 2|Microsoft.Windows.Server.2008.Monitoring|6.0.7296.0|Microsoft.Windows.Server.2008.Monitoring|| with message:
Could not load management pack [ID=Microsoft.Windows.Server.Library, KeyToken=31bf3856ad364e35, Version=6.0.7218.0]. The management pack was not found in the store.
: Version mismatch. The management pack ([Microsoft.Windows.Server.Library, 31bf3856ad364e35, 6.0.6957.0]) requested from the database was version 6.0.7218.0 but the actual version available is 6.0.6957.0.
Please can someone advise.
Regards
Adrian

Hi,
Solution: An exception is thrown while importing the Red Hat Linux Management Pack for Operations Manager 2007
http://blogs.technet.com/b/operationsmgr/archive/2010/12/15/solution-an-exception-is-thrown-while-importing-the-red-hat-linux-management-pack-for-operations-manager-2007.aspx
Based on this case, the issue might be resolved by re-importing the Microsoft.Windows.Server.Library Management Pack.
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]

SCCM 2007 agent fails top install...

Hello,
The installation on two clients from 3 are failing with the following:
No client is currently installed. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Installing version 4.00.6487.2000 of the client with product code {2609EDF1-34C4-4B03-B634-55F3B3BC4931} ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
MSI PROPERTIES are CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
There are no certificate(s) that meet the criteria. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Failed in GetCertificate(...): 0x80040281
ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
File 'C:\Windows\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi' doesn't have a valid digital signature. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
A Fallback Status Point has not been specified. Message with STATEID='316' will not be sent. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Why these agents are suddenly failing to install as more than 1,000 succeeded..
Same OU as others
Same Subnet as others
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

The top listed error message are meaningless and not fatal.
Note that posting a couple of out of context messages is completely meaningless though. Please post the entire relevant, unedited snippets of the ccmsetup.log file.
Jason | http://blog.configmgrftw.com | @jasonsandys
Hello,
Here the complete ccmsetup.log
==========[ ccmsetup started in process 6456 ]========== ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Version: 4.0.6221.1000 ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /mp:configmgrsrv.ad ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
CCMHTTPPORT: 80 ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
CCMHTTPSPORT: 443 ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
CCMHTTPSSTATE: 2147483648 ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
CCMHTTPSCERTNAME: ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
FSP: ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Config file: ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Retry time: 10 minute(s) ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
MSI log file: ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
MSI properties: CCMHTTPPORT="80" CCMHTTPSPORT="443" ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Source List: ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
MPs: ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
configmgrsrv.ad ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Updated security on object C:\Windows\ccmsetup\. ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Running as user "SYSTEM" ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Detected 253651 MB free disk space on system drive. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Client OS is not Windows XP Embedded ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Deleted file C:\Windows\ccmsetup\client.msi ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Successfully ran BITS check. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
SSL Registry key Software\Microsoft\CCM not found, assuming Client SSL is disabled. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Certificate doesn't have EKU, meaning good for all usages. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Verified file 'C:\Windows\ccmsetup\ccmsetup.cab' is MS signed. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Successfully loaded ccmsetup manifest file. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Couldn't get directory list for directory 'http://configmgrsrv.ad/CCM_Client/ClientPatch'. This directory may not exist. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Adding file 'http://configmgrsrv.ad:80/CCM_Client/x64/WindowsUpdateAgent30-x64.exe' to BITS job, saving as 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe'. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Adding file 'http://configmgrsrv.ad:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\Windows\ccmsetup\client.msi'. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Couldn't get directory list for directory 'http://configmgrsrv.ad/CCM_Client/i386/00000409'. This directory may not exist. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Starting BITS download for client deployment files. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Successfully completed BITS download for client deployment files. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
Successfully downloaded client files via BITS. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
Updated security on object C:\Windows\ccmsetup\. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
Certificate doesn't have EKU, meaning good for all usages. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
Certificate doesn't have EKU, meaning good for all usages. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
Verified file 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe' is MS signed. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
Installing file 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe' with options '/quiet /norestart'. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
File 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe' returned exit code 775. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Finished installing file 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe'. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
An MP does not exist on this machine. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
No client is currently installed. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Installing version 4.00.6487.2000 of the client with product code {2609EDF1-34C4-4B03-B634-55F3B3BC4931} ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
MSI PROPERTIES are CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
There are no certificate(s) that meet the criteria. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Failed in GetCertificate(...): 0x80040281
ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
File 'C:\Windows\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi' doesn't have a valid digital signature. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
A Fallback Status Point has not been specified. Message with STATEID='316' will not be sent. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Operations Manager Installation Error - Return Value 3

Hello, I am having issues installing Operations Manager Reporting 2007 R2. The installation hangs with no status update a little more then midway through. I am receiving the following exception below. I am trying to install this on a named reporting instance.
013-12-16T16:00:00.0547063-08:00 Debug:
*** Trace Started ***
2013-12-16T16:00:00.0859563-08:00 Debug:
ConfigureOverridesForDWRules: Root Management Server is: CORP32-VS
2013-12-16T16:30:01.7422063-08:00 Error:
ConfigureOverridesForDWRules error: System.TimeoutException : The requested operation timed out.
Exception thrown by custom action:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.WindowsInstaller.InvalidHandleException: The handle is invalid.
at Microsoft.WindowsInstaller.SessionProperties.set_Item(String name, String value)
at Microsoft.Reporting.Setup.ReportingManagedCAs.ConfigureOverridesForDWRules(Session session)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
at Microsoft.WindowsInstaller.CustomActionProxy.InvokeCustomAction(Int32 sessionHandle, String entryPoint)
CustomAction _ConfigureOverridesForDWRules.9B663534_CD9B_41CC_9D93_4E84D3C5E165 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (1C:FC) [16:30:01:804]: NOTE: custom action _ConfigureOverridesForDWRules.9B663534_CD9B_41CC_9D93_4E84D3C5E165 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
Action ended 16:30:01: InstallFinalize. Return value 3.
MSI (s) (1C:80) [16:30:01:804]: User policy value 'DisableRollback' is 0
MSI (s) (1C:80) [16:30:01:804]: Machine policy value 'DisableRollback' is 0
MSI (s) (1C:80) [16:30:01:882]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1133543036,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (1C:80) [16:30:01:882]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (1C:80) [16:30:01:882]: Executing op: DialogInfo(Type=1,Argument=System Center Operations Manager 2007 R2 Reporting Server)
MSI (s) (1C:80) [16:30:01:882]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
Action 16:30:01: Rollback. Rolling back action:

Niki,
I verified the data warehouse SQL server authentication account is indeed blank. I just tried running the installation again and received the following errors in the SQL log.
12/18/2013 07:43:28,spid177,Unknown,Error 777970008<c/> severity 16<c/> state 1 was raised<c/> but no message with that error number was found in sys.messages. If error is larger than 50000<c/> make sure the user-defined message is
added using sp_addmessage.
12/18/2013 07:43:28,spid177,Unknown,Error: 18054<c/> Severity: 16<c/> State: 1.
12/18/2013 07:43:28,spid88,Unknown,Error 777970008<c/> severity 16<c/> state 1 was raised<c/> but no message with that error number was found in sys.messages. If error is larger than 50000<c/> make sure the user-defined message is added
using sp_addmessage.
12/18/2013 07:43:28,spid88,Unknown,Error: 18054<c/> Severity: 16<c/> State: 1.
12/18/2013 07:43:28,spid173,Unknown,Error 777970008<c/> severity 16<c/> state 1 was raised<c/> but no message with that error number was found in sys.messages. If error is larger than 50000<c/> make sure the user-defined message is added
using sp_addmessage.
12/18/2013 07:43:28,spid173,Unknown,Error: 18054<c/> Severity: 16<c/> State: 1.
12/18/2013 07:43:18,spid173,Unknown,Error 777970008<c/> severity 16<c/> state 1 was raised<c/> but no message with that error number was found in sys.messages. If error is larger than 50000<c/> make sure the user-defined message is added
using sp_addmessage.
12/18/2013 07:43:18,spid173,Unknown,Error: 18054<c/> Severity: 16<c/> State: 1.
12/18/2013 07:43:15,spid13s,Unknown,AppDomain 9702 (OperationsManager.dbo[ddl].9701) unloaded.
12/18/2013 07:43:14,spid21s,Unknown,AppDomain 9701 (OperationsManager.dbo[ddl].9700) unloaded.
Also, please see error in the MOMReporting log below:
2013-12-18T07:41:54.8239565-08:00 Debug: ConfigureOverridesForDWRules: Root Management Server is: COR32
2013-12-18T08:11:56.1874277-08:00 Error: ConfigureOverridesForDWRules error: System.TimeoutException : The requested operation timed out.
Exception thrown by custom action:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.WindowsInstaller.InvalidHandleException: The handle is invalid.
   at Microsoft.WindowsInstaller.SessionProperties.set_Item(String name, String value)
   at Microsoft.Reporting.Setup.ReportingManagedCAs.ConfigureOverridesForDWRules(Session session)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
   at Microsoft.WindowsInstaller.CustomActionProxy.InvokeCustomAction(Int32 sessionHandle, String entryPoint)
CustomAction _ConfigureOverridesForDWRules.9B663534_CD9B_41CC_9D93_4E84D3C5E165 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (38:4C) [08:11:56:281]: NOTE: custom action _ConfigureOverridesForDWRules.9B663534_CD9B_41CC_9D93_4E84D3C5E165 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
Action ended 8:11:56: InstallFinalize. Return value 3.
MSI (s) (38:6C) [08:11:56:359]: User policy value 'DisableRollback' is 0
MSI (s) (38:6C) [08:11:56:359]: Machine policy value 'DisableRollback' is 0
MSI (s) (38:6C) [08:11:56:624]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1133657144,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)

Operations Manager Event ID 31901

Hi all,
I am getting error in operations manager agent status column. The error event id is 31901. I have searched a lot on the net for
it's resolution but did not get any helpful link. So please help me to solve this error.
Thanks,
Vishwajeet.

Hi,
Would you please share the detail Event with us?
Regarding the issue, please check the following:
1. Ensure the Remote Registry service is started on the problematic server
2. Logon with the Management server action account and see if the following commands one works:
1) reg query \\<Server FQDN>\HKLM\Software
2) reg query \\<Server FQDN>\HKLM\Software\Microsoft\Exchange
3) reg query \\<Server FQDN>\HKLM\System\CurrentControlSet\Services
3. Clear the HealthService queue on the agent and see if it works:
1) Stop System Center Management service.
2) Go to C:\Program Files\System Center Operations Manager 2007\, and rename the “Health Service State” folder.
3) Restart System Center Management service.
Hope this helps.
Thanks.
Nicholas Li
TechNet Community Support

Operations Manager Event ID 10

Hello,
I have on several servers several error Event ID 10:
SMI-S Script : Inside Discovery Step 1
SMI-S Script : Inside Discovery Step 2
SMI-S Script : path
SMI-S Script : FileConfigFile.xml
SMI-S Script : Before adding to Ops manager
SMI-S Script : After adding to Ops manager
What does this mean? what should I do to prevent these errors?
Apparently they prevent some Management Packs to be applied ....
Or at least delay the process
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi,
Several Management Pack have been imported:
Exchange Server 2010
HP Blade
HP Storage
HP Work
Veeam MP For Veeamware
at least....
these are the event 10 logged
Log Name: Operations Manager
Source: Health Service Script
Date: 11/27/2013 6:28:50 PM
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: OPMGRRMS1.ad
Description:
SMI-S Script : Inside Discovery Step 1
============================================
Log Name: Operations Manager
Source: Health Service Script
Date: 11/27/2013 6:28:50 PM
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: OPMGRRMS1.ad
Description:
SMI-S Script : Inside Discovery Step 2
============================================
Log Name: Operations Manager
Source: Health Service Script
Date: 11/27/2013 6:28:50 PM
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: OPMGRRMS1.ad
Description:
SMI-S Script : pathC:\Program Files (x86)\HP\HP Enterprise Storage\
=================================================
Log Name: Operations Manager
Source: Health Service Script
Date: 11/27/2013 6:28:50 PM
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: OPMGRRMS1.ad
Description:
SMI-S Script : FileC:\Program Files (x86)\HP\HP Enterprise Storage\ConfigFile.xml
==========================================================
Log Name: Operations Manager
Source: Health Service Script
Date: 11/27/2013 6:28:50 PM
Event ID: 10
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: OPMGRRMS1.ad
Description:
SMI-S Script : FlagTrue
================================================
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Cisco IPT and Microsoft System Centre Operations Manager

Hi All
Does anybody used Cisco IPT with System Centre Operations Manager?
Does System Centre Operations Manager supports Cisco CallManager OS and Hardware for monitoring?
Thanks
VKS

Hi David,
Thanks for your reply. I have gone through the links which you have mentioned. As per the Overview of Operations Manager 2007 R2 section in What's New & Improved in Operations Manager 2007 R2 document it is clearly mentioned the below points:
Delivers monitoring across Windows, Linux and Unix servers–all through a single console.
Extend end to end monitoring of distributed applications to any workload running on Windows, Unix and Linux platforms.
The Cisco Servers are also Windows and Linux Based.
Thanks & Regards,
Vaijanath

Event ID: 1418 Operations Manager SDK service threw an exception

Hi
Today we have received the below event in application event viewer. I have checked connector service working without any issues.
We are using SCOM R2 with CU2 and we are using universal connector
Event Type:   Error
Event Source:   OpsMgr Universal Connector
Event Category:   None
Event ID:   1418
Date:       6/14/2012
Time:       5:09:58 AM
User:       N/A
Computer:   INDRMS1
Description:
2012-06-14 05:09:58.283 [Microsoft.SystemCenter.Interop.Framework.Modules.OpsMgrModule] ERROR Error 1:\nFailure message: Request to update alert ignored due to invalid TimeModified\n0cc6a0f1-08cc-4a44-9c2f-7461c97c9fbd\nMicrosoft.EnterpriseManagement.Common.ConcurrentUpdateException:
Request to update alert ignored due to invalid TimeModified ---> Request to update alert ignored due to invalid TimeModified
   --- End of inner exception stack trace ---\n\n
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp
Help us to understand/troubleshoot on this issue.
Donald D'souza (http://donald-scom.blogspot.com/)

Hi,
Please check if you have applied the following update:
Systems Center Operations Manager 2007 R2 Connectors Cumulative Update 2
http://support.microsoft.com/kb/2274165
If the issue persists, please also check the Event Log on the server and see if there are any related errors.
I also noticed you were using SCOM 2007 R2 Cu2, please try CU6:
OpsMgr 2007 R2 CU6 rollup hotfix ships – and my experience installing it
http://blogs.technet.com/b/kevinholman/archive/2012/05/18/opsmgr-2007-r2-cu6-rollup-hotfix-ships-and-my-experience-installing-it.aspx
Hope this helps.
Thanks.
Nicholas Li
TechNet Community Support

Operations Manager 2007 R2 Failed RMS Promotion

Similar Messages

Maybe you are looking for