Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CRM 4.0 Reporting Error: Timeout Expired RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

     

    I have made a custom report which I have uploaded in CRM 4.0. When trying to run the report CRM gives the following error:

     

    Reporting Error; contact your bla bla

     

    The Eventlog: Timeout Expired.

     

    The report has its timout on 1800 seconds (default). The timeout setting on the (main) dataset within the report is also set on 1800.

     

    The error is given after witing for aprox. 30 seconds (this is within the timout setting). It seems it does not have anything to do with the timeout setting.

     

    The report renders succesfully when executing it again after the error.

     

    Using snapshots isnt an option since the report is user specific.

    I have also tried to use stored procs but this doesnt help.

     

    I have run out of options, does anyone have any clue of what I could try?

     

    Cheers,

     

    Ian

    Wednesday, January 14, 2009 2:54 PM

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote

    To elaborate on the previous answer, there are 3 timeout related settings, the CRM OLEDBTimeout (MSCRM\OLEDBTimeout registry value), the ASP .Net request execution timeout (in web.config), and the reporting services timeout (set on the report and/or dataset).

    When running a report from within CRM, CRM first accesses information within the CRM database, which is subject to the OLEDBTimeout and the ASP .Net request timeout. Only when this is successful will it execute the report.

    Given that the default OLEDBTimeout setting is 30 seconds, and your first error is CRM specific (from the event soruce MSCRMReporting), I think the initial problem is the OLEDBTimeout, so I'd try increasing it, as described here (http://mscrmuk.blogspot.com/2008/09/sql-timeouts-in-crm-generic-sql-error.html)

    Also, as Marcus suggests, try running the report directly from the report server - this should bypass the CRM-specific step, and I'd expect it to work in the scenario you've described

    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    Thursday, May 21, 2009 8:05 AM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Check the registry settings

     

    OLEDBTimeout value in registry

     

    REgards,

    Imran

     

     

    Thursday, January 15, 2009 8:09 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for your reply.

     

    I applied both methods metioned in: http://support.microsoft.com/kb/918609 (incl. editing the registry) unforunately without success Sad

     

    The problem remains...

     

     

    Thursday, January 15, 2009 1:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Two errors/warnings are shown in the eventlog:

     

    First: Error MSCRMReporting

     

    Event Type: Error
    Event Source: MSCRMReporting
    Event Category: None
    Event ID: 19970
    Date:  15-1-2009
    Time:  15:28:53
    User:  N/A
    Computer: INH-CRM02
    Description:
    Report render failure. Error: The operation has timed out

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    Second: Warning

     

    Event Type: Warning
    Event Source: ASP.NET 2.0.50727.0
    Event Category: Web Event
    Event ID: 1309
    Date:  15-1-2009
    Time:  15:28:55
    User:  N/A
    Computer: INH-CRM02
    Description:
    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 15-1-2009 15:28:55
    Event time (UTC): 15-1-2009 14:28:55
    Event ID: 28b6445ff35b4945bd7ef968f4b113a6
    Event sequence: 48
    Event occurrence: 1
    Event detail code: 0
     
    Application information:
        Application domain: /LM/W3SVC/1/ROOT-1-128765030686688196
        Trust level: Full
        Application Virtual Path: /
        Application Path: c:\inetpub\wwwroot\
        Machine name: INH-CRM02
     
    Process information:
        Process ID: 3096
        Process name: w3wp.exe
        Account name: NT AUTHORITY\NETWORK SERVICE
     
    Exception information:
        Exception type: CrmException
        Exception message: An error occurred during report rendering.
     
    Request information:
        Request URL: http://********/Potentials-test/CRMReports/rsviewer/reportviewer.aspx
        Request path: /Potentials-test/CRMReports/rsviewer/reportviewer.aspx
        User host address: 10.212.111.6
        User: INH-SGIDS\adm_ian
        Is authenticated: True
        Authentication Type: Negotiate
        Thread account name: NT AUTHORITY\NETWORK SERVICE
     
    Thread information:
        Thread ID: 1
        Thread account name: NT AUTHORITY\NETWORK SERVICE
        Is impersonating: False
        Stack trace:    at Microsoft.Crm.Web.Reporting.SrsReportViewer.ReportErrorHandler(Object sender, ReportErrorEventArgs e)
       at Microsoft.Reporting.WebForms.ReportViewer.OnError(Exception e)
       at Microsoft.Reporting.WebForms.ReportViewer.OnPreRender(EventArgs e)
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
     
     
    Custom event details:

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Thursday, January 15, 2009 2:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have the same problem.

    Have you found a sollution?

    Wednesday, January 28, 2009 1:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have the similar problem, have you found a solution?

    Thanks

    Wednesday, May 20, 2009 7:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    CRM 4.0 has a few places where you can change the execution timeout settings. Are you running this directly from the report server or from within CRM using the Report Viewer within CRM?
    Wednesday, May 20, 2009 7:33 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    To elaborate on the previous answer, there are 3 timeout related settings, the CRM OLEDBTimeout (MSCRM\OLEDBTimeout registry value), the ASP .Net request execution timeout (in web.config), and the reporting services timeout (set on the report and/or dataset).

    When running a report from within CRM, CRM first accesses information within the CRM database, which is subject to the OLEDBTimeout and the ASP .Net request timeout. Only when this is successful will it execute the report.

    Given that the default OLEDBTimeout setting is 30 seconds, and your first error is CRM specific (from the event soruce MSCRMReporting), I think the initial problem is the OLEDBTimeout, so I'd try increasing it, as described here (http://mscrmuk.blogspot.com/2008/09/sql-timeouts-in-crm-generic-sql-error.html)

    Also, as Marcus suggests, try running the report directly from the report server - this should bypass the CRM-specific step, and I'd expect it to work in the scenario you've described

    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    Thursday, May 21, 2009 8:05 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    You may find this post which deals with exporting to Excel and the SQL timeout issue valuable.

    CRM 4.0 Exporting to Excel over 10000 rows 

    http://msmvps.com/blogs/jeffloucks/archive/2010/08/26/crm-4-0-exporting-to-excel-over-10000-rows.aspx

    The post comprehensively talks about the settings while giving insight on how it can be used. Furthermore it talks about setting infinite timeout.

    • Proposed as answer by Jeff Loucks Thursday, August 26, 2010 8:10 AM
    Thursday, August 26, 2010 7:23 AM