cancel
Showing results for 
Search instead for 
Did you mean: 

UNAUTHORIZED:401

Former Member
0 Kudos

Hi Experts,

We are getting failed messages for the below error in integration engine .After manually restarting the messages processed successfully from integration engine .I am using PI7.1 version .

Please suggest me any parmanent solution for this issue .

-


-SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>

<SAP:P1>401</SAP:P1>

<SAP:P2>Unauthorized</SAP:P2>

<SAP:P3>(See attachment HTMLError for details)</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

-


Regards,

Somenath

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

The issue resolved after increasing the connection size

0 Kudos

Hi,

Please, where is that parameter? how did you set it?

0 Kudos

Hello,

For general issues with the error 401 Unauthorized, please refer to note below maintaining

the same password for all the service users in all the places mentioned (SU01, Exchange

Profile, ...):

#999962 - PI 7.10: Change passwords of PI service users

Also check for users locked in the transaction.

Regards,

Caio Cagnani

Former Member
0 Kudos

Hi,

is there any additional information in the Attachment "HTMLError" ?

regards,

Daniel

iprieto
Contributor
0 Kudos

Probably if there is an error related ICM.

iprieto
Contributor
0 Kudos

Hi,

Could you attach the HTML Error Text please?

Regards

Ivá

Former Member
0 Kudos

Hi All,

Target system is working fine ...No issue .

All the roles are assigned to the messages .We are facing this problem from yesterday .Before that everything was fine ..

If you think any other reason please let me know .

Regards,,

Somenath

Former Member
0 Kudos

Does the user has necessary role assigned to send message to PI.

This may also be one the reasons to get failed in PI.

Shabarish_Nair
Active Contributor
0 Kudos

this might be due to the reason that the target system might have been down (is this a proxy call?).

hence during that time the call failed and when you restarted it worked.