none
msidmCompositeType Request Denied RRS feed

  • Question

  • Hi,

    We are running a full sync this weekend and I noticed that on the FIM MA export the msidmCompositeTypes all return “Denied” as a status.

    The FIM web service reports a SQL timeout expired session.

    I am able to put FIM in pre-asynchronous mode and the exports complete but take a long time.

    We have the timeout on the web service set to 20 minutes. The msidmCompositeType requests hang in a validating state until the 20 minutes are up and then report the Denied status.

    Ever seen this before? It doesn’t appear to be a permissions issue and SQL is definitely responding when the requests are issued in single file.

    I am going to try adjusting the length of the aggregationThreshold to see if that helps, but appreciate any ideas. Tried to figure this out yesterday to no avail.

    Thanks,

    Sami

    Requestor: urn:uuid:fb89aefa-5ea1-47f1-8890-abe7797d6497

    Correlation Identifier: b1c67faf-aa01-465d-90b8-d47d7299c18c

    Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---> System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.CreateRequest(UniqueIdentifier requestor, UniqueIdentifier targetIdentifier, OperationType operation, String businessJustification, List`1 requestParameters, CultureInfo locale, Boolean isChildRequest, Guid cause, Boolean doEvaluation, Nullable`1 serviceId, Nullable`1 servicePartitionId, UniqueId messageIdentifier, UniqueIdentifier requestContextIdentifier, Boolean maintenanceMode)

       at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Put(Message request)

       --- End of inner exception stack trace ---

    .Net SqlClient Data Provider: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

       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.SqlDataReader.ConsumeMetaData()

       at System.Data.SqlClient.SqlDataReader.get_MetaData()

       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)

       at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)

       at System.Data.SqlClient.SqlCommand.ExecuteReader()

       at Microsoft.ResourceManagement.Data.DataAccess.DoRequestCreation(RequestType request, Guid cause, Guid requestMarker, Boolean doEvaluation, Int16 serviceId, Int16 servicePartitionId)

    Sunday, September 15, 2013 1:34 PM

All replies

  • Bouncing SQL server appears to have done the trick.
    Monday, September 16, 2013 1:10 PM
  • Hello,

    I have the same error, just over a Transition In MPR/WF.

    Rebooting the SQL Service solve this.

    Regards,


    Sylvain

    Wednesday, August 13, 2014 8:52 AM
  • Hello!
    I'm having the same problem and found this thread, but rebooting the SQL service doesn't do any good.

    So, is there anyone out there with more ideas on what to try?

    Regards,

    Kristoffer

    Monday, August 10, 2015 8:06 AM
  • Have you tried re-indexing the FIM databases? And maybe restarting all services?
    Wednesday, August 19, 2015 9:02 PM