Visual Admin - Dispatcher - Monitoring Node issue
Hi all,
On a PI 7.0 SP13,
In visual admin, the monitoring node of the dispatcher section doesn't start fully :
Only both tabs "Properties" and "Additional Infos" are available.
When we try to start the Monitoring service manually, we got the following error message :
Start service Monitoring
java.rmi.RemoteException: Could not start service monitor on cluster ID 4226000; nested exception is:
com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Service monitor error. Nested exception is: java.lang.NoClassDefFoundError: com/sap/mona/api/MonitoringNode
at com.sap.engine.services.monitor.common.MonitorServiceRuntime.installCcmsConnector(MonitorServiceRuntime.java:662)
at com.sap.engine.services.monitor.dispatcher.MonitorDispatcherFrame.start(MonitorDispatcherFrame.java:53)
at com.sap.engine.frame.CommunicationFrameAdaptor.start(CommunicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Service monitor error. Nested exception is: java.lang.NoClassDefFoundError: com/sap/mona/api/MonitoringNode
at com.sap.engine.services.monitor.common.MonitorServiceRuntime.installCcmsConnector(MonitorServiceRuntime.java:662)
at com.sap.engine.services.monitor.dispatcher.MonitorDispatcherFrame.start(MonitorDispatcherFrame.java:53)
at com.sap.engine.frame.CommunicationFrameAdaptor.start(CommunicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
Do you have an idea to solve this issue.
Thanks a lot in advance
Edited by: Jean-Charles on Feb 14, 2008 5:02 PM
It is correct one
sorry
The monitoring service is red cross marked as it is not started. when we do rigth click and start we have the message quoted above...
Similar Messages
-
Installing SAP Java License without Visual Admin
Hi All,
I installed a stand alone SAP Java instance a couple of months ago and the temp license key has expired.
I have applied for a perm license key, which I now have.
Here is my main issue:
1. The JControl service will not start because it "failed license check"
2. The Java VM won't start because of issue "1".
3. I can't start the Visual Admin tool because of issue "2".
Hope that all makes sense :-s
Main Question:
Does anyone know how to install my new license WITHOUT using the Visual Admin tool?
Thanks to anyone who responds.
PS: I do credit responses if they are helpful
Edited by: Paul Baverey on Jan 23, 2009 12:44 PMHi Tobias,
Incase if we miss that 30 mins to update the license, how can we install the new license. Is there any possible way to update from configtool?
Thank you,
Kasi -
MS SQL Server JDBC 2.0 datasource creation issue using Visual Admin
Hi,
I need to create an MS SQL Server JDBC 2.0 DataSource using the Visual Admin (running on NetWeaver 2004 SP19). I'm using the Microsoft SQL Server 2005 JDBC driver. Have no problem creating a Version 1.x (no XA support) DataSource.
The issue is that when I try to create a Version 2.0 (with XA support) datasource I get the following exception: java.sql.SQLException: Invalid DataSource reference
This is the setup I used:
JDBC Version "2.0 (with XA support)
JDBC 2.0 Compliant:
object factory: com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory
datasource type: XADataSource
xads class name: com.microsoft.sqlserver.jdbc.SQLServerXADataSource
On the additional tab:
databaseName=fldev_jj
portNumber=1433
serverName=dbsrv61
user=fldev_jj
password=******
Even added the url, but that made no difference. Chose Vendor SQL,
and have initial connections set to 1. This url worked when used
with a version 1.x datasource.
What can I try to do to resolve this?
Full exception:
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "factorylogic.com/FactoryLogicBusinessDS". [id = StartupError]
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
... 42 more
Caused by: java.sql.SQLException: Invalid DataSource reference.
at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
... 43 more
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
... 31 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
... 42 more
Caused by: java.sql.SQLException: Invalid DataSource reference.
at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
... 43 more
at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
... 33 more
at com.sap.engine.services.dbpool.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:178)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1016)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
at javax.management.MBeanException.writeObject(MBeanException.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1309)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:177)
at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)
at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)
at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1272)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1250)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)Leaving the object factory empty is absolutely part of the solution.
I can now start the data source and it can get a connection.
The remaining problem is that the moment I try to do anything with xa (inside of netweaver, using the datasource) I get an xa error... Found a way around that by changing the datasource type from "XADataSource" to a "ConnectionPoolDatasource".
The problem with that is that I'm no longer sure it uses XA transactions...
Will do more testing...
Very helpful reply Yuri!
Thanks -
ISE admin , PSN and monitoring node fail-over and fall back scenario
Hi Experts,
I have question about ISE failover .
I have two ISE appliaces in two different location . I am trying to understand the fail-over scenario and fall-back scenario
I have gone through document as well however still not clear.
my Primary ISE server would have primary admin role , primary monitoring node and secondary ISE would have secondary admin and secondary monitoring role .
In case of primary ISE appliance failure , I will have to login into secondary ISE node and make admin role as primary but how about if primary ISE comes back ? what would be scenario ?
during the primary failure will there any impact with users for authentication ? as far as PSN is available from secondary , it should work ...right ?
and what is the actual method to promote the secondary ISE admin node to primary ? do i have to even manually make monitoring node role changes ?
will i have to reboot the secondary ISE after promoting admin role to primary ?We have the same set up across an OTV link and have tested this scenario out multiple times. You don't have to do anything if communication is broken between the prim and secondary nodes. The secondary will automatically start authenticating devices that it is in contact with. If you promote the secondary to primary after the link is broke it will assume the primary role when the link is restored and force the former primary nodes to secondary.
-
Dispatcher service is yellow and unable to start visual admin.
Hello all:
Here is my new problem.
Everything was going fine untill I finished the post installation activites on PI7.0. I am not sure if I missed any step or not.
After the changes I stopped the instance and restarted it and the "Disp+word.exe" is yellow with the message <b>"Running, Message Server connection ok, Dialog Queue time: J2EE:Some Processes running".</b>
I can't connect to Visual admin. Getting an error when hit connect "<b>unable to loockup connection default, http:
sapinst001:8010/msgserver/text/logon returned empty list of conneciton parameters"</b>
Check the log files and here are some info from them:
Dev_Server0:
Thr 1644] *** WARNING => INFO: Unknown property [instance.box.number=PI7DVEBMGS00sapinst001] [jstartxx.c 841]
[Thr 1644] *** WARNING => INFO: Unknown property [instance.en.host=sapinst001] [jstartxx.c 841]
[Thr 1644] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]
[Thr 1644] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]
Can you please help me with this? I need to finish this install by Monday.
Regards,
N.SIt's important to understand if the dispatcher is not running or just the server is not running: try to look to the log files
/usr/sap/<SID>/DVEBMGS<nr>/work/dispatcher
/usr/sap/<SID>/DVEBMGS<nr>/work/server0
and
/usr/sap/<SID>/DVEBMGS<nr>/j2ee/cluster/server0/log/defaultTrace.trc
You should find the error that prevent the java application to start.
The more common reason are the inability to detect the path of JRE or some parameter wrong in the configtool
Regards
Sandro -
Visual admin and start/stop dispatcher
What is the normal procedure for starting and stopping dispatcher....
Is it normally done at UNIX through ./go script? and what is the normal way to shutdown j2ee engine....
just wonder what the standard practice was...
Also where do I find the Visual admin tool...is this under the admin filesystem and just run go....
Thanks
John RyanCheck if you DEFAULT.PFL contain the following entries
SAP Central Service Instance for J2EE
j2ee/scs/host = <host>
j2ee/scs/system = <SCS Inst.No>
j2ee/ms/port = <port>
j2ee/dbtype =
j2ee/dbname = <sid>
j2ee/dbhost = <host>
And the Instance Profile should have the followin entries
Instance Profile
jstartup/trimming_properties =
jstartup/protocol =
jstartup/vm/home =
jstartup/max_caches =
jstartup/release =
jstartup/instance_properties =
j2ee/dbdriver =
rdisp/j2ee_start_control =
rdisp/j2ee_libpath =
exe/j2ee = $
j2ee/instance_id = -
Experts ,
I want to know about Visual Admin and ConFig Tool and in How many ways they are used
list out all briefly ,
Thanks in Advance,
PhaniHi Phani,
The J2EE Engine Visual Administrator is a graphical user interface (GUI) that enables administration of the whole cluster, all cluster elements, and all modules running on them. It provides remote monitoring and management of managers, services, libraries, and interfaces working on each element in a single GUI
Visual Administrator includes functions for:
a) Obtaining general information about a service, manager, interface, or library (for example, its name, group, and so on).
b) Logging on to the J2EE Engine via the Visual Administrator tool
c) Administrating and changing the properties either specific or common for each service or manager
d) Configuring the global properties
e) Runtime administration and control.
Read out more about its features on [VISUAL ADMINISTRATOR|http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm]
CONFIG TOOL :-
The Config Tool enables offline configuration of the J2EE Engine cluster elements. It is XML-based and allows exporting the system configuration for later use.
When you run the J2EE Engine Config Tool via a GUI or text-only interface, it connects to the database and scans the server configuration. The information provided is passed to the corresponding interface that is used for configuration.
Each change you can perform corresponds to a particular task in the Batch Config tool.
All modifications made using the J2EE Engine Config Tool can be exported to an XML file for later use.
two types:-
a) GUI Config tool :- The J2EE Engine GUI Config Tool enables offline configuration of J2EE Engine cluster elements concerning serviceu2019s and manageru2019s properties, adding new server processes, changing Java parameters, exporting the system configuration to an XML file, and so on.
After installing the SAP Web AS Java, a configtool directory is created, containing a configtool script file. Double clicking on this file starts the Config Tool.
b) Text Only Config tool:- The text-only Config Tool enables you configuration of J2EE Engine cluster elements using a text-only based interface. It enables you to change the cluster element properties, JVM settings, add new elements, export the system configuration to an XML file, and so on.
After installing SAP Web AS Java, a configtool directory is created under <SAP_install_dir>/<system_name>/<instance_name>/j2ee, containing a consoleconfig script file. Double clicking on this file starts the text-only Config Tool.
Read more about config tool on [CONFIG TOOL|http://help.sap.com/saphelp_nw04/helpdata/en/e8/f48b33f9a3423c9e688dfa56330e79/frameset.htm]
Hope this helps,
Regards,
Shailesh -
Hello,
I am trying to install XI 7.0 (NW 2004s). The installation was error-free. However, while doing post installation steps, Visual Admin threw a 'Session expired' error. Since then, I am unable to login to Visual Admin using J2EE_ADMIN (throws "Authentication did not succeed" error). I have activated SAP* user using configtool, and unlocked J2EE_ADMIN. I have also changed J2EE_ADMIN password several times using SAP GUI.
But still, the error persists.
Please let me know if anyone has a solution.
Thanks in advance
ParthaHi Partha,
Try opening Visual Admin if your not able to login with username(administrator) and password. Problem with NWD2004s do the following steps.
C:\usr\sap\J2E\JC01\j2ee\configtool->configtool.bat->open it
1. Click on Secure store
2. Right you will find :
admin/password/J2E->retype your admin passowrd which you gave during installation=>SAVE properly
Restart the server and try login visual admin
Now ur able to login visual admin right follow the steps:
Try here If ur not able to login http://<server name>/irj/portal :home page using (username)administrator and password
do the following steps(user locked).
(**Administrator locked so we have enable superadmin and unlock the administrator and again diasble the super admin
then only can able to login using administrator**)
=>Activating emergency(super admin) user:-
1. Start configtool
2. set the following properties: [Instance_ID<ID> -> Server_ID<ID> -> services -> com.sap.security.core.ume.service]
a. ume.superadmin.activated - true
=>i doubht here did u saved properly
b. ume.superadmin.password - <password> [set the password->click set button->
it will again ask by open popup window type the same and it will say restart to reflects]
3. Restart Java Application server
Unlocking administrator:
Login to Portal Page => http://<severname>/irj/portal
Give username:SAP* and password which u typed
=>under user management tab ->click on search user left pane -> search label followed by input field will be there ->give * in inputfield and click search button->
you can we view ALL users and roles etc.
select user administration by clicking on check box ->modify->reset the password->save properly
Again diable super admin go to
1. Start configtool
2. set the following properties: [Instance_ID<ID> -> Server_ID<ID> -> services -> com.sap.security.core.ume.service]
a. ume.superadmin.activated - false->save it will ask u restart is must for reflect the settings
3. Restart Java Application server
Go to http://<severname>/irj/portal
Give username:aministrator and password which u typed
hopefully i should solve ur problem
Regards, Suresh KB -
Hello sdn,
while I navigate to j2ee folder ,I dont see admin folder.
I am logging on as SIDADM
I want to open visual administrator. I am using PI 7.1.
Can you suggest how to open visual admin?
ThanksHi,
/people/suneet.agera/blog/2008/02/18/sap-landscape-administration-and-java-system-administration-an-overview
Thanks
Anil -
Error while Loggin inot VISUAL ADMIN-No login module succeeded.
Hi,
I am trying to login to the Visual Admin for the first time for my new Portal System (Quality).
But I am getting error while loggin in with Administrator user:-
com.sap.engine.services.security.exceptions.BaseLoginException: No login module succeeded.
The visual_administration.0.trc file shows the following:-
1.5 #C000AC117C1900010000000159CB59CB000455D3152A8478#1220264988408#com.sap.engine.services.adminadapter.gui.tasks.LoginTask##com.sap.engine.services.adminadapter.gui.tasks.LoginTask#######Thread[Thread-15,6,main]##0#0#Error#1#/System/Server/VisualAdministrationTool#Java###Error while trying to login to SBQEP: No login module succeeded.
[EXCEPTION]
#1#com.sap.engine.services.security.exceptions.BaseLoginException: No login module succeeded.
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:188)
at java.security.AccessController.doPrivileged(AccessController.java:231)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:181)
at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:72)
at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
predecessor system -
com.sap.engine.services.security.exceptions.BaseLoginException: No login module succeeded.
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:188)
at java.security.AccessController.doPrivileged(AccessController.java:231)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:181)
at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:72)
at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Have reffered SAP Note 957355 and performed the steps given in the note,but still the same error.
I am able to login to the PORTAL with the same Administrator user and password.
Pls suggest where could be the issue and how to process.
Regards,
AbhijeetProblem solved. ... No, I have also an answer , perhaps it can help some other peoples.
As I said there is a note 957355. I create the entrys in offlineconfigtool, but nothing happens. So I checked the other entrys in the "configuration" node in "security" (the note 957355 treated the authentication entry) , like "UME User Store" "ticket" and so on. I've taking another system and ckecked this entrys and compare it with my system. So I could restore the default entrys in all security nodes (for authentication). After an restart - voila, it workes.
greetings
ps.: hm, can I give some points for me? -
Difference between config toll and visual admin
HI all,
Please let me know all Difference between config toll and visual admin.
and Purpose and how to start.
Thanks & Regards,
satish kHi Satish,
SAP J2EE Engine 6.20 provides three basic tools for administration u2013
Visual Administrator,
Console Administrator, and
Config Tool (both Visual and Console).
There are some other tools namely DBTool, Library Tool, RMIC Tool, Shutdown Tool, and User Tool also used.
First part
Difference between config toll and visual admin:-Visual Administrator is a graphical user interface (GUI) that enables administration of the whole cluster, of the cluster nodes, and all modules running on them.On the other hand with the help of Config Tool you are able to add and configure SAP J2EE Engine 6.20 cluster elements.Again Config Tool can be used without a running SAP J2EE Engine 6.20. The only requirement is to have the server installed on the local machine.
Visual Administrator is written in the Java programming language and can be run in any environment where a Java Virtual Machine is available.On the other hand Config Tool is XML-based, which enables third-party visualizations to be developed or integrated as part of a more complicated configuration system.
Visual Administrator enables remote monitoring and management of the cluster, and for each cluster element, and enables the system administrator to monitor all managers and services working on each node in a single GUI & its online.cofig tool on the otherhand offline.
Second part Purpose
"Visual Administrator":-with the help of this tool you can able to login & logout from the server.It gives you all the details regarding different services running in your SAP server.As already mentioned that with the help of VA we enables administration of the whole cluster, of the cluster nodes, and all modules running on them.
"Config Tool":-Config Tool enables you to run the server in remote debug mode.
Again Config Tool enables you to add dispatcher and server nodes to the SAP J2EE Engine 6.20 Cluster.With the help of config tool we are enable to modification of service or manager module properties.
Third part Start procedure
"Visual Administrator" check the below link
http://help.sap.com/saphelp_nw70/helpdata/EN/23/fa1f1e5f6841cf92c64dc19d79f290/content.htm
http://help.sap.com/saphelp_nw04/helpdata/EN/e8/f48b33f9a3423c9e688dfa56330e79/frameset.htm
For more Info
http://docs.sun.com/app/docs/doc/819-0698/installconfig-53?a=view
http://help.sap.com/saphelp_nwce10/helpdata/en/6f/258b2ef17d45a4afa45a00309a6a33/content.htm
http://help.sap.com/saphelp_nw04/helpdata/EN/e8/f48b33f9a3423c9e688dfa56330e79/frameset.htm -
Visual Admin: Log Viewer not opening
Hello all,
I have logged in to Visual Admin with J2ee_admin user, the Log viewer service is not working properly.
As I am clicking Log viewer, the Visual admin getting hang.
Regrads,
Shanker C
Edited by: shanker c on Jul 29, 2009 8:25 AMThanks to all,
Solution is given in above suggested SAP note.
There are huge number of archives in cluster nodes and dispatcher. after removing it the Log Viewer is working fine.
Thanks,
Shanker C -
Session Expired in Visual Admin
Dears,
I am using netweaver 2004s on windows 2003 server with SQL server.
Upto Some days back my visual admin was working fine but now when i am logging after loging its showing session expired.
I have not made any changes in its properties.
Please suggest.
ShivamHi,
Visual Admin Logs:
predecessor system -
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:178)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:181)
at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:72)
at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:175)
... 13 more
#1.5#C000ACA8010F0001000000000166C11400045DC1F5E60370#1228987542406#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###Could not add subtree of cluster element Server 0 1_34778: java.lang.NullPointerException#
#1.5#C000ACA8010F0001000000020166C11400045DC1F5E60370#1228987542406#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error#1#/System/Server/VisualAdministrationTool#Plain###Could not add subtree of cluster element Server 0 1_34778: null#
#1.5#C000ACA8010F00000000000001D144A400045DC24EBD3D10#1228989032890#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.net.SocketException: socket closed#
#1.5#C000ACA8010F00010000000001D144A400045DC24EBD3D10#1228989032890#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.net.SocketException: socket closed#
#1.5#C000ACA8010F00000000000001A4EB5600045DC2595BED70#1228989211031#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.net.SocketException: socket closed#
#1.5#C000ACA8010F000000000000014562C500045DC2611EAAE8#1228989341265#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###Could not add subtree of cluster element Server 0 1_34778: java.lang.NullPointerException#
#1.5#C000ACA8010F000000000002014562C500045DC2611EAAE8#1228989341281#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error#1#/System/Server/VisualAdministrationTool#Plain###Could not add subtree of cluster element Server 0 1_34778: null#
#1.5#C000ACA8010F0001000000000144E85800045DC279667900#1228989748640#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.net.SocketException: socket closed#
#1.5#C000ACA8010F0000000000000144E85800045DC279667900#1228989748640#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.net.SocketException: socket closed#
#1.5#C000ACA8010F00000000000000913C5600045DC29532CA58#1228990215015#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.net.SocketException: socket closed#
#1.5#C000ACA8010F0000000000000179C7CF00045DC34D61E208#1228993305109#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.net.SocketException: socket closed#
#1.5#C000ACA8010F00000000000000C3E96700045DC39B2429D8#1228994609687#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###Could not add subtree of cluster element Server 0 1_34778: java.lang.NullPointerException#
#1.5#C000ACA8010F00000000000200C3E96700045DC39B2429D8#1228994609687#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error#1#/System/Server/VisualAdministrationTool#Plain###Could not add subtree of cluster element Server 0 1_34778: null#
Checked that Username and Password is correct.
Shivam -
Authentication did not succeed in Visual Admin On solution manager?
Hello friends,
We are unable to log in in visual admin with j2ee_admin default connection. while log in we receiving authentication did not succeed error.
Please help me to solve this issue.
Regards,
Farkath CHello Friends,
Still we are unable to login to visual admin using J2ee_admin user,
Please find the Security log,
If you find any idea to resolve this issue, Please help me.
#1.5 #001EC94523270053000001170000199000050333FB9C3FF5#1410896683295#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SLDDSUSER#895##E7B8C5FD3DD911E4AF340000002B7B0E#e7b8c5fd3dd911e4af340000002b7b0e-0#e7b8c5fd3dd911e4af340000002b7b0e#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SLDDSUSER
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok true true
3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true true
Central Checks true #
#1.5 #001EC9452327004C0000011F0000199000050333FB9E05C9#1410896683405#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SLDDSUSER#896##E7C9690F3DD911E481880000002B7B0E#e7c9690f3dd911e481880000002b7b0e-0#e7c9690f3dd911e481880000002b7b0e#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SLDDSUSER
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok true true
3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true true
Central Checks true #
#1.5 #001EC9452327004B000000EE000019900005033406875E27#1410896866503#/System/Security/Usermanagement##com.sap.security.core.persistence#J2EE_GUEST#0##54E022B53DDA11E48F670000002B7B0E#54e022b53dda11e48f670000002b7b0e-0#54e022b53dda11e48f670000002b7b0e#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.security.core.persistence#Java#User "{0}" is the communication user for the connection between User Management Engine and the ABAP backend system {1}. This user cannot log-on to the User Management Engine.##User "{0}" is the communication user for the connection between User Management Engine and the ABAP backend system {1}. This user cannot log-on to the User Management Engine.#2#J2EE_ADMIN#SLMCLNT100#
#1.5 #001EC9452327004B000000EF00001990000503340687960E#1410896866518#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#J2EE_GUEST#0##54E022B53DDA11E48F670000002B7B0E#54e022b53dda11e48f670000002b7b0e-0#54e022b53dda11e48f670000002b7b0e#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: SAP-J2EE-Engine
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule SUFFICIENT ok exception true Authentication did not succeed.#
#1.5 #001EC9452327004B000000F4000019900005033412BB19D3#1410897071292#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SOLMAN_ADMIN#910##CEF7CEF83DDA11E498040000002B7B0E#cef7cef83dda11e498040000002b7b0e-0#cef7cef83dda11e498040000002b7b0e#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SOLMAN_ADMIN
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok true true
3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true true
Central Checks true #
#1.5 #001EC9452327005700000144000019900005033412BBC3C3#1410897071339#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SOLMAN_ADMIN#911##CF03B6AC3DDA11E4A9C90000002B7B0E#cf03b6ac3dda11e4a9c90000002b7b0e-0#cf03b6ac3dda11e4a9c90000002b7b0e#SAPEngine_Application_Thread[impl:3]_34##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SOLMAN_ADMIN
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok true true
3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true true
Central Checks true #
#1.5 #001EC9452327008900000005000019900005033417E870E1#1410897158131#/System/Security##com.sap.engine.services.keystore####4EF963E63DAE11E4A2050000002B7B0E#4ef963e63dae11e4a2050000002b7b0e-0#4ef963e63dae11e4a2050000002b7b0e#Thread[ExRun:SMD_MGR_26,10,SMD_MGR:ExecTG]##0#0#Error#1#com.sap.engine.services.keystore#Java###Source: com.sap.engine.frame.core.configuration.NameNotFoundException: A file entry with the name "SMDAgent-cert" cannot be found in the configuration "keystore/TrustedCAs/entries".; Description: EntriesStorage - readEntry(SMDAgent-cert) in configuration [keystore/TrustedCAs/entries] failed with unexpected exception; Consequences: ; Countermeasures:check log for details##
#1.5 #001EC945232700500000012800001990000503341E810CD6#1410897268826#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SM_INTERN_WS#918##001EC94523271EE48CE20FF9FB774D30#AC14008B0CDC54189574001F00000000-0#43DB3DE44884F13EB530001EC9452327#SAPEngine_Application_Thread[impl:3]_28##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SM_INTERN_WS
Authentication Stack: sap.com/tc~smd~ws~agent~monitoring*SMDAgentMonitoring_DataProvider
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false
2. com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule SUFFICIENT ok exception false Received no SAP Authentication Assertion Ticket.
3. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule OPTIONAL ok true true
4. com.sap.security.core.server.jaas.CreateTicketLoginModule SUFFICIENT ok true true
Central Checks true #
#1.5 #001EC9452327007E0000011100001990000503341E81D7E9#1410897268873#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SM_INTERN_WS#919##001EC94523271EE48CE20FF9FB774D30#AC14008B0CDC54189574002000000000-0#43DB3DE44884F13EB530001EC9452327#SAPEngine_Application_Thread[impl:3]_33##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SM_INTERN_WS
Authentication Stack: sap.com/tc~smd~ws~agent~monitoring*SMDAgentMonitoring_DataProvider
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false
2. com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule SUFFICIENT ok exception false Received no SAP Authentication Assertion Ticket.
3. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule OPTIONAL ok true true
4. com.sap.security.core.server.jaas.CreateTicketLoginModule SUFFICIENT ok true true
Central Checks true #
#1.5 #001EC94523270053000001280000199000050334253E502B#1410897381878#/System/Security/Usermanagement##com.sap.security.core.persistence#J2EE_GUEST#0##DC2A72A83DDA11E4CB770000002B7B0E#dc2a72a83dda11e4cb770000002b7b0e-0#dc2a72a83dda11e4cb770000002b7b0e#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#com.sap.security.core.persistence#Java#User "{0}" is the communication user for the connection between User Management Engine and the ABAP backend system {1}. This user cannot log-on to the User Management Engine.##User "{0}" is the communication user for the connection between User Management Engine and the ABAP backend system {1}. This user cannot log-on to the User Management Engine.#2#J2EE_ADMIN#SLMCLNT100#
#1.5 #001EC94523270053000001290000199000050334253E5151#1410897381878#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#J2EE_GUEST#0##DC2A72A83DDA11E4CB770000002B7B0E#dc2a72a83dda11e4cb770000002b7b0e-0#dc2a72a83dda11e4cb770000002b7b0e#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: SAP-J2EE-Engine
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule SUFFICIENT ok exception true Authentication did not succeed.#
#1.5 #001EC9452327008A00000102000019900005033431310D8E#1410897582354#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SLDDSUSER#931##FF9A34B63DDB11E4BB010000002B7B0E#ff9a34b63ddb11e4bb010000002b7b0e-0#ff9a34b63ddb11e4bb010000002b7b0e#SAPEngine_Application_Thread[impl:3]_3##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SLDDSUSER
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok true true
3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true true
Central Checks true #
#1.5 #001EC94523270084000000FF000019900005033431329358#1410897582463#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SLDDSUSER#932##FFAADBF23DDB11E4B6910000002B7B0E#ffaadbf23ddb11e4b6910000002b7b0e-0#ffaadbf23ddb11e4b6910000002b7b0e#SAPEngine_Application_Thread[impl:3]_6##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SLDDSUSER
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok true true
3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true true
Central Checks true #
Regards,
Farkath C -
J2EE Visual Admin Tool stops at 99%
Hello everyone,
I have a problem with the Visual Admintool for the J2EE of an EP 6.0 SPS12 Installation on W2k. The tool worked properly before I installed TREX 6.1.
After I connect sucessfully with the admin tool it runs slowly up to 99% and stops here. The Tree of dispatcher and his services are viewable but I cannot expand the server node.
The TREX is running fine, all services are green. The Portal is available and the MMC of Portal shows all green (all services/intances started successfully). I can login and administrate the portal. But I can't configure the TREX for the portal because I can't access the Servernode in Visual Admin.
I checked the logs for the admin tool but there are no errors. The info in admin tool shows no error too. Maybe some additional traces and logs must be first activated.
On the system is a second EP and TREX running but I stopped all other applications, restarted the portal and tried to connect with visual Admin. It stops again at 99%.
Saw some threads with a solution to modify the hosts file or change the heap size of J2EE but no one confirmed that this has helped.
Does someone has an idea what I could check next?
Regards
AlexHello Praveen,
thanks for your hint. I checked the note which is very old and only for release 6.20 (I'm on 6.40). I found a similar error in my logs but this error was produced by a failed login and was not releted to my problem. I checked again my logs after but could not find any helpful entry here.
Some more ideas? Looks like a candidate for a OSS message to SAP again.
Regards
Alex
Maybe you are looking for
-
Is my hp pavillion 14 -b010us sleek book compatable with windows 8.1?
Just need to know if there have been any problems with the windows 8.1 update on my model on lap top as im bombarded every few days with a message urging me to update to 8.1 for free fro windows store im just kinda scared cause i dont want to hurt my
-
Hi Folks, This requirement concerns planned orders creation in ASCP plans. Is there a way we can add lead time to an Item after it is received in warehouse but before it is shipped from warehouse? There are Pre-processing, Processing & post processin
-
Loaded from text cd. will not run samples from same cd
I have adopted Delmar text Electronic Devices: Systems & Applications and intended to use the copies of multisim 2001 that we own. When I discovered that the text includes a limited copy of Multisim textbook edition, that seemed even better; it inst
-
Dear Guru , PO release startegy It is required 3people P1,P2,P3 to release a PO . Once it is released and P3 is the final release . we require only P3 (user) to make any further changes in that same PO. what config is required to make it possible
-
Dreamweaver 8 install on Mac OSX 10.6 Snow Leopard
Hi all, I have just done a fresh install of Mac OSx Snow Leopard (10.6) and am trying to install our copy of Dreamweaver 8 onto it. However I have now run into a few problems. Firstly it came up with an error message stating that some old format is n