This blog is a continuation of the blog "Crystal Reports XI Release 2 support of Windows Server 2008 and Windows 7". E.g.; read that blog and note all warnings contained therein before continuing to read this blog. That blog has no solution(s) specified as there were none known at the time the blog was written. Several solutions have been described in the forum thread "RDC and Windows Server 7" since. In this blog, I condense possible solutions to the issue along with appropriate warnings and disclaimers..
**Warnings**
Please note that the solutions provided are only reported solutions. Neither I, nor anyone else in Support has verified these solutions and given that RDC in classic ASP applications on WIN 7 and WIN 2008 Operating Systems are not supported, are we not likely to verify these solutions in the future. Should any future issues arise on these Operating Systems, there is no escalation path to QA for a fix.
Also note that this blog only applies to Crystal Reports XI release 2, patched up to Service Pack 6 and using the SP 6 RDC MSM runtime files. If you are using CR XI release 1, upgrade to CR XI release 2 which can be downloaded from here. Note; it is recommended that only CR XI r2 exists on the development system. Finally, only Crystal reports XI r2 SP6, Crystal Reports Basic for Visual Studio 2008 (10.5) and Crystal Reports 2008 (12.2.x) are supported on Win 7 and Win 2008 Server. For more details see the wiki "Crystal Reports v. 9.1 to 12.x VS .NET Runtime Distribution & Supported Operating Systems".
Disclaimers:
The forum, where queries regarding the RDC should be posted, contain many complaints as concerns support of the RDC on Win 7 and Win 2008 Server. As a bit of a defense, I'd like to point out that Crystal Reports XI r2 released in 2005 (see the blog "Short history and resources for Crystal Reports Software Developer Kits (SDK))" - almost four years before WIN 7 and Win 2008 Server. Forward compatibility to future Operating Systems is always tricky and not quaranteed. Furthermore, it has been well documented that the RDC is in it's sunset lifecycle phase. See my blog "Report Designer Component - Past, Present & Future" and the "Crystal Reports RDC Statement of Direction", published March 2, 2006.
Reported Issues on Win 2008 Server
1) The crystal report viewer just shows the viewer, but without any report result
2) Some Crystal Reports dlls can not be registered. Specifically reported dlls are Reportparameterdialog.dll, crviewer.dll.
3) Other dlls reports as not being able to register; gdiplus.dll and the ups10.dll, sviewhlp.dll, swebrs.dll. These are not Crystal Reports dlls and are not distributed by any Crystal Reports msm or msi packages. Thus this would indicate other, non Crystal Reports issues.
4) HTTP 401.2 - Unauthorized: Logon failed due to server configuration reported in Internet Information Services logs.
Reported solutions:
1) In the RDCrptserver115.asp (for 11.5) and rptserver.asp (for 8.5) files, change the 1st occurence of the line:
response.addheader "CONTENT-LENGTH", lenb(temp)
to
response.addheader "CONTENT-LENGTH", lenb(temp + 0)
For more details and possible ramifications of the above modification see the forum thread "Record Limit Issue II"
2) Export the report to pdf directly, then add a pdf viewer to your program as documented in the post "Demo: How to use Adobe Acrobat Reader 7.0 Viewer Control (AcroPDF.dll"
3) Export the reports using the HTML format, and then we view the reports with the CHTMLView class.
4) Manually install the ActiveXviewer;
- a) Find the ActiveXviewer.cab file that is part of the Crystal XI R2 Developer install (c:program files usiness objectscommon3.5crystalreportviewers115ActiveXControls)
- Transfer the .cab file to the local machine and open it. It is simply a compressed archive.
- Copy the enclosed dlls to the ...3.5crystalreportviewers115ActiveXControls folder on the local machine.
- Manually register each dll (regsvr32 .....)
Other troubleshooting approaches:
See the article "Troubleshooting the ActiveX Viewer"
Use the following utilities.
Charles
Process Monitor
Depends20
Fiddler
DebugDiag
Final word:
One more time, please note that the solutions given in this blog are reported solutions not tested by Support. If the solutions given do not solve your deployment to WIN 2008 Server, create a new forum thread in the forum. Any answers given will be on "best effort" bases. If you find an alternative solution, please do post this to the forum also.
