SAP Basis Tech Supports

Symptom
6.20/6.40 SAP Patch Collection Installation on Windows
Other terms
SAPinst, SAP Web AS 6.20, SAP Web AS 6.40, NW’04 SR1
Reason and Prerequisites
Installation information for an SAP system that was installed with the 6.20/6.40 SAP Patch Collection Installation Master DVD.
The following patch collection DVDs are available:
NEW:6.40 patch collection installation Master DVD – Edition May 2008 (material number: 51033746).”6.20/6.40-based products Installation Master” – Edition July 2007 (material number: 51032936)
Solution
Contents
1 General
2 Pre-Installation
3 Installation
4 Post-Installation
5 High Availability (MSCS)
This note contains information about the installation of SAP systems with the new 6.40 patch collection DVD (edition May 2008, material number: 51033746), as well as for the former 6.20/6.40 patch collection installation master DVD (edition July 2007, material number 51032936).
Section “General” contains information about what SAP systems you can install, including certain release restrictions, the required installation documentation, and other general information.
The remaining sections (”Pre-Installation”, “Post-Installation”, “High-Availability (MSCS)”) contain information and solutions for installation problems with the patch collection installation master DVD.
Each entry is marked with a prefix (ABAP, Java, ABAP+Java, <SAP_System>, <Release>, Additional Java components (<component>)), to make clear which installation type or SAP system the information applies to. For example, Java applies to a Java system, ABAP+Java to a double-stack or Java Add-In. If there is no prefix, the information applies to all types or SAP systems.
In addition, the following abbreviations or prefixes are used:
ADS for Adobe Document Services.
Additional Java components (<component>): specifc Java component, e.g.
(ERP-XSS). Without any component specification it applies to all additional Java components.
Entries that are only valid for the patch collection edition 2008 or 2007 are marked respectively. Otherwise the information is valid for both patch collection editions.

Date Section Description
======================================================================
05/JUN/09 2 Enterprise Portal (EP): Apply SAP Note 810159
24/FEB/09 4 Dealing safely with installation directories
09/OCT/08 2 Bootstrap error might occur during the installation with SAPinst
JUL/24/08 4 ABAP+Java,Java: Keystore views are not created
during the very first start
03/JUN/08 4 ABAP, ABAP+Java: Errors in transaction ST11 (error log files) every time the SAP system is started
26/OCT/07 3 User access problems when accessing DVDs located on network shares
26/OCT/07 3 Problems with different DLLs in SAP MMC when installing 6.40 systems on a host with an already installed 7.00 (or higher) system
29/JAN/06 2 Inst. Guide – Chapter: Performing a Domain Installation Without Being a Domain Administrator”
10/NOV/06 2 Do not use hostnames beginning with S-<digit>
26/OCT/06 2 Java: Update SCSCLIENT64UC.SAR on the Java DVD
06/OCT/06 2 (Edition July 2007 only:) Updating the Installation Master DVD (if required)
01/SEP/06 3 Use SAP NetWeaver 04 SR 1 Kernel for all databases except for Informix 10
25/AUG/06 4 (Java, EP:) SP11 required
23/AUG/06 3 Non-Unicode kernel DVD required for Unicode installation
22/AUG/06 3 (Java, KMC:) Error “Java Engine did not reach state “Start Application”
18/AUG/06 3 (Edition July 2007 only:) (SAP BW 3.1) Incorrect index entries
07/APR/06 2 (Java, ADS:) Running ADS with non-supported platforms
11/JUL/06 3 (ABAP:) Application server installation in mixed environment
04/APR/06 3 Installation DVDs: Error FSL-02015 Node <path> does not exist
16/MAR/06 4 Backup transport directory before deleting the SAP system
13/JAN/06 4 Unable to perform job COLLECTOR_FOR_PERFORMANCEMONITOR
30/NOV/05 3 (ABAP:) UNICODE conversion error
16/NOV/05 5 High availability (MSCS) on Windows
18/OCT/05 5 igs.xml configuration file is not updated with the virtual host name of the gateway.
05/OCT/05 3 Do not use user <sapsid>adm for the installation
04/AUG/05 3 (Java:) Dialog instance finalization Java Add-In installation
21/JUL/05 3 Problems when performing a local installation as domain user
21/JUL/05 2 Environment variable path must contain value %JAVA_HOME%\bin
29/JUN/05 3 SAPinst GUI crashes: “guiengine: no GUI connected”
15/JUN/05 2 Quicklinks /ti and /network have become obsolete
30/MAY/05 5 (Add. Java Comp., ADS:) Synchronization exception at J2EE Engine start
20/APR/05 3 (R/3 E4.70 Ext.Set 2, SR1, CRM 4.0 SR1:) ITS is not available
30/MAR/05 3 Installation hangs when extracting archives or installing DLLs
21/FEB/05> 4 (ECC 5.0 SR1, Add. Java Comp.,XSS:) Errors in callSdmViaSAPinst.log
08/FEB/05 4 (SCM 4.0, SCM 4.1:) BW-specific post-installation steps
03/FEB/05 4 (CRM 4.0 SR1, CRM Add. Java Comp.:) IC requires SAF to be installed
31/JAN/2005 3 (ECC 5.0 SR1, ERP Add. Java Comp.:) Pop-up requires post-processing steps
05/JAN/05 2 Windows Server 2003 Standard Edition for installation of central instance (ABAP) or SCS instance (Java) is possible
09/DEC/04 4 (Java:) Timeout during the start-up of the J2EE Engine
02/DEC/04 3 Automatically restarted SAPinst, does not remember command line parameters
02/DEC/04 3 Problems with SAPinst Selfextractor
01/DEC/04 4 (Java:) JDI: Enhance maximum memory for Java compiler
26/NOV/04 4 (Add. Java Comp., ADS): JStartup Framework error inerror log can be ignored
26/NOV/04 4 (Java:) Strong crypto deactivated after dialog instance installation
23/NOV/04 2 (Java, ADS:) Java Startup parameter
04/AUG/04 2 Do not use network drives for CDs/DVDs
28/Jun/04 4 (SRM 4.0 [SRM 5.0 Server]:) Performing Basic Operations
25/JUN/04 2 Reducing the size of the file cache
22/JUN/04 2 (SRM 4.0 [SRM 5.0 Server]:) Read composite SRM 4.0 installation note 726147
19/FEB/04 4 (Add. Java Comp., Java:) OutOfMemoryError
04/FEB/04 4 (Add. Java Comp., Java:) Additional Java components are not accessable
16/DEC/02 4 (Edition July 2007 only:) (BW 3.1, Unicode only:) Apply New Library after J2EE Engine installation
———————————————————————–
1 General
a) Information about the SAP Systems you can install with the Patch Collection installation Master DVD
With the patch collection installation Master DVD you can install the following SAP systems:SAP BW 3.1 (Edition July 2007 only)
Note that for BW 3.1, the 6.20/6.40 Patch Collection Installation isnotreleased onWindows x86_64.mySAP CRM 4.0 / SRM 3.0 (SAP CRM Server 4.0, SAP SRM Server 3.0)(Edition July 2007 only)
Note that for CRM 4.0 and SRM 3.0, the 6.20/6.40 Patch Collection Installation isnotreleased onWindows x86_64.mySAP CRM 4.0 SR1 (SAP CRM Server 4.0 SR1)mySAP ERP 2004 SR1 (SAP ECC Server 5.0 SR1)SAP R3E 4.7, Extension Set 2 SR1
For this system the Unicode Installation is availableSAP SCM 4.0 (SAP SCM Server 4.0)(Edition July 2007 only)
Note that for SCM 4.0, the 6.20/6.40 Patch Collection Installation isnotreleased onWindows x86_64.SAP SCM 4.1 (SAP SCM Server 4.1)mySAP SRM 4.0 SR1 (SRM 4.0 Server SR1)SAP Solution Manager 3.2 SR1SAP NetWeaver ‘04 SR1 (SAP Web AS 6.40 SR1)
including:
- TREX
- Portal Platform (EP)
- Content Management and Collaboration (KMC)
- Adobe Document Services (ADS)
- BI UDI Java Components (BW 3.5)
- Exchange Infrastructure (XI)For SAP ECC 5.0 SR1, SRM 4.0 SR1, or CRM 4.0 SR1, you can install the Additional Java Components for ERP, SRM, or CRM respectively.Note the followingDB6 V9.5 restrictionforEdition May 2008:
The 6.40 Patch Collection Installation on Windows isnotreleased for DB6 V9.5 on Windows x86 and Windows IA64.
b) How to obtain the patch collection installation Master DVD
You can download the 6.40 patch collection installation Master DVD (May 2008 edition) from the SAP Service Marketplace at:
http://service.sap.com/swdc –> Download –> Installations and Upgrades –> Entry by Application Group –> SAP NetWeaver –> SAP NETWEAVER –> SAP NETWEAVER 04 –> Installation and Upgrade –> <OS> –> <Database>
If you cannot find the DVD using this path, you can also search for the DVD as follows:
a) Go to “http://service.sap.com/swdc –> Download –> Installations and Upgrades –> Search for Installations and Upgrades”b) Enter “51033746″ as search term.
Alternatively, you can order the installation Master DVD directly from SAP.
c) Installation Documentation to use:
For the installation of the above-mentioned SAP systems with the patch collection installation master DVDs there are no specific installation guides available. Instead, use this SAP note and the relevant installation guides for your SAP product. All installation guides are available on SAP Service Marketplace at: http://service.sap.com/instguides -> <SAP Product>.Edition July 2007 only:For the patch collection July 2007 there are the following exceptions for the guides you have to use:For the installation of SAP BW 3.1, you must use the Web AS 6.40 SR1 installation guide. Also see the SAP BW 3.5 SR1 installation guide for post-installation steps.For the installation of SAP CRM 4.0, you must use the SAP CRM 4.0 SR1 installation guide.For the installation of SAP SCM 4.0, you must use the SAP SCM 4.1 installation guide.For general Windows-specific information, use the SAP NetWeaver ‘04 SR1 installation guide for Windows and for your database.For database-specific information, see the database-specific SAP Notes listed under “Related Notes”.As of SAP Web As 6.40 SR1 the document “Installation Guide – Additional Instances on Windows” has become obsolete. The installation of the ABAP dialog instance and gateway instance is described in the “Installation Guide – SAP Web Application Server 6.40 SR1 on Windows: <your_database>”

2 Pre-Installation
——————– <05/JUN/09, D040837>—————————-
Enterprise Portal (EP): Apply SAP Note 810159
When you installed SAP Web AS Java 6.40, you did not install the SAP JAVA CRYPTO TOOLKIT, which is required for EP.
Apply SAP Note 810159.
————————-<09/OCT/08, D020904>———————–
Bootstrap error might occur during the installation with SAPinst.
When installing the SAP system, a bootstrap error might occur, if the operating system processors timers are not synchronized. If so, update the OS processor driver as described in SAP Note 1036194 and restart the installation.
29/JAN/06
Inst. Guide – Chapter: Performing a Domain Installation Without Being a Domain Administrator”, Section: “Adding the SAPService<SAPSID> User to the SAP_<SAPSID>_GlobalAdmin Group”.
Remove the whole “Caution” Text: The SAPService<SAPSID> user must not be a member of the Domain Users group, including the procedure how to remove this group from the Member of list.
Reason: The user that are created with SAPinst are automatically members of the Domain Users group
—————–<10/Nov/06, D034882>————————-
Do not use hostnames for the installation of an SAP system with SAPinst
that beginn with S-<digit>, for example S-1dddd.

26/OCT/06
(Java:) Update SCSCLIENT64UC.SAR on the Java DVD:
You have to update SCSCLIENT64UC.SAR on the Java DVD before you start the installation. Otherwise you will have problems as soon as you patch your system after the installation. For more information, see SAP Note 710914.
Solution:
Proceed as follows to update the Java DVD:
1. Download SCSCLIENT64UC.SAR from SAP Service Marketplace at:
http://service.sap.com/swdc
-> Download
-> Support Packages and Patches
-> Entry by Application Group
-> SAP NetWeaver
-> SAP NETWEAVER
-> SAP NETWEAVER 04
-> Entry by Component
-> Application Server Java
-> SAP J2EE Engine 6.40
-> <operating system>
-> J2EERTOS*.SAR”WebAS 6.40
SP<required_patch_level>
(Part 3/4): OS Depend. parts of Java Runtime”
(The archives SCS*.SAR are part of J2EERTOS*.SAR).2. Copy the Java DVD to your file system.3. On the copied DVD, replace SCS_<OS>\SCS\UNIX\<OS>\SCSCLIENT64UC.SAR with the downloaded patch.4. Start the installation.
—————–<06/OCT/06, D025095>————————–
(Edition July 2007 only:) Updating the Installation Master DVD (if required)
In the following cases you must update the Installation Master DVD before starting SAPinst:
you want to install a Java system in High Availability (HA) manner or you want to install the Java Add-In for an exisiting HA ABAP systemyou want to install software unit MapBox (CRM-MBX)
Proceed as follows to apply current updates to the Installation Master DVD:
1. Mount the installation DVDs.2. Copy the Installation Master DVD to a local directory.3. Download the attached NW04_09.SAR archive.4. Extract NW04_09.SAR to the root directory of the copied “6.20/6.40 Installation Master (Edition Sept. 2006)” DVD using the SAPCAR 6.40 for your operating system. For more information, see SAP Note 212876.5. Start SAPinst as described in the installation guide.
—————<07/APR/06, D028955>
(Add. Java Comp., ADS:) Running ADS with non-supported platforms
Adobe document services (ADS) are currently not supported to run natively on all platforms supported by SAP systems based on SAP NetWeaver, in particular 64-bit platforms.
To use ADS in SAP landscapes that are set up on non-supported platforms, you haveto install an additional stand-alone AS Java on a platform supported by ADS. For more information, see SAP Note 925741.
21/JUL/05
Make sure that you add to the system environment variable path the value %JAVA_HOME%\bin
05/JAN/05
To install the central instance (ABAP) or central services (SCS) instance (Java), you can also use Windows Server 2003 Standard Edition. In the installation guide (version 1.00) this Windows version is not stated in the respective section under “Hardware and Software Requirements”.
15/JUN/05
The quicklinks /ti and /network stated in the installation guides have become obsolete and are no longer available on SAP Service Marketplace:
<D041479, 23/NOV/04
(Add. Java Comp., ADS:) Java Startup parameter
Make sure that the Java Startup parameter does NOT contain a ‘=’, it must to be: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine. services.ts.jts.ots.PortableInterceptor.JTSInitializer
04/AUG/04
Do not use network drives, when you copy CDs or DVDs manually to local disks. If you want to use network drives, use the “Copy To” option in SAPinst.
25/JUN/04—
Procedure for “Reducing the Size of the File Cache”
To reduce the size of the file cache under Windows Server 2003 and Windows 2000 Server, in some guides the procedure for reducing the size of the file size is not correct. Use one of the following procedure instead:
Windows Server 2003:
Choose “Start” -> “Control Panel” -> “Network Connections” -> “Local Area Connections”.Windows 2000:
Choose “Start” -> “Settings” -> “Control Panel” -> “Network and Dial-up Connections” and double-click “Local Area Connections”.a) In the “Local Area Connection Status” dialog box, choose “Properties”.b) In the “Local Area Connection Properties” dialog box, double-click “File and Printer Sharing for Microsoft Networks”.
If you cannot select “File and Printer Sharing for Microsoft Networks”, this option has not yet been installed. To install it, you need the Windows Server CDs.c) Select “Maximize data throughput for network applications”.d) To confirm your entries, choose “OK”.
22/JUN/04
(SRM 4.0 [SRM 5.0 Server]): Read the composite SRM 4.0 Installation Note 726147, where you find a list of all SAP Notes related to the installation of your SAP SRM 4.0 system.
3 Installation
—————–<26/OCT/07, D033923>——————————–
If you use network drives for mapping or mounting the installation DVDs, make sure that the <sapsid>adm user has access to the UNC paths of the network drives. If the user does not yet exist, you have to create the user manually before you install the SAP system. Instead of using UNC paths, you can either copy the DVDs locally before you start the installation, or you copy the DVDs during the installation by using the “Copy Package To” function on the SAPinst screen when you are asked for the installation DVDs (in elder SAPinst releases the copy function might be named differently).
—————–<26/OCT/07, D033923>——————————–
Problems with different DLLs in SAP MMC when installing 6.40 systems on a host where you already installed an 7.00 (or higher) system.
You might get an error message similar to this:
ERROR 2007-10-23 12:07:04 [ianxbmmc.cpp:220]
CIaNtMMC::create(const map<iastring,iastring>&)
lib=iamodnt module=CIaNtMMC
MOS-01220 Missing file ‘C:\WINDOWS\system32\SAPMMC.DLL’. Copy the file manually.
ERROR 2007-10-23 12:07:04 [ianxbmmc.cpp:87]
CIaNtMMC::create(const map<iastring,iastring>&)
lib=iamodnt module=CIaNtMMC
MOS-01234 The specified procedure could not be found.
! Error in execution of a ‘LoadLibrary’ function, line (221), with parameter(s) (C:\WINDOWS\system32\SAPMMC.DLL).
ERROR 2007-10-23 12:07:04 [ianxbmmc.cpp:337]
CIaNtMMC::create(const map<iastring,iastring>&)
lib=iamodnt module=CIaNtMMC
MOS-01218 Unable to register SAP snap-in in the MMC.
To solve the problem, download the 710 SAP MMC MSI installation package from SAP Service Marketplace at: http://service.sap.com/swdc and install the 7.10 SAP MMC and other DLLs. The 7.10 MMC and DLLs are downward-compatible to the 7.00 and 6.40 kernels. Continue with the installation of your SAP product.
01/SEP/06
Use the SAP NetWeaver 04 SR 1 Kernel DVD for your database for the installation, except for Informix 10. For Informix 10, you must use the Informix 10.00 DVD.
——————–<D025095, 23/AUG/06>—————————
Although you perform a Unicode installation, SAPinst might also ask for the non-Unicode kernel DVD. Therefore have this DVD available for the installation.
———————–<D040270, 22/AUG/06>—————————-
(Java, KMC:) Error “Java Engine did not reach state “Start Application”
During the installation of the KMC, you get the following error message:
“CJS-20058 Java EE Engine of SAP system <SAPSID> did not reach state “Starting Applications” after xxx seconds: giving up.”
To solve the problem, restart the Java engine manually.

———————–<D025095, 18/AUG/06>—————————-
Edition July 2007 only: (SAP BW 3.1:) Incorrect index entries
After the installation, the PACKCHECK_EXCEPT-OBJ and PACKCHECK_EXCEPT ~0 indexes may contain incorrect entries. You can ignore this message.

11/JUL/06
Installation in mixed (heterogeneous) environment
If you install in a mixed environment (32-bit and 64-bit) for example a dialog instance, make sure that in the installation screen ABAP System > Instance Directories, where you are asked for the “Location of SAP System Executable”, you choose “Yes, locate executables on central instance host”, before you choose “Next”.
04/APR/06
You copied the installation DVDs to disk.
You get the error FSL-02015 Node <path> does not exist.
In this case, make sure that the paths to the location of the copied DVD do not contain any blanks.
——-<30/NOV/05, D019130>——————
ABAP: UNICODE Conversion error
During the import into a UNICODE system the following error might occur (for example, in SAPCLUST.log):
myCluster (63.2.Imp): 2085: (Warning:) inconsistent field names (source): physical field K1N05 appears as logic K1N5.
myCluster (63.2.Imp): 2086: (Warning:) further investigation recommended.
myCluster (63.2.Imp): 1924: error when checking key field consistency for logic table TACOPC .
myCluster (63.2.Imp): 1927: logic table is canonical. myCluster (63.2.Imp): 1930: received return code 2 from c3_uc_check_key_field_descr_consistency.
myCluster (63.2.Imp): 1224: unable to retrieve nametab info for logic table TACOPC .
myCluster (63.2.Imp): 8032: unable to acquire nametab info for logic table TACOPC .
myCluster (63.2.Imp): 2807: failed to convert cluster data of cluster item.
myCluster: CLU4 **00001**
myCluster (63.2.Imp): 319: error during conversion of cluster item.
myCluster (63.2.Imp): 322: affected physical table is CLU4.
(CNV) ERROR: code page conversion failed
rc = 2
The problem is caused by incorrect data which should have been removed from the source system before the export.
Use one of the following workarounds:
Modify DDL<dbs>.TPL (<dbs> = ADA, DB2, DB4, DB6, IND, MSS, ORA) before the R3load TSK files are generated; search for the keyword “negdat:” and add “CLU4″ and “VER_CLUSTR” to this line.Modify the TSK file (most probably SAPCLUST.TSK) before the R3load import is (re-)started; search for the lines starting with “D CLU4 I” and “D VER_CLUSTR I” and change the status (i.e. “err” or “xeq”) to “ign” or remove the lines.
05/OCT/05
Do not use user <sapsid>adm for the installation
For the installation of your SAP system and the latest Support Package (SP), do not use the user <sapsid>adm. For a local installation you can use a local user, for a domain installation you must use a domain user. Both users must be members of the Local Administrators group.
<D035521, 04/AUG/2005>
(Java:) Dialog Instance Finalization Java Add-In Installation
Chapter “Running SAPinst on Windows” -> Table: “Installation Services for a Java Add-In Installation”
If you have a central or distributed ABAP system, and you want to run the installation service “Dialog Instance Finalization” for a Java Add-In installation, you require an ABAP dialog instance as prerequisites. Run the installation service “Dialog Instance Finalization” on the host where you have installed the ABAP dialog instance.
<D034882, 21/JUL/05>
Problems may occur when you are logged on as domain user and perform a local installation. If you get an error message that the user does not exist, check the network access to a domain controller and your Windows configuration. If this does not help and you want to perform a local installation only and you do not need to access any domain accounts, do the following:
Create a local user, and add it to the local Administrators group. Log on as this user and start the installation again from beginning.
<D027171, 29/JUN/05>
SAPinst GUI crashes: “guiengine: no GUI connected”
When browsing for a software package or file during the dialog phase of the installation, SAPinst GUI crashes with the error “guiengine: no GUI connected; waiting for a connection on host <host_name> port 21212 to continue with the installation”.
To solve the problem, reconnect with the GUI to SAPinst and enter the path to the software package or file manually. Then continue with the installation.
20/APR/05
(R/3 E4.70 Ext.Set 2, SR1, CRM 4.0 SR1:) ITS is not available
By mistake, in the guide (section “New Features”) it is written that the Internet Transaction Server (ITS) is automatically installed and you can use it by activating it. This is not correct. Therefore, ignore all sections with information on ITS in this guide.
30/MAR/05
The installation hangs when extracting archives or installing DLLs or you get a warning about an unsigned non-driver installation behavior.
In this case change the Windows Policy Settings under “Security Settings” -> “Local Policies” -> “Security Options” for “Devices: Unsigned driver installation behavior” to “Silently succeed”.
————–<D039661 ,31/JAN/2005>—————————
(ECC 5.0 SR1, Addit. Java Comp.:) Pop-up requires post-processing steps
During the installation of ERP Java components a pop-up appears to perform manual post-processing steps and to check callSdmViaSapinst.log.
This log contains an error message like this:
PM Info: Finished successfully: software component ‘FSCM_BD’/’sap. com’/'SAP AG’/'05.20041202080033′
Dec 16, 2004 4:37:42 PM Warning: Caught CVersProxyAccessException while saving repository: CVersAccessExceptionError writing new entries into COMPVERS: java.sql.SQLException: [DataDirect][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.
Dec 16, 2004 4:37:42 PM Info: Starting: Initial deployment: Selected development component ‘com.sap.hcm.ls.webapps’/’sap.com’/'SAP AG’/'300. 0520041202144419.0000′ will be deployed.
Ignore this pop-up and continue with the installation.
02/DEC/04
Automatically restarted SAPinst, does not remember command line parameters after log off.
If you start SAPinst from the command line with specified parameters, for example with a specific host name, and you are asked to log off and log on again, SAPinst restarts automatically but does not use the parameters specified.
To solve the problem, stop SAPinst and restart it with the respective parameters from the command line.
02/DEC/04
Problems with SAPinst Selfextractor
If you are asked during the installation to log off and on again during the installation, you might get afterwards the following error messages:
- This program is not responding.
- the application failed to initialize because the window station is shutting down.
- iancsysex.c:716: WaitForSingleObject() failed: The handle is invalid.
In this case choose ‘OK’ in the Error Message Window to solve the problem.
4 Post-Installation

———————–<24/FEB/09, D041479>————————–
Dealing safely with installation directories
Keep all installation directories until you are sure that the system, including all instances, is completely and correctly installed. Once the system is completely and correctly installed, make a copy of the installation directories with all their contents and save it to a physically separate medium, such as a DVD or a USB drive separate from your installation hosts. This might be useful for analyzing issues occurring later when you use the system. For security reasons, do not keep installation directories on installation hosts, but make sure that you delete them after saving them separately.
——————-<I045708, 24/JUL/08>—————————-
ABAP+Java,Java: Keystore views are not created during the very first
start
You get an error like the following in /usr/sap/<SAPSID>/<INSTANCE>/j2ee/cluster/server0/log/defaultTrace.0.trc
File parsed: /usr/sap/QO1/JC00/j2ee/cluster/server0/log/defaultTrace.0.t FOUND “Line 336: fatal” CREATED ON Wed Jul 2 15:09:28 2008 IN /usr/sap/Q/JC00/j2ee/cluster/server0/log/defaultTrace.0.trc: #1.5#0017A41132BE002000002A000032850004510A33DD78DA#1215004168517#com.sap.engine.services. keystore##com.sap.engine.services.keystore#######Thread[_keystore_manage_system_thread_,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Fatal#1#/System/Security#Java###Source: com.sap.engine.services.security.exceptio.BaseSecurityException: Unexpected – cannot create a configuration.;
Description: system user based security support for view [TicketKeystore and user [null] not generated; Consequences: keystore view [TicketKeystois not created for user [null]; Countermeasures:see log for details##
FOUND “Line 337: fatal” CREATED ON Wed Jul 2 15:09:28 2008 IN /usr/sap/Q/JC00/j2ee/cluster/server0/log/defaultTrace.0.trc: #1.5#0017A41132BE002E000002B000032850004510A33DD79AA#1215004168517#com.sap.engine.services.keystore##com.sap.engine.services.keystore#######Thread[_keystore_manage system_thread_,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Fatal##Jav (thread: _keystore_managed_system_thread_, view:TicketKeystore , user: n – create view permissions failed:
To solve the problem, proceed as described in SAP Note 1230057.
———————–<D044990, 03/JUN/08>————————-
You see error messages like the following in transaction ST11 (error log files) every time when the SAP system is started (IGS and abap appserver with all processes are up and running):
[Thr 4448] Tue Apr 29 12:35:13 2008
[Thr 4448] *** ERROR => SncPDLInit(): DlLoadLib(”sncgss64 .dll”)=DLENOACCESS
[sncxxdl.0340][Thr 4448] *** ERROR => SncPDLInit()==SNCERR_INIT, Adapter (#0) sncgss64.d
[sncxxdl.0604][Thr 3108] Tue Apr 29 12:35:14 2008
[Thr 3108] *** ERROR => SncPDLInit(): DlLoadLib(”sncgss64 .dll”)=DLENOACCESS
[sncxxdl.0340][Thr 3108] *** ERROR => SncPDLInit()==SNCERR_INIT,
Adapter (#0) sncgss64.d
[sncxxdl.0604][Thr 3676] Tue Apr 29 12:35:14 2008
[Thr 3676] *** ERROR => SncPDLInit(): DlLoadLib(”sncgss64 .dll”)=DLENOACCESS
[sncxxdl.0340][Thr 3676] *** ERROR => SncPDLInit()==SNCERR_INIT, Adapter (#0) sncgss64.d
[sncxxdl.0604]
Solution:
1. Apply the latest kernel, IGS, and support packages.2. Adjust TCP/IP connection IGS_RFC_DEST as follows:a) Run transaction SM59.b) Open TCP/IP connection IGS_RFC_DEST.c) Set the program id to IGS.<SAPSID>d) Make sure that the fields for gateway host and gateway service are empty.3. Adjust TCP/IP connection IGS_RFC_DEST in the same way as you did with TCP/IP connection IGS_RFC_DEST.
————————<I808897, 25/AUG/06>————————–
EP: SP11 required
After the installation has finished successfully, you must patch your EPsystem to Support Package 11.
——————16/MAR/06——————————-
Back up the transport directory before deleting the SAP System.
If you use UNINSTSAP.EXE to delete an SAP system or SAP instance, back up the transport directory (\usr\sap\trans) before, otherwise the directory may be deleted.
————- <d019527, 13/JAN/06> ———————————-
Unable to perform job COLLECTOR_FOR_PERFORMANCEMONITOR
After the installation the following error message appears in the system log (TA SM21):
EB9 Batch scheduler: Unable to perform job
COLLECTOR_FOR_PERFORMANCEMONITOR
ECL > Cause: Planned start date too far in the past
ECM > Action: De-allocate batch job
To solve the problem, re-schedule the job (e.g. by copying the old one to SM37).
————–<I027641 ,21/FEB/05>———————-
(ECC 5.0 SR1, Add. Java Comp., XSS) Errors in callSdmViaSAPinst.l
The installation of ERP 2004 SR1 Java components finished successfully. Nevertheless a pop-up requests to perform manual post-processing steps
and to check callSdmViaSapinst.log., for example:
***********************************************************************
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/tra/trp/trt and wait. …
***********************************************************************
Background:
The WebDynpro applications have a lazy start mechanism. This means that they are started upon request. It is normal that some of them need to be stopped after server start. They are started when a request is sent to them. The reason for the error messages listed in the log file is that the applications were requested before the deployment of all referenced applications had finished. When a Web Dynpro application tries to start, it first tries to start all referenced components. The traces show that some of the applications are not available, because they were not deployed at that moment.
If you can start the applications listed in the error message manually, you can ignore these error messages.
08/FEB/05
(SCM 4.0, SCM 4.1:) BW-specific post-installation steps
The following settings are necessary if you want to:
Performing a client copy which is mandatory for using mySAP SCMMaintain a BW-client that is necessary for Demand Planning in mySAP SCM
Note, that there are dependencies in the installation of SCM-Server and liveCache.
The following BW-specific post-installation steps need to be carried out:
1. Installation of SCM Server.2. Import additional languages (optional).3. Apply all Support Packages.4. Create Logical System: SPRO -> Integration with SAP components -> Integration of SAP SCM and SAP R/3 -> Basic Settings -> Name logical systems.
Alternatively you can use transaction BD54 for that.5. Maintain a client and assign logical system to the new client using transaction SCC4 or IMG-PathSPRO -> SCC4 or IMG-Path SPRO -> Integration of SAP SCM and SAP R/3 -> Basic Settings -> Assign logical systems to a client.
If you need more than one new client repeat the steps 4 and 5.6. If the new client(s) should not be used in combination with liveCache (e.g. Lean-Installation), then the client(s) have to be marked as non liveCache relevant. To do so, execute report /SAPAPO/OM_NON_LC_RELEVANT_CLT and mark the new client(s) as not liveCache relevant.
You should not execute the report for clients that will be used in combination with liveCache.7. If any of the new clients will be used with liveCache, thena) Install LC as described in the liveCache Installation Guide and apply latest liveCache-Builds.b) Create LCA/LDA Connections for LC as described in the liveCache Installation Guide.8. Log on to one of the new clients withsap*/pass.9. Copy client 000 using transaction SCCL with user profilSAP_CUST(Customizing ).10. If one of the clients will be used with liveCache: Create RFC destination and RFC-User for global working on the liveCache, see SAP Note 305634.11. Execute report /SAPAPO/DELETE_LC_ANCHORS using transaction SE38.12. Repeat the steps 8 to 11 for all new clients that have been created.13. Set parameterlogin/system_client = <one of the new clients (e.g. productive client)>in the default profile or in the instance profile (see also SAP Notes 116432 and 116520) and delete entrylogon/system_clientif it exists.
Do not change this profile setting after you executed step 16.14. Stop and restart the system in order to activate the default profile.15. Logon to the new client that was set in step 13.16. Start transaction RSA1 and enter the logical system name of this client in the upcoming popup.
Note: It may be possible that you have to enter table RSADMINA and define the BW client before you can execute RSA1.
——————-<I801946, 03/FEB/05>———————-
(CRM 4.0 SR1, CRM Add. Java Comp.:) IC requires SAF to be installed
The IC (Intelligence Connector) requires the Software Agent Framework (SAF) to be installed. To check if the SAF is installed correctly, see section 6.3.4 “SAF: Performing System Checks” in the documentation “Installation Guide – Java Components for SAP Customer Relationship Management 4.0 SR 1″.
————————<D021063, 09/DEC/04>————————–
(Java:) Timeout during the start-up of the J2EE Engine
When you start J2EE Engine for the first time, the J2EE Engine does not come up until it runs into timeout. The reason for this is that the J2EE Engine takes more time to get synchronized from the database when it is started for the first time.
To solve the problem, check if the engine is already started by verifying the log file in the work directory of the instance. If the engine is started, press ‘Retry’. The engine will then come up.
——————<I024157, 09/DEC/04>——————————-
(Java:) JDI: Enhance maximum memory for Java compiler
If you intend to install Java Development Infrastructure (JDI) on your SAP Web AS Java, enhance the default settings for maximum memory for the java compiler as described in SAP Note 759669.
————————<D037196>, 26/NOV/04————————-
(Java:) Strong Crypto deactivated after dialog instance installation
If you have installed the SAP Java Cryptographic libraries and a dialog instance, the following problems arise:
The service com.sap.security.core.ume.service is not properly configuredThe service SSL of the additional dispatcher is set to “manual”
Solution:
1. Open the visual configtool.2. Switch to the configuration editor mode.3. Select “Edit Mode” and edit the property sheet “pcluster_data/server/cfg/services/Propertysheet com.sap.security.core.ume.service”4. Set entry “ume.usermapping.unsecure” to FALSE.5. Set the startup mode of the service ssl to “always” for global dispatcher configurations and instance specific dispatcher configurations.
—————<D041479, 26/NOV/04>—————————
(Add. Java Comp., ADS): JStartup Framework error in error log can be ignored.
When checking the log files of the Adobe Installation the following error might appear in the error log:
Error: An error occured while restoring the cluster instances states
Error: JStartup Framework is not able to deliver an information about the cluster control instances!
Error: Received exception when restoring Engine state: JStartup Framework is not able to deliver an information about the cluster control instances!
You can ignore this error as it does not affect the installation.
29/JUN/04
(SRM 4.0 [SRM 5.0 Server]): “Performing Basic Operations” chapter in installation guide
The paths to the SAP Help Library sections have changed. Use the following information instead to find the specific sections in the SAP Help Library:
Set up operation modes – transaction RZ04:
Solution Life Cycle Management -> System Management -> Configuration -> Operation ModesSet up logon groups – transaction SMLG:
Solution Life Cycle Management -> System Management -> Configuration -> Dynamic Logon Load Distribution -> The SAP LogonSet up administrators:
Solution Life Cycle Management -> System Management -> Background Processing -> Authorizations for Background Processing
Schedule background jobs:
Solution Life Cycle Management -> System Management -> Background Processing
Install a printer:
Solution Life Cycle Management -> System Management -> SAP Printing Guide
Configure the system log:
Solution Life Cycle Management -> System Management -> Tools for System Monitoring -> System log -> Configuring the System Log
———– <C5036314, 19/FEB/04> —————————-
(Add. Java Comp.:) OutOfMemoryError during installation of additional applications
The reason may be that the standard perm size of your system is not sufficient for the Java Virtual Machine.
In this case you have to increase the perm size as described in SAP Note 693662.
————- <I024187, 04/FEB/04> —————————-
(Add. Java Comp.:) Additional Java components are not accessable after redeployment of a specific application or upgrade of SAP Web AS Java. For more information, see SAP Note 701277.
16/12/02
Edition July 2007 only: (BW 3.1, Unicode only:) Apply New Libraries after J2EE Engine installation
If you have installed the SAP J2EE engine, you have to apply patches JLIBNUC1.sar and JLIBNUC2.sar in directory
/usr/sap/SAPSID/DVEBMGS<Number>/j2ee/os_libs.
See SAP Note 672955 for more information.

5 High Availability (MSCS)
16/NOV/05
As of NW04 SR1, you can install your SAP Web Application Server in high availability mode. For more information, see SAP Note 803018 and SAP Service Marketplace at http://service.sap.com/ha
18/OCT/05
igs.xml configuration file is not updated with the virtual host name of the gateway.
After you have clustered your SAP system, check the …\usr\sap\U92\DVEBMGS<InstNumber>\igs\conf\igs.xml file and change the gwhost value to gwhost=”<SAPVirtualHostName>”. Then restart the server. Otherwise you might get error messages in the dev_rfc.trc file.

————– <D000312, 30/MAY/05>————————–
(Add. Java Comp., ADS:) Synchronization Exception at J2EE Engine start
During a high-availability installation, in phase “Start J2EE Engine for Online Deployment”, the installation stops because the J2EE Engine does not come up.
Error message in sapinst.log:
J2EE Engine of SAP system <SID> did not reach state “Starting Applications” after xxx seconds: giving up.
To solve the problem, extend the URL for the dbpool by the connect option longDataCacheS set to 2048.
Example:
configtool, secure store:
Key: jdbc/pool/J2E/Url
Value: jdbc:datadirect:sqlserver://VSMOM:1433;databasename=J2E;
longDataCacheSize=2048
For more information, see SAP Note 819130.