Error in RWB

[Former Member]

Hi all,

The issue we are facing is related to RWB. Whenever we click on "performance monitoring " or othher monitoring like Component Monitoring , we are getting an error like

Unable to log on to system AXI in language EN with user PIRWBUSER

What could be the fix for the issue?

regards

krishna

[Former Member · Accepted solution]

Check the language settings in the ExchangeProfile for the runtime workbench.

[Former Member · Accepted solution]

Hi Barry

Thanks for your response.

I checked in the RWB.

It is EN

Thanks.

what else could be the problem??

regards

krishna

[Former Member · Accepted solution]

Check the language settings assigned to user is SU01.

can you post a screenshot of the error?

<a href="http://imageshack.us">Upload image at this link and post url</a>

Also, check all of these fields in ExchangeProfile

com.sap.aii.rwb.serviceuser.name

com.sap.aii.rwb.serviceuser.pwd

com.sap.aii.rwb.serviceuser.language

com.sap.aii.rwb.serviceuser.certificate

com.sap.aii.rwb.server.centralmonitoring.r3.ashost

com.sap.aii.rwb.server.centralmonitoring.r3.client

com.sap.aii.rwb.server.centralmonitoring.r3.sysnr

com.sap.aii.rwb.server.centralmonitoring.httpport

com.sap.aii.rwb.server.centralmonitoring.name

com.sap.aii.rwb.server.centralmonitoring.r3.mshost

com.sap.aii.rwb.server.centralmonitoring.r3.r3name

com.sap.aii.rwb.server.centralmonitoring.r3.group

Check the user has the following roles:

SAP_SLD_CONFIGURATOR

SAP_XI_RWB_SERV_USER

SAP_XI_RWB_SERV_USER_MAIN

[Former Member · Accepted solution]

Hi

here is a link

http://img412.imageshack.us/img412/5917/errorrwbxn1.png

I have also checked su01. its 'en' there too

regards

krishna

[Former Member · Accepted solution]

Thanks

I think the RWB user bit is a red-herring... It is an Intergration Server Issue and not a runtime workbench issue!

Can you provide the details from exchange profile for these? Is it using the PIISUSER?

IntegrationServer

IntegrationServer.MappingRuntime

com.sap.aii.mapping.root

com.sap.aii.ib.client.applicationname.runtime

com.sap.aii.ib.server.localbeanjndiprefix.runtime

com.sap.aii.integrationserver.serviceuser.certificate

com.sap.aii.integrationserver.serviceuser.language

com.sap.aii.integrationserver.serviceuser.name

com.sap.aii.integrationserver.serviceuser.pwd

I also think a Post installation task was maybe missed.

Check this from page 31 onwards:

http://help.sap.com/bp_bpmv130/Documentation/Installation/XI30InstallGuide.pdf

[Former Member · Accepted solution]

Hi

thanks on the update.

>>>Is it using the PIISUSER?

yes , it is.

the parameters are :

com.sap.aii.mapping.root <b>/xi/mapping</b>

com.sap.aii.ib.client.applicationname.runtime <b>sap.com/com.sap.xi.services/</b>

com.sap.aii.ib.server.localbeanjndiprefix.runtime <b>java:comp/env

</b>

com.sap.aii.integrationserver.serviceuser.certificate <b>I dont have this entry </b>

com.sap.aii.integrationserver.serviceuser.language <b>EN</b>

com.sap.aii.integrationserver.serviceuser.name PIISUSER

com.sap.aii.integrationserver.serviceuser.pwd ********

I also think a Post installation task was maybe missed.

Yes, We even suspect the same. we used a template installer. It threw an error at step 8 ,which we later completed manually ( as per a OSS note) .

Thanks and regards

krishna

[prateek · Accepted solution]

Check again if ur user PIRWBUSER is locked.

Also try changing the password to uppercase like if the password is "xyz" then change it to "XYZ" and try it.

Regards,

Prateek

[Former Member · Accepted solution]

Prateek

thanks 4 ur input but we have checked the lock on the user and it is not locked.

Change the password for PIRWBuser?? Dare we attempt to do after looking at the OSS note that lists the steps to maintain passwords in the event of a password change for a service user

regards

krishna

[Former Member · Accepted solution]

> Prateek

>

> thanks 4 ur input but we have checked the lock on the

> user and it is not locked.

>

> Change the password for PIRWBuser?? Dare we attempt

> to do after looking at the OSS note that lists the

> steps to maintain passwords in the event of a

> password change for a service user

>

> regards

> krishna

It's not as bad as it sounds, if it is just one user....

[Former Member · Accepted solution]

Barry

Thanks 4 ur encouragement

I have a question. As per the note, i am just wondering , why i need to update the passwords in the mentioned in the following help doc (and in the oss note) for other users like XIISUSER if we just have to change the password for PIRWBUSER.

http://help.sap.com/saphelp_nw04/helpdata/en/27/d22940cbf2195de10000000a1550b0/frameset.htm

Can you please clarify on that??

regards

krishna

[Former Member · Accepted solution]

You don't!

It just provides all the locations you need to change for all service users.

That's why I said it was not so bad for one user.

We made the mistake of losing the document that held the passwords for all service users and spent a while sorting this out (for every client!)

It's just the SM59 connections and ExchangeProfile for XIRWBUSER

[Former Member · Accepted solution]

hi

Thanks for your clarification. So, let me just confirm what need to be done.

I go ahead and do the following steps as mentioned in the help doc

<i>

Therefore, whenever you have to change the password of a service user, you must change it in the corresponding com.sap.aii.<component>.serviceuser.pwd entry in the exchange profile and also in the ABAP user administration (transaction SU01).

If you want to change the user itself, you must change both entries com.sap.aii.<component_A>.serviceuser.name and com.sap.aii.<component_A></i>

and then do just this part

<i> XIRWBUSER

&#9675; J2EE destination PMISTORE on J2EE servers with Adapter Engines.

&#9675; SM59 destinations PMI* on the central monitoring server.

&#9675; SM59 destinations maintained for GRMG scenarios (beginning with XI_* in transaction GRMG) on the central monitoring sever. See also SAP Note 634771</i>.

and don't care about other users.Right?

Also, i dont find any sm59 destinations for PMI* . is it OK??? the same is the case for GRMG

regards

krishna

[Former Member · Accepted solution]

That's it!

[Former Member]

Thank you all for your support. The problem was finally solved early this morning. the problem was because the RWB was referring to client 200 and that client did not have a PIRWBUSER in place. This was mainly due to the existence of a BS entry in the sld for client 200 when it was nolonger used anywhere. we solved the problem by removing the BS for client 200 in the SLD

Regards

krishna

[Former Member]

Hi,

Gud to knw ur problem is solved finally..

Regards,

Sumit

[Former Member]

Hi Krishna,

<i>Unable to log on to system AXI in language EN with user PIRWBUSER</i>

What you have to do is ask your basis team to create user PIRWBUSER in system AXI. The password of the user in AXI <b>should be the same</b> as the password of user pirwbuser in your xi server.

There is no need to change password of service user in XI.

Once your basis team creates the user you wont see the error anymore.

Regards,

Sumit

[Former Member]

Hi Sumit

Many thanks fr your response, which seems like it would eventually lead us to getting the problem solved

Actually, we have found that the RWB looks up for the PIRWBUSER from client 200 (IS) whereas the exchangeProfile settings all point up to client 100. What do you think is the cause of this strange behavior?

Note: we have set up IS for XI across 2 clients (001) and (200). Currently , we would like XI to use client 001 and for that the settings in the exchangeProfile are OK.

regards

krishna

[Former Member]

Hi Krishna,

<i>Actually, we have found that the RWB looks up for the PIRWBUSER from client 200 (IS) whereas the exchangeProfile settings all point up to client 100. What do you think is the cause of this strange behavior?</i>

Above statement is little confusing ...

Your basis team might have done a client copy and then maybe wanted to use Client 200 as integration server.

Refer this note 940309 for the list of areas where changes might have been done earlier. you can read that note and undo any changes.

Secondly is the system AXD your XI client?

Did you configure client 001 as IS?

In SLD is a bussiness system created for AXD client 001?

Also search in exchangeProfile the user PIRWBUSER. And check if correct password is maintained. Or better reenter the password and save .

Just check all the above .might solve your problem.

Regards,

Sumit

[Former Member]

Hi,

we dont find the PMI* rfc destination in sm59 as mentioned in the step.

is it ok? or we are missing something here??

thanks

krishna

[Former Member]

That is just CCMS monitoring that may have/have not been set up.

Same with the Java Admin Console changes.

[Former Member]

thanks. I'll check it up.

regards

krishna

[Former Member]

Try to create new user with all the Roles. chager Exchage profile with that user and password.

To create user : t-code SU01