cancel
Showing results for 
Search instead for 
Did you mean: 

IDES ERP 2005 SR2 sapinst error during SLD configuration

Former Member
0 Kudos

Sapinst is reporting a java error during SLD configuration.

CJS-30059 Java EE Engine configuration error.<br>DIAGNOSIS: Error when configur

ing J2EE Engine. See output of logfile java.log: 'JSE'.]]></line><line><![CDATA[

ERROR 2009-02-12 12:58:29

FCO-00011 The step configSLDMainLocalMapSecRolesToUsers with step key |NW_Oneho

st|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|N

W_Usage_Types_Configuration_AS|ind|ind|ind|ind|0|0|NW_CONFIG_SLD|ind|ind|ind|ind

|0|0|configSLDMainLocalMapSecRolesToUsers was executed with status ERROR .]]></l

ine></sapinstlog>

The java log reports:

ConfigMainExt state503

TYPE=A<BR>STATE=503<BR>INFO_SHORT=Error connecting to http://paxbi:50000/ctc/Con

figServlet?param=com.sap.ctc.util.SecurityRoleConfig;MAP_SECURITYROLE_TO_USER;RO

LE=DataSupplierLD,USER=SLDDSUSER,COMPONENT=sap.com/com.sap.lcr*sld,HOST=paxbi,P4

PORT=50004,J2EE_ADMIN=J2EE_ADMIN,J2EE_PASSWORD=des19(66|17|139|163|51|195|246|60

|147|54|). The provided user data might be incorrect or user might be locked.<BR

>CONFIGURATION=

Going to http://host:50000/sld reports:

503 Service Unavailable.

Dispatcher running but no server connected!

I am able to login via sapgui as user J2EE_ADMIN/<master passwd> on client 01.

Accepted Solutions (1)

Accepted Solutions (1)

former_member204746
Active Contributor
0 Kudos

SLD is a JAVA-Stack tool, not ABAP-Stack tool.

so, logging into your system with SAPGUI does not mean that your JAVA-Stack is up and running.

check status of your java stack, it is probably down. from your Unix machine, you MUST be able to connect to http://host:50000

Former Member
0 Kudos

Running browser on my hpux-ia64 box, http://<host>:50000/ also gives same error:

503 Service Unavailable.

Dispatcher running but no server connected!

I see 3 java exe running.

1) for sapinst gui serving port 21212,

2) for oracle

3) for sapinst gui for port 21200

How do I check/restart the java stack?

The last entry in the server0/log/defaultTrace.0.trc is:

#1.5#E6E9A265F3D0007A0000006500000BC6000462B9D4908F79#1234450181557#com.sap.engi

ne.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadM

anagerImpl#J2EE_GUEST#0#####Thread[Thread-1199,5,main]##0#0#Error##Plain###Unexp

ected thread activity after interrupt() is executed in shutdown of SAPEngine_App

lication_Thread[impl:3]_ThreadManager:

Thread[SAP_AFScheduler.Broker]

Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname

: com.sap.aii.af.service.scheduler.JobBroker$Broker | toString: com.sap.aii.af.s

ervice.scheduler.JobBroker$Broker@4f4c535d] with classloader [com.sap.engine.cor

e.service630.container.ComponentClassLoader@3cdb8522@service:com.sap.aii.af.svc]

The last entry in the server0/log/applications.0.log is :

#1.5#E6E9A265F3D0005E0000035C00000BC6000462B9D48E2710#1234450181400#/Application

s/ExchangeInfrastructure##com.sap.aii.utilxi.sld.SldUtil#J2EE_GUEST#0#####SAPEng

ine_Application_Thread[impl:3]_18##0#0#Error#1#com.sap.aii.utilxi.sld.SldUtil#Pl

ain###root cause:

Thrown:

java.security.PrivilegedActionException: null

at com.sap.aii.utilxi.rtcheck.mx.MBeanServerProxy.run(MBeanServerProxy.j

ava:69)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.aii.utilxi.rtcheck.mx.MBeanServerProxy.initialize(MBeanServer

Proxy.java:56)

at com.sap.aii.utilxi.rtcheck.mx.MBeanServerProxy.<init>(MBeanServerProx

y.java:46)

at com.sap.aii.utilxi.sld.SldUtil.getMBeanServer(SldUtil.java:586)

at com.sap.aii.utilxi.sld.SldUtil.setHostAndPortsIfNull(SldUtil.java:554

)

at com.sap.aii.utilxi.sld.J2EESystem.getHostName(J2EESystem.java:69)

at com.sap.aii.utilxi.sld.XISubSystem.getHostName(XISubSystem.java:781)

at com.sap.aii.utilxi.sld.SldAccessor.createAccessClients(SldAccessor.ja

va:112)

at com.sap.aii.utilxi.sld.SldAccessor.actFor(SldAccessor.java:91)

at com.sap.aii.utilxi.sld.SubSystemFactory.createXISubSystemWithoutServi

ces(SubSystemFactory.java:201)

at com.sap.aii.utilxi.sld.SubSystemFactory.createXISubSystemFromAiiProps

(SubSystemFactory.java:123)

at com.sap.aii.utilxi.sld.SubSystemFactory.createXISubSystemFromAiiProps

(SubSystemFactory.java:97)

at com.sap.aii.af.service.sld.SLDAccess.getISData(SLDAccess.java:228)

at com.sap.aii.adapter.xi.ms.SLDReader.fire(SLDReader.java:60)

at com.sap.aii.adapter.xi.ms.SLDReader.run(SLDReader.java:167)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:3

7)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.ja

va:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:1

70)

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: E

rror getting the server-side naming service functionality during getInitialConte

xt operation.

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialCont

ext(InitialContextFactoryImpl.java:243)

at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefau

ltInitCtxt(DefaultInitialContext.java:65)

at com.sap.engine.system.naming.provider.DefaultInitialContext.getURLOrD

efaultInitCtx(DefaultInitialContext.java:131)

at javax.naming.InitialContext.lookup(InitialContext.java:347)

at javax.naming.InitialContext.lookup(InitialContext.java:347)

at com.sap.aii.utilxi.rtcheck.mx.MBeanServerProxy.lookUpMBeanServer(MBea

nServerProxy.java:100)

at com.sap.aii.utilxi.rtcheck.mx.MBeanServerProxy.run(MBeanServerProxy.j

ava:65)

... 19 more

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: T

he JNDI Registry Service is not started.

former_member185031
Active Contributor
0 Kudos

I guess you should login through Visual Administrator using J2EE_ADMIN and check that its running or not, and if the password is not working then search in service marketplace how to reset the password of J2EE_ADMIN, i dont remeber the note number right now.

Regards,

Subhash

Former Member
0 Kudos

http://paxbi.atl.hp.com:50000/ still reports service unavailable.

Started Visual Admin, but can't connect. Gives error while connecting.

User: J2EE_ADMIN, HOST: <hostname>, Port 50004. Using master passwd for J2EE_ADMIN.

Unable to logon

end of stream is reached unexpectedly during input from Socket[addr=/<IP addr>,port=50004,localport=64588]

Started JCmon, shows server0 stopped with error count 4.

I was not able to restart process. I checked the server0 logs in work dir, but no updates since 2/12.

Why is this the case, if server0 restart was attempted?

I restarted the instance. This time, server0 came up fine.

Connection to http://paxbi.atl.hp.com:50000/ works and I was able to login as J2EE_ADMIN w/ master pwd OK.

I'm also able to connect via Visual Admin.

I've restarted the sapinst process, which quickly progressed to phase 42/97 to again attempt to configure the SLD. I had specified a local SLD, since its the first SLD in the landscape, besides the local SLD on the Solution Mgr system. Its my understanding that the SM can not host the global SLD and the SM SLD was the first in the landscape, therefore, I created it local.

I'll let you know if I get past step 42.

Thanks for your help.

former_member201054
Contributor
0 Kudos

For Sever0 problem ensure the sufficient memory size because at times if JAVA memory is less ,it would take much time to up the related services or would not start .

Check the status of J2EE users in 001 client by SUIM

Former Member
0 Kudos

I was able to get past the step configSLDMainABAPBridge. It failed on retry, but succeeded on restart of sapinst /w the continue with existing install.

sapinst proceeded to the next steps and got following error:

ERROR 2009-02-17 16:29:29

MUT-03010 Execution of the command "/tmp/sapinst_exe.4450.1234893546/XTCC /tmp/

sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/xi_profile_adjust_values.xsl xi_profil

e_adjust_values.xti" finished with status TST_ERROR.

ERROR 2009-02-17 16:29:29

FCO-00011 The step Perform_XSL_Profile_Conversion with step key |NW_Onehost|ind

|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Usag

e_Types_Configuration_PI|ind|ind|ind|ind|1|0|PiExchangeProfile|ind|ind|ind|ind|5

|0|Perform_XSL_Profile_Conversion was executed with status ERROR .

Again, a retry failed, but restarting sapinst worked. Other users reported the same issue and get-around.

My install completed successfully.

I ran SUIM tx on client 001 and viewed all the users. I did not see any problems, but not sure what to look for. I looked at Users, Groups, Roles, etc.

I know I'm probably tight on the JVM memory. I'm running with max heap size 1GB. Physical memory size is 4.5GB. (HPVM client). I had attempted to increase the size using ConfigTool to 1.5GB for JVM, but just seem very slow. I need to figure out how to feed the GC data HPjmeter for HPUX systems. I'm reading the note 1053604 "JDK heap dump and heap profiling on HPUX", which should have info I need.

I may have more questions, but will work that out in a separate thread.

Thanks for all your help, and everyone's help. I have completed the sapinst step.

Answers (2)

Answers (2)

Former Member
0 Kudos

one more thing:i feel its related to some user or password issues

as the java.log says"The provided user data might be incorrect or user might be locked"

just check in DB whether this user exists,if not create the user

if it is there ,check whether if it is locked?

I am just saying what the logs are telling but this can be quite useful

Rohit

Former Member
0 Kudos

Hello Don,

Can you clear me few things

what did u select while configuting SLD for ERP installation?

what were the values that you gave

Rohit