Active Directory connector since CU6 (Network Steve Forum)

Active Directory connector since CU6

We are experiencing an issue where Active Directory Connectors have stopped working.

Running Service Manager 2012 R2 with CU6 (KB3039363) and update KB3064088 installed, the issue appeared to start after installing CU6.

When the connector is chosen and a "Synchronize Now" requested from the Service Manager console, I receive confirmation that the request has been submitted. However the Start Time and Finish Time values are never updated and known new objects in Active Directory are not created in Service Manager.

In the Operations Manager log, I see the following event logged when the synchronization is requested -

Log Name: Operations Manager
Source: Lfx Service
Date: 7/7/2015 10:00:21 AM
Event ID: 3334
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MySCSMServer
Description:
Error setting status for property . Error:Column 'NextSyncTime' does not belong to table Table1.. Status data:.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Lfx Service" />
<EventID Qualifiers="0">3334</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-07-07T09:00:21.000000000Z" />
<EventRecordID>6700820</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>MySCSMServer</Computer>
<Security />
</System>
<EventData>
<Data>Error setting status for property . Error:Column 'NextSyncTime' does not belong to table Table1.. Status data:.</Data>
</EventData>
</Event>

We have tried recreating the connector and get the same result. Can anybody help resolve this issue?

July 7th, 2015 5:07am

Hi,

Do other Connectors work normally?

Have you tried to restart the server?

You can use the Cmdlets : Get-SCSMConnector to view the connectors status and use Start-SCSMConnector to start manually the connectors.

http://technet.microsoft.com/en-us/library/hh316209(v=sc.10).aspx

Free Windows Admin Tool Kit Click here and download it now

July 7th, 2015 10:53pm

The server has been rebooted, this hasn't helped.

Other connectors (SCCM, SCOM, Orchestrator) are running successfully.

Using Get-SCSMConnector, I can see my Active Directory connector is listed and enabled.

Using Start-SCSMConnector, I get the same result as starting the syncronization from the console - connector doesn't run and I see the following events logged

Log Name: Operations Manager
Source: Lfx Service
Date: 7/8/2015 7:31:51 AM
Event ID: 3334
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MySCSMServer
Description:
Data synchronization failed by AD Connector.Importer.ADUsers.ADConnector.5dcb6afa03fd4a81bfc0e3d3b30a650b.:Microsoft.EnterpriseManagement.ServiceManager.Connector.AD.DataConnectorAD.
Exception type:ConnectorException
Exception message:createBatchInfoForRealSource failed . Exception type:TypeLoadException
Exception message:Could not load type 'Microsoft.EnterpriseManagement.WindowsUtility.StringManipulations' from assembly 'Microsoft.EnterpriseManagement.WindowsUtility, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'..
StackTrace: at Microsoft.EnterpriseManagement.ServiceManager.Connector.AD.ActiveDirectoryUtility.bind(DirectoryEntry de)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.AD.ActiveDirectoryUtility.GetWatermark(DirectoryServerSates directoryStates)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.AD.DataConnectorAD.OnCreateBatchInfoForRealSource(SessionBase session, String query, String tableName, String batchIdField, Int32 batchIdType, String watermarkField, Int32 watermarkType, Byte[] watermark, String connectionString, Int32 batchSize)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.createBatchInfoForRealSource(SessionBase session, Int32 SessionTableId, EnumTableStatus status).
StackTrace: at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.throwConnectorException(String method, String message, Object[] values)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.createBatchInfoForRealSource(SessionBase session, Int32 SessionTableId, EnumTableStatus status)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.PrepareBatchInfo(SessionBase session)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.GetNextBatch(IConnectorSession connectorSession, Boolean batchInfoOnly)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.Datacenter.SessionHost.DataSync()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Lfx Service" />
<EventID Qualifiers="0">3334</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-07-08T06:31:51.000000000Z" />
<EventRecordID>6704124</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>MySCSMServer</Computer>
<Security />
</System>
<EventData>
<Data>Data synchronization failed by AD Connector.Importer.ADUsers.ADConnector.5dcb6afa03fd4a81bfc0e3d3b30a650b.:Microsoft.EnterpriseManagement.ServiceManager.Connector.AD.DataConnectorAD.
Exception type:ConnectorException
Exception message:createBatchInfoForRealSource failed . Exception type:TypeLoadException
Exception message:Could not load type 'Microsoft.EnterpriseManagement.WindowsUtility.StringManipulations' from assembly 'Microsoft.EnterpriseManagement.WindowsUtility, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'..
StackTrace: at Microsoft.EnterpriseManagement.ServiceManager.Connector.AD.ActiveDirectoryUtility.bind(DirectoryEntry de)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.AD.ActiveDirectoryUtility.GetWatermark(DirectoryServerSates directoryStates)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.AD.DataConnectorAD.OnCreateBatchInfoForRealSource(SessionBase session, String query, String tableName, String batchIdField, Int32 batchIdType, String watermarkField, Int32 watermarkType, Byte[] watermark, String connectionString, Int32 batchSize)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.createBatchInfoForRealSource(SessionBase session, Int32 SessionTableId, EnumTableStatus status).
StackTrace: at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.throwConnectorException(String method, String message, Object[] values)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.createBatchInfoForRealSource(SessionBase session, Int32 SessionTableId, EnumTableStatus status)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.PrepareBatchInfo(SessionBase session)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.GetNextBatch(IConnectorSession connectorSession, Boolean batchInfoOnly)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.Datacenter.SessionHost.DataSync()</Data>
</EventData>
</Event>

This is followed by identical log entries for ADComputers, ADPrinters, ADGroups, and finally the error in my opening post.

July 8th, 2015 2:42am

Looking at the logs, it seems that customer followed the incorrect order of installation of UR6 KB(KB3039363) and HotFix KB(KB3064088)

The Incorrect Order:
1. Install the HotFix KB(KB3064088)
2. Install UR6 KB(KB3039363)

The correct Order:
1. Install UR6 KB(KB3039363)
2. then install the HotFix KB(KB3064088)

The incorrect installation order was earlier documented in the UR6 page, and it is corrected on June 10.

Looking at the logs, it seems that the customer surely followed the incorrect order and it can also be verified by verifying the below binaries versions:
1. Microsoft.EnterpriseManagement.WindowsUtility.dll
2. Microsoft.EnterpriseManagement.ServiceManager.Connector.DataCenter.dll
The version of the above DLLs would NOT be 7.5.3079.367 on the customer machines where the mentioned errors are occuring.

The solution now:
Please use the following steps for roll back
1. Replace the following binaries with the RTM version (3079.0)
Microsoft.EnterpriseManagement.ServiceManager.Connector.AD.dll
Microsoft.EnterpriseManagement.ServiceManager.Linking.Consumer.OperationalStore.dll
2. Restore the SM DB with the DB before the HotFix KB(KB3064088) installation

The connector would run now smoothly, although the customer would be stuck in RTM till next UR(i.e UR7) because installing UR6 wont work now.

Free Windows Admin Tool Kit Click here and download it now

July 11th, 2015 10:10am

Looking at the logs, it seems that customer followed the incorrect order of installation of UR6 KB(KB3039363) and HotFix KB(KB3064088)

The Incorrect Order:
1. Install the HotFix KB(KB3064088)
2. Install UR6 KB(KB3039363)

The correct Order:
1. Install UR6 KB(KB3039363)
2. then install the HotFix KB(KB3064088)

The incorrect installation order was earlier documented in the UR6 page, and it is corrected on June 10.

The connector would run now smoothly, although the customer would be stuck in RTM till next UR(i.e UR7) because installing UR6 wont work now.

Proposed as answer by Xin GuoMicrosoft contingent staff, Moderator 22 hours 27 minutes ago

July 11th, 2015 2:09pm

Looking at the logs, it seems that customer followed the incorrect order of installation of UR6 KB(KB3039363) and HotFix KB(KB3064088)

The Incorrect Order:
1. Install the HotFix KB(KB3064088)
2. Install UR6 KB(KB3039363)

The correct Order:
1. Install UR6 KB(KB3039363)
2. then install the HotFix KB(KB3064088)

The incorrect installation order was earlier documented in the UR6 page, and it is corrected on June 10.

The connector would run now smoothly, although the customer would be stuck in RTM till next UR(i.e UR7) because installing UR6 wont work now.

Proposed as answer by Xin GuoMicrosoft contingent staff, Moderator Tuesday, July 21, 2015 8:48 AM
Marked as answer by Xin GuoMicrosoft contingent staff, Moderator 21 hours 24 minutes ago

Free Windows Admin Tool Kit Click here and download it now

July 11th, 2015 2:09pm

Looking at the logs, it seems that customer followed the incorrect order of installation of UR6 KB(KB3039363) and HotFix KB(KB3064088)

The Incorrect Order:
1. Install the HotFix KB(KB3064088)
2. Install UR6 KB(KB3039363)

The correct Order:
1. Install UR6 KB(KB3039363)
2. then install the HotFix KB(KB3064088)

The incorrect installation order was earlier documented in the UR6 page, and it is corrected on June 10.

The connector would run now smoothly, although the customer would be stuck in RTM till next UR(i.e UR7) because installing UR6 wont work now.

Proposed as answer by Xin GuoMicrosoft contingent staff, Moderator Tuesday, July 21, 2015 8:48 AM
Marked as answer by Xin GuoMicrosoft contingent staff, Moderator Wednesday, July 22, 2015 9:53 AM

July 11th, 2015 2:09pm

Looking at the logs, it seems that customer followed the incorrect order of installation of UR6 KB(KB3039363) and HotFix KB(KB3064088)

The Incorrect Order:
1. Install the HotFix KB(KB3064088)
2. Install UR6 KB(KB3039363)

The correct Order:
1. Install UR6 KB(KB3039363)
2. then install the HotFix KB(KB3064088)

The incorrect installation order was earlier documented in the UR6 page, and it is corrected on June 10.

The connector would run now smoothly, although the customer would be stuck in RTM till next UR(i.e UR7) because installing UR6 wont work now.

Proposed as answer by Xin GuoMicrosoft contingent staff, Moderator Tuesday, July 21, 2015 8:48 AM
Marked as answer by Xin GuoMicrosoft contingent staff, Moderator Wednesday, July 22, 2015 9:53 AM

Free Windows Admin Tool Kit Click here and download it now

July 11th, 2015 2:09pm

Looking at the logs, it seems that customer followed the incorrect order of installation of UR6 KB(KB3039363) and HotFix KB(KB3064088)

The Incorrect Order:
1. Install the HotFix KB(KB3064088)
2. Install UR6 KB(KB3039363)

The correct Order:
1. Install UR6 KB(KB3039363)
2. then install the HotFix KB(KB3064088)

The incorrect installation order was earlier documented in the UR6 page, and it is corrected on June 10.

The connector would run now smoothly, although the customer would be stuck in RTM till next UR(i.e UR7) because installing UR6 wont work now.

Proposed as answer by Xin GuoMicrosoft contingent staff, Moderator Tuesday, July 21, 2015 8:48 AM
Marked as answer by Xin GuoMicrosoft contingent staff, Moderator Wednesday, July 22, 2015 9:53 AM

July 11th, 2015 2:09pm

Looking at the logs, it seems that customer followed the incorrect order of installation of UR6 KB(KB3039363) and HotFix KB(KB3064088)

The Incorrect Order:
1. Install the HotFix KB(KB3064088)
2. Install UR6 KB(KB3039363)

The correct Order:
1. Install UR6 KB(KB3039363)
2. then install the HotFix KB(KB3064088)

The incorrect installation order was earlier documented in the UR6 page, and it is corrected on June 10.

The connector would run now smoothly, although the customer would be stuck in RTM till next UR(i.e UR7) because installing UR6 wont work now.

Proposed as answer by Xin GuoMicrosoft contingent staff, Moderator Tuesday, July 21, 2015 8:48 AM
Marked as answer by Xin GuoMicrosoft contingent staff, Moderator Wednesday, July 22, 2015 9:53 AM

Free Windows Admin Tool Kit Click here and download it now

July 11th, 2015 2:09pm

Looking at the logs, it seems that customer followed the incorrect order of installation of UR6 KB(KB3039363) and HotFix KB(KB3064088)

The Incorrect Order:
1. Install the HotFix KB(KB3064088)
2. Install UR6 KB(KB3039363)

The correct Order:
1. Install UR6 KB(KB3039363)
2. then install the HotFix KB(KB3064088)

The incorrect installation order was earlier documented in the UR6 page, and it is corrected on June 10.

The connector would run now smoothly, although the customer would be stuck in RTM till next UR(i.e UR7) because installing UR6 wont work now.

Proposed as answer by Xin GuoMicrosoft contingent staff, Moderator Tuesday, July 21, 2015 8:48 AM
Marked as answer by Xin GuoMicrosoft contingent staff, Moderator Wednesday, July 22, 2015 9:53 AM

July 11th, 2015 2:09pm

Looking at the logs, it seems that customer followed the incorrect order of installation of UR6 KB(KB3039363) and HotFix KB(KB3064088)

The Incorrect Order:
1. Install the HotFix KB(KB3064088)
2. Install UR6 KB(KB3039363)

The correct Order:
1. Install UR6 KB(KB3039363)
2. then install the HotFix KB(KB3064088)

The incorrect installation order was earlier documented in the UR6 page, and it is corrected on June 10.

The connector would run now smoothly, although the customer would be stuck in RTM till next UR(i.e UR7) because installing UR6 wont work now.

Proposed as answer by Xin GuoMicrosoft contingent staff, Moderator Tuesday, July 21, 2015 8:48 AM
Marked as answer by Xin GuoMicrosoft contingent staff, Moderator Wednesday, July 22, 2015 9:53 AM

Free Windows Admin Tool Kit Click here and download it now

July 11th, 2015 2:09pm

I am having the same problem with the AD connectors in both our DEV environment and our PROD environment. I was careful to apply UR6 on our data warehouse management server first and then our SCSM management server, closed all consoles, disabled AD connectors, per the instructions.

I just installed UR7 in our DEV environment - the connectors still don't work.

In our PROD environment, the AD connectors are missing the Schedule tab - not sure what's up with that, but they don't run when manually sync either.

July 29th, 2015 2:27pm

Hi Lex,

Please install the UR7 on the console machines as well.

Also can you please share the events logs here or with me @ rbansal@microsoft.com

Thanks,

Rajeev

Free Windows Admin Tool Kit Click here and download it now

July 30th, 2015 12:34am

Hi Lex,

Please install the UR7 on the console machines as well.

Also can you please share the events logs here or with me @ rbansal@microsoft.com

Thanks,

Rajeev

Proposed as answer by jonathancliuMicrosoft employee 13 hours 46 minutes ago

July 30th, 2015 4:29am

Hi Lex,

Please install the UR7 on the console machines as well.

Also can you please share the events logs here or with me @ rbansal@microsoft.com

Thanks,

Rajeev

Proposed as answer by jonathancliuMicrosoft employee Thursday, July 30, 2015 5:30 PM

Free Windows Admin Tool Kit Click here and download it now

July 30th, 2015 4:29am

Hi Lex,

Please install the UR7 on the console machines as well.

Also can you please share the events logs here or with me @ rbansal@microsoft.com

Thanks,

Rajeev

Proposed as answer by jonathancliuMicrosoft employee Thursday, July 30, 2015 5:30 PM

July 30th, 2015 4:29am

Hi Lex,

Please install the UR7 on the console machines as well.

Also can you please share the events logs here or with me @ rbansal@microsoft.com

Thanks,

Rajeev

Proposed as answer by jonathancliuMicrosoft employee Thursday, July 30, 2015 5:30 PM

Free Windows Admin Tool Kit Click here and download it now

July 30th, 2015 4:29am

Hi Lex,

Please install the UR7 on the console machines as well.

Also can you please share the events logs here or with me @ rbansal@microsoft.com

Thanks,

Rajeev

Proposed as answer by jonathancliuMicrosoft employee Thursday, July 30, 2015 5:30 PM

July 30th, 2015 4:29am

Hi Lex,

Please install the UR7 on the console machines as well.

Also can you please share the events logs here or with me @ rbansal@microsoft.com

Thanks,

Rajeev

Proposed as answer by jonathancliuMicrosoft employee Thursday, July 30, 2015 5:30 PM

Free Windows Admin Tool Kit Click here and download it now

July 30th, 2015 4:29am

Hi Lex,

Please install the UR7 on the console machines as well.

Also can you please share the events logs here or with me @ rbansal@microsoft.com

Thanks,

Rajeev

Proposed as answer by jonathancliuMicrosoft employee Thursday, July 30, 2015 5:30 PM

July 30th, 2015 4:29am

I will email you a OneDrive link to a zip file of the series of events that are logged after a manual sync of our active users AD connector.

Thank you for your help, Rajeev!

Edited by Lex Jensen 15 hours 20 minutes ago

Free Windows Admin Tool Kit Click here and download it now

July 30th, 2015 11:24am

I will email you a OneDrive link to a zip file of the series of events that are logged after a manual sync of our active users AD connector.

Thank you for your help, Rajeev!

Edited by Lex Jensen Thursday, July 30, 2015 3:56 PM

July 30th, 2015 3:23pm

I will email you a OneDrive link to a zip file of the series of events that are logged after a manual sync of our active users AD connector.

Thank you for your help, Rajeev!

Edited by Lex Jensen Thursday, July 30, 2015 3:56 PM

Free Windows Admin Tool Kit Click here and download it now

July 30th, 2015 3:23pm

I will email you a OneDrive link to a zip file of the series of events that are logged after a manual sync of our active users AD connector.

Thank you for your help, Rajeev!

Edited by Lex Jensen Thursday, July 30, 2015 3:56 PM

July 30th, 2015 3:23pm

I will email you a OneDrive link to a zip file of the series of events that are logged after a manual sync of our active users AD connector.

Thank you for your help, Rajeev!

Edited by Lex Jensen Thursday, July 30, 2015 3:56 PM

Free Windows Admin Tool Kit Click here and download it now

July 30th, 2015 3:23pm

I will email you a OneDrive link to a zip file of the series of events that are logged after a manual sync of our active users AD connector.

Thank you for your help, Rajeev!

Edited by Lex Jensen Thursday, July 30, 2015 3:56 PM

July 30th, 2015 3:23pm

I will email you a OneDrive link to a zip file of the series of events that are logged after a manual sync of our active users AD connector.

Thank you for your help, Rajeev!

Edited by Lex Jensen Thursday, July 30, 2015 3:56 PM

Free Windows Admin Tool Kit Click here and download it now

July 30th, 2015 3:23pm

FYI.

The error events observed by Lex Jensen, related to AD
connector not working, are completely different than the events message in this thread.

I am following up with Lex on this offline.

July 30th, 2015 11:59pm

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