0
Fixed

SQL Connector timeout

Matthew Woolnough 6 years ago • updated by anonymous 3 years ago 2

SQL Connector time out after export from FIM.
Restarting IdB service resolves issue so I can import again, but export continues to timeout.

--------------------------------------
Log Name: Application
Source: FIMSynchronizationService
Date: 11/2/2012 8:32:05 AM
Event ID: 6801
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: IDSYS.widgetcorp.local
Description:
The extensible extension returned an unsupported error.
The stack trace is:

"System.Exception: Error occurred when attempting to save entity with distinguished name

CN=Alex Rujak

Error:

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Unify.Framework.Data.DbConnectionExtensions.OpenIfClosed(IDbConnection connection)
at Unify.Framework.Data.SqlServerDataControl.CreateComponent(Boolean factoryInformation)
at Unify.Framework.Data.AdoNetDataControl.ExecuteDataSetQuery(DataSet resultSet, String commandText, IEnumerable`1 parameters, String[] tableNames, CommandType commandType)
at Unify.Framework.Data.AdoNetDataControl.ReturnDataSetQueryT(String commandText, IEnumerable`1 parameters, String[] tableNames, CommandType commandType)
at Unify.Product.IdentityBroker.DirectCommunicatorBase`1.GetEntitiesDataTable(ICollection`1 keyList)
at Unify.Product.IdentityBroker.DirectCommunicatorBase`1.AddEntities(IEnumerable`1 entities)
at Unify.Product.IdentityBroker.DirectReadWriteConnectorBase`1.AddEntities(IEnumerable`1 entities)
at Unify.Product.IdentityBroker.EventNotifierAddingConnectorDecorator.AddEntities(IEnumerable`1 entities)
at Unify.Product.IdentityBroker.Adapter.AddEntities(IEnumerable`1 entities, Boolean reflect)
at Unify.Product.IdentityBroker.AdapterNotifierDecoratorBase`1.AddEntity(IAdapterEntity entity)
at Unify.Product.IdentityBroker.LDIFAdapterBase.ExportChanges(ExportedLDIFForAdapter exportedLdifForAdapter)
at SyncInvokeExportChanges(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.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
at Unify.Product.IdentityBroker.IdentityBrokerManagementAgentProxy.ExportEntry(ModificationType modificationType, String[] changedAttributes, CSEntry csentry)
Forefront Identity Manager 4.1.2548.0"

Affected Versions:
Fixed by Version:

A fix has been pushed. It appears there was one place where the database connection wasn't being properly disposed.