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!

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

Search results for query: *

  1. Frobisher

    Why does not autosave not work?

    It does work it's just that it doesn't autosave the report to the folder your report is in, instead it puts it in your TEMP folder and calls it <report name>.autosave.rpt. Frobisher
  2. Frobisher

    Autosave Reports - Where did it go?

    It puts it in your TEMP folder and calls it <report name>.autosave.rpt. Frobisher
  3. Frobisher

    Print Engine Error

    Just to tie up this thread a bit...we've given up on trying to get CE to run on that machine so we stuck it on a new machine with a fresh NT install and so far it's been ok. Draw your own conclusions from that! Frobisher
  4. Frobisher

    Print Engine Error

    So is that the way you set the logging level? I couldn't find it documented anywhere. It's funny you were told to do that as I was told:- &quot;Another thing that can cause this type of behaviour is logging. If you are running the Page Server at loglevel 9 or an extended period of time it...
  5. Frobisher

    Print Engine Error

    I'm still talking to Crystal support about this problem. They seem to think it's related to running out of resources, whatever that means. I'll let you know when/if I get a solution. Cheers.
  6. Frobisher

    Print Engine Error

    We've got a problem with CE not running for very long before it starts to generate errors and won't serve up pages anymore. Crystal displays the error: Crystal Reports: Print Engine Error [On Page Server: <x>.pageserver] The pageserver log shows the following: Timestamp (Process ID, Thread...

Part and Inventory Search

Back
Top