I'm running Bea Tuxedo 8.1 on a Peoplesoft Process Scheduler server on Windows 2003. Tuxedo is patched to RP291. The BEA ProcMGR service is set to automatically start and is using an administrator level account that has full access to the Peoplesoft environment.
Each time the service starts, it auotmatically stops itself. Event viewer gives a generic description that says "some services will stop if they have no work to do". I don't believe this applies for ProcMGR since we have other Peoplesoft servers where the service is constantly in a running state and can be started and stopped without any issues.
Despite the fact that the service stops on its own, the tuxipc.exe process is still running in the background. Whether it is truly running, or just a hung process in memory, I'm not sure of.
At any rate, there seems to be a problem accessing shares over mapped drives, and the ProcMGR service is the only oddity I can track down, leading me to believe the issues may be related.
Please advise.
Each time the service starts, it auotmatically stops itself. Event viewer gives a generic description that says "some services will stop if they have no work to do". I don't believe this applies for ProcMGR since we have other Peoplesoft servers where the service is constantly in a running state and can be started and stopped without any issues.
Despite the fact that the service stops on its own, the tuxipc.exe process is still running in the background. Whether it is truly running, or just a hung process in memory, I'm not sure of.
At any rate, there seems to be a problem accessing shares over mapped drives, and the ProcMGR service is the only oddity I can track down, leading me to believe the issues may be related.
Please advise.