Application cannot be started

[Former Member]

Hello,

We have just upgraded our XI 3.0 to PI 7.1.

The upgrade finished successfully but we encounter problems to access some applications on the java side.

For example the links localhost:port/nwa, localhost:port/sld doesn't work.

In the logs we found that those applications don't start correctly.

Please see one example below.

"Application sap.com/tc_lmaci_appswd_uiresource cannot be started. Reason: it has hard reference to resource

tc_lmaci_appswd_uiaclog with type application, which is not active on the server."

Thu Sep 18 06:09:12 G

MT+00:00 2008##0#0#Error##Java###[ERROR CODE DPL.DS.5030] Clusterwide exception:

server ID 614813150:com.sap.engine.services.deploy.exceptions.ServerDeploymentE

xception: [ERROR CODE DPL.DS.5035] Application sap.com/tc_lmaci_appswd_uireso

urce cannot be started. Reason: it has hard reference to resource tc_lmaci~apps

_wdui~aclog with type application, which is not active on the server.

at com.sap.engine.services.deploy.server.ReferenceResolver.processRefere

nceToApplication(ReferenceResolver.java:843)

at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeRe

ference(ReferenceResolver.java:580)

at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartin

gApplication(ReferenceResolver.java:496)

at com.sap.engine.services.deploy.server.application.StartTransaction.be

ginCommon(StartTransaction.java:166)

at com.sap.engine.services.deploy.server.application.StartTransaction.be

gin(StartTransaction.java:134)

at com.sap.engine.services.deploy.server.application.ApplicationTransact

ion.makeAllPhasesOnOneServer(ApplicationTransaction.java:411)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.mak

eAllPhasesImpl(ParallelAdapter.java:498)

at com.sap.engine.services.deploy.server.application.StartTransaction.ma

keAllPhasesImpl(StartTransaction.java:554)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.run

InTheSameThread(ParallelAdapter.java:251)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.mak

eAllPhasesAndWait(ParallelAdapter.java:392)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicat

ionAndWait(DeployServiceImpl.java:3389)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicat

ionAndWait(DeployServiceImpl.java:3375)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicat

ionAndWait(DeployServiceImpl.java:3278)

at com.sap.engine.services.deploy.command.StartApplicationCommand.exec(S

tartApplicationCommand.java:159)

at com.sap.engine.services.shell.processor.environment.CommandBase.exec(

CommandBase.java:132)

at com.sap.engine.services.shell.processor.Interpreter.applyLineCommand(

Interpreter.java:401)

at com.sap.engine.services.shell.processor.Interpreter.apply(Interpreter

.java:153)

...

We tried to start the applications again via the java telnet console. Same error message.

Some other links like user management, webdynpro work very well. (The applications has been started correctly)

Any idea how to solve the problem?

Thanks in advance!

Best regards,

Olivier

[Former Member · Accepted solution]

Hi there,

Looks like some of the referenced applications are not started. Please use JCMON and do a

>lsc

>jump [server]

>add deploy

>start_app -all

See below link:

http://help.sap.com/saphelp_nw70/helpdata/EN/ae/01343ef3f9ff2de10000000a114084/content.htm

Thanks and Regards,

Sarvanan.

[Former Member · Accepted solution]

Hello!

Thanks but unfortunately we have already tried to start all applications with this command.

Same error message.

Best regards,

Olivier

[Former Member · Accepted solution]

Problem solved.

It was a problem with JMS configuration. 2 different applications had the same JMS ID.

[SD78 · Accepted solution]

Hi,

we have the same problem during the upgrade from xi 3.0 to pi 7.1 and found no oss note for this.

But this procedure help us:

1. Open a telnet connection

2. Type add jms

3. Type jms_list config_destinations

4. All JMS topics and destinations will be listed- around 70 entries

5. Copy them and find the duplicate ones (usually in the range 1-20)-look for the ID column

6. Open config tool and switch to edit mode (upper left corner button)

7. go to jms_provider node in the tree

8. Find by name the duplicate entries

9. Edit manually the ID value- for example if it is 7 make it 100007

10. Make that for all duplicate entries

Thank you to the sap developer, but write a official sap oss note.

Bye

Stefan

[Former Member]

Hi,

Is SLDCHECK running successfully. I mean with all checks green ?? Make sure it does first.

Also, since XI 3 and Pi 7.1 have different user names, please check for same in JCo RFC destinations, RFCs etc. Also, try to use server hostname instead of localhost to check.

regards, Sean.

[Former Member]

Hello,

No, sld has not been started. Same error message for sld application.

Best regards,

Olivier

[Former Member]

Ok, then check SLD Data Supplier in visual admin. Check if that service is running. If yes, try to send data to SLD from there first. If not, check usernames in tabs (which generally is SLDDSUSER) along with password as well.

regards, Sean.

[Former Member]

Here is the error we reveice when trying to launch the link localhost:port/sld

Application cannot be started!

Details: com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Naming error.

at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.loadDestination(JmsContainerImpl.java:1090)

at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.prepareStart(JmsContainerImpl.java:629)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:498)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)

at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:749)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:180)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:288)

at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:86)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)

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

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

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)

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

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of SLDClusterNotificationTopic.

Best regards,

Olivier

[Former Member]

Unfortunately Visual Administrator doesn't exist anymore in WAS 7.10.

It's is integrated in the web page localhost:port/nwa which doesn't work for us as the application has not been started correctly.

Best regards,

Olivier

[Former Member]

Hi,

Wow ..

I haven't worked on Netweaver 7.1 stack. VA doesn't exists is a new info .. (also a nightmare I guess, if we can't access it through nwa).

However, regarding your first error log, I believe we need to make sure that sap.com/tc_lmaci_appswd_uiresource and sap.com/tc_lmaci_appswd_uiaclog are running under:

Cluster -> Server -> Services -> SLD Data Supplier -> Runtime -> CIM Client Generation Settings

I'm sorry this sounds stupid on my part, but are all java nodes running? Are you able to get http://localhost:<port>/index.html ??

regards, Sean.

[Former Member]

Thanks for help!

yes we are able to display the home page where some links works and some others not.

The problem is that we cannot access the nwa. Impossible to check what you want.

Best regards,

Olivier

[Former Member]

Hi,

I found a guide, just in case if it can help, please check out for any missing step:

[https://websmp206.sap-ag.de/upgradenwpi71]

[https://websmp206.sap-ag.de/~sapidb/011000358700001186322007E]

I'll continue my search as well

regards, Sean.

[Former Member]

Thanks!

We followed the PI 7.1 upgrade guide and did all post upgrade activities.

Best regards,

Olivier