Posted 4 August 2017, 2:59 pm EST
I am still having issues with reports using our custom .ocx with AR 2.0 on Windows Server 2003 SP1.
Previous post: http://www.datadynamics.com/forums/92084/ShowPost.aspx (Back history.)
I have attached examples of the reports on Windows Server 2003 with (reports do not work) and without SP1 (reports work).
We access this report library .dll via an Intranet web application. The request to generate the report is handled by a .dll that is deployed in COM+. This .dll does not have any AR reports in it. The request is handed from this .dll to the report libaray .dll that is not in COM+. The report library .dll generates the report and saves it to a file. The file path and name is returned to the calling .dll and then handed off to be read into the viewer embedded in the browser.
The report file in both cases is generated and displayed to the viewer in the browser. The report that "does not work" appears to be incomplete. The graphics in the .ocx do not render completely. (See attached report examples.)
This architecture has been working on our current production environment of Windows Server 2000 and development environment of Windows Server 2003. We are attempting to migrate to a new production server loaded with Windows Server 2003 SP1 and cannot seem to resolve this issue.
I have tested the same "code path" that the web uses via a VB .exe to the same result. If the component that is deployed in COM+ is removed from COM+ and just registered, the VB .exe is successful but then the web application cannot generate the report.
2006/10/AR 2.0 W2k3 SP1 Issues.zip