Page Not Found, Must Restart Web Server

[123FakeSt]

Similar to thread782-965562 , I'm using IIS 6.0, Windows 2003 SP1, and CE version 9 (a limitation of our application.)

Everything else is fine, but once the first report comes back 'Page Not Found' then the only way to get CE back up is restarting.

Our software vendor hasn't been much help.

The early bird gets the worm, but the second mouse gets the cheese.

 

[123FakeSt]

More info.....

Microsoft VBScript runtime error '800a01fb' 

An exception occurred: 'objCrystal.OpenReport' 

/Crystal9.asp, line 185

The early bird gets the worm, but the second mouse gets the cheese.

 

[Turkbear]

Hi,
Based on some info from a google search:

Here are the situations I know of that can bring about 800a01fb errors. 
 
Microsoft VBScript runtime error '800a01fb' 
An exception occurred: 'Open' 
 
This error can happen when you 
use an ADODB.Recordset to retrieve a resultset, 
and the resultset is empty.
Switching from ADODB.Recordset to 
conn.execute(sql) seems to alleviate this problem. 
 
Microsoft VBScript runtime error '800a01fb' 
An exception occurred: 'Server.CreateObject' 
 
If you are attempting to create an ADODB.Connection,
ADODB.Recordset, ADODB.Stream or 
ADODB.Command object, this error might be caused by a corrupted MDAC. Update MDAC from MDAC Download Page. 
 
Microsoft VBScript runtime error '800a01fb' 
An exception occurred: 'MethodForYourCOMObject' 
 
If you try to pass an array to a COM object, 
you might see this error. 
See KB #217114 for information on passing arrays as arguments to VB COM objects.

I would suspect that the record set is not returning any data..check the selection criteria and, using that same criteria, run the report from Crystal Designer..





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[123FakeSt]

Once the error starts occurring, I can run reports that have previously worked with the same selection criteria that now display this error. Unless running a report with no results actually causes the entire Crystal Enterprise web service to crash and force a reboot than this can not be the explanation.

I can't imagine Crystal would produce a product that would force you to reboot a server everytime that you ran query that returned no results.


The early bird gets the worm, but the second mouse gets the cheese.

 

[Turkbear]

Hi,
No, I have run many a report that returned no records.
The MDAC ( or its drivers) may be somehow causing the problem...Do the reports that work use the same connection method and drivers?



To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[123FakeSt]

Updating this thread, all of the reports will work or not work.

All of the clients can see the reports, that for some reason all of the clients will get the error message regardless of the report ... until we restart the web server.



The early bird gets the worm, but the second mouse gets the cheese.