0
Answered

Export error Status: 400 Bad Request

Eddie Kirkman 4 weeks ago • updated by Adam van Vliet (Product Manager) 4 weeks ago 3

I am seeing a small number (16) repeating errors in one of my MAs - with exports failing for some users with this error.

System.Exception: Status: 400 Bad Request
   at Unify.IdentityBroker.xxxx.Agent.DefaultCommunicator.SendCommand(String urlPath, Method method, Object data)
   at Unify.IdentityBroker.xxxx.Agent.DefaultCommunicator.Add(AgentEntity entity)
   at Unify.IdentityBroker.xxxx.Connector.Connector.AddEntity(IConnectorEntity entity, ISaveEntityResults`2 results, DefaultCommunicator communicator)

Three of them are for a known data error (malformed email addresses) but I cannot find anything to tell me more about why the others are failing.

I see the same error in Eventviewer for each failed user.  In IdB I see this in the log - it reports 16 entities saved then reports that 0 were successful.  Any help in interpreting this log or the issue would be appreciated

17/Oct/2018 16:41:33
  • Information
AdapterAdapter request to add entities for adapter space.
Adapter request to add entities [Count:16] for adapter xxxx (920ed433-e1e9-4aa3-b682-3bfee876de9f).
17/Oct/2018 16:41:33
  • Information
ConnectorRequest to add entity to connector.
Request to add entities [Count:16] to connector xxxx Connector.
17/Oct/2018 16:41:34
  • Information
ConnectorAdd entities to connector completed.
Add entities [Count:16] to connector xxxx Connector reported 16 entities saved. Duration: 00:00:01.1431907
17/Oct/2018 16:41:34
  • Information
AdapterAdapter added entities to adapter space.
Adapter added [Count:16] entities (0 successful) to adapter xxxx (920ed433-e1e9-4aa3-b682-3bfee876de9f). Duration: 00:00:01.1693154
17/Oct/2018 16:41:34
  • Information
LDAP engineHandling of LDAP Bulk Update request.
Handling of LDAP Bulk Update request received from user xxxx on connection 127.0.0.1:56662 completed successfully without results available for logging. Duration 00:00:02.3027112.


Affected Versions:
Fixed by Version:

Answer

Answer
Answered

A while ago, the error reporting interface in the connectors was improved such that the status of individual entities can be reported back to the identity management platform.

From the log entries, can I assume you're on v5.1? This particular pattern suggests that each entity failed to save (reported back by the connector) - the problem with the logger in v5.1 was that it used the number of attempted entities as the success count (and didn't even report on the failure count). This is improved in future versions.

Look at the MIM logs to see the error details for each entity.

Answer
Answered

A while ago, the error reporting interface in the connectors was improved such that the status of individual entities can be reported back to the identity management platform.

From the log entries, can I assume you're on v5.1? This particular pattern suggests that each entity failed to save (reported back by the connector) - the problem with the logger in v5.1 was that it used the number of attempted entities as the success count (and didn't even report on the failure count). This is improved in future versions.

Look at the MIM logs to see the error details for each entity.

The somewhat useless Status 400 bad request message at the top of my post is what MIM reports, so unfortunately nothing much to be gleaned from that.  I believe upgrades may be planned over the Christmas period

You may wish to open a new request against the connector in question, we may be able to assist with diagnosing that.