AD and Config Manager connectors not running

Hello,

I have been having some issues with both AD and Config Manager connectors not running. The only connectors I can get to run are the Exchange and Orchestrator connectors. Recently, I have noticed some errors that may point to where my problem may be (see below):

Error 1:

Source: Lfx Service 

Error setting status for property &. Error:The relationship source specified in the discovery data item is not valid.

Relationship source ID: 0543b4a6-3042-7035-f8d7-d22166d117d6

Rule ID: eb496966-4fb7-45bd-bdda-b689af383733

Instance:

<?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{1548950d-6cea-d9c1-11ec-53701fbcbbec}" SourceTypeId="{71f6cfcd-99b3-3a07-471d-bb9c4bf5ba76}" TargetTypeId="{2d4afd51-d2ff-92c6-266f-2b6060000dae}"><Settings /><SourceRole><Settings><Setting><Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name><Value>ddd956f5-ef2d-4ea3-9698-d0104f86abb9</Value></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name><Value>ddd956f5-ef2d-4ea3-9698-d0104f86abb9</Value></Setting></Settings></TargetRole></RelationshipInstance>. Status data:ConnectorId:c97a3ccd-68c5-4302-bf5b-7c2c6590eb2d;BaseManagementEntityId:e96190e2-4e9e-70ad-ddf9-e4c0cfcae426;LastRunStartTime:1/1/1900 12:00:00 AM;LastRunFinishTime:1/1/1900 12:00:00 AM;NextSyncTime:1/1/0001 12:00:00 AM;Status:NeverRun;SyncPercent:0;MaxValue:100;MinValue:0;.

Error 2:

Source: OpsMgr SDK Serv

An exception was thrown while processing ProcessDiscoveryData for session ID uuid:fe85de44-0759-417c-9d79-6f1857b08e77;id=8.

Exception message: The relationship source specified in the discovery data item is not valid.

Relationship source ID: 0543b4a6-3042-7035-f8d7-d22166d117d6

Rule ID: eb496966-4fb7-45bd-bdda-b689af383733

Instance:

<?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{1548950d-6cea-d9c1-11ec-53701fbcbbec}" SourceTypeId="{71f6cfcd-99b3-3a07-471d-bb9c4bf5ba76}" TargetTypeId="{2d4afd51-d2ff-92c6-266f-2b6060000dae}"><Settings /><SourceRole><Settings><Setting><Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name><Value>ddd956f5-ef2d-4ea3-9698-d0104f86abb9</Value></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name><Value>ddd956f5-ef2d-4ea3-9698-d0104f86abb9</Value></Setting></Settings></TargetRole></RelationshipInstance>

Full Exception: Microsoft.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipSourceException: The relationship source specified in the discovery data item is not valid.

Relationship source ID: 0543b4a6-3042-7035-f8d7-d22166d117d6

Rule ID: eb496966-4fb7-45bd-bdda-b689af383733

Instance:

<?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{1548950d-6cea-d9c1-11ec-53701fbcbbec}" SourceTypeId="{71f6cfcd-99b3-3a07-471d-bb9c4bf5ba76}" TargetTypeId="{2d4afd51-d2ff-92c6-266f-2b6060000dae}"><Settings /><SourceRole><Settings><Setting><Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name><Value>ddd956f5-ef2d-4ea3-9698-d0104f86abb9</Value></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name><Value>ddd956f5-ef2d-4ea3-9698-d0104f86abb9</Value></Setting></Settings></TargetRole></RelationshipInstance>

   at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.BulkUpsertRelationshipInstances(DiscoveryDatabaseApi dbApi, DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData)

   at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.BulkAddUpdate(DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData, DiscoveryDatabaseApi dbApi)

   at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.Write(DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData, DiscoveryDatabaseApi dbApi)

   at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithNoRetryUnauthorized(DiscoveryDatabaseApi dbApi, Boolean useProcessContext)

   at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.ProcessIncrementalDiscoveryData(DatabaseConnection databaseConnection)

   at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.Process()

   at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithRetry(HandleProcessing handleProcessing, RetryPolicy retryPolicy)

   at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.ProcessDiscoveryDataWithRetry(DatabaseConnection dbconnection, Guid discoverySourceId, IList`1 sdkEntityInstances, IDictionary`2 streams, IContext context)

   at Microsoft.EnterpriseManagement.ServiceDataLayer.ConnectorFrameworkConfigurationService.ProcessDiscoveryData(Guid discoverySourceId, IList`1 entityInstances, IDictionary`2 streams, ObjectChangelist`1 extensions)

Any one have any ideas?

September 10th, 2015 4:38pm

The error shows that there's something wrong with the connectors "sync status" object relationship. Sync Status is an object related to your connector that shows the "status", "percent complete", "last run time", etc.

Based on the error, it sounds like there might be something wrong with your connector's DataSource object (the source object it's complaining about). It could have been inadvertently deleted or something (though deleted data source objects are supposed to take their sync status objects along with them to oblivion)

Before mucking around with the existing connector, are you able to create a new AD connector with the same settings and run that one?

Free Windows Admin Tool Kit Click here and download it now
September 10th, 2015 5:06pm

I can create new AD and Config Manager connectors, but I can not get them to run.

What I find interesting is that even though they are not running I get back some info regarding them.

See some examples below:

Level: Information

Source: Data Connectors

1. Connector name:Configuration Manager Connector - SCCMQA01, Id:SCCMConnector.46a7aeba212d46cc919a4935927bf94a. Finished Importer.CMv5_DEVICESANDCOMPUTERS synchronization

2. Connector Employees,ADConnector.fa53249f17ae46e4b2947fc0dc8dbc4f saving 3 datarows returned by query to table/view ADUsers. These include creates/updates or deletions at source.

3. Connector Amerisure.int Employees Connector imported 150 changes for data of type System.UserHasPreference from cache table AD_UserNotificationPoint_Out.

September 10th, 2015 5:23pm

I can create new AD and Config Manager connectors, but I can not get them to run.

What I find interesting is that even though they are not running I get back some info regarding them.

See some examples below:

Level: Information

Source: Data Connectors

1. Connector name:Configuration Manager Connector - SCCMQA01, Id:SCCMConnector.46a7aeba212d46cc919a4935927bf94a. Finished Importer.CMv5_DEVICESANDCOMPUTERS synchronization

2. Connector Employees,ADConnector.fa53249f17ae46e4b2947fc0dc8dbc4f saving 3 datarows returned by query to table/view ADUsers. These include creates/updates or deletions at source.

3. Connector Employees Connector imported 150 changes for data of type System.UserHasPreference from cache table AD_UserNotificationPoint_Out.


  • Edited by ETechnetG 11 hours 40 minutes ago
Free Windows Admin Tool Kit Click here and download it now
September 10th, 2015 9:21pm

I can create new AD and Config Manager connectors, but I can not get them to run.

What I find interesting is that even though they are not running I get back some info regarding them.

See some examples below:

Level: Information

Source: Data Connectors

1. Connector name:Configuration Manager Connector - SCCMQA01, Id:SCCMConnector.46a7aeba212d46cc919a4935927bf94a. Finished Importer.CMv5_DEVICESANDCOMPUTERS synchronization

2. Connector Employees,ADConnector.fa53249f17ae46e4b2947fc0dc8dbc4f saving 3 datarows returned by query to table/view ADUsers. These include creates/updates or deletions at source.

3. Connector Employees Connector imported 150 changes for data of type System.UserHasPreference from cache table AD_UserNotificationPoint_Out.


  • Edited by ETechnetG Friday, September 11, 2015 7:36 PM
September 10th, 2015 9:21pm

I can create new AD and Config Manager connectors, but I can not get them to run.

What I find interesting is that even though they are not running I get back some info regarding them.

See some examples below:

Level: Information

Source: Data Connectors

1. Connector name:Configuration Manager Connector - SCCMQA01, Id:SCCMConnector.46a7aeba212d46cc919a4935927bf94a. Finished Importer.CMv5_DEVICESANDCOMPUTERS synchronization

2. Connector Employees,ADConnector.fa53249f17ae46e4b2947fc0dc8dbc4f saving 3 datarows returned by query to table/view ADUsers. These include creates/updates or deletions at source.

3. Connector Employees Connector imported 150 changes for data of type System.UserHasPreference from cache table AD_UserNotificationPoint_Out.


  • Edited by ETechnetG Friday, September 11, 2015 7:36 PM
Free Windows Admin Tool Kit Click here and download it now
September 10th, 2015 9:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics