Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Default Servers to Use for Scheduling - Fails

Status
Not open for further replies.

jasonhuibers

Programmer
Sep 12, 2005
290
CA
CE10 (Clustered servers - Server1\Server2)
Sql server 2000
Windows 2003
---

Under the Process tab, 'Default Servers To Use for Scheduling':

Select - Only use Servers belonging to the selected group
We have this option selected to be generated onto Server2. When we schedule our reports VIA ASP code, the 20 batches are generated, first two are Succesful and then the next two fail and the remaining ones are completed successfully. We run the failed batches a second time anf the batches are generated successfully. It is never the two same batches that fail.

When we remove this option and use the default: Use the First Available Server, the jobs are completed successfully.

Is there an additional config setting that maybe not set or does anyone have a workaround or a solution?

Any feedback is appreciated!

 
Report Info:
CR10
Main report uses SP
10 Subreports
43 parameters
 
Hi,
What message do the failed runs show?



[profile]

To Paraphrase:"The Help you get is proportional to the Help you give.."
 
Have tou tried running the failed report via Crystal Reports on the server that fails ? This may give more info on the "Query Engine Error" eg formulas need a UFL which is not on the server. Let me know how you get on.

ShortyA
 
This is a production server. Management will never approve having CR installed on the server.
 
Previous clients I have worked with have installed it as it enables prompter issue resolution as you can test the report on the server with ODBC connections, DLLs etc and isolate areas before replicating on a test environment. But if they won't approve it!
 
Thoughts ... maybe one is helpful:

1. Sounds like a DB issue -- is it possible that you have exceeded concurrent logins available to connect to that particular database (if all these reports use the same one)?

2. CR does give much better error messages ... could you try opening the report through Enterprise folders (or saving to your desktop) and see if it runs successfully on your computer? That isn't exactly the same as if you could run CR on the actual CE server, but if it fails on your machine it might give more indication.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top