The RUN NOW option is not available when running DAS in console mode…maybe the DAS is already running as a service? _________________________
Tim Heuer
PacifiCare Health Systems
(714) 825-5702
(800) 759-8888 pin 1251901 - pager tim.heuer@phs.com
try to force the job to run, the run now option is greyed out and unavailable. I can suspend and delete, but not run now. This applies
to all jobs sent either by myself or other people. It has worked fine
in the past.
I am using BO 4.1.2 with DAS running on a Windows NT4 PC.
Recently I have found that when a user (any user) sends a report to DAS, the status is consistently listed as waiting. This is even after the scheduled time for the report to run has been and gone. When I try to force the job to run, the run now option is greyed out and unavailable. I can suspend and delete, but not run now. This applies to all jobs sent either by myself or other people. It has worked fine in the past.
Anyone experienced something similar and know of any solutions?
In a message dated 98-09-30 13:06:11 EDT, you write:
Recently I have found that when a user (any user) sends a report to
DAS, the status is consistently listed as waiting. This is even after the scheduled time for the report to run has been and gone. When I try to force the job to run, the run now option is greyed out and unavailable. I can suspend and delete, but not run now. This applies to all jobs sent either by myself or other people. It has worked fine in the past.
Anyone experienced something similar and know of any solutions?
I saw this one time at a client site. There were new network settings that had been rolled out on the client pc’s but had not made it to the DAS machine. (Specifically a TNSNAMES.ORA file, Oracle configuration) DAS could not run the documents because the connection information contained in the universe was no longer valid.
Once we updated the TNSNAMES.ORA configuration file on the DAS machine everything worked fine.
Recently I have found that when a user (any user) sends a report to DAS, the status is consistently listed as waiting. This is even after the scheduled time for the report to run has been and gone. When I try to force the job to run, the run now option is greyed out and unavailable. I can suspend and delete, but not run now. This applies to all jobs sent either by myself or other people. It has worked fine in the past.
Ginny,
We have experienced something similar in the past when our DAS got into console mode because it temporarily lost its connection to the repository. In console mode you can do everything except “run now”. Might that be your problem?
We experienced the same problem recently, but installed version 4.1.3 of Business Objects on our Doc Agent machine and this seemed to have sorted out the problem.
I am using BO 4.1.2 with DAS running on a Windows NT4 PC. Recently I have found that when a user (any user) sends a report to
DAS, the status is consistently listed as waiting. This is even after
the scheduled time for the report to run has been and gone. When I
try to force the job to run, the run now option is greyed out and
unavailable. I can suspend and delete, but not run now. This applies
to all jobs sent either by myself or other people. It has worked fine
in the past.
Anyone experienced something similar and know of any solutions? Thanks,
Ginny.
But if you start DAS on a different workstation than the current DAServer u should be able to choose run now.
hans
The RUN NOW option is not available when running DAS in console mode…maybe the DAS is already running as a service? _________________________
Tim Heuer