Message Monitoring issue during XI replacing

[Former Member]

Hi XIer,

Due to hardware replacement, so what we are doing is replace QXI( XI testing system) with a new hardware. So we have installed another new XI to replace old QXI.It look ok when we installed new QXI. Because we are using centre SLD to maintain the system info on QXI, so we need to push DXI and PXI info to new SLD on QXI.

the problem comes out when we pushed DXI and QXI info to SLD, we log on to DXI, open RWB->message monitoring->integration engine, then we got following error:

javax.ejb.CreateException: Unable to log on to system SXI in language en with user PIRWBUSER

When I click Message Monitoring again, the error message changes to:

com.sap.aii.utilxi.misc.api.UnexpectedException: Internal Error: An unexpected error occurred (java.lang.NullPointerException: null)

Anyone can give me some suggestions? thank you very much for your effort~

[Former Member]

Hi again

just check if the users exits in ABC system

if not you can create it:

http://help.sap.com/saphelp_nw2004s/helpdata/en/87/ca12416c17ef6fe10000000a1550b0/content.htm

more about service users and their role descriptions:

http://help.sap.com/saphelp_nw04s/helpdata/en/56/361041ebf0f06fe10000000a1550b0/content.htm

check the password that is written in the http://host:j2ee_port/exchangeProfile

i think it will help you...

[Former Member]

Hi Zhang,

The EJBException exception is thrown by an enterprise Bean instance to its container to report that the invoked business method or callback method could not be completed because of an unexpected error (e.g. the instance failed to open a database connection).

public class RemoveException

extends Exception

The RemoveException exception is thrown at an attempt to remove an EJB object when the enterprise Bean or the container does not allow the EJB object to be removed.

for your more help

http://publib.boulder.ibm.com/infocenter/wsphelp/index.jsp?topic=/com.sun.j2ee.api.doc/javax/ejb/Cre...

If your interface implementation class is private then

try changing your method declaration from

private to public

*PS: Reward points if useful**

[aashish_sinha]

Hi

Check out if user exist in the system. if exists then check the following :

Can you please check the Role of PIRWBUSER using SU01 and provide the roles

SAP_SLD_CONFIGURATOR

SAP_XI_RWB_SERV_USER

SAP_XI_RWB_SERV_USER_MAIN.

If it is already there the try to check

com.sap.aii.rwb.serviceuser.name

com.sap.aii.rwb.serviceuser.pwd

com.sap.aii.rwb.serviceuser.language

in exchange profile.

Ccheck out here if user doesn't exists http://help.sap.com/saphelp_nw2004s/helpdata/en/87/ca12416c17ef6fe10000000a1550b0/content.htm

regards

Aashish Sinha

PS : reward points if helpful

[Former Member]

Before we replace the QXI system, every thing runs ok, so I don;t think we will miss any user in business system~~

[aashish_sinha]

Then you check the roles and for precaution please check out the users also.

regards

Aashish Sinha

[Former Member]

Can you restart J2EE engine

Go to

1. tcode smicm

2. j2ee local instance

3. send soft shutdown

4. with restart.

I think this should allow you to login.

PS: reward points if it is helpful

Vishal

[Former Member]

I have restarted QXI system, but result is the same.