Error with Collapse and Expand Functions in RS 2000
- Several of our reports on a client site have stopped working correctly when you click on the toggle in order to view collapsed data.
This also coincided with the Printing error introduced in the MS09-062 patch release, is there a connection.
The error we get is
'An Unexpected Error Occured in report Processing. (rsInternalError), Object Type cannot be converted to target type'
When looking at what was released (kb970899), I notice that several of the rendering engines have been updated as well.
Can anyone confirm if there is a known issues, and a fix that we can implement
Jason
Answers
- A quick update,
We tested the MS09-062 patch on a server that was running SQL Server RS 2000 and SP2, and then tested the report, we recieved the same error as the client reported.
On rolling back the main RS libraries that are detailed in the article http://support.microsoft.com/default.aspx/kb/970899/ on affected server, the report start to work as normal.
This in my mind proves that there is an issue with the MS09-062 patch and RS 2000, and the toggle state of various reports.
Regards,
Jason- Marked As Answer byJNHL Monday, November 09, 2009 5:03 PM
All Replies
Hi Jason,
MS09-062 affected Reporting Services by RSClientPrint ActiveX control. This ActiveX control distributes a copy of gdiplus.dll containing the affected code. Customers are only impacted when the RSClientPrint ActiveX control is installed on Microsoft Windows 2000 operating systems. If the RSClientPrint ActiveX control is installed on any other operating system, the system version of GDI+ will be used and the corresponding operating system update will protect them.
This issue only occurs when you installed MS09-062? How about recreate a report?
Yao Jie Tang -Microsoft Online Community- Hi Yao,
Thanks for the response, the reason we suspect it was the MS09-062 patch that caused this, is becuase the reports were working perfectly fine prior to this, and it wasnt until after the application of the patch, when the client reported the known Printing Issue (which we fixed) and the Toggle issue at the same time, and as these reports are being run daily (weekly at worst) it is unlikely that the client would not have noticed the issue with the toggle before now.
Unfortunately it is not feasible to recreate the report, as it is quite complex (approx 5 days of work), and the client is unwilling to pay for us to do this work.
We are going to try and redeploy one the affected report, just in case it has become corrupted, which i think is highly unlikley as it wouldnt render if was corrupt.
Jason.
Jason - A quick update,
We tested the MS09-062 patch on a server that was running SQL Server RS 2000 and SP2, and then tested the report, we recieved the same error as the client reported.
On rolling back the main RS libraries that are detailed in the article http://support.microsoft.com/default.aspx/kb/970899/ on affected server, the report start to work as normal.
This in my mind proves that there is an issue with the MS09-062 patch and RS 2000, and the toggle state of various reports.
Regards,
Jason- Marked As Answer byJNHL Monday, November 09, 2009 5:03 PM
- JNHL:We have the exact same problem after this update. We dont mind going back but one problem the KB970899 is not shown in teh add remove, you stated that you rolled back the libraries from the that KB which is the update how was that achieved? Thanks
- Hi BSI admin,
Glad to here we're not the only ones that ave had this.
Having spoken with the tech guys here, these are the steps that we went through, its a little convoluted but should work,
1. Download (but do not install) the previous security update from the following location:
2. Move the existing files that were installed by the latest security update (listed in the following Knowledge Base article) to a backup folder:
http://support.microsoft.com/?kbid=970899
3. Install the previous security update which was downloaded at the first step.
4. Verify that the version of Reporting Services is 8.00.1062.00 (previously it would have been 8.00.1067.00) by navigating to http://warehouse/reportserver and scrolling to the bottom of the page. Assuming it is, check that the “expand issue” is resolved
I hope this resolves your issue,
Jason - Thanks Jason, funny you say that I did those steps yesterday but never moved the library files before the install and it stayed to the current version, but makes since to move those files out then install the previous path. Thanks I will keep you updated on that.
- Jason, took those instructions to the "T" and still showing version 1067. I look at the new files it installs and they are showing version of 1067 not 1062, driving me crazy, wonder if microsoft somehow updated that old patch with the new version of files?
