Hi all,I have created a new custom report and published to report server 2005.Running the source query for the report in management studio takes about 5 Min. Results as expected.Preview in Visual Studio works as well.Running the report in browsers ends after 15 Min. with the following error msg.An error has occurred during report processing.Query execution failed for data set 'RptDWHP'.A severe error occurred on the current command. The results, if any, should be discarded. Operation cancelled by user. How to track down the error ??TIAacki4711

Checking the eventlog of report server shows error below whitch made me think of a IE session timout error.Increasing report server session timeout does not solve the problem. After 30 Min. Reporting is canceld.(See: http://blogs.msdn.com/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx)But I'm not sure if after applying the script there is somghing else needs to be done)(Do I have to restart report server service) ??Event Type: WarningEvent Source: ASP.NET 2.0.50727.0Event Category: Web Event Event ID: 1309Date: 14.10.2009Time: 11:49:18User: N/AComputer: xxxDescription:Event code: 3005 Event message: An unhandled exception has occurred. Event time: 14.10.2009 11:49:18 Event time (UTC): 14.10.2009 09:49:18 Event ID: 31c0341fa79a41e6b51f441bc422ad04 Event sequence: 148 Event occurrence: 3 Event detail code: 0 Application information: Application domain: /LM/W3SVC/1/root/Reports-2-128999154819914107 Trust level: RosettaMgr Application Virtual Path: /Reports Application Path: D:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportManager\ Machine name: xxx Process information: Process ID: 3576 Process name: w3wp.exe Account name: PFIN\s-momdb Exception information: Exception type: ReportServerException Exception message: Execution 'yefqtg55nic0cl55iiianiz3' cannot be found (rsExecutionNotFound) Request information: Request URL: http://xxx/Reports/Reserved.ReportViewerWebControl.axd?ReportSession=yefqtg55nic0cl55iiianiz3&ControlID=4b6aaf

Ok, folks, I just don't get it.I thought setting "SET NOCOUNT ON" solved the problem because I had it up and running... until I changed again some minor look&feel things on the report and republished it again. Now I'm running into the same problem again, report hangs for half a hour and times out then...WTF is going wrong here..?Any help is highly appreciated!TIAacki

Hi Acki,That is a known issue.In Microsoft SQL Server 2005 or in Microsoft SQL Server 2008, an access violation occurs when you run a query, and then you receive the following error message: Msg 0, Level 11, State 0, Line 0 A severe error occurred on the current command. The results, if any, should be discarded. Msg 0, Level 20, State 0, Line 0 A severe error occurred on the current command. The results, if any, should be discarded. Additionally, a minidump file is generated in the SQL Server 2005 log folder. The following error messages are logged in the SQL Server 2005 error log: Date Time SPID SqlDumpExceptionHandler: Process SPID generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. Date Time SPID * ******************************************************************************* Date Time SPID * Date Time SPID * BEGIN STACK DUMP: Date Time SPID * Date Time spid SPID Date Time SPID * Date Time SPID * Date Time SPID * Exception Address = 01550D56 Module(sqlservr+00550D56) Date Time SPID * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION Date Time SPID * Access Violation occurred reading address 00000007 If you enable trace flag 9259, the query runs successfully. RESOLUTION: SQL Server 2005 Service Pack 3 Important You must install this cumulative update package if your computer is running SQL Server 2005 Service Pack 3. The fix for this issue was first released in Cumulative Update 4 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 970279 Cumulative update package 4 for SQL Server 2005 Service Pack 3 The release version of SQL Server 2008 Important You must install this cumulative update package if your computer is running the release version of SQL Server 2008. The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base: 971490 Cumulative update package 6 for SQL Server 2008 The latest cumulate update is Cumulative Update 5 fro SQL Server 2005 Service Pack 3. For more information, please see:Cumulative Update #5 for SQL Server 2005 Service Pack 3 Please feel free to ask, if you have any more qeustions.Thanks,Jin Chen Jin Chen - MSFT

Jin, Installing cummulative update 5 for sp3 on sql 2005 does not solved the problem (only client components have been updated because server was already on 4053).

Hi Acki,Please update the server components too.To apply cumulative update 5 form SQL Server 2005 SP3, we need to apply SP3 before. Thanks,Jin ChenJin Chen - MSFT

The serer components are already up to date 9.00.4053 !!! (Means SQL 2005, SP3, Level 4053)Cummulative update does not install server components because the are up to date !!!

9.00.4053 means SQL Server 2005 SP3.I suggested you updating to Cumulative update 5 for SQL Server 2005 SP3.The version for CU5 for SQL Server 2005 SP3 is 9.00.4230. The issue is solve in CU4 for SQL Server 2005 SP3(9.00.4226)To get the hotfix, please follow:1.Open the http://support.microsoft.com/kb/972511/en-us2.Click "View and request hotfix downloads" to download the hotfixs.Jin Chen - MSFT

As I mentioned in earlyer post, the cummulative update 5 does NOT update server components if server components are on 4053 level already !!!-> The product instance MSSQLSERVER has had update 4053 installed. You do not need to install this update. An update equal to or greater than 4261 should be downloaded.BTW, which part needs to be updated Database Engine (where the data for the report resists) or Report Server (with DB's for report service) or both ?(we have DB Engine and Report Server on different servers)BTW2 Setting trace flag 9259 on report server does not change anything...Cheersacki

Hi, I too am getting this error. I am using ssrs 2005. I recently migrated the databases to 2008 but ssrs still is ssrs2005. Just moved the ReportServer database and the databases used by the reports to SQL 2008. Earlier they were on sql 2000. I started getting this error since the upgrade. Sometimes even thought the report is run ok and in the executionlog tbl the status shows as rssuccess, in the log I see this error showing up. Is this a problem with sql reporting services or an issue with the sql 2008 databases? Want to understand how this cumulative update fix this issue? Appreciate your response. Thanks.

Actually yes. Version 9.00.4053 is a re-release of SP3 including a securty fix that was released on 13 october 2009. Every CU before CU 6 was released at a data before 13 October 2009 and it seems it looks at the date and not numbers when determing which hotfix to install or not. So, since CU 6 was released on 19 october 2009 and higher CUs on a date later then that thoughs will work. Br. Raoul