ActiveReports PDF Export DLL: Internal Error. Out of memory or corrupt pages collection.

06-22-2009, 1:11 PM

Hi one again. I compiled a dll from VB using AR2 and use it from a web page using IIS. Every report I made works fine in my computer. I installed everything for the client in a Virtual Machine running with Microsoft Windows Server 2000.

I tested in the client machine and when I try to export any report to pdf (I have three different RPX formats I use) all of them return the error:

"PDF Export Object (0x800A1B5A)"

"ActiveReports PDF Export DLL: Internal Error. Out of memory or corrupt pages collection."

I searched in other forums and in half of them the problem is the ammount of pages and WORD attachment, etc. In my case it doesn´t apply because the report is plain text and no more than 2 o 3 pages long.

The other half claim that the problema is with IIS security permission. The IIS user created for the site, IWAN and IUSR have all permissions and application security was set to low. The problem persists.

I need help with it, I think that the problem may still be the permissions with the dll any other AR2 component.

Thank you in advance for your help

 

PS: I tried the web based examples from AR2 using NorthWind and they all work fine 

Re: ActiveReports PDF Export DLL: Internal Error. Out of memory or corrupt pages collection.

06-23-2009, 10:13 AM
Hello,

In order to analyze the issue better, please check if you have pages in the pages collection before exporting them to PDF. Also, you have mentioned that our samples work fine in your test. Are you using any third party component in your report? Would it be possible for you to send us a small sample that replicates the issue consistently? Also, please let us know the current build of ActiveReports that you are using.

Regards,
Prantik

Re: ActiveReports PDF Export DLL: Internal Error. Out of memory or corrupt pages collection.

06-24-2009, 7:30 AM

Problem solved... I uninstalled everything asociated to the web application (dll and AR2), stopped IIS and COM+. Reinstalled AR2, recompiled dlls, registered them, start again IIS and COM+ and the site worked fine for the client.

I think the problem was something with security and permissions. But not sure where.

Thanks for your help.