Article ID: 912705 - Last Review: July 26, 2006 - Revision: 2.6 FIX: Error message when you try to drill through a report in SQL Server 2005 Reporting Services: "An internal error occurred on the report server. See the error log for more details"
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. On This PageSUMMARYThis article describes the following about this hotfix
release:
SYMPTOMSIn SQL Server 2005 Reporting Services, when you try to drill
through a report that is upgraded from Microsoft SQL Server 2000 Reporting Services, you
receive the following error message: An internal
error occurred on the report server. See the error log for more
details Date-Time::
i INFO: Call to RenderFirst( '/Samplereport/Report1' )
aspnet_wp!library!1!Date-Time:: Using folder Drive:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\RSTempFiles for temporary files. aspnet_wp!webserver!1!Date-Time:: i INFO: Processed report. Report='/Samplereport/Report1', Stream='' aspnet_wp!library!1!Date-Time:: i INFO: Call to RenderNext( '/SampleReport/Report1' ) aspnet_wp!processing!1!Date-Time:: a ASSERT: Assertion failed! RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:913089
(http://support.microsoft.com/kb/913089/
)
How to obtain the latest service pack for SQL Server 2005
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesTo apply this hotfix, you must have SQL Server 2005 installed on the computer.Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry after you apply this hotfix.Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. SQL Server 2005 32-bit versionsCollapse this table
SQL Server 2005 IA-64 versionsCollapse this table
SQL Server 2005 x64 versionsCollapse this table
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 1. MORE INFORMATION
For more information about the naming schema for Microsoft SQL
Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft
SQL Server software update packages
For more information about software update
terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard
terminology that is used to describe Microsoft software updates
| Article Translations
|
Back to the top
