cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to log on to system SAPECC_SHD in language en with user PIRWBUSER1

Former Member
0 Kudos

Hi Frends,

Senario: JDBC(sender adapter) - XI(reciver adapter - proxy).

We are getting another error in RWB > integration engine > "Unable to log on to system SAPECC_SHD in language en with user PIRWBUSER1 Last Retry 15-Sep-2008 12:10:17 BST ... Details ".

We are getting this error while testing the our proxy runtime in integration engine.

-We have created the PI* <service user><1> in PI dev for solving our previous issue, We have maintianed the same user and all PI* service user in ECC too.

- In ECC PIRWUSER1 have theses roles(same as PI PIRWUSER1 user):

SAP_SLD_CONFIGURATOR,SAP_XI_RWB_SERV_USER,SAP_XI_RWB_SERV_USER_MAIN.

- Have maintianed the PIRWUSER1 user in XI adapter for login to ECC too.

- We have created the RFC: H type in ECC for communicate to PI with follwoing parameter:

Target host, service number(PI http Port), path prefix: of PI, log on detail - null, HTTP proxy option parameter - null, connection test: successfull.

Do we require to maintain RFC: H type from PI to ECC? to solve this issue and

Could you help out to solve this issue if you ever come accross such.

Thanks and Regards,

Dushyant.

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

there was bug in SAP exchange profile, SAP developers log on and solved and we have to reinstall some component.

Former Member
0 Kudos

there was bug in SAP exchange profile, SAP developers log on and solved and we have to reinstall some component.

Former Member
0 Kudos

Hi Dushi,

you have to establish HTTP connection from R/3 to XI and XI to R/3 ,

also use SLD check,

Former Member
0 Kudos

Hi NetWeaver Expert ,

Already there is RFC h type from ECC to PI with following detial:

We have created the RFC: H type in ECC for communicate to PI with follwoing parameter:

Target host, service number(PI http Port), path prefix: of PI, log on detail - null, HTTP proxy option parameter - null, connection test: successfull.

there is already one RFC of H type from PI to PI itself named "INTEGRATION_DIRECTORY_HMI" path prefix: /dir/CacheRefresh for CACHE refresh.

Do you eman we need to create RFC H type from PI to ECC too? if yes with which user?

Thanks

dushyant.

Former Member
0 Kudos

Hi Dushyant,

So you are trying to send a message via proxy from XI to your ECC, is it correct?

If so your cannot use PIRWBUSER to communication pourposes. Instead, use PIAPPLUSER user in your receiver XI Communication Channel.

Set SAP_ALL to this user in your ECC and try to run your scenario.

Regards,

Carlos

Former Member
0 Kudos

hi Carlos Gonzalez ,

Intitially there was my own user name of ECC, though we were getting same error in RWB> inegration engine > proxy runtime - that "unable to logon with PIRWUSER1",

now we change to PIRWUSER1, but though same error.

SO i dont think so by changing to PIAPPLUSER in XI reciver comm. channel problem will be solved,

what you say?

thanks.

dushyant.

Former Member
0 Kudos

Hi Dushyant,

So, your problem is different.

PIRWUSER user is used to retireve data and displayed it in Runtime Workbench for monitoring pourposes of your R3 Backend proxy.

You must not use PIRWUSER1 or something like that. So, change it in Exchange profile.

This user (PIRWUSER must be created in your R3 Backend with the same roles that in XI and the same password that in XI).

However, in order to configure your Receiver communication Channel you should use PIAPPLUSER because this user has the roles needed to execute the proxy.

This user also is needed to be created in the R3 backend with the same password than in XI and with SAP_ALL.

I think if your try this, your scenario will work.

Regards,

Carlos

Former Member
0 Kudos

Hi Carlos Gonzalez

Its not working.

thanks.

Former Member
0 Kudos

Hi Dushyant,

Have you checked if there is any user locked (PIRWUSER) in both systems, XI and R3.

If you changed any password or parameter in Exchange profile you must reloaded the Exchange profile or restart java stack.

Try to log on with PIRWUSER in your R3.

Carlos

Former Member
0 Kudos

Hi,

Thats everything is fine.

thanks.

former_member183906
Active Contributor
0 Kudos

check role assigned to PIRWBUSER1

SAP_SLD_CONFIGURATOR

SAP_XI_RWB_SERV_USER

SAP_XI_RWB_SERV_USER_MAIN

There may be problem in exchange profle parameters...

Com.sap.aii.rwb.serviceuser.name

Com.sap.aii.rwb.serviceuser.pwd

Com.sap.aii.rwb.serviceuser.lang

check it

and ensure that the role of the business sytem in (sxmb_adm) is integration server

check this thread

Former Member
0 Kudos

Hi friends,

My exchange profile parameter for RWB are:

user: pirwbuser1

password: ****

language: en

and in sxmb_adm also there is Integration server as bussiness sytem.

Thanks.