0
Answered

Error occurs once per page "Cannot access destination table 'EntityValueOrigin'"

Tom Parker 6 days ago in PowerShell connector • updated 3 days ago 5
Topic collaborators

Once per page on export the following error occurs.There doesn't appear to be any impact from the error as the user is provisioned correctly by powershell and they also appear correctly in UNIFYBroker. They also appear in both the "adds" section of MIM and the "errors" section under "unexpected-error". The following stack trace appears in the Identity Broker logs.

We very recently upgraded from 5.0.3 but we are unsure if that's related.

UNIFYBroker Version: 5.1.0 Revision #2

MIM Version: 4.4.1749.0


System.InvalidOperationException: Cannot access destination table 'EntityValueOrigin'. ---> System.Data.SqlClient.SqlException: Invalid object name 'EntityValueOrigin'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlBulkCopy.RunParser(BulkCopySimpleResultSet bulkCopyHandler)
at System.Data.SqlClient.SqlBulkCopy.CreateAndExecuteInitialQueryAsync(BulkCopySimpleResultSet& result)
at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync(CancellationToken cts, TaskCompletionSource`1 source)
--- End of inner exception stack trace ---
at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync(CancellationToken cts, TaskCompletionSource`1 source)
at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync(CancellationToken ctoken)
at System.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount, CancellationToken ctoken)
at System.Data.SqlClient.SqlBulkCopy.WriteToServer(DataTable table, DataRowState rowState)
at Unify.Product.IdentityBroker.EntityValueOriginContext.InsertItems(ISet`1 addedItems, EntityValueOriginDataContext sourceContext, SqlConnection connection)
at Unify.Framework.Data.LinqContextConversionBase`4.SubmitChanges()
at Unify.Product.IdentityBroker.OriginInformationProcessor.RunBase()
at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)",Normal

Affected Versions:
Fixed by Version:

Answer

Answer
Answered

Please run the Database upgrade script, located in the Database sub-directory of the Identity Broker installation directory.

GOOD, I'M SATISFIED
Satisfaction mark by Tom Parker 3 days ago
Under review

Any chance you upgraded from Identity Broker v5.0 to v5.1? Did you run the Database upgrade script?

Answer
Answered

Please run the Database upgrade script, located in the Database sub-directory of the Identity Broker installation directory.

I've run the script and seen the tables that were missing have been created but we're still seeing the same behavior from the MA exports. The really weird thing though is that the errors have disappeared from the logs, they only appear in the MIM console, one per page exported, that appear as each page is completed.There's still no issue in provisioning to either the target system or identity broker.

Hi Tom,

Can you confirm that you're seeing the same error? A screenshot or fresh copy-paste to confirm would be great.

+1

Although the specific error that was appearing in the logs has been fixed, I haven't fixed the behavior that's been observed yet but it's confirmed to not be on the UNIFY Broker side, confirmed by sending ldap requests directly to Broker with no issues. I'll update with the solution to save the next person who finds this on google.

Thanks for the assistance Curtis.