SCOM CI Connector is stuck in runnig state

Hello,
I have problem with SCOM CI Connector in SCSM. It is stuck in running and 5%. I have tried to disable and re-enable but without success. I can't see any workflow related to this connector in workflow status. Is there any possibility how to stop this or diagnose
what is wrong?
Thanks

I'm assuming you've tried refreshing the connector view. Have you tried reconnecting the console to ensure that you're looking at fresh data?
You can try this:
Get-SCSMConnector "Name" |Set-SCSMConnector -state:disabled
And then try restarting it.
- Get on the floor, do that dinosaur

Similar Messages

Error importing DA from SCOM through connector

Hi,
After the System Center 2012 R2 upgrade we are seeing event log (operations manager log) errors when the SCOM CI Connector runs.
It states that not everything is synced and it complains about the MP Microsoft.Windows.Peripheral.Networkadapter class, that seems to be included in the SCOM Microsoft.WIndows.Library MP but not in the Microsoft.Windows.Library for SCSM.
Instead it is a separate MP that has not changed version.
I´m investigating if it in fact is not syncing all items, maybe it just warns, but either way this seems strange, and I wonder if anyone else has seen this and if so, what have you done?
ERRORS in operations manager log during SCOM CI Connector sync (there are a lot of these errors for different objets).
log error: 34096
Skipping import of instances of class Microsoft.Windows.Peripheral.NetworkAdapter. The management pack Microsoft.Windows.Library that defines this class has version 7.5.8501.0 in Operations Manager that is higher than its version 7.5.3079.0 in Service Manager.
The following steps will resume import of instances of this class:
1) Import management pack Microsoft.Windows.Library with version 7.5.8501.0 into Service Manager.
2) Edit the connector configuration and ensure that this management pack is selected for synchronization.
And also
log error: 34094
Connector Name=Operations Manager CI Connector, Id=rxc51f96-3434-071c-6b93-34ad39962620
Cannot create part of service map [servicename].
Skipped component: resourcename.domain.net.
Class of skipped component: Health Service.
The component resourcename.domain.net is defined in management pack System Center Core Library. Check for prior errors that indicate if importing a missing management pack can help resolve this issue.
E.O

We are finding something similar when syncing OpsMgr DA's with Service Manager.
Cannot create part of service map [xxxx-xxxxxxx].
Skipped component: Local Area Connection 3.
Class of skipped component: Computer Network Adapter.
The component Local Area Connection 3 is defined in management pack Windows Core Library. Check for prior errors that indicate if importing a missing management pack can help resolve this issue.
Skipping import of instances of class Microsoft.Windows.Peripheral.NetworkAdapter. The management pack Microsoft.Windows.Library that defines this class has version 7.5.8501.0 in Operations Manager that is higher than its version 7.5.3079.0 in Service Manager.
The following steps will resume import of instances of this class:
1) Import management pack Microsoft.Windows.Library with version 7.5.8501.0 into Service Manager.
2) Edit the connector configuration and ensure that this management pack is selected for synchronization.
Well, that's not true, I verified the version is 7.5.8501.0 in the ManagementPacks table.
Service Manager 2012 R2 has the Windows Peripheral Library MP that defines a handful of classes derived from classes in the Windows Library MP.
<ClassType ID="Microsoft.Windows.Peripheral.NetworkAdapter" Accessibility="Public" Abstract="false" Base="Windows!Microsoft.Windows.NetworkAdapter" Hosted="true" Singleton="false" Extension="false">
OpsMgr 2012 R2 does not have this MP, it's not in the Management Packs folder in the bits, and I can't find it in the Service Manager bits. There are no discoveries in it, so this is a fun mystery. Anyone else run into this?

Risk Analysis Batch Job Stuck in Ready State

Hi,
I am not able to schedule Risk Analysis Batch job in RAR.The job is getting stuck on READY state(for unlimited period) and not performing any actions.
Nothing is displayed under job history or job logs with job ID.I have check background job demaon ,connectors and other miscell. options but not abl to find any clue.
Even i am executing risk analysis for single user,it's not happening.
Rgds,
Mukesh

For your problem, of job not getting schedule....it seems Deamon is not running.
To delete status of job which are in hung status
change VIRSA_CC_SCHEDULER job id should with status five will show job aborted.
are you using connection type 'Adaptive RFC', don't use it, use SAP JCO.
and restart your GRC box.
Regards,
Surpreet
please do check backend system, for VIRSANH is installed or not.
Edited by: Surpreet Singh Bal on Jan 28, 2011 10:32 AM

Workflow stuck in starting state after applying SharePoint 2010 CU December 2012

I have custom visual studio workflow which are associated with Custom content type. workflow gets triggered automatically when a file is uploaded to SharePoint. Everything was working fine till when i apply the following CU
http://blogs.msdn.com/b/joerg_sinemus/archive/2012/12/27/sharepoint-2010-and-december-2012-cu.aspx
After applying this my workflow get stuck in "Starting" state.
No error were logged in 14 hive logs.
Thanks in Advance!

It took me a while but I came up with a work around. There is a PowerShell script below that can be used to trigger the workflow. Hopefully this will hold all of us over until the official fix arrives.
First remove the auto start on change or new from the affected workflow
Edit the script below to match your environment
Add the script to Windows task scheduler with the PowerShell.exe in the command line
This assumes PowerShell.exe is in the path
Then add the full path and script name in the add arguements text box
Script:
#The purpose of this script is to start the SPD workflow with the windows task scheduler for a trigger
#This should avoid the check in-out issue caused by the December 2012 SP CU patch
#This needs to be run on an account with membership in the farm administration group for SharePoint and Shell in SQL
#You can use a find and replace to replace the server and other names with your actual names
#There are no status messages being used since this will be a scheduled task in the Windows task scheduler
#Add SharePoint modules and create variable space
add-pssnapin microsoft.sharepoint.powershell
start-spassignment -global
#Open the web site, list and the workflow
$site=get-spsite %site url%"
$web=get-spweb %Web url%
#Open the %affected% library or list and workflow association
$%affected%=$web.getlist("%affected%")
$manager=$site.workflowmanager
$culture=[system.globalization.cultureinfo]::currentculture
$wfname="%affected workflow name"
$association=$%affected%.workflowassociations.getassociationbyname($wfname,$culture)
$data=$association.associationdata
$wfrunoption=[microsoft.sharepoint.workflow.spworkflowrunoptions]::synchronous
#Start workflow
foreach ($item in $%affected%.items) {
$site.workflowmanager.startworkflow($item,$association,$data,$wfrunoption)
stop-spassignment -global

Agent get stucked in Reserved State

HI CUCCE gurus,
Need assistance on this issue. In our remote office, our Sales Team has a linegroup setup, the Sales extensions are part of the linegroup and at the same time its their ACD line when they logged in to Cisco Agent Desktop.
The issue is, when they got a call from the linegroup their CAD state change to "Reserved" and it stuck from that state and nothing they can do to change the state but to logoff, close the apps and log back in.
I enabled debug on once of the Sales CAD (see attached output).
Any troubleshooting tips that you can advise or detailed steps to check from our system.
Our CAD is 7.X
Our CUCCE is 7.X
Our CUCM 7.X
Thank you.

Hi Jhun,
Agent stuck in reserved state it means, the ICM has reserved the agent, but the call is not getting delivered to the agent extension.
If you are using SIP trunk, you would probably need to check the CSS and Partitions over the trunk. Also, any recent changes made on the CSS of the SIP trunk you would need to reset the SIP trunk.
The CSS on the SIP trunk should contain the partition of the phone.
Also, you would need to check on the Agent targetting rule in the config manager of the ICM. The agent extensions should be added to the Agent targetting rule
Hope this helps!!!
Cheers,
Dass
Please rate useful posts

I have a set of 3 USB disk connected to my TC via a USB hud. I usually swithc the TC at night. When I restart the next day it stucks in amber state. when I disconnect the USB hub where my discs connects and restart, it start properly. Any hints?

I have a set of 3 USB disks connected to my Time capsule (TC) via a USB hub. I usually switch the TC at night. When I restart the next day it stucks in amber state. When I disconnect the USB hub where my discs connects and restart, the TC will start properly. Any hints?

LOL.. don't switch off the TC.. this is fairly typical behaviour..
Or try a different usb hub.. but you could well and truly run out of hubs before you fix the problem.
Are you running latest firmware for your TC?
What error message is coming up in the airport utility.. amber led is a fault indicator.. look up what the actual fault is and see if it is for instance overloading the usb. You are using a powered hub??
Get one bigger USB hard disk instead of 3 smaller ones.

Content Switching Module (CSM): Sessions stuck in closing state

Hi guys,
I'm troubleshooting a CSM with 4.3(1).
We migrated a real server from windows to linux, since then lot's of sessions stuck in closing state until the idle timer expires.
I traced the traffic from the client to the csm and from the csm to the real server what I saw is the following behaviour at the end of a session:
windows real server: client sends FIN -> real server acks the FIN -> real server sends FIN -> client sends RST -> real server sends RST -> CSM deletes session from session table
The linux real server mostly behaves like the windows real server but sometimes behaves as follows:
client sends FIN -> real server sends FIN, but does not ack the FIN sequence number of the client -> real server sends RST -> client sends RST -> CSM does not delete session from session table, it stucks in closing state
Does anybody know how I can solve this problem of half-closed sessions other than decreasing the idle timeout?
Is it possible to configure CSM to close and delete sessions not only on FIN-ACK packets but also on RST packets?
Or to use a different fast idle timeout when sessions are half-closed?
Many thanks in advance,
Thorsten

Hi Fabrizio,
CSM_FAST_FIN_TIMEOUT is already set to 10 seconds.
What I found out while testing is that CSM_FAST_FIN_TIMEOUT works with configurations where idle timeout is configured > 0.
But when idle timeout is configured to 0 (what meas no idle timeout) the csm seems not to use CSM_FAST_FIN_TIMEOUT: Half closed sessions will stuck in closing state.
Any idea why cms behaves this way?
Regards,
Thorsten

Workflows stuck in "Starting" state.

Workflows have been running fine for awhile. All workflows are currently stuck in a "Starting" state. Was finally able to capture this in ULS
03/20/2014 11:58:23.46 w3wp.exe (0x15AC)                       0x2A98 SharePoint Foundation
Workflow Infrastructure       72fv Unexpected AutoStart Workflow: System.ArgumentException: Value does not fall within the expected range.     at Microsoft.SharePoint.Workflow.SPWorkflowActivationProperties..ctor(SPWorkflow
workflow, String initiationData, Object context)     at Microsoft.SharePoint.Workflow.SPWorkflowManager.StartWorkflowElev(Object context, SPWorkflowAssociation association, DateTime elevationTimeUtc, SPWorkflowEvent startEvent, SPWorkflowRunOptions
runOptions)     at Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver.<>c__DisplayClass1.<AutoStartWorkflow>b__0(SPSite superUserSite, SPWeb superUserWeb)
Any ideas?
TIA

Hi Milo,
Please check whether you have installed any CUs for SharePoint 2010.
Please install June 2013 CU or higher for SharePoint 2010, compare the result.
Here are some similar posts for you to take a look at:
http://blogs.msdn.com/b/chaun/archive/2013/05/16/if-your-sp2010-workflows-are-stuck-in-the-starting-state.aspx
http://social.technet.microsoft.com/Forums/sharepoint/en-US/5a6e6e83-b59f-4099-a86f-a07723ff2b98/workflow-stuck-in-starting-state-after-applying-sharepoint-2010-cu-december-2012?forum=sharepointadminprevious
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

SCSM's Allowed List for SCOM CI Connector not working as expected

Hi Everyone,
We're running into some unexpected behavior with the SCOM CI Connector, wondering if anyone can shed some light on it. Our requirement is to ensure Distributed Applications are not sync'd from SCOM to SCSM (hence, they don't show up in the "All
Business Services" view). We have only two MPs in SCOM/SCSM that sync Distributed Applications, both of which are for SharePoint monitoring.
We have the 2 SharePoint MP's in both SCSM and SCOM. We've configured the SCOM CI Connector to select the 2 SharePoint MP's for synchronization.
Now, we thought all we'd need to do to ensure the SharePoint Distributed Applications no longer sync from SCOM to SCSM is remove the "System.Service" class from the Allowed List of classes for SCOM CI -- which we did, however, they continue to
sync.
After a fair amount of back and forth trying to figure out how we need to configure the Allowed List of classes for the SCOM CI Connector to ensure the DA's aren't sync'd any more, we finally removed ALL classes from the Allowed List. Surely, this
will stop the sync we thought -- however, after having deleted the SharePoint Business Service CI's, removing ALL classes from the Allowed List, and then rerunning the SCOM CI Connector, the Distributed Applications associated with the SharePoint MP's STILL
come over.
Is there something I'm missing here?
Thanks!

Hi -- can anyone provide any feedback for me on this one?
Thanks!

SCOM Alerts Connector run as failed

Hi
I have setup the SCOM alerts connector in SCSM but after that i starts to get wernings in scom on servers there are in a difrent domain.
werning:
Description:
The Health Service cannot verify the future validity of the RunAs account Domain1\SCOMAlertsConnectorUser for management group SCOMMG01. The error is Logon failure: the user has not been granted the requested
logon type at this computer.(1385L).
SCSM and scom is in domain1
the servers i got the werning on is in Domain2
what can i do to fix this?

The connectors runas account must be administrator in SCOM (as I recall). Is that the case for Domain2?
Cheers,
Anders Spælling
Senior Consultant
Blog:
Twitter: LinkedIn:
Please remember to 'Propose as answer' if you find a reply helpful

SCOM Alert Connector - not updating the start time and finish time

When I am monitoring the status of connectors in service manager console, I found that for SCOM Alert Connector the Start Time and Finish Time are not updating. Previously it was updated daily. As of now, service manager is working fine but would like
to check will it create any issues? Even I have cliked on Synchronize Now, but there is no update. Please guide me on this to trouble shoot further? Thanks.

Hi,
Based on my research, the Start Time and Finish Time values are not updated when an alert connector is synchronized. These values are only updated when alert data is transferred between Operations Manager 2007 and Service
Manager.
More details, please refer to the link below:
http://technet.microsoft.com/en-us/library/hh495609.aspx
In addition, here is a blog about troubleshooting for SCSM and SCOM alert connector:
http://blogs.technet.com/b/servicemanager/archive/2010/04/14/troubleshooting-tips-for-your-scsm-scom-alert-connector.aspx
Regards,
Yan Li
Regards, Yan Li

SCSM to SCOM Alert Connector Error

Hello,
Long story short, the SCSM admin created an Alert Connector between SCSM and SCOM, then uninstalled SCSM and started over. That means I had an orphaned SCSM connector in SCOM.
In order to set up a new connection, I followed the instructions found in Kevin Holman's blog post:
http://blogs.technet.com/b/kevinholman/archive/2012/09/28/opsmgr-2012-how-to-delete-an-old-product-connector.aspx
Now, when I try to re-create a new Alert Connector, I get this error:
"Found at least one other alert connector in Operations Manager. Alerts may not be routed as expected if multiple connectors subscribe to the same alert."
I checked the SCOM server to make sure there were no orphaned connectors by running this SQL code against the OperationsManager database:
Aside from the copious number of SCVMM connectors, there were six connectors. Of those six, the previous SCSM connector is marked as "IsDeleted":
Next, I checked the "Microsoft.SystemCenter.Notifications.Internal" management pack to verify that there are no orphaned subscriptions. The ONLY alert referenced is for the "Advisor Data Connector".
At this point, my questions are as follows:
1) Will the System Center Advisor (now renamed Azure Operational Insights) connector cause the warning message I listed above when setting up an Alert Connector in SCSM?
2) Is there another orphaned entry in SCOM that I need to check for and remove before setting up the SCSM alert connector?

Hi,
I would like to suggest you remove the subscription that was orphaned. When remove a connector we should remove the subscriptions first.
And here is a similar thread
SCSM 2012 Cannot create SCOM Alert Connector
https://social.technet.microsoft.com/Forums/en-US/a5d0b921-bb0a-43b8-99ca-8b0112ab3bf0/scsm-2012-cannot-create-scom-alert-connector?forum=connectors
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

[SOLVED] Mailbox import requests stuck in 'queued' state

We have a small Exchange 2013 environment with one server having all roles. I try to import archive mailboxes from an Exchange 2010 environment. It has worked quite well for a while. However, all import requests are now 'stuck' in 'queued' state. Restart
of Replication service, transport service and even server reboot didn't help.
When I run
get-mailboximportrequest | Get-MailboxImportRequestStatistics -Includereport | fl
I observe that PositionInQueue value tells me that there are 85 import requests waiting :
ItemsTransferred                       :
PercentComplete                        : 0
CompletedRequestAgeLimit               : 30.00:00:00
PositionInQueue                        : 85/90 (Position/Queue Length)
InternalFlags                          : None
FailureCode                            :
There should be no requests waiting as I removed all requests in advance before I issued new import requests:
get-mailboximportrequest | Remove-MailboxImportRequest
How can I really reset an import queue by zeroing PositionInQueue ?
Any suggestions/tips?

Hi,
Glade to hear the good news. Thanks for your update.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Ciscoworks daemon manager stuck at Stopping state

I am working on LMS 3.2 . Tried to stop the daemon service with " net stop crmdmgtd ". It stuck on stopping state since few hours now. I can still open the application. Need a suggestion to terminate the previous command and restart the
daemon service.

You should have dmgtd.exe process in Task Manager stuck.
Although you can kill it directly and then try the stop command once again before starting. But to be sure if any process in not stuck, best way would be to reboot the server once.

VM got stuck in "stopping" state, and cannot be stopped

Dear all,
I am using Oracle VM 3.2.2.
One of my VM got stuck in "stopping" state, and cannot be stopped.
How can I troubleshoot this problem...

Q: Is the VM still running, i.e. can you ssh to the VM?
Q: Find the server where the VM is running, and restart the ovs-agent, i.e. "service ovs-agent restart". Did this help, or is the agent crashed, any zombies?
Possible root cause: These type of errors are typically ovs-agent bugs. First update oracle vm manager to the 3.2.4 release, not 3.2.6. Next update the dom0s to 3.2.4, not 3.2.6. You may need to setup a ULN 3.2.4 yum repo to update the dom0s. As you can see in these forms, 3.2.6 is may not ready for prime time, stick with 3.2.4, is stable.

SCOM CI Connector is stuck in runnig state

Similar Messages

Maybe you are looking for