- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- EP installation error at UME configurator .
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
EP installation error at UME configurator .
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 04-08-2008 3:35 PM
Hello All,
While installing EP 7.0 using netweaver 7.0 sr2 we are getting error at import java dump and
configure ume stages. The issue seems like the sapinst is not detecting the MS SQL instance JEP
Here are the details of the server
OS : Microsoft Windows server 2003 IA64
DB: MS SQL 2005
RAM: 7.98 G.B
j2sdk : 1.4.2_13
##
C:\Documents and Settings\support>java -version
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
##
When we set the environment variable SAPINST_SKIP_ERRORSTEP = true , the error at import java dump
is not occurring any more. However the error at configure ume still occurs.
Here are the log details
from sapinst.log
###
ERROR 2008-04-08 16:11:07
CJS-30059 Java EE Engine configuration error.<br>DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile umconfigurator.log: 'Apr 8, 2008 4:10:53 PM Info: UME configurator (com.sap.security.tools.UMConfiguratorLoad) called for action "setup"PerfTimes : loadNativeLayer: loading jperflib failed. no jperflib in java.library.pathApr 8, 2008 4:11:07 PM Error: main() [EXCEPTION] com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB. at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360) at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125) at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38) at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149) at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236) at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:60) at com.sap.security.tools.UMConfigModel.<init>(UMConfigModel.java:79) at com.sap.security.tools.UMConfiguratorLoad.main(UMConfiguratorLoad.java:179) 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.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)Caused by: java.sql.SQLException: [NWMss][SQLServer JDBC Driver][NWMss][SQLServer JDBC Driver]The requested instance is either invalid or not running. at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source) at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source) at com.sap.nwmss.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source) at com.sap.nwmss.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source) at com.sap.nwmss.jdbc.base.BaseConnection.connect(Unknown Source) at com.sap.nwmss.jdbc.base.BaseConnection.setupImplConnection(Unknown Source) at com.sap.nwmss.jdbc.base.BaseConnection.open(Unknown Source) at com.sap.nwmss.jdbc.base.BaseDriver.connect(Unknown Source) at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215) at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608) at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285) at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302) ... 12 more
ERROR 2008-04-08 16:11:07
FCO-00011 The step runUMConfigurator with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_UME_Configuration|ind|ind|ind|ind|1|0|NW_UME_Configuration_Standalone|ind|ind|ind|ind|0|0|runUMConfigurator was executed with status ERROR .
###
from jlog.
###
08.04.08 12:08:45 com.sap.inst.jload.Jload main
SEVERE: couldn't connect to DB
08.04.08 12:08:45 com.sap.inst.jload.Jload logStackTrace
SEVERE: com.sap.sql.log.OpenSQLException: Could not load class com.sap.nwmss.jdbc.sqlserver.SQLServerDriver.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:143)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
at com.sap.inst.jload.db.DBConnection.connectViaSecureStore(DBConnection.java:105)
at com.sap.inst.jload.db.DBConnection.connect(DBConnection.java:149)
at com.sap.inst.jload.Jload.main(Jload.java:580)
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.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver
at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)
###
Guys can you please give some tips to solve the issue. I will reward full points.
- SAP Managed Tags:
- SAP NetWeaver Application Server
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
The root cause of the problem is that SAP Java cannot load the database driver for MSSQL
"SEVERE: com.sap.sql.log.OpenSQLException: Could not load class com.sap.nwmss.jdbc.sqlserver.SQLServerDriver."
Because of this it reports it cannot find the database, but it actually hasn't tried at all.
There seems to be a solution reference in this thread (note 872060)
Regards
Dagfinn
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Dagfinn
You are absolutely correct. The issue is just as you said.
But rt now the installation is not yet complete and the note you specified talks about updating the driver after applying sp13.
I did tried to connect to visual administrator and config tool as per note but unfortunately there is no entries for default database there.
Can you tell how to manually check the jdbc classes in sqlserver.jar
and how to check secure store to find the new jdbc directory?.
Thank you once again for your help. Is there any other work arounds?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Since the error was because SAPINST was not able to connect to MS SQL 2005, we tried to manually connect to database using configtool. But since default databases details was missing( config.properties, dataSourceConfiguration.dtd) we copied config.properties, dataSourceConfiguration.dtd from another server and renamed sid and hostname on config.properties. Now when we connect to to default database, but it gets terminated with following error.
######
Exception occurred in openJar(null) :
java.io.IOException: Jar name is null
at com.sap.engine.offline.JarFilter.<init>(JarFilter.java:25)
at com.sap.engine.offline.FileClassLoader.openJar(FileClassLoader.java:1
131)
at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java
:623)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java
:600)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java
:578)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnection
Pool.<init>(DBConnectionPool.java:108)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceH
andler.<init>(PersistenceHandler.java:38)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init
(ConfigurationCache.java:149)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBoots
trapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBoots
trapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
at com.sap.engine.configtool.visual.ConfigTool.loadClusterData(ConfigToo
l.java:99)
at com.sap.engine.configtool.visual.ConfigTool.initScan(ConfigTool.java:
87)
at com.sap.engine.configtool.visual.ConfigTool.<init>(ConfigTool.java:82
)
at com.sap.engine.configtool.visual.ConfigTool.main(ConfigTool.java:961)
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:324)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81
)
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:324)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81
)
Caused by: java.lang.NoClassDefFoundError: com/sap/nwmss/util/UtilDummyPrintWrit
er
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(Nativ
eConnectionFactory.java:134)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(Open
SQLDataSourceImpl.java:608)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQL
DataSourceImpl.java:285)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnection
Pool.createConnection(DBConnectionPool.java:302)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnection
Pool.<init>(DBConnectionPool.java:125)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceH
andler.<init>(PersistenceHandler.java:38)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init
(ConfigurationCache.java:149)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBoots
trapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBoots
trapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
at com.sap.engine.configtool.visual.ConfigTool.loadClusterData(ConfigToo
l.java:99)
at com.sap.engine.configtool.visual.ConfigTool.initScan(ConfigTool.java:
87)
at com.sap.engine.configtool.visual.ConfigTool.<init>(ConfigTool.java:82
)
at com.sap.engine.configtool.visual.ConfigTool.main(ConfigTool.java:961)
... 5 more
Program terminated abnormally
Press any key to continue . . .
#####
I did tried to restart the sapinst , but it stopped exactly at the same state, ume config , with this error.
#####
Apr 9, 2008 11:56:34 AM Info: Leaving with return code 99
ERROR 2008-04-09 11:56:52
CJS-30059 Java EE Engine configuration error.
DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile umconfigurator.log: '
Apr 9, 2008 11:56:05 AM Info: UME configurator (com.sap.security.tools.UMConfiguratorLoad) called for action "setup"
Apr 9, 2008 11:56:34 AM Error: main()
EXCEPTION
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:60)
at com.sap.security.tools.UMConfigModel.<init>(UMConfigModel.java:79)
at com.sap.security.tools.UMConfiguratorLoad.main(UMConfiguratorLoad.java:179)
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.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: java.sql.SQLException: NWMssSQLServer JDBC DriverNWMssSQLServer JDBC DriverThe requested instance is either invalid or not running.
at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseConnection.connect(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseConnection.setupImplConnection(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseConnection.open(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseDriver.connect(Unknown Source)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302)
... 12 more
Apr 9, 2008 11:56:34 AM Info: Leaving with return code 99'.
ERROR 2008-04-09 11:56:52
FCO-00011 The step runUMConfigurator with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_UME_Configuration|ind|ind|ind|ind|1|0|NW_UME_Configuration_Standalone|ind|ind|ind|ind|0|0|runUMConfigurator was executed with status ERROR .
#####
From umconfigurator.log
#####
Apr 9, 2008 11:56:05 AM Info: UME configurator (com.sap.security.tools.UMConfiguratorLoad) called for action "setup"
Apr 9, 2008 11:56:34 AM Error: main()
EXCEPTION
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:60)
at com.sap.security.tools.UMConfigModel.<init>(UMConfigModel.java:79)
at com.sap.security.tools.UMConfiguratorLoad.main(UMConfiguratorLoad.java:179)
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.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: java.sql.SQLException: NWMssSQLServer JDBC DriverNWMssSQLServer JDBC DriverThe requested instance is either invalid or not running.
at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseConnection.connect(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseConnection.setupImplConnection(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseConnection.open(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseDriver.connect(Unknown Source)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302)
... 12 more
Apr 9, 2008 11:56:34 AM Info: Leaving with return code 99
####
The issue is sapinst cannot connect to MS SQL INSTANCE jep since most of the necessery files are missing (not created while installation ) eg :- config.properties, dataSourceConfiguration.dtd . Please let us know a solution for this.
Do you still think we go for a re installation?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
The root cause error is now: Caused by: java.lang.NoClassDefFoundError: com/sap/nwmss/util/UtilDummyPrintWriter
This usually means that you are missing some jar files (or they are empty or the classpath is wrong).
The jar file with this class is in the following location at a portal system here:
C:\usr\sap\<SID>\JC00\j2ee\cluster\server0\bin\ext\com.sap.portal.jdbcdrivers\P9util.jar
Regards
Dagfinn
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Dagfinn
Sahad here.
As i said the installation is stuck mid way, when i checked C:\usr\sap\<SID>\JC01\j2ee, there is no cluster directory itself.
As I said when i compared with another development server all those jar files are there exaclty at that position. So do you think I copy that entire cluster directory from development to the current server which is more than 2 g.b. or does we need to restart the installation again after un installation of current instance?
Thank you once again, Digfinn
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Dagfinn
Thanks for the help. But interesting thing is that I was able to install EP 7.0 successfully with the same installation dump on development. Only when i am installing on the production it is getting stucked at java import dump and ume configaration.
I did contacted SAP regarding this but got no response from them yet,
Do you have any other work arounds?
Answers (1)
Answers (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hai,
Check whether the installation of MSSQL is completed or not. and also check all the services are started or not.Is the Database is opened and can you able to login into the SQL Enterprise Manager.
Check the Serverproperty('Collation') and changefrom SQL_ Latin1_General_CP850_BIN to SQL_ Latin1_General_CP850_BIN2.And start the installation and try.
Thanks and Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hai,
First check the collation of your server by going to the SQL Query Analyzer and give command
select serverproperty('collation') and execute.If the output is
SQL_Latin1_General_CP850_BIN,then try download the instcoll.exe from the ServiceMarketplace and execute it
by giving the command -
instcoll.exe -S<hostname>\SID
Also check the Note 600027 - Installing the Corrected MS SQL Server Collation
and note - 675939 SAP Web AS 6.40 Installation on Windows: MS SQL Server
for reference.
Thanks and Regards,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Venketa,
I executed the select serverproperty('collation') and got the result as
SQL_Latin1_General_CP850_BIN2 . So the note is not applicable for me.
Also I found that note is for MS SQL 2000 while my installation is MS
SQL 2005 while the note 675939 is for SAP Web AS 6.40 while mine
is Web AS 7.00
Do you have any other suggestions?
- LLM, RAG and Cloud Foundry: No space left on device in Technology Q&A
- FCO-00011 The step start with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|i in Technology Q&A
- error during install SAP S/4HANA Server 2022 in Technology Q&A
- Explore Business Continuity Options for SAP workload using AWS Elastic DisasterRecoveryService (DRS) in Technology Blogs by Members
- Getting error while configuring SAP system in VSCode in Technology Q&A
| User | Count |
|---|---|
| 87 | |
| 10 | |
| 10 | |
| 10 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 5 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.