Identity Broker Forum

Welcome to the community forum for Identity Broker.

Browse the knowledge base, ask questions directly to the product group, or leverage the community to get answers. Leave ideas for new features and vote for the features or bug fixes you want most.

0
Answered

Chris21 Connector status="fail" existing

Hi guys,

I have multiple Chris21 connectors failing in a customer system with the following error when running a full import:

My initial thoughts were that this was a problem with Chris21. But I have had the customer run the GTR query directly against Chris21 and it has received no such status failed messages.

The customer had recently upgraded to Chris21 version 8.19.10. Identity Broker version is 4.1.1 and Chris21 Connector version 4.1.1.0. Version upgrades were undertaken on the 12/05 and completed on the 14/05, however the issue was only recently raised so we weren't able to grab logs before these date's to see if it was an active issue.

The customer has pointed out that one field has been renamed on one of the forms but this field is not used in the schema in Idb.

Before this the agent and connector was displaying this error which we fixed by setting the interface in Chris21 to "Default":


Not sure if it is related but I thought it would be helpful as to understanding the full scope of the problem.

Would anyone be able to shed any light as to why this could be happening?

Thanks, Liam

Answer

Hi guys,

We found out why Identity Broker was failing at importing from some of the forms. The method of posting to c21connect.asp is no longer supported and calls have to be funneled through licensed components. We switched to the Web Services method of connecting and have now resolved the issue.

This ticket can now be closed.

Thanks

0
Not a bug

Chris21 "Trying to pass a table-valued parameter with 6 column(s) where the corresponding user-defined table type requires 5 column(s)" during processing

In my newly upgraded customer environment I am seeing the following error when running an Import All for a Chris21 connector:

No entries were imported.  Could you please advise what I should do about it?

UNIFYBroker v5.3.2.0
UNIFYBroker/Chris21 v5.3.0.0

0
Planned

Error "EaiFlagDeleteAttribute field is required" when upgrading from an older Chris21 connector

When upgrading from a pre-UNIFYBroker v5 Chris21 environment I copied the Connector configuration XML across directly.  When associating the Chris21 Connector to the new v5 Agent, there was a UI error on save:

This happened because the newer version of the Chris21 Agent/Connector package has an additional attribute in the XML configuration that wasn't previously present (and UNIFYBroker doesn't automatically add it).

The solution is to edit the XML configuration file to add the attribute by hand then restart the UNIFYBroker service:

The value used for the attribute (eaiFlagDeleteAttribute="eaiunifyfl") were obtained by manually creating a new Chris21 Connector to see what value the system assigned to the attribute.

0
Won't fix

Cannot specify default (blank) Logon Application for the Chris21 Agent in the UI

In the Chris21 Agent form in the UNIFYBroker UI the "Logon Application" field is mandatory:


However the help for the the field says it can be left blank to not include it in the logon:

I was able to workaround this by editing the Agent configuration XML directly, to remove the value.  When I did so the value passed to Chris21 defaulted to "chris21".  So another workaround is likely to be entering "chris21" into the field directly rather than leaving it blank.

UNIFYBroker v5.3.2.0
Chris21 Connector v5.3.0.0

0
Planned

UNIFYBroker for chris21 v5.3.0 RTM Agent UI Issue

For the Chirs21 connector on the Agent screen Logon Application field should be optional. In the UNIFYBroker for chris21 v5.3.0 RTM it is mandatory.

0
Answered

Cannot retreive schema for Chris21 DET connector

Jack Cheng 1 year ago in UNIFYBroker/Frontier ichris/chris21 updated 1 year ago 7

Chris21 DET Connector is configured as follow:

However, retrieving schema failed with the below error in the log:

20190628,03:22:53,UNIFYBroker,Logging Engine,Information,Log file started.,Minimal
20190628,03:22:53,UNIFYBroker,Connector Engine,Error,"The schema for 'c21 DET Connector' connector was not updated for the following reason: System.AggregateException: One or more errors occurred. ---> System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at Unify.Product.IdentityBroker.Chris21RecordtoChris21FieldDefinitionsAdapter.Transform(IChris21Record sourceValue, Boolean showTranslations)
at Unify.Product.IdentityBroker.Chris21Agent.d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Unify.Product.IdentityBroker.Chris21ConnectorBase.d__33.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at Unify.Product.IdentityBroker.Chris21ConnectorSchemaProvider.GetSchema(ISchemaProviderFactoryInformation factoryInformation)
at Unify.Product.IdentityBroker.ConnectorEngine.SchemaProviderResult(IOperationalConnector`1 operationalConnector, Func`2 selector, IEnumerable`1 appliedFields)
---> (Inner Exception #0) System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at Unify.Product.IdentityBroker.Chris21RecordtoChris21FieldDefinitionsAdapter.Transform(IChris21Record sourceValue, Boolean showTranslations)
at Unify.Product.IdentityBroker.Chris21Agent.d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Unify.Product.IdentityBroker.Chris21ConnectorBase.d__33.MoveNext()<---
",Normal

Same error with a new Unify.IdentityBroker database as well.

The Frontiner chris21 agent connects without any error.

Answer

Run the following in the GTR form in chris21. This will run the same query the connector uses to retrieve its schema.

cbr="componentlist",screen="DET"
0
Answered

Timeout on Chris 21 Connectors

I'm getting timeouts on some Chris21 connectors. They seem to be intermittent, sometimes it works fine. Using v4.1.x Identity Broker and Chris21 connector. The error I get is as follows:

Are there any settings I can tweak on the IdB side to resolve this or is this Chris21 ending the connection early? I think there's a batch size setting or something similar but IdB is so slow to load with this customer I can't check again.

0
Answered

Chris21 Connector Failing - no status attribute

I'm getting the exact same error as in this ticket https://voice.unifysolutions.net/communities/6/topics/3223-import-all-entities-from-connector-chris21-secondment-connector-failed-with-reason-result-record

From the looks of things it's the exact same issue at the same customer. I don't know if Jerry ever resolved it. I've attached the log entry that's showing the error. It's using Idb and Chris 21 versions 4.1.x. Their Chris21 instance is version 8.16.17.

Adam suggested running some Chris 21 query as a resolution but I'm not sure where that query should be run. Is this likely to be a misconfiguration of Chris21 or something with IdB? This is in a test environment.

Please let me know if you need any more information.

0
Won't fix

Chris21 full import not completing

Matthew Davis (Engineering Manager) 2 years ago in UNIFYBroker/Frontier ichris/chris21 updated 10 months ago 1

Chris21 full import is getting partway through and then blocking - no errors thrown, just doesn't complete.

It's only processing 23,000 entities out of a total of 114,000.

0
Answered

Any known issues with C21 upgrades?

HSF are upgrading their C21 instance over the weekend so I just wanted to check if there's any known issues with upgrades and the broker c21 connector. They say it's an Engine update, going to version 8.16.5. They're using Identity Broker version 4. Any known issues?

Answer

Hi Daniel,

None that I have been made aware of. As you haven't mentioned what version of the connector, or what version of chris21 they are upgrading from, just ensure that you're on the latest available connector, as there was a change to the way logons were performed quite some time ago that we had to update the connector for (logonapplication became an invalid argument). Additionally, as with any upgrade (and in line with Frontier advice), ensure that the integration is included in the upgrade and test plan.

Thanks.