cancel
Showing results for 
Search instead for 
Did you mean: 

Portal Error 500

Former Member
0 Kudos

I am getting the below error in portal while click on "Employee self service"

" An expception occured while processing your request. Send the exception ID to your portal administrator.

Exception ID:01:22_04/04/11/11_0001_106365150

Refer to the log file for details about this exception " .

Could you please some one help me to fix this.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Madavan,

Check you have created the system properly, all the tests are working fine. And have created the alias as per the standard and in the abap system all the relevant services are active.

Regards,

Rakesh

Former Member
0 Kudos

Hi Madhavan,

You will need to inform us the default trace.

Thanks

Former Member
0 Kudos

Hi ,

I would like to know where default is trace is located ?

Please help me

Madhavan K

Former Member
0 Kudos

Hi Madhavan,

Defaulttrace path will be under path

/usr/sap/<SID>/JC<instance no>/j2ee/cluster/server<n>/log/defaulttrace<n>.trc

If you have multiple server nodes configured, monitor the log closely on each server node during this error..or else paste the error here for review..

Regards

Suresh

Former Member
0 Kudos

Hi Suresh,

We have 2 servers configured (SAP0202 10 and SAP0202 11).

Find the default trace log below,

Default trace for server 0

#1.5 #005056A03918009300000040000042C40004A06794F66384#1302266649213#com.sap.jms#sap.com/irj#com.sap.jms.server.sessioncontainer.InboundBus instance=default#J2EE_GUEST#0##n/a##e582007c61dd11e0aac00000065700de#Thread[Thread-142,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerCommunicationException: Communication exception.

at com.sap.jms.server.JMSServerContainer.sendToRemoteRouterSynchronously(JMSServerContainer.java:882)

at com.sap.jms.server.JMSServerContainer.sendToRemoteDestinationContainerSynchronously(JMSServerContainer.java:975)

at com.sap.jms.server.routingcontainer.RoutingContainer.sendToDestinationContainerSynchronously(RoutingContainer.java:227)

at com.sap.jms.server.service.impl.RoutingServiceImpl.sendToDestinationContainerSynchronously(RoutingServiceImpl.java:57)

at com.sap.jms.server.sessioncontainer.handler.ConsumerHandler.onCreateRequest(ConsumerHandler.java:177)

at com.sap.jms.server.sessioncontainer.handler.ConsumerHandler.process(ConsumerHandler.java:79)

at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:144)

at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:117)

at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)

at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)

at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:576)

at com.sap.jms.server.SynchronousNetworkAdapter.sendAndWait(SynchronousNetworkAdapter.java:136)

at com.sap.jms.client.connection.Connection.sendPacket(Connection.java:657)

at com.sap.jms.client.session.Session.createConsumer(Session.java:2212)

at com.sap.jms.client.session.Session.createConsumer(Session.java:2141)

at com.sap.jms.client.session.QueueSession.createReceiver(QueueSession.java:67)

at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.createQueueReceiver(RTMFMessaging.java:835)

at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.recreateJMSConsumers(RTMFMessaging.java:1000)

at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1201)

at java.lang.Thread.run(Thread.java:534)

Caused by: com.sap.engine.frame.cluster.message.DestinationNotAvailableException: Participant 106,365,151 is not available.

at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendRequest(ClusterManagerImpl.java:2436)

at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.sendAndWaitForAnswer(MessageContextImpl.java:93)

at com.sap.jms.server.JMSServerContainer.sendToRemoteRouterSynchronously(JMSServerContainer.java:860)

... 19 more

Default trace for server 1

Loading model: {parent,references,local}

-


at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:382)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:141)

at com.sap.isa.core.init.InitDescription.getInitializable(InitDescription.java:79)

at com.sap.isa.core.init.InitializationHandler.checkInitHandler(InitializationHandler.java:406)

at com.sap.isa.core.init.InitializationHandler.performInitialization(InitializationHandler.java:234)

at com.sap.isa.core.init.InitializationHandler.performInitialization(InitializationHandler.java:309)

at com.sap.isa.core.init.InitializationHandler.initialize(InitializationHandler.java:219)

at com.sap.isa.core.ActionServlet.init(ActionServlet.java:139)

at javax.servlet.GenericServlet.init(GenericServlet.java:258)

at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)

at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:391)

at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:115)

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:104)

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

#

#1.5 #005056A03918002D000001F100002B240004A18176D6B921#1303477323530#com.sap.engine.services.monitor.config##com.sap.engine.services.monitor.config####n/a##5d8c939c6cde11e0878e0000065700df#SAPEngine_System_Thread[impl:5]_80##0#0#Error##Plain###[CRM Active Version Attribute] Equal groups,but with different description. Please change the group name to prevent errors.#

#1.5 #005056A03918002D000001F200002B240004A18176D6BC4F#1303477323530#com.sap.engine.services.monitor.common##com.sap.engine.services.monitor.common####n/a##5d8c939c6cde11e0878e0000065700df#SAPEngine_System_Thread[impl:5]_80##0#0#Error##Plain###error :Monitor configuration group with name [CRM Active Version Attribute] already exists.#

#1.5 #005056A03918002D0000025700002B240004A1817CFD9C57#1303477426776#com.sap.engine.services.monitor.config##com.sap.engine.services.monitor.config####n/a##5d8c939c6cde11e0878e0000065700df#SAPEngine_System_Thread[impl:5]_80##0#0#Error##Plain###[CRM Active Version Attribute] Equal groups,but with different description. Please change the group name to prevent errors.#

#1.5 #005056A03918002D0000025800002B240004A1817CFD9D4F#1303477426776#com.sap.engine.services.monitor.common##com.sap.engine.services.monitor.common####n/a##5d8c939c6cde11e0878e0000065700df#SAPEngine_System_Thread[impl:5]_80##0#0#Error##Plain###error :Monitor configuration group with name [CRM Active Version Attribute] already exists.#

#1.5 #005056A03918002D0000025900002B240004A1817CFD9DA0#1303477426776#com.sap.engine.services.monitor.config##com.sap.engine.services.monitor.config####n/a##5d8c939c6cde11e0878e0000065700df#SAPEngine_System_Thread[impl:5]_80##0#0#Error##Plain###[CRM Active Configuration Attribute] Equal groups,but with different description. Please change the group name to prevent errors.#

#1.5 #005056A03918002D0000025A00002B240004A1817CFD9DED#1303477426776#com.sap.engine.services.monitor.common##com.sap.engine.services.monitor.common####n/a##5d8c939c6cde11e0878e0000065700df#SAPEngine_System_Thread[impl:5]_80##0#0#Error##Plain###error :Monitor configuration group with name [CRM Active Configuration Attribute] already exists.#

#1.5 #005056A0391800780000000000002B240004A181818D90DF#1303477503363#com.sap.slm.exec.message.SLMApplication#sap.com/tcslmslmapp#com.sap.slm.exec.message.SLMApplication#J2EE_GUEST#0##n/a##231cb4086ce111e090ec0000065700df#SAPEngine_Application_Thread[impl:3]_7##0#0#Error##Java###null##

Now when i try to open the portal in the initial screen i am getting the error like " Message: Dispatcher running but no server connected! "

Could you please let me know how to fix this.

Madhavan K

Former Member
0 Kudos

Dear Experts,

Now i am getting "503 Service Unavailable" Error.

Madhavan K

Former Member
0 Kudos

Hi,

Is the connection from portal to ABAP backend working perfectly fine?

Check this using the Support tool in portal.

Rgds,

Soujanya

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Could you please paste corresponding error log from default traces ?

Thanks

Sunny

Former Member
0 Kudos

Hi Sunny,

Could you please let me konw how to ger the corresponding error log from default traces ?

Madhavan K