SAP Basis Tech Supports

Symptom

******************************************************************
*
* Installation on IBM i
*
* Based on SAP NetWeaver 7.0 EhP1
* (SAP NetWeaver 7.0 EhP1,
* SAP ERP 6.0 (2005) EhP4,
* SAP CRM 7.0,
* SAP SRM 7.0,
* SAP SCM 7.0 )
*
* Based on SAP Solution Manager 7.0 EHP1
*
* Based on SAP NetWeaver 7.0 EHP1 SR1
* (SAP NetWeaver 7.0 EHP1 SR1,
* SAP ERP 6.0 EHP4 SR1,
* SAP CRM 7.0 SR1,
* SAP SRM 7.0 SR1,
* SAP SCM 7.0 SR1 )
*
******************************************************************
Other terms

install, SAPinst, AS/400, J2EE, iSeries, IGS, Homogeneous system copy, UME, ISERPACK, SAP NetWeaver 7.0 EhP1, SAP NetWeaver 7.0 EhP1 SR1, SAP ERP 6.0(2005) EhP4, SAP ERP 6.0 EhP4 SR1, SAP CRM 7.0, SAP CRM 7.0 SR1, SAP SRM 7.0, SAP SRM 7.0 SR1, SAP SCM 7.0, SAP SCM 7.0 SR1, SAP Solution Manager 7.0 EHP1, System i, IBM i
Reason and Prerequisites

Problems discovered after the publication of the installation guide.
Solution

DO NOT CHANGE OR ADD INFORMATION TO THIS NOTE !
This SAP Note is available in English only.
Topics Date changed
====== ============
1 General Information Oct/2008
2 Pre-Installation Feb/2009
3 Installation Mar/2009
4 Post-Installation Jul/2009
5 Troubleshooting Jul/2009
6 Corrections in the installation guides Aug/2008

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 HhP1, you can
also install the NetWeaver 7.0 EhP1 usage types.
SAP NetWeaver 7.0 EhP1 (SR1), 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)

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.
+===================================================================+
1: General Information

+===================================================================+
——————– < D027171 29/OCT/07 > ———————–
SAPinst GUI: You cannot close message boxes of SAPinst GUI using the close button (’X').
Use the buttons of the message box instead.
+===================================================================+
2: Pre-Installation

+===================================================================+
———————–————————–
ABAP+Java, Java: Make sure there is not an older version of the JCE policy zip file for your platform on the installation host.
If there is an old JCE policy zip file, the Prerequisite Checker does
not recognize this fact. Because of this, SAPInst throws a
java.lang.SecurityException during the Create Secure Store step stating
the jurisdiction policy files are not signed by trusted signers.
—————–————————–
jt400.jar / JTOpen / Toolbox JDBC driver
When you download the Toolbox JDBC driver from the web as described in the InfoAPAR take care you choose the right zip file.
Correct zip file: jtopen_x_y.zip
Wrong zip file: jtopen_x_y_jdbc40.zip
For more information seeSAP Note 1232613.
—————–————————–
IBM i 6.1
Before starting an SAP installation on V6R1M0 seeSAP Note 1148480.
—————–————————–
Export of a Java Stack (System Copy)
If you want to export your Java Stack while you are performing a System Copy of a Doublestack or a Java Only System make sure that you have at least SP14. LM-Tools must have at least SP14 patch 01.
If the export does not have the right SP stack your Java import on IBM System i (i5/OS) will fail because the script offlineCTC.sh (part of the export) will put the string “init” into the java parameters of the Java EE engine. This will break the start of the Java EE processes.
—————–————————–
If you perform an installation and there is only one Windows DVD drive available on your Windows installation host, you must copy at least
the Installation Master DVD to the local file system on iSeries. However, we recommend that you copy all of the DVDs to your iSeries host as described in Installation documentation section “Preparing the Installation DVDs”.
——————————————–
Convert the profile file DEFAULT.PFL of all old EBCDIC SAP systems
At the beginning of the installation SAPinst checks all existing SAP systems installed on your iSeries. At that time SAPinst tries to read the file DEFAULT.PFL of each system. Files in EBCDIC cannot be read and the SAPinst will end with a read error. To avoid this error convert all DEFAULT.PFL files written in EBCDIC into ASCII. The EBCDIC SAP system will still be able to handle the converted profile DEFAULT.PFL!
——————————————–
Installing additional double byte language locales
The kernel shipped with NetWeaver 7.0 EhP1 contains all needed single byte language locales. If you need additional double byte language locales, you have to install the missing locales using additional language DVDs. To determine which language DVD and which language library you have to install, see the IBM internet link: http://publib.boulder.ibm.com/iseries/v5r3/ic2924/index.htm?info/apis/pase_locales.htm
For example for the double byte locales ZH_TW you need the language DVD “Traditional Chinese” to install the language library QSYS2987.
Before you install an additional double byte language library to create additional double byte locales, make sure that PASE is installed and up-to-date.
After you have installed a new double byte language also all locales of this language are created. As a final step check if there are any PTFs to be installed using the INFOAPAR.
+===================================================================+
3: Installation

+===================================================================+
————————————–
Changing “Custom” to “Typical” on the “Parameter Summary” screen does
not work.
Symptom: You want to change from “Custom” to “Typical” parameter mode or from “Typical” to “Custom” parameter mode by using the “Revise” button on the “Parameter Summary” screen. However, this does not work.
Cause: In “Revise” mode, you can change all parameters that you can select fromthe “Parameter Summary” screen except for the parameter mode (”Typical” or “Custom”).
Solution: Restart the installation with option “Run a new option”.
———————-—————————
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.

———————-————————–
ABAP+Java, Java: Do not uninstallallapplication server
instances
You must not uninstallallapplication server instances of an SAP
system if you want to continue using the database instance of the SAP
system.

—————-—————————
Error when using the “Media Browser” screen
You get the following error while selecting an installation DVD on the
“Media Browser” screen:
Caught ESAPinstException in Modulecall: could not call evaluator in
class CCdCheckUserInput.
To solve the problem, restart SAPinst and continue with the old
installation option.

—————–—————————
HA Java: SAPinst hangs during deployment30000009
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:
ApplySAP Note 757692.
——————————————–
SAPCRYPTO.CAR
You do not have to mark the installation option of the security package SAPCRYPTO.CAR. All needed security files are part of the kernel.
But if you are asked to install the SAPCRYPTO.CAR you have to consider the following points:
iSeries uses the SAPCRYPTO.CAR of AIXthe SAPCRYPTO.CAR of AIX embodies different versions. Be sure to select the 64 bit version of AIX 5.1 when you are asked by SAPinst.

+===================================================================+
4: Post-Installation

+===================================================================+
————————————————–
Integrated SMD agent installation
SMD agent administrator user ADM doesnot get the Master Installation Password
Symptom:
You try to logon as the SMD agent administrator user ADM using the Master Installation Password and it fails because of a wrong password.
Cause:
The SMD agent administrator user is not created with the Master Installation Password by the integrated SMD agent installation.
The standalone SMD agent installation does set the users password correctly.
Solution:
Change the password of the SMD agent administrator user ADM manually using the command WRKUSRPRF.
——————-—————————-
CRM: Errors in sapinst_dev.log
Symptom:
The installation of CRM 7.0 SR1 Java components finished successfully.
However, some error messages may occur in sapinst_dev.log, for example:
***********************************************************************
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/tra/trp/trt and wait. …
***********************************************************************
Cause:
The WebDynpro applications have a lazy starting mechanism. This means that they are started upon request. It is normal that some of them need to be stopped after server start. They will be started when a request issent to them. The reason of the error messages listed in the log file is, that the applications were requested before the deployment of referenced applications had finished. When a Web Dynpro application all tries to start, it tries first to start all referenced components. The traces show that some of the applications are not available, because they were not deployed at that moment.
Solution:
You can ignore these error messages if you are able to start the applications listed in the error message manually.
——————-—————————-
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. 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 inSAP 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 inSAP Note 1155392.
————————————————–
EPC, EP: “HTTP response: 500 – Internal Server Error” when accessing
Forms Builder iView
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:
ApplySAP Note 1143603.
—————-——————————
EP: KM integration of CAF does not work.
There is a null pointer exception like the following:
class com.sapportals.portal.prt.service.soap.exception.PRTFaultInternalE
java.lang.NullPointerException
To solve the problem, applyNote 1143603.

Wrong IGS permissions after installation.
When IGS is installed the wrong permissions are set. This will not hurt your running SAP system but when you try to patch the IGS using JSPM youwill get an error because of wrong permissions.
To set the right permissions to IGS do following steps.
1. Change the permissions of the IGS directory and all included files:
QSH CMD(’chmod -R 775 /usr/sap///igs’)
QSH CMD(’chown -R ADM:GROUP /usr/sap///igs’)
2. Change the permissions of all IGS files in the kernel directory:
QSH CMD(’cd /sapmnt//exe && chown -R R3OWNER:GROUP igsmux_mt igspw_mt igswd_mt bwgis.so gfwchart.so imgconv.so sgxgis.so xmlchart.so zipper.so’)
——————-——————————–
RAISE_EXCEPTION short dumps occur
RAISE_EXCEPTION short dumps occur when the system starts after it was
installed. To solve the problem, apply SAP Note 1120534.
————————————————–
For more information about unexpected hostnames of registered systems
in SLD, seeSAP Note 1020043.
————————————————–
Java VM Parameters
After a Java installation you should check the VM parameters of your
freshly installed SAP system as well as the global system parameters of
your System i host according toSAP Note 717376.
————————————————–
To use the Visual Administrator tool for reconfiguring your system,
seeSAP Note 937418.
——————————————–
Edit the SDM file sdm_jdk.bat in /usr/sap///SDM/ program.
When SDM is installed on iSeries all java path variables are set to
/QIBM/ProdData/Java400/jdk14.
This is wrong for a remote SDM call using a Windows PC.
To solve this edit the file sdm_jdk.bat. Change the following entry:
set sdm_java_home=/QIBM/ProdData/Java400/jdk14
to
set sdm_java_home=%JAVA_HOME%
Also change sdm_heap_size to 512. (set sdm_heap_size=512)

Now you can use for example RemoteGui.bat to start the SDM GUI remotely on your Windows PC to connect to the SDM Server running on iSeries. Make sure that the environment variable JAVA_HOME is set on your Windows PC.
+===================================================================+
5: Troubleshooting

+===================================================================+
————————————————–
NW 7.0 EHP1 SR1, SolMan 7.0 EHP1
Startup of SMD Agent hangs during the installation
When SAPinst is starting the SMD agent the installation starts hanging. At the end of the log file sapinst_dev.log you will find an entry similar like this:
…
CJSlibModule::writeInfo_impl()
Starting agent SMD/J98…
…
To solve this issue seeSAP note 1326779.
———————–————————-
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 /statistic.xml.
Solution:
Remove the file statistic.xml from the installation directory and
restart sapinst.
———————–————————–
SAPinst finished successfully but “Selfextractor error” message windows pops up
Symptom:
The installation das finished successfully, but you see an error message popup window like the following:
Selfextractor error
iaextract.c:895: child has signaled an exec error. Keeping directory C:/Temp/sapinst_exe.5928.1246448368
Solution:
You can ignore this error message. Just push the OK button of the error message window.
———————–—————————
ABAP,ABAP+Java: FJS-00003 TypeError: dir_instance.get is not a function
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 the following line in control.xml in the respective
sapinst_instdir directory:
var maybeName = fmgt.getFSPath(dir_instance.get()). …
into
var maybeName = fmgt.getFSPath(dir_instance.value()). …3. Restart SAPinst and continue your old installation

————————————————–
IBM i 6.1
SAPinst breaks in the step createPorts
When SAPinst breaks in the step “createPorts” check the file tmkliblog_nnnn in the installation directory. Following error message should be found:
…
[12:23:36] UERZS001:59976 Sending request EXECUTE (command: “ADDSRVTBLESERVICE(’sapmsC01′) PORT(3600) PROTOCOL(’tcp’) ALIAS()”)
[12:23:36] UERZS001:59976 TMKSVR returned 0 (return code: -1)
…
To solve the problem apply thePTF MF45089. An IPL is needed afterwards. For more details seeSAP Note 1148480.
————————————————–
IBM i 6.1
Java Development Infrastructure (DI)
Installation fails in the phase “Install software units”
When you install on IBM i 6.1 the usage type Java Development Infrastructure (DI) the installation will fail in the phase “Install software units”.
You will find in the SDM log an SQL error -356 when using the statement
CREATE TABLE “CBS_NODE” …
To solve this issue see theSAP note 1138824.
Afterwards you can continue your old installation.
————————————————–
Retry button and restart of TMKSVR
When an installation fails and the logs do not clearly indicate the error, it is always a good idea to press the Retry button to check if the error still exists.
If the installation fails a second time at the same point after pressing the Retry button, it is sometimes helpful to restart the TMKSVR. As the TMKSVR is a bridge between the iSeries and Windows it may happen that an unexpected event will put the TMKSVR into an unstable state.
Always stop the SAPinst before you restart the TMKSVR.
You can restart the TMKSVR in one of the following ways:
1. Enter ADDLIBLE TMKSVR00 (or any other number you are currently
using) and use ENDTMKSVR / STRTMKSVR to end and start the TMKSVR.
2. Just stop the process SAPINST in the subsystem TMKSVR00 (or any
other number) using option 4. The required SAPINST process will be
restarted automatically by SAPinst as long as the process DISPATCH is running.
3. Reinstall the TMKSVR using the command SETUP.EXE from the Installation Master DVD.
Now you can start the SAPinst again to continue your old installation.
——————————————–
SAPinst fails during SLD content import
In the java.log in the installation directory, you find an error message java.net.SocketTimeoutException: Read timed out or the import itself takes longer than 1,5 hours with little progress found in java.log (Import Status: LOADING xxx of 95791).
Solution: Shutdown the central instance, start j2ee\configtool\offlinecfgeditor.bat and decrease the -Xms value for the server instance from -Xms1024m to -Xms512m
Restart the central instance. In the SAPinst error dialog, press Retry.
——————————————–
SAPinst reports error during ABAP database import, but the TMKSVRnn subsystem still contains r3load jobs
The logfiles in the installation directory show no error.
Solution: Wait, until the TMKSVRnn subsystem contains only the DISPATCH and SAPINST jobs. That is, the R3LOAD jobs have finished.
Check for errors in the log files of the load. If there are no errors, press Retry or restart SAPinst.
——————————————–
Java call has return code 0, but SAPinst reports error
In the sapinst_dev.log, you find an entry similar to this:
INFO
CJSlibModule::writeInfo_impl()
Execution of the command “\QIBM\ProdData\Java400\jdk14\bin\java -classpath /usr/sap/SAPinst/NW04S/SYSTEM/DB4/CENTRAL/AS/install/sharedlib/launcher.jar -Xmx256m ” … finished with return code 0.
That is, this Java call finished successfully. Despite that, you find another entry similar to this:
ERROR
CJSlibModule::writeError_impl()
CJS-30059 J2EE Engine configuration error.
directly behind the first INFO statement. SAPinst fails and the installation stops.
Solution: With the configtool, switch off the JDBC tracing you had switched on before. Do this by removing the part “trace=true;errors=full” from the database URL.
——————————————–
ZDAEXIT error during Java database import
In case the installation fails in step IMPORT_JAVA_DUMP with the following error message in file jload.log:
com.sap.inst.jload.Jload logStackTrace SEVERE: java.sql.SQLException: [PWS9801] Function rejected by user exit program ZDAEXIT in R3SYS.
Please press Retry in SAPinst.