We have Crystal Reports 8 web services installed on our IIS 4 server, and when we test it using some simple reports, it crashes the web server when you use any reports that try to connect to the database. A server reboot is needed to fix it.
I've installed it on a second development server and they don't render the server completely inoperative, but any page that uses the CR services stops responding once you try to use a report that connects to the database, and
only a full reboot fixes the problem. All reports work fine if you open them using the CR main application at the server console.
Reports that don't actually hit the database (i.e. you save the data with the report) work just fine (until you try a report that does connect, then even these stop working as I described above).
These are just simple test reports- I'm not even to where we are ready for our big reports I migrated that use external UFLs.
I'm contemplating opening an incident with CR tech support but before we plunk down $200 I figured I'd check with you guys.
This seems like an ODBC problem but the Crystal support site is no help.
Any ideas?
I've installed it on a second development server and they don't render the server completely inoperative, but any page that uses the CR services stops responding once you try to use a report that connects to the database, and
only a full reboot fixes the problem. All reports work fine if you open them using the CR main application at the server console.
Reports that don't actually hit the database (i.e. you save the data with the report) work just fine (until you try a report that does connect, then even these stop working as I described above).
These are just simple test reports- I'm not even to where we are ready for our big reports I migrated that use external UFLs.
I'm contemplating opening an incident with CR tech support but before we plunk down $200 I figured I'd check with you guys.
This seems like an ODBC problem but the Crystal support site is no help.
Any ideas?