crxf_pdf.dll appears to cause IIS to crash

[Former Member]

When exporting crystal reports to pdf from a web based application using Crystal 2008, the crxf_pdf.dll causes IIS to crash. This happens about once every five times with a particular large report. But it has happened with small reports on occassion as well. We have seen this on several windows 2008 server boxes (IIS7)hosting our website which allows this type of export . Below is the error...

Inw3wp__PID__5036__Date__01_27_2010__Time_12_18_13PM__735__Second_Chance_Exception_C0000005.dmp the assembly instruction at crxf_pdf+1a483 in C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\crxf_pdf.dll from Business Objects has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000000 on thread 99

Please follow up with the vendor Business Objects for C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\crxf_pdf.dll

Any thoughts, ideas or solutions appreciated!

Thanks

[Former Member · Accepted solution]

hi, David;

First, do you have our latest service pack / fix pack installed on this system? We are currently at fix pack 2.4.

Second, as it happens after 4 or 5 runs, are you cleaning up your report document object after each run / export?

Regards,

Jonathan

Follow us on Twitter u2013 http://twitter.com/SAPCRNetSup

[Former Member]

While trying to reproduce the original issue using the 2.4 fix pack merge modules I've noticed that exporting to pdf from the website seems to consume the worker process to the point other web users get a very very delayed response. So if your report takes 60 seconds to generate, other users almost appear locked up when they try to access the website or try to do a submit.

[Former Member]

This looks like a non issue. Here is what I did to reproduce the issue: 1)I setup a separate website on my server that contained one page that simply exported a pdf report with a press of a button. I brought up two browsers, logged in anonymously to that site. I started the the exports at roughly the same time. The report I created listed several fields out of the db table and would run for about one minute. For the setup described above the reports both finished processing at just about the same time. I tried the same using windows authentication and had the same results. 2) I moved the single web page to my main website, then opened two browsers to the site logged in as my windows user. While my report was exporting in one browser, I could not get to the database with the other browser. Once the report finished, the second browser came up with data immediately.3) I changed the test web page by removing the report export code and adding code to bring back the same records into a dataset. I was able to duplicate the problem this way as well. This took Crystal out of the picture. 4) I created a new windows user on my server and set it up in the development database. I opened one browser with my login and a second browser with the new login. While loading the dataset with the first browser, I did not have any problem accessing the database table with the browser connected as the new user. 5) Finally, I decided to try using the second browser from a remote location. This time I logged both browsers in as my user, but one browser was on a different client. While loading the dataset with one browser the other browser did not have a problem accessing the Account Detail. 6) It appears that when working on a single box with mulitiple browsers logged in as the same user, IIS(?) limits the amount of access as if there was only one instance. So far, I have found no documentation for this, but will include it when I do.

As it stands this does not appear to be a critical issue since it only limits a single user on a single box and does not limit multiple users logged in with Anonymous (for example) from many different boxes.

[Former Member]

Jonathan, Thanks for the reply. To answer you second question first, I am doing a close and then a dispose on the report document each time I'm done with the document object.

As for the first question, we did recently get a new version of the merge modules to our clients, but not in time for the latest 2.4 release. I will get this on one of our servers and see if the problem persists. I will let you know what happens. Thanks for the suggestion.