web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Error in crm 2011 custom report

(0) ShareShare
ReportReport
Posted on by 464

processing!ReportServer_0-9!1790!05/28/2012-16:55:45:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot read the next data row for the dataset DSMain. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: Microsoft.Crm.CrmException: An unexpected error occurred. Microsoft.Crm.CrmException: The fetch data set query timed out after 468.4788045 seconds. Increase the query timeout, and try again. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: An unexpected error occurred. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: The fetch data set query timed out after 468.4788045 seconds. Increase the query timeout, and try again.

*This post is locked for comments

I have the same question (0)
  • AaronRic Profile Picture
    10,035 on at

    Hi Santosh,

    Is this occurring in CRM Online or CRM On-Premise?

    Thanks

  • Santosh bhagat Profile Picture
    464 on at

    HI AaronRic,

    this occurring in CRM On-Premise

  • AaronRic Profile Picture
    10,035 on at

    Hi Santosh,

    The first thing we need to look at is if this is happening on all reports or only reports that are returning a large amount of data. It also seems that the trace file would contain other errors before this leading to what is failing. Are you seeing any other errors before or after this at all? You can try increasing the timeouts of the CRM server to see if the report generates:

    Create OleDBTimeout Key

    a. Open the registry (regedit)

    b. Go to HKEY_LOCAL_MACHINE>SOFTWARE>MICROSOFT>MSCRM

    c. Create a new DWORD Value (do this by right clicking on MSCRM and selecting new).

    d. Call the key OleDBTimeout

    e. Double click on the key name and give it a value of 86400 and select hexadecimal.

    f. After this is done, do an IISRESET

    Create ExtendedTimeout Key

    a. Open the registry (regedit)

    b. Go to HKEY_LOCAL_MACHINE>SOFTWARE>MICROSOFT>MSCRM

    c. Create a new DWORD Value (do this by right clicking on MSCRM and selecting new).

    d. Rename the DWORD value to "ExtendedTimeout."  

    e. Right-click the DWORD value, and then click Modify.  

    f. In the Edit DWORD Value dialog box, type 1000000 in the Value data field, and then click OK.

    Note You can enter a value that is larger than 1000000 in the Value data field.  

    g.  After this is done, do an IISRESET

    I would also ensure that you have the latest Update Rollup installed to the CRM Server and the SRS server.

    Thank you

  • Santosh bhagat Profile Picture
    464 on at

    Hi AaronRic,

    Thanks for your valuable reply and time.

    This is happening on only reports that are returning a large amount of data.

    It shows only timeout error.

  • Santosh bhagat Profile Picture
    464 on at

    Hi AaronRic,

    After doing the specified changes in registry i am getting error as:

    processing!ReportServer_0-6!66c!07/10/2012-09:31:17:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot read the next data row for the dataset DSMain. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException:

    Microsoft.Crm.CrmException: An unexpected error occurred.

    Microsoft.Crm.CrmException: The fetch data set query timed out after 320.476 seconds. Increase the query timeout, and try again. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: An unexpected error occurred. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: The fetch data set query timed out after 320.476 seconds. Increase the query timeout, and try again.

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

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

      at Microsoft.Crm.Reporting.DataExtension.Common.Fetch.FetchDataExtensionDataReaderBase.RetrieveResults(FetchExpression outerQuery, QueryByEntityNameDictionary subQueries)

      at Microsoft.Crm.Reporting.DataExtension.Common.Fetch.FetchDataExtensionDataReaderBase.RetrieveNextBatch()

      at Microsoft.Crm.Reporting.DataExtension.Common.Fetch.FetchDataExtensionDataReaderBase.<Read>b__0()

      at Microsoft.Crm.Reporting.DataExtension.Common.ExceptionManager.HandleUnsafeException[TResult](Func`1 body)

      at Microsoft.Crm.Reporting.DataExtensionShim.Common.ICrmDataReader.Read()

      at Microsoft.Crm.Reporting.DataExtensionShim.Common.SrsExtDataReader.Read()

      at Microsoft.ReportingServices.DataExtensions.MappingDataReader.GetNextRow()

  • Suggested answer
    AaronRic Profile Picture
    10,035 on at

    Thank you for the update Santosh. I do believe there are other errors that we are missing. At this time, we would need to troubleshoot 1-on-1 to grab additional details. Please go ahead and create a support case and be sure to include the SRS logs and the exact time of the reproduction of the error.

    Thanks!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans