I have configured SCSM 2010 to SCOM 2007 R2 for automating the pull of alerts from SCOM to SCSM. I've also set up the subscription for the internal connector created in SCOM by SCSM. However, the alerts are never pulled into SCSM as incidents. I can, however, forward/push an alert in SCOM to the internal connector created by SCSM and have it show up in SCSM as an incident as well as see the incident number on the alert in SCOM. Has anyone ever seen this behavior or better yet fixed the automated pull into SCSM? :) Is anyone using the Alerts to Incidents Connector successfully for SCSM 2010 and SCOM 2K7 R2? Thanks!!!!!

Hi, Did you see any event regarding this issue in SCOM? Please check if any troubleshooting information on the following link will work: http://www.systemcenterforum.net/index.php?/topic/840-troubleshooting-tips-for-your-scsm-scom-alert-connector/ Please Note: Since above web sites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information You can also post this issue to SCSM forum to check if there is any troubleshooting method from other side.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.

Hi OpsMgr 2007 R2 --> SCSM 2010 for Incident Management is a case of setting up the connector within SCSM and the subscription within OpsMgr. What routing rules have you set up within the SCSM console \ connector for the OpsMgr alerts? What user did you use for the Run As Account for the Connector? Does it have rights to OpsMgr to pull the data? If you look at the connector state within SCSM - when was the last time it executed? Do you see any errors in the SCSM Management Server event logs? http://blogs.technet.com/b/servicemanager/archive/2010/04/14/troubleshooting-tips-for-your-scsm-scom-alert-connector.aspx Cheers Graham View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Hi OpsMgr 2007 R2 --> SCSM 2010 for Incident Management is a case of setting up the connector within SCSM and the subscription within OpsMgr. What routing rules have you set up within the SCSM console \ connector for the OpsMgr alerts? What user did you use for the Run As Account for the Connector? Does it have rights to OpsMgr to pull the data? If you look at the connector state within SCSM - when was the last time it executed? Do you see any errors in the SCSM Management Server event logs? http://blogs.technet.com/b/servicemanager/archive/2010/04/14/troubleshooting-tips-for-your-scsm-scom-alert-connector.aspx Cheers Graham View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Graham, Thanks for the reply!! I've added a registry setting to see SCSM starting and ending a synch in the Operations Manager Event log to be able to narrow the search on the SCOM server. --------------------------- Connector Name=Error Severity, Medium Priority Alerts To SvcMgr, Id=2fda02ac-5c62-a63e-93cb-9f6038a7632d Starting alert synchronization. ---------------------------- There are no other log entries except for the following Audit Failure in the Security Event log on the SCSM server which may or may not be part of the issue but is within the window of synchronization. --------------------------- An application attempted an operation: Subject: Client Name: CSLSCMGRSVC Client Domain: DCFCNT Client Context ID: 4500324 Object: Object Name: IsUserAdministrator Scope Names: 210e5fdf-dbe8-4f56-9ebc-00ed728d057f Application Information: Application Name: Microsoft System Center Application Instance ID: 4487145 Access Request Information: Role: Role Groups: Group Operation Name: User_IsAdministrator__Check (142) --------------------------------- The RunAs user for the Alert Connector has all the authorizations and is in all the right groups (as described here Operations Manager 2007 Alert Connector - http://technet.microsoft.com/en-us/library/ff461084.aspx). The subscriptions in SCOM's internal connector have the same criteria as what the Alert Routing rules specify in SCSM. I have validated that Alerts do exist in SCOM that also fit this criteria, so that after the subscription is setup in SCOM, alerts show up in SCSM just like the MSFT documentation states. :) The execution times (Start and Finish Time) are not updating. These times do not update unless data is found to be synched. SCOM is not a new install of SCOM 2k7 R2. It has been upgraded from some other prior version. I'm smelling this might be an issue since I setup up a whole new environment in the cloud (CloudShare) and have gotten all this to work. I have not tried to make SCOM log verbosely. The environment has a box for SCOM, box for SCSM, box for SCSM Data Warehouse, and a SQL cluster for data and reporting services (ops mgr rpt svc is a separate instance due to authorization implementation). All the latest service packs and cumulative updates have been applied. Thanks!!!

Fixed by unistalling and reinstalling Ops Mgr. Yeah, not fun.JoeyD