cancel
Showing results for 
Search instead for 
Did you mean: 

Value Mapping Replication : Error Category: XIServer

prabhu_s2
Active Contributor
0 Kudos

Hi All,

I'm doing a value mapping replication. Have configured the interface proxy-pi (Async) and the message is transferred to pi with no issues but in pi the message is logged with the following error as in payload:

>Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received

Link to payload > [http://www.esnips.com/web/SAPIssues ]

tried various cases yet the issue remains the same. any helpful tip on this?

thanks

Prabhu

Accepted Solutions (1)

Accepted Solutions (1)

stefan_grube
Active Contributor
0 Kudos

The error code states: Expired password.

prabhu_s2
Active Contributor
0 Kudos

yeah but for which user....XIISUSER??? the pwd for XIISUSER seems to have no issues....no idea in which part of the framework the pwd needs to be corrected.

stefan_grube
Active Contributor
0 Kudos

can you see the message in RWB message monitor for adapter framework?

Is your user/pw combination in the receiver channel correct?

prabhu_s2
Active Contributor
0 Kudos

Error in RWB: To be delivered

Error in moni: Payload as posted in the thread (refer link)

Error in SMQ2: User column:XIISUSER statustext column: Command to tRFC/qRFC: Execute LUW again

stefan_grube
Active Contributor
0 Kudos

Check if user is created as service user.

It seems that the system want the user to change the password, so it might be a dialog user.

Do you have other scenarios running well in your system?

prabhu_s2
Active Contributor
0 Kudos

yes checked and it is service user...shud the pwd be changed in exchange profile or in visual admin?

prabhu_s2
Active Contributor
0 Kudos

This is an issue with the user authentication....fixed and up running.....

executed for the first time and the value are update in cache...when executed for the second time the data is not updating in cache....any solution on it pls?

prabhu_s2
Active Contributor
0 Kudos

its cache issue.....gud and clean now!!!

Answers (0)