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

I am upgrading from IDB to UNIFYBroker and recreating the Aderant Expert connector (using a SQL Agent).  Test Connection on the Agent returns successfully with no warnings or errors.

When I run an Import All I immediately see the following error logged:

Looking at the Aderant Expert database in SSMS I see that the HSM_PERSNL table has an OBSOLETE_1 field as might be expected:

Can you advise what SQL command is being executed, or otherwise help work out why it's failing?

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.

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

Hi Guys,

Getting this error when trying to do DIDS operations in FIM. Issue started last night and all DI operaions appear to be failing now. I'm doing Full imports now as a work around for now.

Reading through a similar ticket I stumbled across this one Richard had raise quite a while ago:
https://voice.unifysolutions.net/communities/6/topics/474-delta-imports-from-idb-on-ldap-groups-consistently-fail-with-sequence-contains-more-than-one

The comments on this ticket say that this was resolved in v5.0.2 however the version in this environment is v5.0.4. For some additional imformation the version of FIM is 4.1.3646.0.

The extensible extension returned an unsupported error.
The stack trace is:
"Unify.Product.IdentityBroker.LdapOperationException: Internal Server Error #11: System.InvalidOperationException: Sequence contains more than one element
at System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query, QueryInfo queryInfo, IObjectReaderFactory factory, Object[] parentArgs, Object[] userArgs, ICompiledSubQuery[] subQueries, Object lastResult)
at System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query, QueryInfo[] queryInfos, IObjectReaderFactory factory, Object[] userArguments, ICompiledSubQuery[] subQueries)
at System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query)
at System.Data.Linq.Table`1.System.Linq.IQueryProvider.Execute[TResult](Expression expression)
at Unify.Framework.Data.LinqQueryConversionProvider`5.ExecuteMethodCallExpression[TResult](MethodCallExpression methodCallExpression)
at Unify.Framework.Data.LinqQueryConversionProvider`5.Execute[TResult](Expression expression)
at System.Linq.Queryable.SingleOrDefault[TSource](IQueryable`1 source, Expression`1 predicate)
at Unify.Product.IdentityBroker.ChangeLogToLDAPEntryConverter.EntryUuidAttributeValue(IChangeLogItem sourceValue, IDictionary`2 partialAttributes)
at Unify.Product.IdentityBroker.ChangeLogToLDAPEntryConverter.Transform(IChangeLogItem sourceValue)
at Unify.Product.IdentityBroker.SearchRequestHandlerBase.d__13.MoveNext()
at Unify.Framework.Visitor.Visit[T](IEnumerable`1 visitCollection, Action`2 visitor)
at Unify.Product.IdentityBroker.LDAPConnection.d__33.MoveNext()
at Unify.Product.IdentityBroker.LdapConnection.GetMessage(Int32 messageId)
at Unify.Product.IdentityBroker.SearchRequest.Send(Func`2 send, Func`2 recv)
at Unify.Product.IdentityBroker.LdapConnection.SendRequest(ILdapRequest request)
at Unify.Product.IdentityBroker.LdapConnectionProxy.PartitionDeltaRequestPaged(String partitionDN, Int64 lastChangeNumber, Int32 pageSize)
at System.Linq.Enumerable.d__14`2.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Enumerable.d__14`2.MoveNext()
at Unify.Product.IdentityBroker.ExtensionMethods.Take[TSource](IEnumerator`1 source, Int32 count, IList`1& items)
at Unify.Product.IdentityBroker.ExtensionMethods.d__0`1.MoveNext()
at Unify.Product.IdentityBroker.ImportProxy.Import(GetImportEntriesRunStep importRunStep)
Forefront Identity Manager 4.1.3646.0"

This is current a high priority ticket so any help is greatly appreciated.

Thanks,

Hayden

Hi,

I have a connector named "Student" with 28k users but in the Student adapter I have at the momentL 3k entities.

The maximum entities in the adapter was 13k. 

UNIFY Broker has been fully reinstalled and the database re-created to try to fix the issue.

The logs are in Diagnostic mode, there is no error.

We are in UAT env, the same configuration is working fine in DEV and TEST environments.

Seems this has happened before - but in version 5.2.1 Revision #0 the SQL connector instances do not allow you to save comments

Sometimes SQL tables and views are not able to be modified as part of an implementation, but the next best thing would often be the use of virtual tables (i.e. a select statement encapsulated by parentheses followed by a table alias.  Presently this is not possible to configure via the UI - perhaps this is only a UI limitation and not a service limitation.

The benefits of this will be in removing dependencies on DBAs, particularly during the build phase when 3rd party SQL resource availability may be an issue (e.g. 3rd party).

When using polling with the AD connector, a new record is created for objects where any attribute that is part of the key has been changed, and the old object is not removed.  This either means that the polling functionality is not useful, or else the connector cannot be usefully used with any key other than objectGUID.

If this behaviour can't be improved then it really should be mentioned in the documentation for the connector since it's quite important.

How can I view which Adapters and Lockers objects are currently joined in the UNIFYBroker/Plus UI?