2 Replies Latest reply on Mar 2, 2016 8:12 AM by 2785276

    AD Entitlement provisioning error "The file exists."

    2785276

      Hi guys,

      I need your expert advice, please.

      We provision AD entitlements via a custom scheduled task on OIM 11gR2 PS2 and it used to work just fine.

      Since a few weeks however we get an error (see OIM and connector server logs below) and the entitlements do not get provisioned anymore on our production server.

       

      Any ideas what could be behind this mysterious "The file exists" error?

       

      Thanks

      Kevin

       

       

      OIM-Diagnostic-Log:

       

      [2016-02-29T13:14:07.111+01:00] [oim_server1] [ERROR] [] [ORACLE.IAM.CONNECTORS.ICFCOMMON.CONNECTOROPHELPER] [tid: OIMQuartzScheduler_Worker-6] [userId: xelsysadm] [ecid: 0000LA2ONDr7y0uLsa9DiX1Me8hu000002,1:17745] [APP: oim#11.1.2.0.0] oracle.iam.connectors.icfcommon.ConnectorOpHelper : execute : Error occured while executing action[[

      java.lang.RuntimeException: The file exists.

       

          at org.identityconnectors.framework.impl.serializer.CommonObjectHandlers$15.createException(CommonObjectHandlers.java:283)

          at org.identityconnectors.framework.impl.serializer.CommonObjectHandlers$15.createException(CommonObjectHandlers.java:282)

          at org.identityconnectors.framework.impl.serializer.CommonObjectHandlers$ThrowableHandler.deserialize(CommonObjectHandlers.java:115)

          at org.identityconnectors.framework.impl.serializer.binary.BinaryObjectDecoder$InternalDecoder.readObject(BinaryObjectDecoder.java:162)

          at org.identityconnectors.framework.impl.serializer.binary.BinaryObjectDecoder.readObject(BinaryObjectDecoder.java:313)

          at org.identityconnectors.framework.impl.serializer.binary.BinaryObjectDecoder.readObjectField(BinaryObjectDecoder.java:417)

          at org.identityconnectors.framework.impl.serializer.MessageHandlers$5.deserialize(MessageHandlers.java:155)

        

       

       

       

      The AD Connector Server Log is not much more verbose...

      The paragraph with the "ConnectorServer.exe    Error    0    The file exists." is written to the log file over and over.

       

       

       

      AD Connector Server Log:

       

       

      ConnectorServer.exe    Error    0    The file exists.

      at Org.IdentityConnectors.Framework.Impl.Api.Remote.Messages.OperationResponsePart ProcessOperationRequest(Org.IdentityConnectors.Framework.Impl.Api.Remote.Messages.OperationRequest) in Server.cs:609

          2016-02-29 13:30:12Z

       

      ConnectorServer.exe    Error    0    The file exists.

      at Org.IdentityConnectors.Framework.Impl.Api.Remote.Messages.OperationResponsePart ProcessOperationRequest(Org.IdentityConnectors.Framework.Impl.Api.Remote.Messages.OperationRequest) in Server.cs:609

          2016-02-29 13:30:25Z

       

      ConnectorServer.exe    Error    0    The file exists.

      at Org.IdentityConnectors.Framework.Impl.Api.Remote.Messages.OperationResponsePart ProcessOperationRequest(Org.IdentityConnectors.Framework.Impl.Api.Remote.Messages.OperationRequest) in Server.cs:609

          2016-02-29 13:30:38Z

      ConnectorServer.exe    Error    0    The file exists.