chris21 Import All fails with "Access has been denied"
Andrew Josephson 8 years ago in UNIFYBroker/Frontier ichris/chris21 • updated by anonymous 4 years ago • 6
When the Identity Broker is accessed, all the Connectors are currently Red and the errors in the log are as follows:
Change detection engine import all items failed.
Change detection engine import all items for connector Chris21 POS failed with reason Line type is recognized but not valid Command. Line: GTR:cbr="logon",logonapplication="breoption",user="REDACTED",password="REDACTED",credentialsrequired="Y",error01="BRE029:Unable to access interface. Contact your Security Officer.",error02="BRE103:Access has been denied.",status="fail". Duration: 00:00:01.4218568
System.IO.InvalidDataException: Line type is recognized but not valid Command. Line: GTR:cbr="logon",logonapplication="breoption",user="REDACTED",password="REDACTED",credentialsrequired="Y",error01="BRE029:Unable to access interface. Contact your Security Officer.",error02="BRE103:Access has been denied.",status="fail"
at Unify.Product.IdentityBroker.Chris21Agent.CheckLoginResult(IChris21Record loginResultRecord, Action`1 pre)
at Unify.Product.IdentityBroker.Chris21Agent.GetLoginToken(IChris21ConnectorInformation connectorRequest)
at Unify.Product.IdentityBroker.Chris21Agent.List(IEnumerable`1 keyColumnNames, IChris21ConnectorInformation connectorRequest)
at Unify.Product.IdentityBroker.Chris21ConnectorBase.GetAllEntities(IStoredValueCollection storedValueState)
at Unify.Product.IdentityBroker.ConnectorToReadingConnectorBridge.GetAllEntities(IStoredValueCollection storedValueState)
at Unify.Product.IdentityBroker.EventNotifierReadingConnectorDecoratorBase`1.GetAllEntities(IStoredValueCollection storedValues)
at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)
Looks like a permissions issue at this point with the BRE, but we need to know where we should be looking.
Customer support service by UserEcho
Hi Richard Green, please check what version of Identity Broker for Frontier chris21 is installed. A patch is likely required due to the regression in the chris21 interface.
Version 220.127.116.11 of the Chris21 connector is installed.
Hi Richard Green,
Would it be possible to upgrade to the latest v4.1 RTM (v4.1.1)? As it already contains the required update. There are a number of places in the source for v18.104.22.168 and it'd probably take longer to get the right one than it would to upgrade.
I expect an upgrade will be fine, i'll check with the customer.
Updated connector successfully deployed into PRE, awaiting go-ahead to roll into Prod.
I saw the same error in a much later version of the Chris21 Connector (v22.214.171.124) but the cause was completely different:
In my case the error was appearing because I had specified an invalid Logon Application.