Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CRM 4 - Org import fails after creating reprt in report services RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Org import fails (the error follows at the bottom).

    Does this look like the last Reporting Services report is causing the problem or is there something happening after that?

    20:50:08|   Info| PublishReportsFromDatabase: Creating report in Reporting Services.  ReportId: {1e3a3e71-1382-de11-ab2d-000c297b488b}, Name: User Summary
    20:50:10|   Info| PublishReportsFromDatabase: Creating report in Reporting Services.  ReportId: {c14bddd6-8ca9-4d3f-80ec-fdd30d7e0e74}, Name: User Summary
    20:50:47|  Error| Import Organization (Name=MyOrg, Id=7690eaec-c823-e011-8402-00155d293509) failed with Exception:
    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.ExecuteDbDataReader(CommandBehavior behavior)
       at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader()
       at Microsoft.Crm.Tools.Admin.ImportOrganizationInstaller.GetWorkflows(Guid orgId)
       at Microsoft.Crm.Tools.Admin.ImportOrganizationInstaller.ProcessWorkflowUIData(Guid organizationId)
       at Microsoft.Crm.Tools.Admin.ImportOrganizationInstaller.Import(Guid organizationId, String organizationUniqueName, String organizationFriendlyName, String sqlServerName, String databaseName, Uri reportServerUrl, String privilegedUserGroupName, String sqlAccessGroupName, String userGroupName, String reportingGroupName, String privilegedReportingGroupName, ICollection`1 users, MultipleTenancy multipleTenancy)
    20:50:47|Warning| Attempting to cancel a long running process: ProgressWizard. This might leave the data in an invalid state and the application might not function correctly.
    09:06:23|Warning| Attempting to cancel a long running process: FinishWizard. This might leave the data in an invalid state and the application might not function correctly.

     

    Friday, January 21, 2011 1:21 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    We had tried increasing the timeout but it didn't work.

    In the end , it turned out that we had to empty the Workflow History tables.  There were rather a lot of records in there.

    I suppose it seems obvious now although it's not one of the solutions I've seen in my searches so hopefully this will help someone.

    Tuesday, January 25, 2011 8:49 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Just spotted the GetWorkflows(Guid orgId) line in the error.

    Perhaps it has completed the reports and moved on to the workflows.  Any ideas how to get to the bottom of this?

    What happens if the workflow needs an assembly and it's not on the new sserver?

    Friday, January 21, 2011 1:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    More info about the live server:

    1. There is a single unpublished workflow which has not been completed so shows a red X.

    2. There are a number of assemblies which supply extra functions to the workflows which have not been brought actoss to the development server.

    3. Some workflows were created by the system admin (I read a note that sait this might cause a problem with imports but I'm not convinced).

    Other options that I can see:

    1. Remove the workflow records from the database before running the import.  Not sure how many dependent tables there will be that will also require deletion.

    2. The live server is Rollup 10 and the development server is Rollup 14.  Can probably upgrade the live server without too much fuss.

    Shame the trace file is so vague!!

    • Edited by Gordon Johnston Friday, January 21, 2011 2:11 PM spelling error
    Friday, January 21, 2011 2:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It looks like the reports are fine, and the problem is a SQL timeout when read Workflow information. The first thing I'd try is increasing the timeout, as described here - http://mscrmuk.blogspot.com/2008/09/sql-timeouts-in-crm-generic-sql-error.html

    If that doesn't help, then I'd suggest removing the asyncoperation records, as described here - http://support.microsoft.com/kb/968520

    I doubt the rollup mismatch is relevant, but you can never be certain

    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    Monday, January 24, 2011 1:03 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    We had tried increasing the timeout but it didn't work.

    In the end , it turned out that we had to empty the Workflow History tables.  There were rather a lot of records in there.

    I suppose it seems obvious now although it's not one of the solutions I've seen in my searches so hopefully this will help someone.

    Tuesday, January 25, 2011 8:49 AM