OperationFailedException: error creating client instance SYS_XXX not found
Article ID: KB0082461
Updated On:
| Products | Versions |
|---|---|
| TIBCO Administrator | 5.x..x |
Description
==========================
2009 Mar 26 08:23:25:686 GMT -4 Error [Administrator] AESDKJ-0000 [main] com.tibco.pof.entity.EntityStoreException: com.tibco.infra.repository.OperationFailedException: error creating client instance SYS_XXX not found
at com.tibco.pof.entitystore.tibrepo.TibRepoEntityStore.init(TibRepoEntityStore.java:359)
============================
Environment
OS: All
Resolution
The above error is a generic error and can be thrown due to multiple reasons.
Generally, the listed messages above indicates that the repo client (TRA Hawk Agent, AppManage etc) is unable to communicate with the Admin server as the discovery request for repo instance named SYS_XXX did not receive a reply.
This could be due to a secondary server with sync problems causing problems processing the request, but most likely either TIBCO Administrator is not running or due to messaging problems.
Another reason can be not following proper procedure to change the domain password i.e. changing the Admin password in the GUI and not propagating the changes to the machines using domainutility.
If the issue is occurring due to incorrect password reset procedure use the following workaround:
1) Open the tibcoadmin_<domain name>.tra file present in <tibco home>/administrator/domain/<domain name>/bin and change the following property to false:
repo.isSecurityEnabled=false
2) Restart the Administrator service.
3) Login to the TIBCO Administrator GUI and change the admin password as desired
4) Start the domainutility and change the domain password to exactly the same password as used in step 3 (using the server settings/update domain credentials option).
5) Open the "administrator.properties" file again and change the following property back to true:
repo.isSecurityEnabled=true
6) Restart the Administrator server.
Generally, the listed messages above indicates that the repo client (TRA Hawk Agent, AppManage etc) is unable to communicate with the Admin server as the discovery request for repo instance named SYS_XXX did not receive a reply.
This could be due to a secondary server with sync problems causing problems processing the request, but most likely either TIBCO Administrator is not running or due to messaging problems.
Another reason can be not following proper procedure to change the domain password i.e. changing the Admin password in the GUI and not propagating the changes to the machines using domainutility.
If the issue is occurring due to incorrect password reset procedure use the following workaround:
1) Open the tibcoadmin_<domain name>.tra file present in <tibco home>/administrator/domain/<domain name>/bin and change the following property to false:
repo.isSecurityEnabled=false
2) Restart the Administrator service.
3) Login to the TIBCO Administrator GUI and change the admin password as desired
4) Start the domainutility and change the domain password to exactly the same password as used in step 3 (using the server settings/update domain credentials option).
5) Open the "administrator.properties" file again and change the following property back to true:
repo.isSecurityEnabled=true
6) Restart the Administrator server.
Issue/Introduction
OperationFailedException: error creating client instance SYS_XXX not found
Feedback
Yes
No
Powered by
