0
Answered

Import all entities from connector failed in Aurion IdB, Not Importing any changes from Aurion

Jerry Natarajan 3 years ago in UNIFYBroker/Aurion • updated by anonymous 3 years ago 11

@Northcott, one fine day, IdB started throwing these errors on all its connectors.

Error in One liner:

Change detection engine import all items failed.
Change detection engine import all items for connector SecurityUser failed with reason Aurion API error -1: . Duration: 00:00:01.0940697

And to Note: This error is happening in all the Connectors(Schedule, Person, Sec User and Position)

Work did from my end:

1. Tested Connectivity from Aurion Agent and it is connecting successfully

2. Tested the URL and I am able to see the XML output.

3. Tried restarting the IdB Service and still the error pops up

Some Investigation from my side, This error started with HTTP404 error which was thrown on Schedule Connector

Import all entities from connector failed.Import all entities from connector Schedule failed with reason The request failed with HTTP status 404: Not Found.. Duration: 00:00:00.0270257
Error details:
System.Net.WebException: The request failed with HTTP status 404: Not Found.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Unify.Communicators.AurionAPI.EV397_AURION_WSService.LOGON(String P_USER, String P_PASSWORD, String& P_TOKEN, String& P_MESSAGE, Decimal& P_STATUS)
at Unify.Communicators.AurionWSCommunicator.Logon(String userName, String password)
at Unify.Communicators.AurionAgent.Open()
at Unify.Connectors.AurionApiReadingConnector.<GetAllEntities>d__4.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at Unify.Framework.Collections.ActionOnExceptionEnumerator`1.MoveNext()
at Unify.Framework.Collections.EnumerableExtensions.<ActionOnLast>d__10`1.MoveNext()
at Unify.Framework.Collections.EnumerableExtensions.<ProduceAutoPages>d__7`1.MoveNext()
at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.Visit()
at Unify.Framework.Visitor.VisitEvaluateOnThreadPool[T](IEnumerable`1 visitCollection, Action`2 visitor, Int32 maxThreads)
at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetection(IEnumerable`1 connectorEntities)
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.ImportAllChangeProcess()
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.RunBase()
at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run()
at Unify.Product.IdentityBroker.ConnectorJobExecutor.<>c__DisplayClass33_0.<Run>b__0()
at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)

And ever since that happened, the below error started to happen.

Change detection engine import all items failed.Change detection engine import all items for connector SecurityUser failed with reason Aurion API error -1: . Duration: 00:00:01.0940697
Error details:
System.Exception: Aurion API error -1: 
at Unify.Communicators.AurionWSCommunicator.RaiseExceptionOnErrorCondition(Decimal pStatus, String pMessage)
at Unify.Communicators.AurionWSCommunicator.SetFunction(String function)
at Unify.Communicators.AurionApiFunctionBase.RunFunction()
at Unify.Communicators.AurionAgent.QueryToXml(String queryId, String expectedObjectName)
at Unify.Connectors.AurionApiReadingConnector.<GetAllEntities>d__4.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at Unify.Framework.Collections.ActionOnExceptionEnumerator`1.MoveNext()
at Unify.Framework.Collections.EnumerableExtensions.<ActionOnLast>d__10`1.MoveNext()
at Unify.Framework.Collections.EnumerableExtensions.<ProduceAutoPages>d__7`1.MoveNext()
at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.Visit()
at Unify.Framework.Visitor.VisitEvaluateOnThreadPool[T](IEnumerable`1 visitCollection, Action`2 visitor, Int32 maxThreads)
at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetection(IEnumerable`1 connectorEntities)
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.ImportAllChangeProcess()
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.RunBase()
at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run()
at Unify.Product.IdentityBroker.ConnectorJobExecutor.<>c__DisplayClass33_0.<Run>b__0()
at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)

P.S. Please let me know if you need the configuration and logs. I cannot find an attachment where I can attach the logs

Affected Versions:
Fixed by Version:

Answer

Answer
Answered

An update to Aurion (11.16) introduced a breaking change. Aurion are working on the issue. A workaround has been issued, update to the latest versions of the connector.

GOOD, I'M SATISFIED
Satisfaction mark by Jerry Natarajan 3 years ago
Under review

Hi Jerry,

What's the question? The error is in the details (404: Not Found).

Thanks.

Hi Adam,

Thanks for looking into this.

I just need to understand what to ask the customer. so I can ask the right person to fix things on Aurion side of things.

Can we find out what is not found? the Query_To_XML API not available?

There's not enough information to know why, generally 404 are raised by the .NET framework when it's unable to reach the destination. However, there's nothing stopping the remote service return a 404 error code. If the client can't just tell you the correct settings, you might need to use some tools to help diagnose the problem (e.g. .NET trace, Fiddler or Wireshark).

Regarding the API error -1, that gets raised when an error code is returned by Aurion. Unfortunately it hasn't returned a message along with the error code (it would appear after the colon), so it makes it difficult to tell what's going wrong. That might require help from the client's Aurion admin and/or Aurion support.

thanks Adam, I have raised this issue with Customer and let you know how it goes.

Hi Adam,

As per documentation, the IdB for Aurion supports version v10.1.2.04 MR1. The customer has now version 11.18. Should we update the IdB to support 11.18 or it is tested and supported already? Just want to confirm. Thanks

Hi Jerry,

Our test environment is on Aurion v11.15, so there shouldn't be any problems with 11.18. How recently did the customer upgrade? Did the errors occur immediately after upgrading, or did it work temporarily and then start to fail? Is it possible that an error was made during the upgrade process?

Hi Curtis,

The customer updated on 26th Oct late afternoon. The errors started on 27th Oct first with HTTP404 and then followed by Full Import error by Change detection engine.

Hi Curtis,

I think we have narrowed down the problem to Aurion Product upgrade IS causing this issue. We tested by creating a test Agent and Connector with a Test Aurion Instance running v11.14 and it works there. Can we test IdB 5.0 with 11.18 in our labs and let us know how it goes? So we can update the customer? Thanks.

Answer
Answered

An update to Aurion (11.16) introduced a breaking change. Aurion are working on the issue. A workaround has been issued, update to the latest versions of the connector.

Thanks Adam, appreciate your efforts to get this situation resolved!