pzTransactionid and pxclientExchange

Question

Replies

1169

Views

GAURAVBV

Member since 2011

30 posts

Infosys

Posted: May 31, 2016

Last activity: June 2, 2016

Posted: 31 May 2016 3:04 EDT
Last activity: 2 Jun 2016 12:12 EDT

Closed

Solved

pzTransactionid and pxclientExchange

What values do the parameter pztransaction id and the property pxRequestor.pxClientExchange hold? And also when exactly do these change?

We are facing an attachment issue due to these properties in 6.3 sp1. Any response would be helpful.

Thanks,

Gaurav

System Administration

User Experience

Data Integration

Moderation Team has archived post,

This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.

Accepted Solution

Posted: 5 years ago

Posted: 2 Jun 2016 12:12 EDT

mahab_GCS

PEGA

replied to GAURAVBV

Hi Gaurav

Every time the client speaks to the server, it needs to provide a transaction id (pzTransactionID). Once a commit is made in the database, the server provides in exchange a new transaction id via the pxClientExchange so that going forward the client could use the new one as its transaction id.

I have a feeling you are running to an error like so "2015-11-20 18:03:41,862 [ WebContainer : 10] ( mgmt.base.ThreadUITransaction) ERROR - ERROR: posted transaction id '9143f677524349fe81f16da214216fec' for frame 'pyWorkPage' DOES NOT match record '6f1c6a4cbb8b60b138adc9207a85d32b'"

There are lots of PDN articles and mesh posts that discuss this topic.

You mention that you are facing an attachment issue in 6.3 sp1. Please take a look at this PDN link.

https://pdn.pega.com/support-articles/posted-transaction-id-frame-pyworkpage-does-not-match

Here are few others that talk about the error in detail:-