Log files in Visual Admin of SAP Netweaver
Hi Netweaver Experts,
Could any one help me where to find the log files in Visual Administrator of SAP Netweaver. If you could mention the directory where the files are stored, that would be more helpful for me!!!
Thanks in Advance,
Raaj and Suniel
hi,
you can find the log files in the following directory.
<b><drive>:\usr\sap\<SID>\DVEBMGS01\j2ee\admin\log\system</b>
hope this info helps!
with regards,
Raj.
<i>pls, award points</i>
Similar Messages
-
How to log on to visual admin and create destination service
Hi all,
I see this statement everywhere while trying to configure adobe forms.
*it was only the HTTP destination FPICF_DATA_<SID> that was not created in the Visual Admin under Cluster -> Services -> Destinations*_
I got 2 questions here:-
1. the programs "FP_CHECK_DESTINATION_SERVICE" runs fine w/o destination check box. andwith the check box it gives the error "ADS: Request start time: Thu Nov 26 12:07:42 ........". SO how to resolve this. I have checked the blogs before and I did everything so far and stuck at the statement given above in bold.
2. What is this destination fp_icf_data_sid........... where to look for, I understand u need to log on to visual adm. But how is there a sap transaction "AL11" or from the web url. if it is web url ... "http://server_name:port/ ....." then I am lost after this I dont see anything called cluster and services anywhere....
And if am looking for visual admin at wrong places please provide step by step guide. I have seen steps to log on to visual admin on wesites but i dont know what am i doing, thats not clear. If someone can help from here.
Thanks,
Anu.The Visual Administrator is a Java tool installed during the installation of a Java AS. It is a separate tool that can be copied and used remotely if desired. On a system running Java AS it can be found under /usr/sap/<SID>/JC00/j2ee/admin - just run 'go' under Linux/Unix or 'go.bat' under Windows. You must have Java installed on your remote system.
Once you have logged into your Java AS system using the Visual Administrator you can then setup your "Destinations", located under Server -> Services.
Check Note 944221 - Troubleshooting if problems occur in forms processing ...which will make clear the errors you are experiencing and help you solve them.
Nelis -
How to start/ restart the service in visual admin of SAP WAS 6.4?
I have installed the sneak preview version of SAP NetWeaver WAS 6.4 for default Database MaxDB. While developing a simple application to manage simple database table citymaster with 2 columns in jsp I am getting error as
Exception e com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at : java.comp.
Looking at visual admin tool for WAS 6.4 all the entries are in color blue but the last entry for 'DATASOURCE' is in RED color where 'java.comp/env/JDBC/DATASOURCE' is the jndi reference created for default DataSource.
Can any one help me that why the last entry is in RED and it that say that some error has occured or that entry is not started then how to start that?
Please help....Dear Daniel,
I have checked the Visual Administrator's JNDI Registry service entry in the ejbContexts node but there is no entry for the project which I have created.
It get deployed while I right click on the project's ear file and click on "Deploy on J2EE Engine". But same as before while checking in Browserthe site gives the same error...
503 Service Unavailable
Application cannot be started!
Details: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application bcone.com/EntityCMPAppln cannot be started, because it has hard reference to resource CONFIG_DB with type javax.sql.DataSource, but it is not active on the server.
at com.sap.engine.services.deploy.server.ReferenceResolver.processUsageOfComponent(ReferenceResolver.java:508)
at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:337)
at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:149)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:285)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:355)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:120)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:224)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4170)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2390)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2267)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:41)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:101)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:80)
at com.sap.engine.core.thread.impl4.SingleThread.execute(SingleThread.java:70)
at com.sap.engine.core.thread.impl4.SingleThread.run(SingleThread.java:111)
Please help me, how to recover this error.
Rgds,
Vivek -
Can't locate .properties file on Visual Admin
Hello,
I have created an RID.properties file inside a DynPro application under src/packages/... and I am able to load it and get it's attributes from the DynPro code.
So far so good...
As far as I know this properties file can be viewd and modifed on the Visual Admin under:
Configuration Adapter -> webdynpro...
I've browsed all the folders at this location and couldn't locate my .properties file. So where is it...?
Royi think you only want to access and maintain the properties on server side...
ok, check out
http://help.sap.com/saphelp_nw04/helpdata/en/b8/aa343e32ff1033e10000000a114084/content.htm
for an example how to access the properties from your wdp app.
i suggest loading all props into a specific context node and corresponding attributes. perhaps there are better ways.
Now sth. uncomfortable:
Be careful when you redeploy your app. All properties are overwritten with the ones you defined locally.
you also cant delete the config on local side, it would be deleted on server, too. (at least i think so) -
Canu00B4t see log with J2EE Visual Admin or Standalone Log Viewer
Bom dia!
When logging on Log Viewer, it shows de error message: Unable to invoke LogControllerFacadeMBean method:"getMetaDataOfReaders" In J2EE Visual Admin the error message after click in the item Log Viewer is Error while loading service Log Viewer
When I click in defaultTrace.trc nothing appears. The same for the others log archives listed in Log Viewer.
Can someone help me with this?
Very thanks from Spain.
In the console I see the following java exception:
Exception in thread "AWT-EventQueue-0" com.sapmarkets.bam.util.BAMRuntimeExcepti
on: Unable to invoke LogControllerFacadeMBean method: "getMetaDataOfReaders".
at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.invokeFacade
Method(AbstractLogDepot.java:225)
at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getMetaDataO
fReaders(AbstractLogDepot.java:303)
at com.sapmarkets.bam.view.config.AbstractViewConfiguration.getColumnInf
oFromServer(AbstractViewConfiguration.java:218)
at com.sapmarkets.bam.view.config.AbstractViewConfiguration.readSetting(
AbstractViewConfiguration.java:126)
at com.sapmarkets.bam.view.config.AbstractViewConfiguration.getColumnSet
tingForLogType(AbstractViewConfiguration.java:247)
at com.sapmarkets.bam.view.buffertable.ContentPane.obtainColumnSettings(
ContentPane.java:915)
at com.sapmarkets.bam.view.buffertable.ContentPane.<init>(ContentPane.ja
va:127)
at com.sapmarkets.bam.view.AbstractLogViewerAppplication.makeTablePane(A
bstractLogViewerAppplication.java:423)
at com.sapmarkets.bam.view.AbstractLogViewerAppplication.displayLogs(Abs
tractLogViewerAppplication.java:474)
at com.sapmarkets.bam.view.overview.OverviewFilePathTreeWrapper.openLog(
OverviewFilePathTreeWrapper.java:334)
at com.sapmarkets.bam.view.overview.OverviewFilePathTreeWrapper$TreeMous
eListener.mousePressed(OverviewFilePathTreeWrapper.java:359)
at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:26
3)
at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:26
2)
at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:26
2)
at java.awt.Component.processMouseEvent(Component.java:6038)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
at java.awt.Component.processEvent(Component.java:5806)
at java.awt.Container.processEvent(Container.java:2058)
at java.awt.Component.dispatchEventImpl(Component.java:4413)
at java.awt.Container.dispatchEventImpl(Container.java:2116)
at java.awt.Component.dispatchEvent(Component.java:4243)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3983)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
at java.awt.Container.dispatchEventImpl(Container.java:2102)
at java.awt.Window.dispatchEventImpl(Window.java:2440)
at java.awt.Component.dispatchEvent(Component.java:4243)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThre
ad.java:273)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.
java:183)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre
ad.java:173)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy0.invoke(Unknown Source)
at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.invokeMBeanM
ethod(AbstractLogDepot.java:163)
at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.invokeFacade
Method(AbstractLogDepot.java:206)
... 33 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sapmarkets.bam.jmx.connector.AbstractLVServer.invoke(AbstractLVSe
rver.java:184)
at com.sapmarkets.bam.jmx.connector.rmi.IntegratedConnectorClient.invoke
(IntegratedConnectorClient.java:107)
... 36 more
Caused by: javax.management.ReflectionException: No such operation: getMetaDataO
fReaders
at com.sun.jmx.mbeanserver.PerInterface.noSuchMethod(PerInterface.java:1
52)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:94)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
BeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761
... 42 more
Caused by: java.lang.NoSuchMethodException: getMetaDataOfReaders()
at com.sun.jmx.mbeanserver.PerInterface.noSuchMethod(PerInterface.java:1
50)
... 46 moreHello Ivan,
Make sure that you are using a supported JDK version as per note below:
723909 Java VM settings for J2EE 6.40/7.0
And also, make sure that the necessary environment variables are pointing to the correct JDK version.
Regards,
Rafael -
Log files under the admin node are getting filled up
I installed Sun One Web Server 7.o u3 in the following way:
a. Installed admin server on MC1
b. installed admin node on MC2.
c. When I started MC1 and MC2, the access log file (C:\Program Files\Sun\WebServer7\admin-server\logs) under the admin node MC2 is getting filled up with these messages for every 2 minutes:
MC1 IP ADDRESS - CN=admin-client-cert [24/Mar/2010:18:03:46 -0400] "POST /jmxconnector/remotejmx HTTP/1.1" 200 291
I checked for errors file under the admin server, and I did not see any errors, as such. Please help me to fix the problem. I installed node and server, as per guidelines
I have not installed any web app or deployed any config.
Thanks,
PhaniJoe,
That worked. Thanks a lot. 1 more thing. I made a new configuration, while migrating 6.1(SP2) instances.After deploying on MC1/MC2, and when I am trying to start the configuration on the instances, it is giving the following errors for both nodes MC1 & MC2:
ADMIN3584: Error while starting the server. Please check the server logs.
I ran the log mode with 'finest' level and it is showing following exceptions:
25/Mar/2010:17:55:28] fine ( 6044): for host 10.248.131.38 trying to POST /admingui/admingui/startInstances, service-j2ee reports:
com.sun.web.admin.exceptions.AdminException: ADMIN3584: Error while starting the server. Please check the server logs.
at com.sun.web.admin.mbeans.AgentMBean.startServer(AgentMBean.java:212)
at com.sun.web.admin.mbeans.AgentMBean.startServer(AgentMBean.java:198)
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:585)
[25/Mar/2010:17:55:28] info ( 6044): for host 10.248.131.38 trying to POST /admingui/admingui/startInstances, service-j2ee reports: Exception : ADMIN3011: The operation failed with errors on the following nodes:
Node 'MC1.test.com':
ADMIN3584: Error while starting the server. Please check the server logs.
[25/Mar/2010:17:55:28] fine ( 6044): for host 10.248.131.38 trying to POST /admingui/admingui/startInstances, service-j2ee reports:
com.sun.web.admin.exceptions.MultiNodeException: ADMIN3011: The operation failed with errors on the following nodes:
Node ''MC1'
ADMIN3584: Error while starting the server. Please check the server logs.
at com.sun.web.admin.mbeans.NodeMBean.doLifecycleAction(NodeMBean.java:84)
at com.sun.web.admin.mbeans.NodeMBean.startServer(NodeMBean.java:299)
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:585)
at com.sun.web.admin.mbeans.BaseAdminMBean.invoke(BaseAdminMBean.java:49)
at
Any help on this issue is appreciated.
Thanks,
Phani -
Missing file on download page for SAP NetWeaver 7.01 - ABAP Trial
Tried to download the file, but server return http 404, file not found.
SAML Response from SAP ID ServiceYou must be logged in to access this URL so make sure there aren't any blocked popups asking you to authenticate.
Try this secure URL: SAML Response from SAP ID Service
If you still experience issues, open a support ticket with SCN by eMailing [email protected] -
hii guys,
in my netweaver system visula admin tool not working .when ever im trying to connect with user id and password its showing like this.how can i solve this issue.plz help meHi,
Try to login to system info page with administrator or j2ee_admin for java and dual stack respectively to check if the password is correct.
If the password is incorrect, then check if you have any alternate admin ID. Change the administrator or j2ee_admin password, then try to login with the new password. Change the password of SDM and securestore to the new one.
If this is not the case, then check the log files in visual admin directory. Please post the same.
Cheers...,
Raghu -
[SAP NetWeaver 2004] Can't logon in Visual Administrator
Hi community,
I can't login in Visual Administrator with SAP NetWeaver 2004 - Trial Version on Linux (NW4)
I try to logon using J2EE_ADMIN/ADMIN as login/password but when I try to connect it remains in connecting state.
In the logs I can see the following error:
Caller J2EE_ADMIN not authorized, only role administrators is allowed to access JMX
User J2EE_ADMIN on SU01 transaction seems correctly configured, and has the role SAP_J2EE_ADMIN
Where do I go wrong?
Thanks, Valerio
PS I know this release is old and not supported but it's not so resource-demanding as the 2004s versionHi Valerio,
I think you dont have correct password maintained in the secure store. please try this.
1. check if j2ee_admin is locked or not in SU01.
2. if you know j2ee_admin's correct password
- go to configtool, by running /usr/sap/<SID>/DVEBMGS00/j2ee/configtool/configtool.sh
- in the secure store maintain the password of j2ee_admin in the field "admin/password/<SID>"
- set and this will ask you to restart java cluster.
- restart the java cluster by going through SMICM tcode in ABAP side. SMICM > Adminstration > J2ee cluster global > send hard shutdown > with restart.
Hope this helps.
Debasis. -
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 -
Process DMI files from Informatica into SAP NetWeaver
hi,
Can anyone help me out in processing the dmi files (given by Informatica) in SAP NetWeaver. . .
As i'm new to this plz provide me some useful links regarding the pre-requisites of SAP NetWeaver for accepting the dmi files and also some useful material regarding the process.
Thanx in advanceHi
Scenaio 1.
Process xml file given by informatica and create IDOC in SAP to update records - DONE
Scenario 2.
Process DMI file given by Informatica and update records in SAP. For this i need to know how i should process the DMI file.What will be the pre-requisite for DMI files to work. And how will i be able to update records (like in Scenario 1 thru IDOC).
Thanks & Regards,
Revathi. -
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 -
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 -
Visual Admin Hangs @ 99%
Hello All
When i try to log in into visual admin, it hangs at 99% and it throws below error.
java.lang.NullPointerException at com.sap.engine.services.adminadapter.gui.ClusterView$4.run(ClusterView.java:405)
Your help would be greatly appreciated!
Thank you guys in advance.
RonHi Ron,
the only thing I can think of now is to take thread dumps and check if we can see anything there.
Usually the error message you mentioned does point to a wrong JDK being used (are you sure that you have not 1.5 installed which might be taken by accident?). Please check the JAVA_HOME again.
Which portal version are you using?
Regards,
Holger. -
Hello,,
I am unable to log into my Visual admin. It says "Cannot open connection on host: 64.13.232.162 & port:51004" .
I dont know which host it is referring to??? That IP is not our servers IP.
I referred many forums andI checked Port Number on Config Tool. Its correct & i tried with different Transport Layer options but nothing is working??
Any help on this???Hi
First check the Java stack is up or not.
If java is up do the following
open the visual admin
In the connect to sap j2ee Engine screen
Select new
select the lookup method Via message Server
Display name as Test click Next
username : provide J2ee_admin
host : localhost
HTTP Port : 81(scs instance number) which is java instance number
click save
select test and click on connect .
It will direct to the correct Port
Give the password and u will login to visual admin
Maybe you are looking for
-
my iphone 3g is disabled, its says connet to itunes,i tired in itunes but its says locked with the passcord .but there is no space to enter passcord pls help
-
== Issue == I have another kind of problem with Firefox == Description == Please stop this horrible screen savers that I receive from firefox every fiew seconds. How do we stop them? <blockquote>removed your email address from the topic heading, we d
-
SD card import faulty - Camera Connection Kit
I am travelling around and the camera connection kit has been working well for importing pics from my SD cards. However one day the import warned me I was importing 1gb of pics, but only had 0.7gb free on the iPad. It asked me whether to import until
-
HT2470 My finder does not have the option to search for everything, only file names.
Is there a place I have to change settings?
-
Only computer background shows on LED tv
i have the older model macbook from 09 and the screen gave out on me and was told it would cost 200 - 400 dollars to fix so i bought the mini dvi output to connect to me led tv and all i see on the tv is the background of my computer nothing else,i c