All,
I looked through the archives, and while there are many postings
dealing with NT service/DAS, none seemed to address the issue I am
having.
I installed BO 4.1.4 on a v.4 NT workstation with sp4. The install
was easy enough, and I can now launch the service manually with no
problem. However, I cannot get it to start automatically even though
that is how it is configured. I know that there is no issue w/
primary v. secondary because I can start it manually (and I confirmed
as much on the repository). When I re-start the machine, everything
else comes up OK; it just does not start the DAS service.
I have tested the launch time setting with 60s and 120s, with the same
result. Any ideas?
Thanks,
Jason Beard
“I installed BO 4.1.4 on a v.4 NT workstation with sp4. The install
was easy enough, and I can now launch the service manually with no
problem. However, I cannot get it to start automatically …”
We also have not been able to get the service to start automatically. But,
we did come up with a work around. In our reboot script, we use “net stop
doc_agent_name” during shut down and “net start doc_agent_name” during
startup. We set the start up type in the services panel to manual.
“I installed BO 4.1.4 on a v.4 NT workstation with sp4. The install
was easy enough, and I can now launch the service manually with no
problem. However, I cannot get it to start automatically …”
We also have not been able to get the service to start automatically. But,
we did come up with a work around. In our reboot script, we use “net stop
doc_agent_name” during shut down and “net start doc_agent_name” during
startup. We set the start up type in the services panel to manual.
Thomas,
I have everthing installed on c:\, as well...bu it still does not
start automatically. Any other tricks you came across?
Jason
----------------------------------------------------------------------
The only way I found to get the service to start automatically is to put all the
software on the C: drive and configure it per the instructions.
“I installed BO 4.1.4 on a v.4 NT workstation with sp4. The install
was easy enough, and I can now launch the service manually with no
problem. However, I cannot get it to start automatically …”
We also have not been able to get the service to start automatically. But,
we did come up with a work around. In our reboot script, we use “net stop
doc_agent_name” during shut down and “net start doc_agent_name” during
startup. We set the start up type in the services panel to manual.
Reason for not being able to startup the DAS is that the NT domain is
not yet ready to do logons early in the booting process. While booting
NT tries to startup all services at the same time. There is, however, a
timeout value on the service definition. This could cure the problem.
But currently we use the same approach by starting the DAS services with
a net start call and this seesm to work now for months without major
problems.
hans
Jason Beard wrote:
“I installed BO 4.1.4 on a v.4 NT workstation with sp4. The
install
was easy enough, and I can now launch the service manually with
no
problem. However, I cannot get it to start automatically …”
We also have not been able to get the service to start automatically.
But,
we did come up with a work around. In our reboot script, we use “net
stop
doc_agent_name” during shut down and “net start doc_agent_name” during
startup. We set the start up type in the services panel to manual.