SAP Basis Tech Supports

Symptom

***********************************************************************
*
* Installation on Unix
* Based on SAP NetWeaver 7.0 SR3
* (SAP NetWeaver 7.0 SR3,
* SAP ERP 6.0 (2005) SR3,
* SAP CRM 5.0 SR3,
* SAP SRM 5.0 SR3,
* SAP SCM 5.0 SR3,
* SAP Solution Manager 7.0)
*
*
***********************************************************************

Other terms

SAPinst, SAP NetWeaver 7.0 SR3, SAP ERP 6.0 (2005) SR3, SAP CRM 5.0 SR3,
SAP SRM 5.0 SR3, SAP SCM 5.0 SR3, SAP Solution Manager 7.0
Reason and Prerequisites

Problems discovered after the publication of the installation guide

Solution

DO NOT CHANGE OR ADD INFORMATION TO THIS NOTE !
If you want to contribute something, please send a mail to:
Klaus Billig klaus.billig@sap.com

Always use the latest documentation version (see SAP Service Marketplace at:
http://service.sap.com/installNW70
http://service.sap.com/erp-inst
http://service.sap.com/crm-inst
http://service.sap.com/srm-inst
http://service.sap.com/instguides -> SAP Business Suite Applications -> SAP SCM -> SAP SCM Server
http://service.sap.com/instguides -> SAP Components -> SAP Solution Manager -> Release 7.0

Contents

Sections of this note are:

1. General2. OS-Dependencies3. Pre-Installation4. Installation5. Post-Installation6. Corrections in the installation guides

Date Section Description
———————————————————————–
JUL/23/09 4 SAPINST fails at phase “Start Java Engine”
MAY/19/09 5 AIX: Check user limits for operating system users
MAY/18/09 3 Use current version of SAPINST 7.00
MAR/27/09 4 ABAP, ABAP+Java, AIX: Do not use 01 or 02 for instance number
MAR/13/09 4 Restarting sapinst aborts with error message
MAR/05/09 5 Delete usagetype.properties file manually due to security reasons
FEB/24/09 4 Make sure that GID of ’sapinst’ is unique
FEB/24/09 5 Dealing safely with installation directories
JAN/30/09 4 Uninstall Diagnostics Agent only: Manually delete the adm user.
DEC/19/08 3 Dialog Instance: Check entries in sapservices file and naming of profile backup files
OCT/10/08 3 ABAP+Java,Java, Java Add-In: Exchange control.xml when installing with virtual host name
OCT/02/08 1 mounts under // must be permanent
SEP/22/08 4 Do not use an existing when installing a new SAP system
AUG/28/08 4 Error when using the “Media Browser” screen
JUL/24/08 5 ABAP+Java,Java: Keystore views are not created during the very first start
JUNE/24/08 3 Dialog instance, Java Add-In: no gateway instance with same SAPSID
JUNE/02/08 4 ABAP,ABAP+Java: FJS-00003 TypeError: dir_instance.get is not a function
MAY/16/08 4 Problem: installation directory mounted with NFS
APR/25/08 6 ABAP+Java, Java: Inst.guide correction: Default group of users J2EE_GUEST and Guest
APR/16/08 5 ABAP+Java: Individual passwords not assigned to ABAP UME users
APR/02/08 4 zLinux: ERP Rapid Configuration: Execution of the command “db2radm -m chkc” failed
APR/02/08 5 BI Java: BEx Web Applications: Access denied
MAR/26/08 5 EPC, EP: “HTTP response: 500 – Internal Server Error” when accessing Forms Builder iView
MAR/25/08 4 ABAP: liveCache Client in SCM Installations
MAR/14/08 4 Java Add-In: Installation fails in phase ‘Create Java users’
MAR/05/08 5 EP: KM integration of CAF does not work at all
MAR/03/08 5 ABAP+Java, Java, Linux, AIX, Diagnostics Agent: Upgrade JDK
FEB/21/08 4 ABAP+Java, Java: SAPinst terminates with error message in step initED
19/FEB/08 4 ABAP+Java,Java Add-In:FSL-01003 Unable to modify account user=”adm” uid=”adm”
FEB/19/08 4 ABAP+Java, Java: Assign a unique User ID for the adm user.
JAN/24/08 5 RAISE_EXCEPTION short dumps occur
DEC/19/07 4 ABAP+Java, Java Add-In: SAPinst terminates with error message in step createJSF
OCT/29/07 4 SAPinst GUI: Close buttons (’X') of message boxes do not work
02/MAY/07 2 Release of HP-UX 11i for Itanium processor family
23/AUG/07 4 Using “Back” button with “Typical” Mode
31/JUL/07 3 OS users: do not delete shell initialization scripts
17/JUL/07 4 Linux x86_64: Error “cannot open libj9vm22.so”
12/JUN/07 4 Uninstall: Error message FCO-00011
01/JUN/07 4 Uninstall aborts with error message
04/MAY/07 5 Errors in syslog: Unable to create directory
05/MAR/07 3 Copy Installation Master DVD if only one DVD drive available
05/FEB/07 5 Post-installation step before running the Template Installer
15/NOV/06 5 Incorrect permissions of softlinks to sapinit system startup script
15/NOV/06 5 Incorrect permissions of some files under DIR_INSTANCE/j2ee/ctc
24/OCT/06 5 Error message when you close SAPinst GUI
19/OCT/06 4 Error during uninstall on HP-UX: “Login adm is currently in use”
11/OCT/06 4 Java HA: SAPinst hangs during deployment
18/SEP/06 2 AIX 5.3, AIX 5.2 Maintenance Level (ML)
08/SEP/06 5 BI Java / PI: Setting Environment Variable
CPIC_MAX_CONV
23/AUG/06 4 Non-Unicode kernel DVD required for Unicode installation
14/AUG/06 3 Wrong kernel DVDs for Unicode installation
21/JUN/06 3 same password for local OS user accounts on all hosts
14/JUN/06 5 Java: Passwords are logged plain in the http-access logs
31/MAY/06 4 Java: Import of software units or usage types fails with message “Access denied”
29/MAY/06 5 Install Replicated Enqueue Server for HA
24/MAY/06 4 Multiple entries for the same parameter(s) on
“Parameter Summary” screen
19/MAY/06 4 Sharing same JDK between system based on
NetWeaver 2004s SR3 and other software
18/APR/06 3 Installing dialog instance(s) for an SAP system
upgraded to SAP NetWeaver 2004s SR3
12/APR/06 5 (PI): Client copy considerations
10/APR/06 5 ABAP, ABAP+Java: Check value of parameter
rdisp/bufrefmode in DEFAULT.PFL
06/APR/06 5 Java on SUNOS/X86_64 5.10 – 64 Bit:
FATAL: Caught OutOfMemoryError! Node will exit with exit code 666
04/APR/06 5 (PI): Apply patch before running the Template Installer
28/MAR/06 5 (PI): Increase number of dialog work processes
22/MAR/06 5 Java, ABAP+Java: J2EE Engine reboots permanently
17/MAR/06 5 ABAP dialog instance: check parameter
login/system_client
10/MAR/06 4 Java: SDM deployment fails
28/FEB/06 1 New SAPCAR for products based on SAP NW 2004s
05/DEC/05 4 ABAP: UNICODE conversion error

======================================================================
1 General

======================================================================
This SAP Note contains information relevant to the following installation types (usage types, software units). Since the Business Suite 2005 SR3 solutions are based on SAP NetWeaver 7.0 SR3, you can also install the NetWeaver 7.0 SR3 usage types.
SAP NetWeaver 7.0 SR3, including:AS ABAP (ABAP)AS Java (Java)AS ABAP and AS Java (ABAP+Java)Development Infrastructure (DI)Business Intelligence Java (BI Java)Enterprise Portal (EP)Mobile Infrastructure (MI)Process Integration (PI)ERP 6.0 (2005) SR3, including:ERP Application Set (ERP-APP)ERP Biller Direct (BD)ERP Business Packages (BP-ERP)ERP Learning Solution (Content Player) (LSOCP)ERP Extended E-Selling Components (XECO)ERP Self Services (XSS)CRM 5.0 SR3, including:CRM Application Set (CRM-APP)CRM Java Components (JCRM)CRM Business Packages (BP-CRM)CRM Mapbox (MBX)SRM 5.0 SR3 including:SRM Application Set (SRM-APP)SRM Live Auction Cockpit (SRMLAC)SRM Business Packages (BP-SRM)SCM 5.0 SR3 including:SAP SCM Server (SCM)Store User Interface (SUI)Web Communication Layer (WCL)

This note contains information relevant to the following installation types (usage types):
AS ABAP (ABAP)AS Java (Java)AS ABAP and AS Java (ABAP+Java)Business Intelligence Java (BI Java)Development Infrastructure (DI)Enterprise Portal Core (EPC)Enterprise Portal (EP)Mobile Infrastructure (MI)Process Integration (PI)

Each entry is marked with a prefix (ABAP, Java, ABAP+Java, BI, DI, EP, MI, PI) to make clear which installation type the information applies to.
The prefix “HA” is for “High Availability”.
If there is no prefix, the information applies to all types.

See also related SAP Notes “SAP NetWeaver 7.0 SR3 Installation on UNIX:” for database-specific information:

1094599 SAP NetWeaver 7.0 SR3 Installation on UNIX:Oracle1135524 SAP NetWeaver 7.0 SR3 Installation on UNIX: MaxDB1125951 DB6: SAP NetWeaver 7.0 SR3 – Installation on UNIX

SAP system installation only on 64-bit platforms (exception: you can install dialog instances furtheron on 32-bit platforms):

As of SAP NetWeaver 7.0 SR3 and Business Suite 2005 SR3 (SAP ERP 6.0, SAP CRM 5.0 SR3, SAP SCM 5.0 SR3, SAP SRM 5.0 SR3)you can only install dialog instances on 32-bit platforms.All remaining SAP system instances (central instance, database instance, central services instance (SCS), ABAP central services instance (ASCS)) you can only install on 64-bit platforms.Therefore the folder “SAP Systems” is not available on the “Welcome screen”, when you start the installation from a installation master DVD for 32-bit.
You may need to install dialog instances on 32-bit if you want to use 32-bit SAP NetWeaver components, such as Adobe document services. We recommend, however, to first check whether these 32-bit components can run on 64-bit operating systems. If so, we recommend to use 64-bit systems for these components, including the dialog instance.
If you want to install a complete SAP NetWeaver 7.0 SR3 SAP ERP 6.0, SAP CRM 5.0 SR3, SAP SCM 5.0 SR3, SAP SRM 5.0 SR3) system on a 32-bit platform, you have to proceed as follows:
1.) Install a SAP NetWeaver 7.0 SR2 (SAP ERP 2005 SR2, SAP CRM 5.0 SR2 SAP SCM 5.0 SR2, SAP SRM 5.0 SR2) system.
2.) Patch this system to SAP NetWeaver 7.0 SR3 (SAP ERP 6.0, SAP CRM 5.0 SR3, SAP SCM 5.0 SR3, SAP SRM 5.0 SR3).
Support package levels of SAP NetWeaver 7.0 SR3 / Business Suite 2005 SR3:
For more information on support package levels of SAP NetWeaver 7.0 SR3, see SAP Note 789220.
For more information on support package levels of SAP ERP 6.0, see SAP Note 774615.
For more information on support package levels of SAP CRM 5.0 SR3 , see SAP Note 837413.
For more information on support package levels of SAP SCM 5.0 SR3 , see SAP Note 850038.
For more information on support package levels of SAP SRM 5.0 SR3 , see SAP Note 819722.

New SAPCAR for products based on SAP NW 7.0

SAPCAR has been made downward compatible for all Releases. Due to this change, older versions of SAPCAR can no longer unpack the current SAR files. To unpack the archives, you need at least SAPCAR 700 or SAPCAR 640 with patch level 4 or higher.
For the latest SAPCAR version, see SAP Service Marketplace at service.sap.com/swdc.
For more information, see Note 212876.
———————–< D034879 OCT/02/08 >————————–
Make sure that the required mounts under // are permanent. Otherwise automatic start of the instance services will not work when you reboot the system.

======================================================================
2 OS Dependencies

======================================================================
This section contains operating system-specific information that is not covered by the installation guide.
As of SAP Web AS 6.40 SR1 (SAP NetWeaver ‘04 SR1) the former documentation “SAP Software on UNIX – OS Dependencies” has been re-integrated in the installation guides.
So, you find all OS-specific information furtheron in the installation guides.
See SAP Service Marketplace at:
http://service.sap.com/installNW70
http://service.sap. com/erp-inst
http://service.sap.com/crm-inst
http://service.s ap.com/srm-inst
As of SAP NetWeaver 2004s (7.0) SR1, the SAP Note “SAP Software
on UNIX : OS Dependencies for ” was merged with the
this SAP note (SAP NetWeaver Installation on UNIX).
NOTE:
For information on downloading patches from SAP, see http://service.sap.com/sp-stacks
Installation Perequisite Checker:
As of SAP NetWeaver 7. 0 (2004s) and Business Suite 2005 (CRM 5.0, ERP 6.0 (2005), CRM 5.0, SRM 5.0, SCM 5.0), you check the hardware and software requirements for your operating system (OS) and the SAP system instances using the Prerequisite Checker tool.
The Prerequisite Checker provides detailed information about the requirements that you need to meet before you start the installation. For example, it checks the requirements for the different installation services.
For more information, see chapter “Hardware and Software Requirements”
in the installation guide for your SAP solution and SAP Note 855498.

======================================================================
AIX:

Required swap space (update of the information in “Hardware and Software Requirements” in the installation guides):

Hard disk drives with sufficient space for swap:
Optimistic strategy:
At least 20 GB for the first SAP Instance to be installed on a server and at least 10 GB for each additional active SAP Instance on that serverDefensive strategy:
3 * RAM
For more information, see SAP Note 1121904.

======================================================================
HP-UX:
———————————————-
HP has released HP-UX 11i for the Itanium processor family.
HP-UX 11i for Itanium is built from the same code base as HP-UX 11i for PA-RISC and has the same look-and-feel.
In general, all OS requirements for HP-UX are valid for both the PA-RISC version and the Itanium versions.
There are some exceptions due to new functionality of the latest HP-UX releases.
For more information on HP-UX 11iv3 and HP-UX 11.31, see SAP Note 1031960.

======================================================================
LINUX:

======================================================================
3 Pre-Installation

======================================================================
———————-—————————-
Use current version of SAPINST 7.00
Symptom:
Make sure that you use the current version of SAPINST 7.00, available at http://service.sap.com/swdc -> Download -> Installations and Upgrades -> Entry by Application Group -> SAP Technology Components -> SAPINST -> SAPINST 7.00
If you do not use the current version you might get an error like “The evaluator class CCdCheckUserInput is missing in the registry.” during the “Define Parameters” phase of the installation.
Solution:
Proceed as follows:
1. Copy the installation master DVD to your local file system.2. Download the SAPINST 7.00 archive from SAP Service Marketplace (SMP) at service.sap.com/swdc -> Download -> Installations and Upgrades -> Entry by Application Group -> SAP Technology Components -> SAPINST -> SAPINST 7.00 -> .3. Extract the archive to your local file system.4. Replace the sapinst executable of the copied installation master DVD with the sapinst executable from the extracted archive.5. Start SAPinst as decribed in the installation guide.

———————–————————–
Dialog Instance: Check entries in sapservices file and naming of profile backup files
If you want to install an additional application server instance (AAS) to an existing SAP system, make sure that:
There is exactly one entry in the /usr/sap/sapservices file for each SAP instance installed on this host. Be sure to check that the entry refers to the correct profile.There are no profile backup files with an underscore ‘_’ in their profile name. If so, you must replace the ‘_’ with a ‘.’.
Example:
Rename /usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2_D20081204 to
/usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2.D20081204.

——————< D019130, 19/SEP/08 >—————————-
ABAP+Java,Java, Java Add-In: Exchange control.xml when installing with virtual host name
Symptom:
If you want to install an SAP system with virtual host name using environment variable SAPINST_USE_HOSTNAME on a host (distributed system: several hosts) on which other SAP system(s) already exist(s), youmustreplace the control.xml file of the installation master DVD with the modified control.xml file that is attached to this SAP Note.
Solution:
Proceed as follows:
1. Copy the installation master DVD to a local directory on the installation host(s).2. Go to tab strip “Attachments” of this SAP Note and download the attached control.zip file.3. Unpack the control.zip file.4. Go to the folder ///WEBAS/IND (for example /IM_LINUX_X86_64/NW701/WEBAS/IND) and replace the existing control.xml file with the new one that you got from control.zip.5. You can now start the installation as described in the installation guide.

Note:
If you do not apply the workaround described under “Solution”, you get various errors during the installation process (for example ‘instance has no properties’ in step ‘unpackJ2EEINSTALL’ if you install the Java Add-In). You then have to restart the installation with option “Run a New Option” after having done the modifications described above (choose “Run a new Option” on the “What do you want to do” screen).
———————–—————————
Dialog instance, Java Add-In: no gateway instance with same SAPSID
If you want to install the Java Add-In for an existing ABAP system or a dialog instance, make sure that no gateway instance with the same SAP System ID (SAPSID) exists in your SAP system landscape.
———————–—————————
OS users: do not delete shell initialization scripts
Do not delete any shell initialization scripts in the home directory of the OS users, even if you do not intend to use the shells that these scripts are for.
————————————————-
Copy Installation Master DVD if only one DVD drive available
If you are performing a local installation and there is only one DVD drive available on your installation host, you must copy at least the Installation Master DVD to the local file system.
————————————————-
Do not use kernel DVDs delivered before 11 August 2006 for Unicode installation:
Do not use your kernel DVD for a Unicode installation if you received it before 11 August 2006, and the material number of the DVD is one of the following:
HP-UX, Solaris: 51031943Linux: 51031944AIX, OS/400: 51031945Windows, Linux_X86: 51031946Solaris on x64: 51031911z/OS 64bit: 51031912

For the Unicode installation, you require instead one of the following DVDs:
HP-UX, Solaris: 51031791Linux: 51031777AIX, OS/400: 51031792Windows, Linux_X86: 51031778Solaris on x64: 51031835z/OS 64bit: 51031834

You can order these DVDs from SAP, or download them from SAP Service Marketplace at:
service.sap.com/swdc -> Download -> Installations and Upgrades -> Entry by Application Group -> SAP NetWeaver -> SAP NETWEAVER -> SAP NETWEAVER 2004s -> Installation and Upgrade …
Note that in a Unicode installation SAPinst may also require the non-Unicode kernel DVD.
————————————————-
same password for local OS user accounts on all hosts
If you install a distributed system and you do not use central user management (for example, NIS), and you use local
operating system user accounts instead, then adm and
the database operating system user must have the same
password on all hosts.
————————————————-
Installing dialog instance(s) for an SAP system upgraded to SAP NetWeaver 7.0 SR3
If you want to install a dialog instance for an SAP system upgraded to
SAP NetWeaver 7.0 SR3, do the following:

ABAP+Java system

================
1. Edit DEFAULT.PFL.a) Insert a line with the parameter ‘rdisp/msserv_internal = ‘and set it to a free port number.2. Edit the central services instance profile.a) Set the parameter ‘rdisp/msserv’ to 0.b) Insert a line with the parameter ‘rdisp/msserv_internal = ‘and set it to the port number that was assigned before to rdisp/msserv.c) Restart all instances.

Example:
========
DEFAULT.PFL
Before:
…
rdisp/msserv = sapms
…
After:
…
rdisp/msserv = sapms
rdisp/msserv_internal =
…Central services instance profile:
Before:
…
rdisp/msserv = 4711
…
After:
…
rdisp/msserv = 0
rdisp/msserv_internal = 4711
…

Java system

===========
1. Edit the central services instance profile.2. Set the parameter ‘rdisp/msserv’ to ‘0′.3. Insert a line with the parameter ‘rdisp/msserv_internal = ‘and set it to the port number that was assigned before to rdisp/msserv4. Restart the central services instance.

Example:
========
Central services instance profile:
Before:
…
rdisp/msserv = 4711
…
After:
…
rdisp/msserv = 0
rdisp/msserv_internal = 4711
…

ABAP system

============
1. Edit DEFAULT.PFL.2. Insert a line with the parameter ‘rdisp/msserv_internal = ‘and set it to a free port number.3. Restart all instances.

Example:
========
DEFAULT.PFL
Before:
…
rdisp/msserv = sapms
…
After:
…
rdisp/msserv = sapms
rdisp/msserv_internal =
…

======================================================================
4 Installation

======================================================================
———————————————–
SAPINST fails at phase “Start Java Engine”
Symptom:
SAPINST fails at phase “Start Java Engine”
Solution:
Proceed as follows:
1. Insert the following line into /sapmnt//profile/:
jstartup/native_stack_size = 20971522. Save .3. Continue the installation by choosing “Retry”.

————————————–
ABAP, ABAP+Java, AIX: Do not use 01 or 02 for instance number
If you are using NIM Service Handler (NIMSH), do not use 01 or 02 for the instance number. SAPinst uses the instance number for the internal message server port 39. The NIM client daemon uses reserved ports 3901 and 3902.
———————————————–
Restarting sapinst aborts with error message
Symptom:
After restart sapinst aborts with an error message like the following:
FKD-00049 XML parser error: error: no DTD specified, can’t validate in line 2, 2 in file /Install/statistic.xml.
Solution:
Remove the file statistic.xml from the installation directory and restart sapinst.
———————————————–
Make sure that GID of ’sapinst’ is unique
If you are installing an SAP system whose instances are to run on several hosts (distributed or high-availability system), make sure that the group ID of group ’sapinst’ is always different from the group ID of any other group (for example, of group ’sapsys’) that is used during the installation.
Example:
You are installing an additional application server instance to an existing SAP system.
Then you must make sure that the group ID of group ’sapinst’ that is created on the host of the additional application server instance is different from the group ID of any other group (for example, of group ’sapsys’) on the primary application server instance host of the existing SAP system.
———————-—————————
Uninstall Diagnostics Agent only: Manually delete the adm user.
Symptom:
You have uninstalled a Diagnostics Agent instance using SAPinst with installation optionSoftware Life-Cycle Options -> Uninstall -> Uninstall – Solution Manager Diagnostics Agent
After the uninstall with SAPinst has finished successfully, user adm is still existing.
Solution:
Delete user adm manually.

——————–—————————-
Do not use an existing when installing a new SAP system.
For example, if you have already installed an ABAP system, and want to install a Java system on the same host, make sure that you enter a SAP that is different from the of the first (ABAP) system.
———————-—————————
Error when using the “Media Browser” screen
Symptom:
You get the following error while you select an installation DVD
on the “Media Browser” screen:
Caught ESAPinstException in Modulecall:
could not call evaluator in class CCdCheckUserInput.
Solution:
Restart SAPinst and continue with the old installation option (choose “Continue with the Old Option” on the “What do you want to do” screen).
———————–————————-
ABAP,ABAP+Java: FJS-00003 TypeError: dir_instance.get is not a function
Symptom:
You get an error message like the following
ERROR:
FJS-00003 TypeError: dir_instance.get is not a function
(in script NW_ABAP_Prepare ind ind ind ind, line 13937: ???)
occurs during an installation
Solution:
1. Stop SAPinst2. Change following line in control.xml in respective sapinst_instdir
var maybeName = fmgt.getFSPath(dir_instance.get()). …
to
var maybeName = fmgt.getFSPath(dir_instance.value()). …

3. Restart SAPinst and continue your old installation

———————–—————————
Problem: installation directory mounted with NFS
Make sure that the installation directory is not mounted with NFS, or there might be problems when the Java Virtual Machine is started.
———————–—————————
zLinux: ERP Rapid Configuration: Execution of the command “db2radm -m chkc”fails
Symptom:
When performing ERP Rapid Configuration on zLinux, you get an error message like the following:
ERROR 2008-03-07 10:42:52.241
CJSlibModule::writeError_impl()
MUT-03010 Execution of the command “db2radm -m chkc” finished with
status TST_ERROR.
ERROR 2008-03-07 10:42:52.243
CJSlibModule::writeError_impl()
MUT-03010 Execution of the command “db2radm -m chkc” finished with
status TST_ERROR.
ERROR 2008-03-07 10:42:52.291 [sixxcstepexecute.cpp:951]
FCO-00011 The step setInstanceValues2 with step key
rapidconfig ind ind ind ind 0 0 NW_GetCI ind ind ind ind 1 0 NW_getDBIn
fo ind ind ind ind 2 0 NW_DB2_DBParameters ind ind ind ind 1 0 setInstan
ceValues2 was executed with status ERROR ( Last error reported by the
step :Execution of the command “db2radm -m chkc” finished with status
TST_ERROR.).
Solution:
Proceed as described in SAP Note 1151952.
———————–—————————
ABAP: liveCache Client in SCM Installations
Symptom:
When you install an SCM system, liveCache client software is automatically installed, even when you explicitly choose not to install liveCache server during the installation.
Solution:
There is no solution currently available. However, this has no effect on the functioning of your SCM system.
————————-————————–
Java Add-In: Installation fails in phase ‘Create Java users’.
Symptom:
Installation fails in phase ‘Create Java users’.
WARNING[E] 2008-03-13 16:29:46.295
CJS-30196 The function module “PRGN_GEN_PROFILES_FOR_ROLES”
cannot be used for ‘remote’ calls.
Solution:
Apply SAP Note 1126481.
————————-————————–
ABAP+Java,Java Add-In: FSL-01003 Unable to modify account user=”adm” uid=”adm”
Symptom:
You get an error message like the following:
=================================
WARNING 2008-01-16 18:30:18
Existing account adm is not a member of group sapinst. Changing membership of account.
ERROR 2008-01-16 18:30:18
FSL-05014 Command ‘/usr/sbin/usermod’ with parameters ‘-G “dba,oper,sapsys,sapinst” adm’ failed with return code 8: Login adm is currently in use
.
ERROR 2008-01-16 18:30:18
FSL-01003 Unable to modify account user=”adm” uid=”adm>”.
ERROR 2008-01-16 18:30:18
MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text undefined.
ERROR 2008-01-16 18:30:18
FCO-00011 The step createAccounts with step key |NW_Addin_SCS|ind|ind|ind|ind|0|0|NW_Users_Create_Do|ind|ind|ind|ind|3|0|createAccounts was executed with status ERROR .
================================
Solution:
1. Stop the ABAP stack as described in the installation guide (Additional Information -> Starting and Stopping the SAP System).2. Open a command prompt and execute the command ‘/usr/sbin/usermod’.3. Continue with the installation.

———————–————————–
ABAP+Java, Java: SAPinst terminates with error message in step initED
Symptom:
SAPinst terminates with the following error message:
FCO-00011 The step initED with step key |NW_Onehost|ind|ind|ind|ind|0|0|SA_Integrated|ind|ind|ind|ind|7|0|initED was executed with status ERROR
#
Variable group(sapsys) should be defined.
Solution: before starting the installation, the sapsys group should be created manually
———————–————————–
ABAP+Java, Java: Assign a unique User ID for the adm user.
Do n o t leave the field “User ID” empty on the screen
“Diagnostics Agent > OS User Parameters”. Instead, you have to enter
a user ID in this field that is n o t already assigned to the
adm user or to any other user.
You can do this in one of the following ways:
If you choose parameter mode “Typical”, proceed as follows:
1.) Check the entry in the “User ID” field for adm on screen “SAP System > Administrator Password”.
2.) On the “Parameter Summary Screen”, select “Diagnostics Agent > OS User Parameters”.
3.) Enter a user ID that is not already assigned to the adm user or to any other user in the “User ID” field for the adm .If you choose parameter mode “Custom”:
You can enter the user ID directly during the phase “Define Parameters” on the screen “Diagnostics Agent > OS User Parameters”.
However, you can also check and – if required – change the user ID assigned to adm via the “Parameter Summary Screen” as described above.

If you do not perform these steps, you might get an error during the
installation of the central instance or of dialog instances like the following:
in sapinst_dev.log:
ERROR 2008-01-29 16:26:44.698 [syuxcuser.cpp:1654]
CSyUserImpl::addToOS(const CUserData& data,ISyProgressObserver*)
FSL-01002 Unable to create account adm. UserId 1000 is not unique.in smd.log:
[createOSUser]
User account already existing: {
role:SMDAdm
type:USER
systems:os
name:smdadm
password:XXXXXX
instancenumber:98
…

———————–————————–
ABAP+Java, Java Add-In: SAPinst terminates with error message in step createJSF
Symptom:
SAPinst terminates with the following error message:
ERROR 2007-12-17 12:13:42.463
CJSlibModule::writeError_impl()
CJS-30196 The function module “PRGN_GEN_PROFILES_FOR_ROLES”
cannot be used for ‘remote’ calls.
TRACE 2007-12-17 12:13:42.473 [iaxxejsbas.hpp:460]
EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2007-12-17 12:13:42.493 [iaxxgenimp.cpp:731]
showDialog()
FCO-00011 The step createJSF with step key |NW_Onehost|ind|ind|ind|ind|0|
0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|
NW_CI_Instance_Doublestack|ind|ind|ind|ind|3|0|createJSF was executed with
status ERROR .
Solution:
Follow the instructions in SAP Note 1126481.
———————–< D027171 OCT/29/07 >————————–
SAPinst GUI: Close button (’X') of message boxes does not work
Symptom:
You cannot close message boxes of SAPinst GUI using the close button (’X').
Solution:
Use the buttons of the message box (’Stop’, ‘Continue’, ‘Retry’, ‘Cancel’). For example, when you chose “File -> Exit” from the SAPinst menu bar, you can only use either ‘Stop’ or ‘Continue’ to close the message box.
———————–————————–
Using “Back” button with “Typical” Mode
Note the following when you process the screen “Parameter Mode > Default Settings”: If you chose the “Typical” setting and press “Back” after processing one or more input screens, the installer now guides you through all screens with default parameters that it has processed in the background so far.
———————–————————–
Linux x86_64: Error “cannot open libj9vm22.so”
Symptom:
SAPinst aborts during “Start Java engine” with the following error: libjvm.so preloadLibrary: /opt/IBMJava2-amd64-142/jre/libj9vm22.so: cannot open shared object file: No such file or directory libjvm.so failed to load: j9vm22
Solution:
Proceed as described in SAP Note 1066142.
———————–————————–
Uninstall: Error message FCO-00011
Symptom:
During “Uninstall System / Standalone Engine / Optional Standalone Unit” you get the following error message:
***********************************************************************
FCO-00011 The step removeSystemUsers with step key
NW_Uninstall ind ind ind ind 0 0 NW_System_Uninstall ind ind ind ind 3
0 NW_System_Uninstall_Users ind ind ind ind 5 0 removeSystemUsers was
executed with status ERROR .
***********************************************************************
Solution:
1. Stop sapinst2. Remove or comment out with “//” the following line in control.xml :
user.removePrivileges(ad.privileges);3. Restart sapinst with continue old installation

————————-————————–
Uninstall aborts with error message
Symptom:
SAPinst aborts during “Uninstall System / Standalone Engine / Optional Standalone Unit” with an error message like the following :
**********************************************************************
ERROR 2007-04-26 10:31:05.164
FSH-00006 Return value of function /usr/sbin/userdel is 8.
ERROR 2007-04-26 10:31:05.164
FSL-01004 Unable to delete account user=”qe1adm” uid=”101″.
ERROR 2007-04-26 10:31:05.174
MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error
text undefined.
ERROR 2007-04-26 10:31:05.214
FCO-00011 The step removeSystemUsers with step key
NW_Uninstall ind ind ind ind 0 0 NW_System_Uninstall ind ind ind ind 3
0 NW_System_Uninstall_Users ind ind ind ind 5 0 removeSystemUsers was
executed with status ERROR .
***********************************************************************
Solution:
Proceed as follows:
1. Terminate the “saposcol” process with the command “saposcol -k”.2. Press “Retry” and continue uninstall

—————— Error during uninstall on HP-UX: "Login adm is currently in use”
Symptom
While running one of the installation services under “Additional Software Lifecycle Tasks -> Uninstall”, you get an error like the following in sapinst_dev.log:
Login qe1adm is currently in use
ERROR 2006-09-18 09:33:57 [syuxcuser.cpp:1084]
CSyUserImpl::remove()
FSH-00006 Return value of function /usr/sbin/userdel is 8.
ERROR 2006-09-18 09:33:57 [syuxcuser.cpp:1092]
CSyUserImpl::remove()
FSL-01004 Unable to delete account user=”qe1adm” uid=”101″.
ERROR 2006-09-18 09:33:57
CJSlibModule::writeError_impl()
MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error
Solution:
stop all processes running with adm and press RETRY

—————–—————————
HA Java: SAPinst hangs during deployment
Symptom: SAPinst hangs during deployment in a HA setup. SDM logs say that SDM is waiting for a control instance of the cluster to start.
Cause:
SDM uses as a SDM host the local host of the system on which it was installed, not the HA virtual host.
SDM requests JStartUp to start the central instance and asks regularly JStartUp if the instance is up and running.
JStartUp returns a list with instances and SDM searches in it for a control instance running on a host the same as SDM host.
But the control instance on HA system is running with the virtual host which is not equal with the SDM host (local host).
Solution:
Apply SAP Note 757692.
——————–—————————
Although you perform a Unicode installation, SAPinst might also ask for the non-Unicode kernel DVD. Therefore have this DVD available for the installation.
————————————————-
Java: Import of software units or usage types fails with message “Access denied”
Solution:
Proceed as described in related SAP Note 946377.
————————————————-
Multiple entries for the same parameter(s) on “Parameter Summary”
screen
Symptom:
You enter the input parameters prompted by the SAPinst screens.
From time to time you used the “Back” button to get back to a previous screen.
After you have entered all input parameters for the installation, the “Parameter Summary” screen appears.
on the “Parameter Summary” screen, you see multiple entries for the same parameter corresponding to the number of times you pressed the “Back” button for the screen which prompts for the parameter(s) in question.
Solution:
This is a known bug. You can ignore it. If you want to change the parameter(s) that are dispayed multiple times, it is sufficient that you choose one checkbox for the respective parameter.

————————————————-
Sharing same JDK between system based on NetWeaver 7.0 SR3 and other software
Symptom:
You are installing a SAP system based on NetWeaver 7.0 SR3 and want to use a JDK that is already in use for other software packages.
During the installation SAPinst prompts for JDK and JCE Unlimited Strength Jurisdiction policy archives and uses them to overwrite your JDK’s existing JCE policy archives.
Cause:
SAPinst does not set “read” permission for “other” to these archives which may cause problems in other software using the same JDK.
Solution:
Do the following after the installation:
1. Assign “read” permission for “other” to the policy files in /jre/lib/security of your JDK.2. Switch the group of the policy files in /jre/lib/security of your JDK from “sapinst” back to “root”.

————————————————-
Java: SDM deployment fails
Symptom:
You install an ABAP+Java system with all usage types.
SAPinst stops with the following error message:
SDM deployment failed for at least one of the components to deploy…
Logfile callSdmViaSapinst.log:
Caught exception during application deployment from SAP J2EE Engine’s
deploy service:
java.rmi.RemoteException: ERROR : ; nested exception is:
java.lang.OutOfMemoryError
Solution:
1. Configure the VM settings for release 700 as described in SAP Note
723909:
-XX:MaxPermSize=256
-XX:PermSize=2562. Continue with the installation.

—————-——————
ABAP: UNICODE conversion error
Symptom:
During the import into a UNICODE system the following error occurs
(for example in the 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
———————————————————-
|
| RSCP – Error
| Error from: Codepage handling (RSCP)
| code: 128 RSCPENOOBJ No such object
| Dummy module without real rscpmc[34]
| module: rscpmm no: 2 line: 75 T100: TS008
| TSL01: CPV p3: Dummy-IPC p4: rscpmc4_init
`———————————————————-
Cause:
This problem is caused by incorrect data which should have been removed from the source system before the export.
Solution:
There are two possible workarounds:
1. Modify DDL.TPL ( = 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.2. Modify the TSK file (most probably SAPCLUST.TSK) BEFORE 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.

=====================================================================
5 Post-Installation

=====================================================================

———————–<19/MAY/09, D042481>————————–
AIX: Check user limits for operating system users
Check and – if required – adjust user limits for operating system users as described in SAP Note 323816.

——————-—————————-
Delete usagetype.properties file manually due to security reasons
Symptom:
Once the installation with SAPinst has finished successfully, you have to manually delete the usagetype.properties file.
This file contains data that is not fully secure. It is possible that the data might be cracked if access is available for a long period. The data might be outdated by that time in any case, but we cannot guarantee this because it depends on how you use the system.
Solution:
Proceed as follows:
1. On UNIX, change to directory /usr/sap//config
On Windows, change to directory :\usr\sap\\config2. Delete the usagetype.properties file manually.

———————–<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.
——————-——————————–
ABAP+Java,Java: Keystore views are not created during the very first start
Symptom:
You get an error like the following in
/usr/sap///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#0017A41132BE002E
000002A000032850004510A33DD78DA#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 [TicketKeysto
is 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#0017A41132BE002E
000002B000032850004510A33DD79AA#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:
Solution:
Proceed as described in SAP Note 1230057

———————–—————————
ABAP+Java: Individual passwords not assigned to ABAP UME users
Symptom:
You chose “Custom Mode” during the “Define Parameters” phase.
On the screen “SAP System > ABAP UME”, you overwrote the master password and assigned individual passwords for ABAP UME users (administrator user, communication user, SDM).
After the installation has finished successfully, you cannot log on with these users using the individual passwords you assigned before.
Solution:
Log on using the master password and assign the required individual passwords to the ABAP UME users.

——————-——————————–
BI Java: BEx Web Applications: Access denied
Symptom:
You get a portal runtime error (Access denied) when calling a BEx Web Application (Java).
Solution:
Proceed as described in SAP Note 1155392.
——————-——————————–
EPC, EP: “HTTP response: 500 – Internal Server Error” when accessing Forms Builder iView
Symptom:
You get an “HTTP response: 500 – Internal Server Error” when trying to access the Forms Builder iView.
Solution:
Proceed as described in SAP Note 1150307.

——————-——————————–
EP: KM integration of CAF does not work at all
Symptom:
KM integration of CAF does not work at all.
A null pointer exception is thrown like the following:
class com.sapportals.portal.prt.service.soap.exception.PRTFaultInternalE
java.lang.NullPointerException
Solution:
Apply SAP Note 1143603.
——————-——————————–
ABAP+Java, Java, Linux, AIX, Diagnostics Agent: Upgrade JDK
Follow the instructions in SAP Note 1093831 to upgrade the JDK on AIX and Linux x86_64 operating systems.
This will help you to avoid various connection problems between the Diagnostics Agent and the Diagnostics Managing system, out-of-memory errors and class loader problems.
——————-——————————–
RAISE_EXCEPTION short dumps occur
Symptom:
RAISE_EXCEPTION short dumps occur when the system starts after the
installation.
Solution:
Apply SAP Note 1120534.
——————-——————————–
Errors in syslog: Unable to create directory
Symptom:
You get an error like the following in the syslog, when you start the system for the first time:
18:50:23 DIA 000 000 SAPSYS F6 9 Unable to create
directory . Error no. 17
18:50:23 BTC 008 000 SAPSYS F6 7 Directory was created
18:50:26 DIA 000 000 SAPSYS D0 1 Transaction Canceled
BT 513 ( )
18:50:26 DIA 000 000 SAPSYS R6 8 Perform rollback
18:50:26 DIA 000 000 SAPSYS F6 1 TemSe input/output to
unopened file
18:50:26 DIA 000 000 SAPSYS R3 8 Error at DB commit,
return code 001024
Cause:
The DIALOG and BATCH process try to create a directory at the same time. The DIALOG process fails with error 17 (ALREADY EXIST). The BATCH process creates the directory successfully.
Further errors in syslog that you can see at that time might be related this cause. You get these errors only when you start the system for the first time.
Solution:
You can ignore these errors.
————————————————-
Incorrect permissions of softlinks to sapinit system startup script
Symptom:
Incorrect permissions of softlinks to sapinit system startup script are set. These softlinks should be owned by group root, not group sapinst.
Solution:
You can ignore this issue.
————————————————-
Incorrect permissions of some files under DIR_INSTANCE/j2ee/ctc
Symptom:
Some files under DIR_INSTANCE/j2ee/ctc have incorrect permissions. These files should be owned by group sapsys, not by group sapinst.
Solution:
You can ignore this issue.
————————————————-
Error message when you close SAPinst GUI
Symptom:
Sapinst has finished successfully. However, an error like the following is written on the console when you close Sapinst GUI:
iauxsysex.c:317: child /tmp/sapinst_exe.4584.1159433231/sapinst (pid 4585) has crashed. Executable directory is /tmp/sapinst_exe.4584.
1159433231. Contact Support.
iaextract.c:814: child has signaled an exec error. Keeping directory /tmp/sapinst_exe.4584.1159433231
Solution:
You can ignore this error message.
————————————————–
BI Java / PI: Setting Environment Variable CPIC_MAX_CONV
Proceed as follows:
1. Log on to your SAP system as a user with administration rights and run transaction RZ102. Set the value gw/max_conn_per_wp to a higher value (at least 200) and restart the system.

————————————————–
Install Replicated Enqueue Server for High Availability (HA)
If you want to install a high-availability system with switchover software, you need to install the standalone replicated enqueue server.
For a Java system, you must install the standalone replicated enqueue server. For an ABAP system, we strongly recommend you to install it.
This fully protects the enqueue server from failure.
For more information on how to install the replicated enqueue server, see:
help.sap.com -> SAP NetWeaver -> SAP NetWeaver 2004s -> English -> SAP NetWeaver Library -> SAP NetWeaver by Key Capability -> Application Platform by Key Capability -> ABAP Technology -> Client/Server Technology -> The SAP Lock Concept -> Standalone Enqueue Server -> Installing the Standalone Enqueue Server
———–—————————————
PI: Client copy considerations
We recommend that you use client 001 as source client. However, you can also use client 000 as source client.
Make sure you use the profile SAP_UCUS.
Do not use the profile SAP_CUST as stated in the SAP Library
documentation .
After the client copy, you must logon to your J2EE engine and change the parameter ume.r3.connection.master.client to the new PI/XI client.

———–—————————————
ABAP, ABAP+Java:Check value of parameter rdisp/bufrefmode in DEFAULT.PFL
After the installation, you must check the value of the parameter rdisp/bufrefmode in DEFAULT.PFL:
For an SAP NetWeaver 2004s system without dialog instances, the
value must be set to ’sendoff,exeauto’.For an SAP NetWeaver 2004s system with dialog instances, the
value must be set to ’sendon,exeauto’.
For more information, see SAP Note 14754.
———–—————————————
Java on SUNOS/X86_64 5.10 – 64 Bit:
FATAL: Caught OutOfMemoryError! Node will exit with exit code 666
Symptom:
You get an error message like the following:
std_server0.out: FATAL: Caught OutOfMemoryError! Node will exit with exit code 666
Solution:
“-XX:MaxPermSize” and “-XX:PermSize” should be set to 256m
Configure the VM settings for SUNOS/X86_64 5.10 – 64 Bit as described in SAP Note 716604:
-XX:MaxPermSize=256
-XX:PermSize=256
This problem will be fixed with SP8.
———–—————————————-
(PI): Before running the Template Installer, you need to apply patch LMTOOLS06P_2-10003486.SCA as described in SAP Note 938261.

———–—————————————–
(PI): Increase number of dialog work processes
After the installation has finished, you need to increase the number of dialog work processes to at least 5.

————-——————————
Java, ABAP+Java: J2EE Engine reboots permanently
After the successful installation of the SAP system, the J2EE Engine reboots permanently. To solve the problem, set the VM parameter “-Xss2m” according to SAP Note 716604.

————————————————-
ABAP dialog instance: check parameter login/system_client
If the profile parameter login/system_client is not set in the default profile, the dialog instance installation will set it to 001.
If client 001 is not your productive client, change the parameter in the default profile.

======================================================================
6 Corrections in the installation guides

======================================================================
———————–————————–
ABAP+Java, Java: Inst.guide correction: Default group of users J2EE_GUEST and Guest
Symptom:
The following statement in “Basic SAP System Parameters” ->
table “User Management Engine (UME)” is wrong:
“Guest users belong to the default group Authenticated Users.”
Solution:
“Guest users areanonymousand belong to theAnonymous Usersgroup by default.”