SMA connector stopped working due to "The location monitoring object is not managed" error
Tomi_Kaartama
Customer IT Monkey ✭
The SMA connector suddenly stopped working in our environment producing the "The location monitoring object is not managed" error for data access services. The connector license is valid. The full error is:
The database subscription is unable to trigger the Windows workflow because of Data Access service errors.
The following errors were encountered:
Exception message: The location monitoring object is not managed.
One or more subscriptions were affected by this.
Subscription name: Microsoft.EnterpriseManagement.ServiceManager.Connector.SMAConnector.RunbookMonitorRule
Instance name: Microsoft.EnterpriseManagement.LinkingFramework.SCOConnector.MonitoringWorkflowTarget
Instance ID: {5312E86C-61D6-9AA1-1F58-A3DA08F813F7}
Management group: *****
Any ideas how to fix this?
Any ideas how to fix this?
0
Best Answers
-
seth_coussens
Member Ninja IT Monkey ✭✭✭✭
Maybe try removing it forcefully, via powershell, see above.5 -
Tomi_Kaartama
Customer IT Monkey ✭
This was finally resolved together with MS support. We had to uninstall the management server and reinstall it again to resume operation.5
Answers
Seems like something changed on the SMA side for the runbook monitoring rule to have an issue.
Unfortunately the Operations Manager log has been overwritten so no help from there. Application log does not seem to have anything that would explain this.
If I were to look for events on the SQL server or SMA server, any ideas which event logs to search?
I've also opened a ticket on the Cireson support portal. Ticket # is IR59874.
T: Tomi
Any ideas on how to get rid of the ghost connector and whether it could be the root cause of the issues?
http://windowsitpro.com/service-manager/delete-orphaned-connector-service-manager-2012
A: It's possible you had been using the Exchange Connector RC and just installed the RTM version without first deleting the old connector and uninstalling the old code. You would then be left with an Exchange Connector that couldn't be used or deleted. Your first instinct might be to try and delete it using the native Windows PowerShell:
Confirm
Are you sure you want to perform this action?
Performing operation "Remove-SCSMConnector" on Target "SAVDALEX01 Exchange
Connector".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(default is "Y"):Y
Unfortunately, the command above doesn't actually delete the connector. We therefore have to fall back to the SMLets, which are available at Codeplex. They were originally written for Service Manager 2010. Download and install the SMLets, then perform the following:
<strong>PS C:\> Import-Module smlets<br></strong><strong>PS C:\> Get-SCSMObject –Class (Get-SCSMClass –Name Microsoft.SystemCenter.Connector) | ?{$_.DisplayName –eq “SAVDALEX01 Exchange Connector”}<br></strong><strong>ClassName DisplayName LastModified<br></strong><strong>--------- ----------- ------------<br></strong><strong>Microsoft.SystemCenter.Connector SAVDALEX01 Exchange Connector 4/29/2013 1:16:53 PM<br></strong><strong>PS C:\> Get-SCSMObject –Class (Get-SCSMClass –Name Microsoft.SystemCenter.Connector) | ?{$_.DisplayName –eq “SAVDALEX01 Exchange Connector”} | Remove-SCSMObject -Force -Confirm</strong>The connector should now be gone. The big difference between the SMLets Remove-SCSMObject and the 2012 built-in Remove-SCSMConnector is that the Remove-SCSMObject has a -Force option.
<strong>Get-SCSMObject –Class (Get-SCSMClass –Name Microsoft.SystemCenter.Connect<pre class="CodeBlock"><code>or) | ?{$_.DisplayName –eq “SAVDALEX01 Exchange Connector”} | Remove-SCSMObject -Force -Confirmor" I had to add the dollar sign like this "Microsoft.SystemCenter.Connector$". Connector is gone, now I'll try to set up a new connector and see if the root cause is resolved.