I’m having trouble installing DAS as a Service. I’m using BO 4.1.3 w/ CSP #22, Oracle 7.3 and SQL*NET.
I installed the service in two ways. First I used the INSTSRV command as it says in the documentation. It installs the service correctly, but I can’t get it to start. I keep getting a NT Internal ERROR. I changed the username of the service and still no results. I then called BO (CASE 75264) and they sent me a technical write up. I then installed a different service per these instructions using SRVINSTW instead of INSTSRV. Same problems. I did one other thing. I clicked on “Interact with desktop”. When I do this I get the BO Banner and it says cannot reach repository. On this NT machine I can run BO reporter, Designer, etc. Also, if I startup DocAgent from this machine everything works fine. I just can’t get it installed as a service.
I’m having trouble installing DAS as a Service…
I installed the service in two ways. First I used the INSTSRV command as it
says in the documentation. It installs the service correctly, but I can’t
get it to start. I keep getting a NT Internal ERROR. I changed the
username of the service and still no results.
Hector:
I’ve gotten this error whenever the account I’m trying to use does not have
administrative privileges on the DAS machine … I read somewhere in the
documentation that the user needs to be a part of the Administrator group or
the service will return a 2140 internal NT error.
Jay Clise
Sandia National Labs
Albuquerque, New Mexico
You are just not giving enough time for the service to start in Primary
mode.
Check the Begin Time and End time values in the OBJ_M_TIMESTAMP table in
the repository. They should be the same. If they are not that means your
DOCAGENT is not shut down. Wait for them to be the same (one way of
Updating them will be to starting and shutting down the Doc Agent in
Console Mode). Once they are the same then start the NT service and
should be fine.
Good Luck
Are you installing the service locally or as a system service?
You might also want to contact Carmen Sanchez at GE. She had the same
setup as you and got it to work.
Hector Valenzuela wrote:
I’m having trouble installing DAS as a Service. I’m using BO 4.1.3 w/ CSP #22, Oracle 7.3 and SQL*NET.
I installed the service in two ways. First I used the INSTSRV command as it says in the documentation. It installs the service correctly, but I can’t get it to start. I keep getting a NT Internal ERROR. I changed the username of the service and still no results. I then called BO (CASE 75264) and they sent me a technical write up. I then installed a different service per these instructions using SRVINSTW instead of INSTSRV. Same problems. I did one other thing. I clicked on “Interact with desktop”… When I do this I get the BO Banner and it says cannot reach repository. On this NT machine I can run BO reporter, Designer, etc. Also, if I startup DocAgent from this machine everything works fine. I just can’t get it installed as a service.
when installing DAS as a service make sure you are logged on the server LOCALLY (in my situation that means logging on to PLTC08 vs LOGISTICS) not as part of the domain. This effects the install and overrides the persmissions some how.
Logon LOCALLY and install per the instructions and everything will work.
It took us two weeks to figure this out.
Sincerely,
Thomas Nather
Penske Logistics
email: Tom.Nather@Penske.com
Ph: 216-765-5787
Fax: 216-765-5666
“Clise, Jay” ljclise@SANDIA.GOV 01/07 3:27 PM >>>
I’m having trouble installing DAS as a Service…
I installed the service in two ways. First I used the INSTSRV command as it
says in the documentation. It installs the service correctly, but I can’t
get it to start. I keep getting a NT Internal ERROR. I changed the
username of the service and still no results.
The system account which you specified in the startup is a LOCAL system
account. It has no access to any net-resources. Therefor, it cannot find
the BOmain.key, the databases etc. (provided they are indeed on other
servers). You should specify a specific account in the startup options,
which does have access to the necessary resources. Try, for example,
specifying the same account you are using when logged on to that server and
starting up the DAS.