Visual admin version upgrade.

Hi All,
When i open remotegui for Visual admin.in netweaveer 2004s,i am getting warning on system that:
"Visual Admin. version is older then J2EE Karnal Version.
Visual admin ver. SP 6
J2EE Karnal Ver. SP 15"
Please help me to know process to upgrade Visual admin. Version.
Regards
Gyan

Hi,
You can upgrade your SDM Version of your system. But only thing you need to do is download the J2EERT<lower_SP_version>_xxx.SAR file from service market place.
873769 note will give you complete step by step procedure to do the same for SAP netweaver 2004.
You can follow the same for n/w 2004s (7.0).
Rgds
Radhakrishna D S
Edited by: Radhakrishna D S on Aug 4, 2008 5:37 AM

Similar Messages

Visual Admin. upgrade process steps

Hi All,
When i open Visual admin.in netweaveer 2004s,i am getting warning on system that:
"Visual Admin. version is older then J2EE Karnal Version.
Visual admin ver. SP 6
J2EE Karnal Ver. SP 15"
Please help me to know process to upgrade Visual admin. Version.
Regards
Gyan
Edited by: Gyan Prakash on Aug 5, 2008 5:04 PM

this is a comman warnning displayed when java stack is not upgraded fully
try to upgrade SAP-JEECOR , SAP-JEE componenet to patch 16
recomended is update your all componnets java stack to 16
you can view the component list in
http://host:port/sap/monitoring/SystemInfo
Samrat

How to chwck MS SQL server driver version in visual admin

Please let me know jow to check MS SQL server driver version in visual admin

We make a JDBC connector connection for a datasource for the Database in visual Admin.Please check the version in that.
Goto Visual admin then In the Runtime tab of JDBC Connector Service, choose Resources and check there.
You can check the version of server driver at os level then y do you want to go for visual admin.
Thanks
Rishi Abrol

Error while deploying in Visual Admin

Hi,
Currently I'm having an error while I do my application deployment via Visual Admin. I realized afterI login to Visual Admin then I press Services>Deploy, it will printed a stack of error of java.lang.NullPointerException. I screenshot for better reference.
[Click Here|http://img687.imageshack.us/img687/3205/errorq.gif]
It showed error on com.sap.engine.services.rmi_p4/MarshalInputStream.setProfile. Any cause of this or solution as now I can't deploy my application.
Thanks.

Hi Blanca,
I just checked the server and the version is SP13. But before I request for an upgrade I need to justify also.
I checked out the note 1325234 and follow what it asked. Is correct as I unable to see any entries after I clicked All Application. But in my defaultTrace log didn't print out the error message.
I only will see the message when I go to Visual Admin>Server>Services>Deploy and it will print as I showed in the screenshot. Just want to double confirm for the error.
Thanks.

Visual admin stoping at 99%

Hi
we have Nw04sp17 portal installation and except visual admin tool every thing workingfine.
when we logon to VA with aministrator and pwd its stoping at 99% and throwing following error at console
java.lang.NullPointerException
 at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.connectAction(LoginTask.java:191)
 at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.run(LoginTask.java:79)
 at java.lang.Thread.run(Thread.java:534)
We found some notes on sdn about this and upgrade the WAS to sp18 even though its showing same error.any body has suggestions to
resolve these issue.
Thanks in advance
Gopal

Hi Gopal,
another option is to check if maybe the filesystem /usr/sap/<SID> is full (that the Visual Admin cannot write any logs).
Which operating system and which database do you use?
Try the login with another user than Administrator which is also in the group "Administrator" and see if that brings the same error.
You can also try to download the Visual Admin from another system and log in from your local PC (copy the directory /usr/sap/<SID>/j2ee/admin to your PC, make sure you have Java Version 1.4. installed, open go.bat with Notepad or something similar and make sure that "set JAVA_CMD=" points to the java version 1.4 - then start go.bat and try to login)
Sorry, I start running out of more ideas ....
Regards,
Cornelia

ESS/MSS webpage is down,visual admin not up

We have successfully upgraded the Java J9 version on AIX Development server TOYHRD01.
(which has SAP Java portal EP6.0 ESS/MSS instances:
EPD - for ESS/MSS development, and
EPQ - for ESS/MSS Test system.
AIX TOYHRD01 - AIX Java J9 upgraded
SAP JAVA EPD (ESS/MSS Development) and EPQ (ESS/MSS Test system) - SAP Portal Config tool upgraded
Problem occured On Production ESS/MSS portal EP6.0 AIX server TOYPRT01
AIX TOYPRT01 ESS/MSS - AIX Java J9 upgraded
SAP JAVA EPP (ESS/MSS Production system) - SAP Portal Config tool upgraded
Issue:
We upgraded the SAP Portal J2EE config tool based on SAP note# 1024539
Problem encountered as below:
ESS/MSS production (SAP SID: EPP) web page not come up.
SAP Portal EPP (ESS/MSS production) Visual Administration not come up.
Logged on Config Tool was okay.
Regards,
Chinnu

Hi,
If installation completed sucessful, login to sap visual admin will work, if not set the java path correctly your installation will be failed.
check whether j2ee process SDM is running are not , if its not running you can't loging to visual Admin.
Thanks
BM
Do not use text message language
Read the "Rules of Engagement"
Edited by: Juan Reyes on Mar 1, 2011 9:13 AM

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

Error while creating RFC Jco provider in visual Admin

Hi,
I have crated a rfc jco provider in visual admin , I have given all the ECC related details both in registered server AND Spcific application server. In both of these I have given R/3 related details like host of ecc and all.
All i have given correct used ID and passowrd also (I am using my own user id and password in this jco rfc provider). that user id is there in ecc with sap all in profile and in roles also i have given 2 roles for that used id, namely sap_bc_jsf_communication AND sap_bc_usr_cua_client_rfc
Still when i try to start it its giving me error: Error starting bundle
please help

This I am getting:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=sapecdsrv SYSNR=00 GWHOST=sapecdsrv GWSERV=sapgw00 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       hostname 'sapecdsrv' unknown
TIME        Wed May 26 14:26:21 2010
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -2
MODULE      nixxhsl.cpp
LINE        223
DETAIL      NiHsLGetNodeAddr: hostname cached as unknown
COUNTER     2
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1025)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
at com.sap.mw.jco.JCO$Pool.initPool(JCO.java:4725)
at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6180)
at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6135)
at com.sap.mw.jco.JCO.getClient(JCO.java:8803)
at com.sap.engine.services.rfcengine.Bundle.startAll(Bundle.java:248)
at com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.addBundle(RFCRuntimeInterfaceImpl.java:350)
at com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.changeBundleConfiguration(RFCRuntimeInterfaceImpl.java:654)
at sun.reflect.GeneratedMethodAccessor401.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62)
at java.lang.reflect.Method.invoke(Method.java:391)
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: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:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172

Error in creating MSSQL 2005 server Datasource in visual admin

I need to create a datasource in Visual Admin for SQL Server 2005. I have already downloaded the JDBC Driver for SQL server 2005 and while creating the driver in visual admin I specified sqljdbc.jar from the downloaded directory.
Then created the datasource, filling out the following properties:
o Main tab > DataSource Name: fx MyDatasource
o Main tab > Add Alias: fx MyAlias
o Main tab > Driver Name: SQL Server
o Main tab > JDBC version: 2.0 (with XA support)
o Main tab > Object factory: com.microsoft.jdbcx.sqlserver.SQLServerDataSourceFactory
o Main tab > DataSource Type: ConnectionPoolDataSource
o Main tab > CPDS classname: com.microsoft.jdbcx.sqlserver.SQLServerDataSource
o Additional tab > add property serverName = <myserver>,
o Additional tab > add property databaseName = <mydb>,
o Additional tab > add property portNumber = <port>, fx 1433
o Additional tab > add property user = <sql database user>, fx sa
o Additional tab > add property password = <password>
Then I set the initial connections to 1. On saving, I was shown an error saying:
Causedby: java.lang.ClassNotFoundException:com.microsoft.jdbcx.sqlserver.SQLServerDataSourceFactory
Then I tried with SAPs Driver for MSSQL, giving the parameters as:
Driver Name: SYSTEM_DRIVER
JDBC Version: 1.x
Driver Class: com.sap.portals.jdbc.sqlserver.SQLServerDriver.class
Database URL: jdbc:sap:sqlserver://<myserver>:1433;DatabaseName=<mydb>
On saving an error was generated saying:
Causedby:java.lang.ClassNotFoundException:com.sap.portals.jdbc.sqlserver.SQLServerDriver.class
Where have I gone wrong? Pls help.
Regards
Shyam.


hi all,
i have solved the issue.
it was due to the changes in formats of the driverclass name&URl for accessing SQLServer2005.
Details:
in SQLServer2000:
the driverclass name format is like:
com.sqlserver.microsoft.jdbc.SQLServerDriver
but in SQLServer2005 it is:
com.microsoft.sqlserver.jdbc.SQLServerDriver
and
the URL in SQLServer2005 should be of the format:
jdbc:sqlserver://<server>:1433;DatabaseName=<db>
instead of SQLServer2000's
jdbc:microsoft:sqlserver://<server>:1433;DatabaseName=<db>.the prefix has
changed.
i selected JDBC version as 1.x.
now its working fine and i cud fetch data from the db in my Web dynpro appln.
Thanks a lot.
regards
shyam.

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 more

Hello 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

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

Problem visual admin java parameters

Hi guys,
I just wanna know in the visual admin, how to put a new java parameters ?
I can't press enter and had a new line ... Can someone had a parameter ? Not a change but a new one ?
Thanks.

yes it is ! had a parameter in the config tool !
-Xbootclasspath
-Dcom.wily.introscope-agentProfile
-Dcom.wily.introscope
By the documentation Introscop Version 8 Installation Guide For sap June 2009 page 27
I can modify the parameters, but not had a new line, so not had a newx parameter

One Visual Admin (local) for all my SAP Systems

Hi there,
i have a little question.
I have to administrate about 20 different SAP Systems.
And it gets me on my nerves that i always have to go with putty on one of my systems.. set the DISPLAY variable and open the Visual Admin.
So what i have done is that i copied the /admin/ folder to my local PC
And put in all the different connections to my systems
XII
POI
XIK
POK
etc...
So i only have to open the visual Admin on my PC and choose on which system i want to connect. But i have now the problem that i become the following messages on different systems i wanna connect:
Warning: J2EE Engine kerner version is older than the version of Visual Administrator
J2EE Engine kernel Version: SP13
Visual Administrator version: SP18
So is it dangerous to work with this message? Or is this really just a warning and i can go on?
Or what can i do to administrate different Systems with different SP`s with one Visual Admin?
Regards
Bjoern

So thanks for your help. I just logon then
I thought i ask first..
Yeah.. all systems on the same kernel.. that would be nice..

Not able to start the Visual Admin and configTool - URGENT

hi Experts,
Hi have installed the portal 7.0 evalution version. But when i am trying start the visual admin. when click on go.bat file. It is giving the following message.
D:\usr\sap\J2E\JC01\j2ee\admin>go.bat
D:\usr\sap\J2E\JC01\j2ee\admin>"C:\j2sdk1.4.2_09\bin\bin\java" -showversion -Dsu
n.java2d.noddraw=true -Duser.language=en -DP4ClassLoad=P4Connection -Dp4Cache=cl
ean -jar "D:\usr\sap\J2E\JC01\j2ee\admin\go.jar"
The system cannot find the path specified.
Program terminated abnormally
Press any key to continue . . .
Even ConfigTool also giving the same problem.
D:\usr\sap\J2E\JC01\j2ee\configtool>configtool.bat
The system cannot find the path specified.
Program terminated abnormally
Press any key to continue . . .
Kindly tell me how to fix the above problems. But I am able to run the SDM Tool and login.
Regards
Vijay

Check 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 =

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.
Ron

Hi 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.

Visual admin version upgrade.

Similar Messages

Maybe you are looking for