none
CRM 2011 and Reporting Services "ArgumentNullException: Value cannot be null."

    Question

  • Hello Experts,

    Does anyone meet the following situation:

    We have custom Reporting Services reports. We deploy it into our development CRM instance and it works perfect in this environment.

    However during deployint it into test environment and running the report from CRM inteface, the following information is presented to user: "Rs Aborted - Value cannot be null".

    Here is all the information we found in TRACE file:

    >MSCRM Error Report:
    --------------------------------------------------------------------------------------------------------
    Error: Exception of type 'System.Web.HttpUnhandledException' was thrown.

    Error Number: 0x80040203

    Error Message: name

    Error Details: name

    Source File: Not available

    Line Number: Not available

    Request URL: http://localhost/XXX/CRMReports/rsviewer/reportviewer.aspx

    Stack Trace Info: [ArgumentNullException: Value cannot be null.
    Parameter name: name]


    [CrmArgumentNullException: name]
       at Microsoft.Crm.ReportObjectModel.ReportServerOrganizationContext.GetItemPath(String name, Boolean isSharedReport)
       at Microsoft.Crm.Web.Reporting.RemoteSrsReportViewer.LoadReportAndSetParameters()
       at Microsoft.Crm.Application.Controls.AppUIPage.OnPreRender(EventArgs e)
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    [HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown.]
       at System.Web.UI.Page.HandleError(Exception e)
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
       at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
       at System.Web.UI.Page.ProcessRequest()
       at System.Web.UI.Page.ProcessRequest(HttpContext context)
       at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


    [2012-01-09 10:40:06.659] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:   32 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Error | ExceptionConverter.ConvertMessageAndErrorCode
    >System.Web.HttpUnhandledException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #F71D1C4A: System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> Microsoft.Crm.CrmArgumentNullException: name ---> System.ArgumentNullException: Value cannot be null.
    >Parameter name: name
    >   --- End of inner exception stack trace ---
    >   at Microsoft.Crm.ReportObjectModel.ReportServerOrganizationContext.GetItemPath(String name, Boolean isSharedReport)
    >   at Microsoft.Crm.Web.Reporting.RemoteSrsReportViewer.LoadReportAndSetParameters()
    >   at Microsoft.Crm.Application.Controls.AppUIPage.OnPreRender(EventArgs e)
    >   at System.Web.UI.Control.PreRenderRecursiveInternal()
    >   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    >   at System.Web.UI.Page.HandleError(Exception e)
    >   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    >   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    >   at System.Web.UI.Page.ProcessRequest()
    >   at System.Web.UI.Page.ProcessRequest(HttpContext context)
    >   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    >   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

    Any ideas what may cause this problem ? Like I said before - this report works perfecly in DEV environment and problems happens during deploying it into another env.

    Any help will be apprieciated.

    Best regards.

    Monday, January 09, 2012 10:28 AM

Answers

  • I had a similar error on my 2011 front end server when running reports.

     

    When the report was requested, the failure was logged here on the SSRS Server logs: C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\LogFiles

     

    The event that showed for the time I ran the report was:

    ReportID for failed report:

    IP:Port which did not respond

     

    library!ReportServer_0-50!7188!10/25/2012-13:14:25:: i INFO: RenderForNewSession('/MSCRM_MSCRM/CustomReports/{15A60C17-E3C6-E111-8BDA-00155D289978}')

    runningjobs!ReportServer_0-50!754c!10/25/2012-13:15:00:: i INFO: Adding: 1 running jobs to the database

    processing!ReportServer_0-50!7188!10/25/2012-13:15:08:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'DSMain'., ;

    Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'DSMain'. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException:

    Microsoft.Crm.CrmException: An unexpected error occurred.

    System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://buscrm/CrmSandboxSdkListener-w3wp. The connection attempt lasted for a time span of 00:00:21.0028692. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:808.

    System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:808 ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: An unexpected error occurred. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: Could not connect to net.tcp://crm/CrmSandboxSdkListener-w3wp. The connection attempt lasted for a time span of 00:00:21.0028692. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:808.  ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:808

     

    On CRM, running this command in PowerShell showed that the server had a service listening on :808 for all IPs

    PS C:\Users\me> netstat -na | select-string :808

     

    TCP    0.0.0.0:808            0.0.0.0:0              LISTENING

    TCP    x.x.x.x:51282     x.x.x.x.62:808       SYN_SENT

    TCP    [::]:808               [::]:0                 LISTENING

     

    On CRM, in the Firewall.cpl > Advanced Configuration, sorting by Local Port, showed a disabled rule for port :808.  Enabling the rule solved the error.  

     

    Matthew

    Thursday, October 25, 2012 8:08 PM

All replies

  • Hi,

    According to the trace, your report contains parameter called "name" and while generating report it set to null but while executing query it not to be null that's the reason I understand after go through the trace please check the parameters and how set values while generating report then you can identify the error.

    Thanks.

    Monday, January 09, 2012 11:29 AM
  • Contrary to the previous post, it looks like the problem is that RS or CRM is not recognising the report's name, rather than the report having a parameter called 'name'.

    I suggest you start by checking the ReportServer log file (which would typically be in path like C:\Program Files\Microsoft SQL Server\MSRS10.SQL2008\Reporting Services\LogFiles ) to see if that gives you some more information. Otherwise, a few things to consider are:

    1. Does the report contain one or more sub-reports, and if so, have these been deployed and configured (via the Parent Report attribute) correctly in your test environment ?
    2. Has the report been deployed in the same way in each environment - ie. deployed via the CRM interface (or not), with the same properties ?
    3. Any other environmental differences - e.g. do they either both have, or not have, the CRM RS extensions installed ?

    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    Monday, January 09, 2012 1:30 PM
    Moderator
  • Have you changed the connection string in Dataset to point to the test server?
    Regards Faisal
    Monday, January 09, 2012 1:33 PM
  • Thanx for all the responses.

    It has occured that deleting and publishing report one more time - solve the problem.

    Best regards,

    Piotr

    Thursday, January 12, 2012 7:44 AM
  • I had a similar error on my 2011 front end server when running reports.

     

    When the report was requested, the failure was logged here on the SSRS Server logs: C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\LogFiles

     

    The event that showed for the time I ran the report was:

    ReportID for failed report:

    IP:Port which did not respond

     

    library!ReportServer_0-50!7188!10/25/2012-13:14:25:: i INFO: RenderForNewSession('/MSCRM_MSCRM/CustomReports/{15A60C17-E3C6-E111-8BDA-00155D289978}')

    runningjobs!ReportServer_0-50!754c!10/25/2012-13:15:00:: i INFO: Adding: 1 running jobs to the database

    processing!ReportServer_0-50!7188!10/25/2012-13:15:08:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'DSMain'., ;

    Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'DSMain'. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException:

    Microsoft.Crm.CrmException: An unexpected error occurred.

    System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://buscrm/CrmSandboxSdkListener-w3wp. The connection attempt lasted for a time span of 00:00:21.0028692. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:808.

    System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:808 ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: An unexpected error occurred. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: Could not connect to net.tcp://crm/CrmSandboxSdkListener-w3wp. The connection attempt lasted for a time span of 00:00:21.0028692. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:808.  ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:808

     

    On CRM, running this command in PowerShell showed that the server had a service listening on :808 for all IPs

    PS C:\Users\me> netstat -na | select-string :808

     

    TCP    0.0.0.0:808            0.0.0.0:0              LISTENING

    TCP    x.x.x.x:51282     x.x.x.x.62:808       SYN_SENT

    TCP    [::]:808               [::]:0                 LISTENING

     

    On CRM, in the Firewall.cpl > Advanced Configuration, sorting by Local Port, showed a disabled rule for port :808.  Enabling the rule solved the error.  

     

    Matthew

    Thursday, October 25, 2012 8:08 PM