Hard to diagnose, but seems like it could be a "Network Communications Error" between the the Crystal "Reports" Server and their "Datasource"...if I'm understanding your setup correctly....
M
Main Topics
Browse All TopicsI have a Windows Server 2003 r2 sp2, clean install, with Crystal Reports 9.2 sp7. This server is dedicated only to serving reports through standard asp. I use both html and activex viewers.
It works fine sometimes and sometimes I get the error message:
The oPageEngine object was not created or is not in scope. Please check that the Viewer is referencing rptserver.asp in the correct virtual directory. It is also possible that the ReadRecords method failed. Ensure that you are logging on to the datasource correctly and have provided values for Parameter Fields.
It is pretty random. I get the error for like 10 to 50% of the reports I request. If I request again, I get it right.
Checking the event viewer I see several of these:
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1009
Date: 9/24/2009
Time: 7:41:54 PM
User: N/A
Computer:
Description:
A process serving application pool 'AppPool #1' terminated unexpectedly. The process id was '3220'. The process exit code was '0x80'.
Event Type: Information
Event Source: W3SVC
Event Category: None
Event ID: 1074
Date: 9/24/2009
Time: 7:41:22 PM
User: N/A
Computer:
Description:
A worker process with process id of '5508' serving application pool 'AppPool #1' has requested a recycle because the worker process reached its allowed processing time limit.
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 9/24/2009
Time: 7:23:16 PM
User: N/A
Computer:
Description:
Application popup: w3wp.exe - Application Error : The instruction at "0x0385e38a" referenced memory at "0x0385e38a". The memory could not be "read".
Click on OK to terminate the program
And this last one pops up a dialog on the server's screen. I googled these errors but none of the solutions presented worked. It has been suggested that these errors began after applying sp1 on Windows.
Any ideas?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Maybe. But a communications error should not cause a "segmentation fault" and cause a process to crash.
For some reason I stopped getting the 0x80 errors. Don't know what exactly what I did. But I still get the others.
The first error seems to be happening because IIS loses the session information. IIS doesn't seem to keep track of the session objects very efficiently.
Despite the random crashes, the system is usable. If things get worse, I'm gonna try installing server 2003 sp0 or switching to Apache+php.
I solved the main problem. IIS was indeed losing session information. I googled about it and found out that, for standard ASP pages, sessions are lost if a worker process recycles. Also, if you have many worker processes, session objects are only stored in one of them. You request a page of the report and get process #1. If your next request goes to process #2, you get an error, since all the session data are stored in process #1.
I set up only one application pool with only one worker process. I also disabled all automatic recycles. This seems to have solved the problem. I also did not get any errors on event log when I was testing, but I have to check again tomorrow when the server is at full load.
Business Accounts
Answer for Membership
by: acerolaPosted on 2009-09-24 at 16:15:53ID: 25418883
BTW, I am looking for a solution that does not involve installing a different OS version. I have to make this one work.