Hi All,
Has anybody out there experienced the following problem with the DocAgent : Any report that is sent to the Document Agent automatically goes into a permanent status of WAITING. No matter what schedule is set on the report, docagent does not realise that there are reports to be processed. The only way to run the report is then to select the RUN NOW button from the docagent console.
Has anybody got any suggestions on how to sort this problem out, or perhaps give me an idea of what is causing the problem.
Thanks in advance.
Shirley Morris (Caltex Oil South Africa) Information Management Team
Have you tried changing the settings within DocAgent to run a job every minute. A report may not run at your scheduled time because of how often it checks for new jobs. Try changing the setting to one minute as a test. If that resolves the problem, then I would find a suitable setting from there.
Hope this helps a little.
At 03:58 PM 7/21/98 +0200, you wrote:
Hi All,
Has anybody out there experienced the following problem with the DocAgent : Any report that is sent to the Document Agent automatically goes into a permanent status of WAITING. No matter what schedule is set on the report, docagent does not realise that there are reports to be processed. The only way to run the report is then to select the RUN NOW button from the docagent console.
Has anybody got any suggestions on how to sort this problem out, or perhaps give me an idea of what is causing the problem.
Thanks in advance.
Shirley Morris (Caltex Oil South Africa) Information Management Team
Has anybody out there experienced the following problem with the DocAgent : Any report that is sent to the Document Agent automatically goes into a permanent status of WAITING.
Shirley, yes we’ve seen this. Unfortunately for us we had a corrupt repository. Here is what I would suggest, though the latter option may not be too practical, depending on the # of reports you currently have scheduled:
Scenario 1:
shut down DAS and cold boot the DAS machine. This should reestablish the connection to the database. It sounds simple, but sometimes this is all it takes.
Scenario 2 (the more involved option):
do a “scan and repair” and see what it tells you 2) via the DAS console, delete all currently scheduled jobs 3) check the repository tables via SQL*Plus or other means to make sure the DS_PENDING_JOB is empty. If it’s not empty after you have manually deleted all entries from the DAS console, you probably have a corrupt repository.
Hopefully the scan and repair can help you with this.
Also, there is at least one patch related to DAS that I’m aware of. I’m not sure of all the symptoms it fixes, but you may want to contact tech support to get the latest patch. Good luck. –
– Ron Sinicki
– Braun Technology Group
– (317) 822-4510
– http://www.brauntech.com
Hi All,
Has anybody out there experienced the following problem with the DocAgent : Any report that is sent to the Document Agent automatically goes into a permanent status of WAITING.
Hi Shirley:
The suggestions made by Seth Cohen and Ron Sinicki are good ones to follow up on. Also, we had some wierd problems with the DAS that we got the patch for – the patch is ver 4.1.2a.
Regards,
Chander Aggarwal
COMPUEXCEL
The home of BusinessObjects Essentials
WORLD’S FIRST AND ONLY FULL MULTIMEDIA
COMPUTER BASED TRAINING FOR BusinessObjects!
Hi All,
Has anybody out there experienced the following problem with the DocAgent : Any report that is sent to the Document Agent automatically goes into a permanent status of WAITING. No matter what schedule is set on the report, docagent does not realise that there are reports to be processed. The only way to run the report is then to select the RUN NOW button from the docagent console.
Has anybody got any suggestions on how to sort this problem out, or perhaps give me an idea of what is causing the problem.
Perhaps some problems with the rights on the document repository?
Walter
DI Walter Muellner
Delphi Software GmbH, Vivenotgasse 48, A-1120 Vienna / Austria Tel: +43-1-8151456-12, Fax: +43-1-8151456-21 e-mail: w.muellner@delphi.at, WEB: http://www.delphi.at
We’ve been running DAS from its inception, and certainly not without problems.
The “waiting” status you are experiencing is normal for reports “waiting to run”. I have not run into the problem of DAS not recognizing that a new report is waiting to run. Might check some of the various flags in the repository to see if any clues are there.
We are having a lot of problems with Document Agent Server… When we bring
it up and click run now, we get lots of different errors on our documents.
BO has not been able to help much, they say it is our server. Here are the
errors we are getting…
FileOpen failed and the error is not a multi access error
Unable to work with this container
Cannot complete job execution
when we send a new document to the document agent server or modify something on a existing job.
The next time the report is proccesed, it runs always twice!
We use document agent server version 4.1.5.
Am I the only person that has this problem or can somebody help me with this?
Some of our Business Objects 4.1.3 customers are receiving error messages when sending queries to run on the Document Agent Server version 4.1.4. I am interested in knowing what causes these errors and how to get these queries to run. All suggestions will be appreciated! The error messages are:
“Could not be saved due to disk error” and “Invalid exit code”
Deborah A. Mitchell
Business Technology Consultant
CNA Insurance
Chicago, IL