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

Error on creating tenant

SA-76185

Summary


 

Error occurs while creating a tenant.


Error Messages


 

Caused by: pub.clipboard.InvalidStreamError: Invalid clipboard stream detected in module StorageStreamCommon.create(byte []).  Reason: Invalid signature found in stream. Stream length = 11; signature: [[email protected]; compressed = false
at pegarules.data.internal.clipboard.StorageStreamCommonImpl.create(StorageStreamCommonImpl.java:486) ~[prprivate.jar:?]
at pegarules.data.internal.clipboard.StorageStreamCommonImpl.create(StorageStreamCommonImpl.java:416) ~[prprivate.jar:?]
at pegarules.data.internal.clipboard.ClipboardPageImpl.adoptStreamForm(ClipboardPageImpl.java:396) ~[prprivate.jar:?]
at pegarules.data.internal.clipboard.ClipboardPageImpl.adoptStreamForm(ClipboardPageImpl.java:391) ~[prprivate.jar:?]
at pegarules.data.internal.clipboard.ClipboardPageFactoryImpl.acquireAndAdopt(ClipboardPageFactoryImpl.java:170) ~[prprivate.jar:?]
at pegarules.data.internal.access.PageDatabaseMapperImpl.populatePageOrStringMapFromStreamColumnUsingDataStore(PageDatabaseMapperImpl.java:2243) ~[prprivate.jar:?]
at pegarules.data.internal.access.PageDatabaseMapperImpl.populatePageOrStringMapFromStreamColumn(PageDatabaseMapperImpl.java:2174) ~[prprivate.jar:?]
at pegarules.data.internal.store.rdbms.ResultPageIteratorImpl.getClipboardPage(ResultPageIteratorImpl.java:1020) ~[prprivate.jar:?]
at pegarules.data.internal.store.rdbms.ResultPageIteratorImpl.next(ResultPageIteratorImpl.java:497) ~[prprivate.jar:?]
at pegarules.session.internal.mgmt.util.TenantInformationCacheImpl.getAllTenantInformation(TenantInformationCacheImpl.java:311) ~[prprivate.jar:?]


Steps to Reproduce


 

Add a new tenant.

 

Root Cause



A software use or operation error. Error stack indicated that the system retrieved getAllTenantInformation during the creation. The pzinskey Data-Admin-Tenent YOUR_TENANTID had Binary Large Object (BLOB) size of 11 bytes whereas on others the BLOB size was more than 1kb. Thus, the record Binary Large Object (BLOB) was corrupt. 


Resolution

Perform the following local-change:
  1. Select SQL
  2. Select pzinskey and length (pzpvstream) from pegadata.pr_data_admin_tenant where the length (pzpvstream) < 900 order by 2; to identify the corrupt record
  3. Delete the record with the corrupt Binary Large Object (BLOB)

Published April 2, 2019 - Updated December 2, 2021

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