0
Answered

Fatal error 9001 in Identity Broker for Frontier chris21

Shane Day (Chief Technology Officer) 4 years ago in UNIFYBroker/Frontier ichris/chris21 • updated by anonymous 4 years ago 1

As reported by customer:


We started to have an issue with the Unify Connector on Friday night.

The connection between UMC and IdM has failed with the following error;

30/10/2015 20:42:39        Warning        Adapterrequest to get entity from adapter space failed.        Adapter        "Adapter request to get attribute changes from adapter space 53e85508-7648-409c-bd3a-0737028eba29 failed with reason Warning: Fatal error 9001 occurred at Oct 30 2015  8:42PM. Note the error and time, and contact your system administrator

The rest of the error is listed below. Is this an error that you’ve seen before? Would you know how to resolve this?

We have UNIFY Identity Broker v3.0.6 service running.


Reason: System.Data.SqlClient.SqlException:Warning: Fatal error 9001 occurred at Oct 30 2015  8:42PM. Note the errorand time, and contact your system administrator.   at
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean
breakConnection)   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)   at
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand
cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler,
TdsParserStateObject stateObj)   at
System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName,
Boolean async)   at
System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result,
String methodName, Boolean sendToPipe)  at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()   at
Unify.Repository.ChangesItemContext.CreateContext(SqlConnection connection)   at
Unify.Framework.LinqWhereQuery`5.GetEnumerator()   at
System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()   at System.Linq.Enumerable.<DistinctIterator>d__7a`1.MoveNext()   at
Unify.Framework.EnumerableExtensions.<ProduceAutoPages>d__9`1.MoveNext()   at
System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()   at
System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()   at
Unify.Framework.EnumerableExtensions.<ActionOnLast>d__16`1.MoveNext()   at
Unify.Framework.EnumerableExtensions.<ActionOnFirst>d__1c`1.MoveNext()   at
System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()   at Unify.Framework.ActionOnExceptionEnumerator`1.MoveNext()   at
Unify.Framework.EnumerableExtensions.<ActionOnLast>d__16`1.MoveNext()   at
System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)   at
Unify.Adapters.NovellIdentityManagerIdentityBrokerDriverAdapter.Publish(Guid
adapterId)   at
Unify.Adapters.NovellIdentityManagerIdentityBrokerDriverNotificationDecorator.Publish(Guid
adapterId)   at
Unify.Adapters.NovellIdentityManagerIdentityBrokerDriver.Publish(Guid
adapterId)   at SyncInvokePublish(Object ,
Object[] , Object[] )   at
System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance,
Object[] inputs, Object[]& outputs)   at
System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc&
rpc)   at
System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc&
rpc)   at
System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc&
rpc)   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean
isOperationContextSet)"

Affected Versions:
Fixed by Version:

Answer

Answer
Answered

SQL Server Fatal Error 9001 can occur when one of the log database files is unavailable.

Either you have run out of space on your SQL Server instance, or the log file is at its maximum and needs truncating.

I would suggest:

  • Clearing up space on the SQL Server hard drive containing the log and/or database files
  • Truncating the log file using the SQL Server Management Studio (or the appropriate T-SQL commands)
  • Restarting the Windows Server with SQL Server.

If any of those don’t work, then please let me know and we’ll arrange to have a look.

Answer
Answered

SQL Server Fatal Error 9001 can occur when one of the log database files is unavailable.

Either you have run out of space on your SQL Server instance, or the log file is at its maximum and needs truncating.

I would suggest:

  • Clearing up space on the SQL Server hard drive containing the log and/or database files
  • Truncating the log file using the SQL Server Management Studio (or the appropriate T-SQL commands)
  • Restarting the Windows Server with SQL Server.

If any of those don’t work, then please let me know and we’ll arrange to have a look.