Hi All, I have a ASP.NET based application which uses SSRS reports to generate reports. I can generate reports and export to excel. However If I generate the report and then wait for soemtime say 5 minutes and then click on Export>Excel option in SSRS I get the following error: The remote name could not be resolved: 'dummy' Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Net.WebException: The remote name could not be resolved: 'dummy' Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [WebException: The remote name could not be resolved: 'dummy'] Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.GetSecureMethods() +206 Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.IsSecureMethod(String methodname) +47 Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.GetExecutionInfo() +105 Microsoft.Reporting.WebForms.ServerReport.GetExecutionInfo() +269 Microsoft.Reporting.WebForms.ServerReport.SetExecutionId(String executionId, Boolean fullReportLoad) +120 Microsoft.Reporting.WebForms.ServerReport.LoadFromUrlQuery(NameValueCollection requestParameters, Boolean fullReportLoad) +101 Microsoft.Reporting.WebForms.ReportDataOperation..ctor() +366 Microsoft.Reporting.WebForms.HttpHandler.GetHandler(String operationType) +242 Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +56 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +181 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75 It looks like a timeout issue and I have set the default time more than 2.5 hours but it does not resolve the issue. Of course because I do not wait 2.5 hours. I just wait 5 minutes and I end up getting the errors. Can anyone please help.

Hello, Quick question for you... Does the report renders perfectly without doing any kind of Exports? Does the report renders more than 65K record count? If yes export to 65K will give an error message, please check below thread for more details:- http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/d2b6c9d6-17c4-46aa-8b57-e1f37ff7413d http://msdn.microsoft.com/en-us/library/ms156418.aspx Thanks KumarKG, MCTS

Hi, The report generates fine and with everything. I don't have 65K rows of data and only a few lines. I don't think this is an excel issue as it happens in Excel 2003 and 2007 both.

Hi Again, How are you exporting? Their is no way to export to Excel 2007. By default export will Excel 97-2003 format only. Thanks KumarKG, MCTS

Hi, I just click export on the SQL Server reports. I am not sure it is a problem with the exporting to a particular format. It is more like, you generate the report click export and everything is fine. But if you generate the report and wait say 2-3 minutes and then click export then you can see the browser window going blank and it tries to export the report but could not and ends up throwing the error. To me after 2-3 minutes the report probably looses the URL of the report that is why 'dummy' comes up. I am not sure where 'dummy' is coming from. Does anyone know when and why the word or url 'dummy' turns up in .NET error log? Thanks.

Hi SQL_Server, Thanks for your question and _Kumar’s replies. Based on my research and past experiences, this issue may be caused by the session time value of the report. Please try to change the session timeout value by below command, rs -i sessionTimeout.rss -s http://localhost/reportserver -v timeout="6000" The more information, please see this blog:http://blogs.msdn.com/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx. Hope it helps you. If you issue still exists, please feel free let me know. Thanks, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.

Hi SQL_Server, Thanks for your question and _Kumar’s replies. Based on my research and past experiences, this issue may be caused by the session time value of the report, please try to change the session timeout value. For the detail information and detail steps, please reference this blog: http://blogs.msdn.com/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx. In order to run below command, please create the sessionTimeout.rss file in advance. Locate to the root folder of the current account, for example: C:\Users\Username, create one text document with the script had mentioned in the article, then rename it with sessionTimeout.rss. rs -i sessionTimeout.rss -s http://localhost/reportserver -v timeout="6000" Hope it helps you. If you issue still exists, please feel free let me know. Thanks, Sharp Wang

Hi Sharp Wang, Thanks for your suggestion. what is sessionTimeout.rss as I get an error : could not find file 'C:\Users\UserA\sessionTimeOut.rss' I am running it from command prompt: "'C:\Users\UserA\rs -i sessionTimeout.rss -s http://localhost/reportserver_sql2008 -v timeout="6000"" when I try to run your command. I can't find the file sessiontimout.rss anywhere in RS installtion directory. Can you please tell me where is this file Thanks.

Hi Sharp Wang, I have tried that command by using a script found on the given link. It does not resolve the issue. In fact I have already tried that by changing the default settings on the SSRS site settings. I think this error is pointing to us that the report server name and url that we are providing is not being resolved. But interesting thing is our application runs the report by using SSRS and uses the URL stored on our application. It seems like after 2 or 3 minutes when I click export, application tries to connect to the URL and fails. Normally we provide the SSRS server address on the application using the server name such as http://myserver/ReportServer_SQL but I have also tried using the IP address to see if it can't resolve the computer name. But unfortunately the application still can't find the url using the ip address. Does anyone have any more idea about this error? Thanks.

Hi SQL_Server, Thanks for your replies. I should apology for didn’t explain the detail steps accurately. Since this solution hasn’t resolved the issue, let’s continue spending much time to research it, if I find the better solution, I will post it here. Thanks, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.

Thanks

Hi SQL_Server, Based on my research, I have two directions would like to share with you. One, Timeout. 1. The Time out in Report Manager. You had set it. It helps us to control the maximum time of report execution, if timeout, though the report haven’t been represented, it also stop executing. 2. The Time out in Data Source. Please check it. It helps us to control the maximum time of creating one connection to the Data Source server, if timeout, though the connection haven’t been created, it will stop. 3. The Time out time in Data Set. Please check it. It helps us to control the maximum time of querying data from the Data Source server, if timeout, though the querying haven’t been finished, it will stop executing. 4. The Time out in application to connect to the Report Server. You had set it by previous script. It helps us to control the maximum time of keeping ping connection from application to Report Server, if timeout, it stops the ping connection. 5. The Time out in application to keep the application available. Please check it. You can double-click the Web.config file in your application project then check it. For more information, please see: HttpSessionState.Timeout Property. Two, Available Memory and resources for Report Server Applications. 1. Available Memory. As we know, when the report being exported in one excel document, it will spend much memory source. If the available memory size is too low, after few times, the Report Server will redistribute these resources to other reports, so please increase the size of the Available Memory. Configuring Available Memory for Report Server Applications. 2. System resources. Although the Available Memory is big enough, if the system resources is limited, after few times, system will recycle the resource from the report then redistributing the resource to other applications. Please try to free sources by disabling the unimportant startup items, then rebooting the machine. Please try to test previous suggestion in your project. If the issue still exists, please feel free let me know. Thanks, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.