Document sent to DAS has errors if it runs a script

          without a
          MsgBox

We have encountered a very similar problem to Darren’s below. It occurs
with DAS versions 4.1.2a and 4.1.4 running under Windows NT 4.0 (as a
user-started task, not as an NT service).

We use a script called BusObj with one subroutine called AtStart, which is
executed by Business Objects every time it starts up. Without going into
the messy details, this subroutine assigns a value to a BO variable which
is the userid for a connection to mainframe DB2. The subroutine uses SQL
calls to get some information about the user from the security repository.

It all works fine with Business Objects run on users’ PCs. However, when
documents are run by a DAS, the Business Objects task fails just before it
finishes with a STATUS_ABANDONED_WAIT_0 error. If the output was directed
to a printer or a web server, it is printed or saved ok on the web server,
but if directed back to a user via the repository it is not stored in the
repository. The BusObj script has set up the BO variable correctly and the
connection has extracted the data correctly from DB2.

If I cut the BusObj script down to two lines, ‘sub OnStart’ and ‘end sub’ I
get a Dr Watson addressing exception as Darren described, and if I insert a
third line ‘MsgBox “Message”,64’ everything works perfectly, as Darren also
found.

Any suggestions would be very welcome.

David Bellair
Information Management Group, Global Information Services
Mobil Oil Australia Ltd.
Phone: +61 3 9252 3395, Fax: +61 3 9252 3790

On Mon, 8 Feb 1999 10:01:30 +0000, Darren Turland wrote:

I am currently trying to develop a similar scheduling system, but have
encountered a problem.
The scheduling seems to work, and reports are being sent to DAS. The
problem
arises when they are running. Each report fails with a ‘Dr. Watson’ just
as
its completing (I knowthis from writing lines to a file).
Each report that is sent using the scheduler has a script attatched which
exports the document into the repository.
I can get round the failure if a put a MsgBox statement as the last line
of
the attached script, but this is not acceptable.

Any ideas…

Darren Turland Senior A/P
Argos Distributors Ltd.
E-Mail: darren.turland@argos.co.uk


Listserv Archives (BOB member since 2002-06-25)