Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Jaffer Sathick Mohideen Abdul Kather (jafferSathick)
TCS
Engineering Lead
TCS
GB
jafferSathick Member since 2010 23 posts
TCS
Posted: Mar 28, 2016
Last activity: Apr 6, 2018
Posted: 28 Mar 2016 2:19 EDT
Last activity: 6 Apr 2018 19:26 EDT
Closed

Post Upgrade - This action is not allowed as it is outside the current transaction
I upgraded one of the customer's application in 6.1SP2 to 7.2 and configured with WAS 8.5 Post upgrade, I launched with login on administrator and proceed to IMPORT wizard so as to import framework's (BiX) jar files. After I choose the path of the JAR file and clicked submit. I see the error message - "This action is not allowed as it is outside the current transaction." In logs, I see the message. 2016-03-24 14:55:44,783 [ WebContainer : 0] [TABTHREAD0] [ ] [ PegaRULES:07.10] ( mgmt.base.ThreadUITransaction) ERROR Proprietary information hidden|wchodb2w7hyd.rpega.com [email protected] - ERROR: posted transaction id 'ddd61c5b191cded3a517c8b6466b54db' for frame 'pyWorkPage' DOES NOT match record '3dc7e76d8e164cc3d2436e25971173ac'. It would have made sense if I had received this message on submit of any forms of Customer code but receiving in the OOTB IMPORT wizard puzzles me. But, when I re-configured the same 7.2 application with Tomcat, the above problem is not faced. I double checked to make sure WAS configuration are as per the Install/Upgrade guides. Guys, Any clue ?

**Moderation Team has archived post**


This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
Updates

Posted: 8 years ago
Posted: 6 Apr 2016 11:18 EDT
Dhevendra Earva (earvd)
PEGA
Senior Director of Cloud Engineering
Pegasystems Inc.
IN

This is an issue with Datasource configuration of WebSphere. After configuring the DataSource properly this issue got resolved.

To see attachments, please log in.
Posted: 8 years ago
Posted: 31 May 2016 1:49 EDT
Sam Lanka (LANKAS02)
United Health Group

United Health Group
US

Hi,

      Could you please help us as what changes have you done exactly, to resolve this problem, we are also seeing the same problem.

 

Thanks and Best REgards

Sam

To see attachments, please log in.
Posted: 7 years ago
Posted: 3 Mar 2017 1:20 EST
Arpita Das (Arpita_D)
ING, Netherlands

ING, Netherlands
NL

Hi,

For one of our Clients, we are facing the issue when importing CustomerService, could you please let know what datasource configuration fixed the issue in your case?

Regards,

Arpita

To see attachments, please log in.
Posted: 7 years ago
Posted: 3 Mar 2017 9:39 EST
Sreeni vaddineni (SREENI4634)
Ashfiled
Pega Lead System Architect
Ashfiled
US

Hi Dhevendra,

 

We are also facing the same issue when we are installing the CS FW.

Could you please let me know how you resolved this issue.

 

thanks,

Sreeni.

To see attachments, please log in.
Posted: 7 years ago
Posted: 6 Mar 2017 0:55 EST
Dhevendra Earva (earvd)
PEGA
Senior Director of Cloud Engineering
Pegasystems Inc.
IN

When we have encountered this issue two Data sources are defined in WAS server(jdbc/PegaRULES and jdbc/PegaDATA). After deleting the PegaDATA it worked properly.

To see attachments, please log in.

Related content:

Discussion

This action is not allowed as it is outside the current transaction.

Question

This action is not allowed as it is outside the current transaction

Discussion

This action is not allowed as it is outside the current transaction.

Question

action is not allowed as it is outside the current transaction

Question

This action is not allowed as it is outside the current transaction.

Question Solved

Reversion Request: This action is not allowed as it is outside the current transaction.

Question

This action is not allowed as it is outside the current transaction in Schedule absence

Question Solved

This action is not allowed as it is outside the current transaction in screenflow

Question

Error - This action is not allowed as it is outside the current transaction.

Question

Err - This action is not allowed as it is outside the current transaction

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

Pega Collaboration Center 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