0
Fixed

An error occurred at the adapter level, before the entity was exported to the connector.

Matthew Woolnough 2 years ago in UNIFYBroker/Microsoft SharePoint • updated by anonymous 2 years ago 11

Error exporting users to Sharepoint:

Unify.Framework.UnifyDataException: An error occurred at the adapter level, before the entity was exported to the connector. Check the logs for any exceptions related to the export.
   at Unify.Product.IdentityBroker.Adapter.<>c.<.ctor>b__24_5
Affected Versions:
Fixed by Version:

Answer

Answer

Hi Matt, Please replace the following DLL: Unify.Connectors.Microsoft.SharePoint.dll and re-request the schema - the RecordId field should swap to not required.

Under review

Hi Matt,

Can you provide the extra logs as suggested in the error message? This is likely related to Add request failed as the converted DN blah does not match the request DN otherBlah

Hi Matt,

I noticed from your logs that you have the following warning near an LDAP Bulk Update request with failed entities:

The entity <null> (a04a8a94-b49b-4787-9494-7f0bcc9d4fa3) in the connector SharePoint Organisations (8a31845f-6996-42e0-bf3d-f7456a4adb78)  failed validation 1 times for the following reasons: RecordId is a required field and is not present.

If this is a key generated by SharePoint, try updating the connector schema to remove the required flag from the RecordId field.

RecordId is a locked field, I can't update it. 

Answer

Hi Matt, Please replace the following DLL: Unify.Connectors.Microsoft.SharePoint.dll and re-request the schema - the RecordId field should swap to not required.

I'm fairly certain this has resolved it, but there are 136 errors caused by this issue & it's too much effort to view each error. 

Once we've resolved the above mentioned issue, i'll update here to say if this has been resolved. 



I have found this error in the logs again. Can we re-open this one please?

What's the log entry this time? It shouldn't be RecordId is a required field and is not present. as we changed that to not required.

Ah, OK. its still showing up as required.  Is it possible that the latest DLL provided does not include this fix?

no probs. fixed. thanks.