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

Encountering errors when creating tenants



Two out of three MT servers are unable to create a specific tenant (YOUR_TENENT). However, other tenants that use the same Product rule were created successfully.

Error Messages

2017-01-05 00:04:19,500 [tp-apr-8080-exec-364] [ STANDARD] [ shared] [ PegaRULES:07.10] (rnal.mgmt.MultiTenantUtilsImpl)
ERROR YOUR_IP|SOAP|MTManagement|Service|CreateTenant|ADE5B03B9C78FA14692E8A54733085F5E -
Exception occurred fetching table details from pegadata caught exception during autocommit check

Steps to Reproduce

Import a Product rule file (YOUR_ARCHIVE.jar) by passing the necessary arguments to the pzCreateTenantWrapper out-of-the-box activity.

Root Cause

A software use or operation error:
Rows from pr_data_admin_tenant table for YOUR_TENENT were accidentally deleted. The code execution jumps from step 15 to step 29 when observed in the tracer. Step 29 is labeled "ORGFAIL" and calls pzDeleteTenant. This is happening because after step 15 there is an error. The administrator record already exists, which is an error, according to the tracer.

Since tenant instances were deleted directly from the database, only tenant records (metadata for the tenant) were removed. Other tenant artifacts (rules, data instances, and system cache) remained, which resulted in this issue when a new tenant with same name was created.


Perform the following local-change:
Use a different tenant name that does not conflict with existing records. Do not delete tenants directly from the database.

Published February 6, 2017 - 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