Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to locate jmsuser on executing SIB scripts



When the scripts for SIB creation on test or production environment executed, WAS Admin encountered issue related to jmsuser with Foudation Server 5.6 version. 

Error Messages

[15/09/14 15:17:03:070 BST] 0000000c LdapRegistryI E No user jmsuser found
[15/09/14 15:17:02:962 BST] 0000000c FfdcProvider W logIncident FFDC1003I: FFDC Incident emitted on /my_path/my_log_file.txt 1:285:
[15/09/14 15:17:03:076 BST] 0000000c LdapRegistryI E SECJ0336E: Authentication failed for user jmsuser because of the following exception No user jmsuser found
[15/09/14 15:17:03:078 BST] 0000000c LTPAServerObj E SECJ0369E: Authentication failed when using LTPA. The exception is No user jmsuser found.

[15/09/14 15:17:03:082 BST] 0000000c SibMessage W [epg_sit-ChordiantBusService:my_server-ChordiantBusService] CWSII0205W: The bus epg_sit-ChordiantBusService could not authenticate the user jmsuser.

Steps to Reproduce

Admin was trying to deploy fresh EAR file to Test Server and ecountered this issue.
This issue is not replicable in-house.

Root Cause

Following are the observations:

1. Warning message "The bus epg_sit-ChordiantBusService could not authenticate the user jmsuser."
When the configuration was reviewed via WAS Integrated Solutions Console, it was found that Bus Security is enabled for epg_sit-ChordiantBusService.

2. Application was being deployed with  ".ear " in the name (Example: chordiantear.ear)


Following changes resolve the reported behavior:

1. Disable Bus security.
2. Application must be deployed without ".ear" in the name (Example: chordiantear)

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us