DAS setup as automatic startup service

scheduling Broadcast Agent (BCA)
1

I have two document agent instances setup as services with automatic startup on NT 4.0 workstation. After the machine starts, I check the services status and only one of the two DAS services shows as being started.

I can start both manually with no problem but when the machine restarts, only one of the DAS services shows as started. It is inconsistent as to which DAS service is started as well.

Has anyone experienced a similar problem or have any ideas?

Thanks in advance,

Justin T. Katen
BO Developer
Anheuser-Busch, Inc.

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

2

This seems to be a new “feature” of the 4.1.3. I did not have this kind of problem with the 4.1.2 but discovered it after having installed the 4.1.3 this morning …
On my machine, I have 2 such services, and none starts automatically.

Pierrot

I have two document agent instances setup as services with automatic
startup on
NT 4.0 workstation. After the machine starts, I check the services status
and
only one of the two DAS services shows as being started.

I can start both manually with no problem but when the machine restarts, only one of the DAS services shows as started. It is inconsistent as to which DAS service is started as well.

Has anyone experienced a similar problem or have any ideas?

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

3

If you increase timeout, the service is able to start automatically on server reboot.

Run SRVDASDG.EXE, which configures DAS as a service, and increase the parameter “Launch time”

fyi/CL
BusObj Product Mktg Paris

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