RS 2005: Excessively Long String error when printing

I have a VB.NET 2003 WinForms application that contains a browser control to render reports within. I have a SQL Server 2005 Reporting Services instance - and through the RS site, the reports come up great, and print just fine. However, when pulling in the reports through the WinForms application, when trying to print - I receive an error. A message box pops up that says "An error occured trying to get the current window." The next message is:

Line: 26; Char:4; Error: Marshaler restriction: Excessively long string. Code: 0; URL: http://svr-sqlreport1/ReportServer$QA/Reserved.ReportViewerWebControl.axd?

Jon,

We are also experiencing exactly your issue described above. I read on one forum that embedded web forms using URL access to get reports is not a supported feature of RS2005 which is absolutely dumbfounding. We have invested heavily in embedding the web form in a Visual Studio application that can apparently no longer support this for 2005.

I've been told by MS that we need to use there new controls, but your assuming that our clients are willing and able to deploy the .net framework 2.0 to the desktop and that requires XP SP2 - which in the case of one of our clients is also not on the desktop.

Is there any work around to this issue?

|||We've yet to find a work around...sorry. At this point, we've decided to spend some time testing and estimating effort required to upgrade to VS.NET 2005 (.NET fx 2.0). Provided that doesn't take too long, we'll upgrade. I'm really disappointed to hear that it is not supported and MSFT's only solution is to use new controls.|||

This is a known issue and will be fixed in SP1 for RS 2005. If you cannot wait for SP1, you can contact Microsoft PSS. There is a fix in development to address this issue and should be available soon.

The workaround for now is to use the ReportViewer controls in a 2.0 .Net application instead of the Web control.

|||

Thanks Brad. Do you have a bug # / code that I can reference as I deal with support people on the Microsoft side? Much appreciated.

-Dan

|||

Sure

SQL Hotfix 319. This is the code I know it by, but PSS should be able to figure it out with a little bit of looking.

|||

Thanks so much Brad - really appreciate the help.

Jon

|||

Brad -

In speaking with product support, they are unable to provide the hotfix unless I am able to provide the actual article number associated with the hotfix - they are saying that SQL Hotfix 319 is not enough for them to go by. Do you happen to have the article number?

Thanks,

Jon

|||

I've also spoken to my contacts at MS and they are unable to help without having the Knowledge base article associatied with this issue. Problem is, i've looked on the KB and can't find a one. Brad, any assistance you can provide would be helpful - in a time crunch with our client to get a resolution on this issue.

Thanks
-Dan

|||

Dan - not sure if you've done this yet...but SQL Server 2005 Service Pack 1 appears to have fixed this issue in our environment.

Jon

|||It does indeed! Thanks for your note Jon!