5405 1

[DebiJo]

Running Progress 8.3A on Windows NT

I have a script that starts proservice that runs daily. About half the time, it opens the database and immediately shuts it back down. On the failed instances, at the begining of the proservice start I get:

Message from PROGRESS database d:\lsp\ra\db\fac001\ra (5199) SERVER : This broker will terminate when session ends. (5405)

I am unable to duplicate this behavior. And half the time it works correctly. Any ideas as to why this would be happening?

We do have our database set to autostart and we are using the -S switch.

Thanks in advance,
Debi

 

[HelloMike]

Have a look at the NT Event Viewer. There should be at least one associated message in there that may give you some clues. Message 5199 gets posted by Progress when something has happened that causes an event to be posted to the NT event log. And 5405 says that Progress is NOT running as a service.

Mike.

 

[DebiJo]

Yes, but why is progress not running as a service?

I changed my script, it now does a

Net Start "ProService 8.3A"

It worked in testing, but in real life, it again decided to not run as service and progress immediately shut down when the script finished.

Any ideas?
Thanks,
Debi

 

[HelloMike]

Debi,

What parameter are you issuing with your -S switch ?

It needs to be either the name of a service or its associated port number, and these should be referenced in the Services file on the host machine -- in c:\winnt\system32\drivers\etc\services or somewhere similar.

If this doesn't help, can you post the full startup script ?


Mike.

 

[DebiJo]

The is virtually a one liner (if you don't count the echo's).

Yesterday it was: d:\dlc\bin\pccmd ProService Start
Today it was: net start "ProService for 8.3A"

Both failed the same way. Well, the commands worked, but because they were not executed as a service, the database immediately shut down again when the script was complete.

Procontrol is set to autostart this database with:
-N tcp -H facility -S ra001facility -L 10000

The services file has:
ra001facility 2501/tcp

Thanks again for your help.
Debi

 

[HelloMike]

Hmm. What logon account are you running the script from ? You may need to be logged into the local system account or administrator account.

Beyond that, I'm stumped. I'd suggest you have another shot at the Peg dba list.


Mike

 

[DebiJo]

It turned out that our AT scheduler got hosed and lost the network account it was running as. It had defaulted back to the local system account and evidently that's not good enough if progress is installed over a network.

Thanks for the tip.
Debi