Kbase P48018: Client spawned from ProControl Other Tasks encounters error 1720.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/1/2004 |
|
Status: Unverified
SYMPTOM(s):
Client spawned from ProControl Other Tasks.
Batch Client is launched from ProControl Other Tasks.
Unable to attach shared memory <shmname>, error <n>. (1720)
CAUSE:
The problem here is NOT ProControl. Programs ran from ProControl are run as NT "Services". This means that it is run under "LocalSystem" with its own security domain in a detached state (somewhat like a Unix daemon).
The "Other Tasks" tab in ProControl was put in during the original development of ProControl (V8.0B) to allow startup of aiwriters, biwriters, etc. The startup of these was then moved to the proper "Database" tab by the original authors of ProControl. The "Other Tasks" tab was not removed as it should have been.
FIX:
The Progress client was not written to support being run in this type of environment.
What happens now is the "Other Tasks" tab is used to startup all sorts of things that it was never intended for. Mostly, this tab is now used to startup a batch client (as in this case). Unfortunately, the client does not know anything about running in this environment. It normally runs ok but sometimes it doesn't.