0

LIBTUX_CAT:250: ERROR: tpsvrinit() failed

When you try to boot process scheduler or appserver domain, you may observe that the domain does not start and instead errors out with the message: LIBTUX_CAT:250: ERROR: tpsvrinit() failed

The most irritating part of this error is that often it does not provide enough clues as to what is wrong.

Basically what this error means is that tpsvrinit() function executed got executed to check for error, which is most likely database connectivity issue. Common issues include – incorrect path, locked database userid, firewall etc.

The complete set of error message may be like:

For process scheduler

tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler

LIBTUX_CAT:262: INFO: Standard main starting
LIBTUX_CAT:250: ERROR: tpsvrinit() failed
Tuxedo Version 12.2.2.0.0, 64-bit
tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler

For application server

tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler

Tuxedo Version 12.2.2.0.0, 64-bit
LIBTUX_CAT:262: INFO: Standard main starting
LIBTUX_CAT:250: ERROR: tpsvrinit() failed
CMDTUX_CAT:825: ERROR: Process xxx at yyy failed with /T tperrno (TPESVCFAIL – application level service failure)
tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler

Resolution for LIBTUX_CAT:250: ERROR: tpsvrinit() failed

Take a look at the below mentioned resolutions. Note that not all these scenarios may apply to your situation but hopefully one of them will apply to your situation and will help resolve the issue.

1. Verify that the userid used to bring up process scheduler or application server domain is not locked and is using a correct password. For example, you might have done database refresh and the common application server domain admin userid, PSAPPS may have an incorrect password (password from production) specified or is locked.
2. For the above situation, try to reset the password and bring up domain.
3. Have a look at environment variable, ORACLE_HOME and make sure that it points to the correct path and has no typo.
4. Go to PSADMIN and configure the domain. Domains Gateway (Option 12 in PT8.56) might be set to Y. Try to disable the same. If you enable Domains Gateway, it tries to search for a remote server to send search requests.
5. Check if you have DBBIN parameter specified in the process scheduler domain (psprcs.cfg file) and make sure that it is correct.
6. Check with the firewall team if they notice any drops.

Hopefully this will resolve your issue and if not, do let us know in the comments section below.