ID, IR error when try to login ( JNDI related error)

[Former Member]

Hi Guys,

I have installed NW2004s ABAP and JAVA with PI and DI for XI usage ( we are SP8, NW2004s for ABAP, J2EE stack). We intend to use CMS for XI Java transports.

I have performed all the postconfig w/o any errors ( SLD, Import Basis SP7 repository content in IR, RWB etc..). and everything was working fine.

After I imported without any problems or errors ABAP SP7, SP8, BASIS SP8 repository content ( in IR)delivered by SAP I have problems to log in IR and ID ( SLD and RWB are working), getting the follow errors ( after click on ID or IR, got the login screen for user/pwd and after entering getting the error):

Unable to map from JNDI delivered class com.sap.engine.services.jndi.persistent.UnsatisfiedReferenceImpl

to class com.sap.aii.ib.sbeans.login.LoginServiceHome

registered during login service (CLASS_CAST_HOME)

I want to mention that DI was selected but no postprocessing was done in integreting DI( JNDI) with our PI.

Thank you, Virgil

[Former Member]

Hi,

Finally the error is gone.

We first applied:

966155 P4 Connection fails with NoClassDefFoundError or loops

without any success (not sure whether anything happened in the background).

And then:

609603 Problems with Multiple NICs and SAP J2EE Engine

Then we could log on to the Integration Builder without any problem.

Regards.

[Former Member]

Hi,

I have exactly the same issue as Virgil.

How did you sort it out?

In SM51 and SLDAPICUST, I have the same host names.

Also in the xiprofile.xml file, I have the same host names everywhere.

So what do I miss?

Regards.

[Former Member]

Lionel,

You try to increase the trace level and check the trace. Also see the log.

To increase the trace level, use the following URL:

Integration Directory: http://server:port/dir/support/private

Integration Repository: http://server:port/rep/support/private

Click on Edit Memory Log Configuration-->Reset to DEBUG --> Save

To check the log, use the following URL:

Integration Directory: http://server:port/dir/support/private

Integration Repository: http://server:port/rep/support/private

Click on View Memory Log --> Show this filter

Dont forget to Reset the log level to DEFAULT after your analysis and save to avoid performance problems.

If this dont help you try to see the J2EE Logs because all XI applications that run in the J2EE engine write their logs to the J2EE engine logs.

Check SAP Notes : 998481, 790075

Please go through this weblogs also:

/people/shabarish.vijayakumar/blog/2006/02/13/unable-to-open-iresrid-xipipi-71-updated-for-pi-71-support

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1688 [original link is broken] [original link is broken] [original link is broken] [original link is broken]

/people/sravya.talanki2/blog/2006/02/21/verifying-xi-components

Hope this helps.......

---Satish

[Former Member]

Hi Again,

Just to clarify that we did NW2004s ABAP+J2EE ( with PI and DI) and applied SP8 ( ABAP + J2ee+PI and DI components). There were no errors at all but now we do have errors connecting to IR and IB as I mentioned and I only could think that happened after importing Basis and ABAP Content SP8 in Integration repository ( wich was done as the latest activity in the env).

The error having trying to log in ID or IR of IB ( No errors to log in SLD or RWB)is:

Unable to map from JNDI delivered class com.sap.engine.services.jndi.persistent.UnsatisfiedReferenceImpl to class com.sap.aii.ib.sbeans.login.LoginServiceHome registered during login service

There is somebody which saw this error in the past? Any idea? As I said CMS is not enabled and nothing was done in customizing DI after installation ( Just PI piece).

Thank you much for any clues..

Virgil

[Former Member]

Hi Vrigil

I had the same problem in exactly the same version of NW2004sSR1 PI system A+J system on SP08 (no DI though). I initially used the alias name in the PI configuration. SO the hostname in the SM51 was different from the hostname used in the exchangeprofile configuration although they were the same host. I changed it to use the native hostname and restarted the PI. I no longer had that error.

Hope this helps.

Good luck.