SAP Basis Tech Supports

Symptom
Installation of SAP NetWeaver 7.0 SR3 and Business Suite 2005 SR3 on Windows
Other terms
SAPinst, 7.0, NW 7.0
Reason and Prerequisites
Installation problems for an SAP system based on SAP NetWeaver 7.0 SR3 on Windows, including the Business Suite 2005 SR3 (ERP, CRM, SRM, SCM), discovered after the publication of the installation guide.
For database-specific installation problems with SAP NetWeaver 7.0 SR3/Business Suite 2005 SR3, see the following SAP Notes:
1108857 SAP NetWeaver 7.0/Business Suite 2005 SR3:Oracle Windows
1108827 SAP NetWeaver 7.0/Business Suite 2005 SR3: SQL Server
1135525 SAP NetWeaver 7.0/Business Suite 2005 SR3: SAP MaxDB
Solution
Contents
1 General
2 Pre-Installation
3 Installation
4 Post-Installation
5 High Availability (HA)
This note contains information relevant to the installation of following SAP systems and software units on Windows. Since the Business Suite 2005 SR3 is based on SAP NetWeaver 7.0 SR3, you can also install the NetWeaver 7.0 SR3 software units.
SAP NetWeaver 7.0 SR3, including the software units:AS ABAP (ABAP)AS Java (Java)AS ABAP and AS Java (ABAP+Java)Development Infrastructure (DI)EP Core (EPC)Enterprise Portal (EP)Mobile Infrastructure (MI)Process Integration (PI)SAP ERP 6.0 SR3, including the software units: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 the software units:CRM Application Set (CRM-APP)CRM Java Components (JCRM)CRM Business Packages (BP-CRM)CRM Mapbox (MBX)SRM 5.0 SR3, including the software units:SRM Application Set (SRM-APP)SRM Live Auction Cockpit (SRMLAC)SRM Business Packages (BP-SRM)SCM 5.0 SR3, including the software units:SAP SCM Server (SCM)Store User Interface (SUI)Web Communication Layer (WCL)

Each entry is marked with a prefix, to make clear for which SAP systems, software units, and technical stack (ABAP, Java, ABAP+Java), the information applies to. If there is no prefix, the information applies to all SAP systems.

Date Section Description
———————————————————————
15/JUN/09 5 HA, Windows Server 2008: Error when installing a central or dialog instance
18/MAY/09 2 Use current version of SAPINST 7.00
24/APR/09 5 HA, Windows Server 2008: Error when installing a central or dialog instance
30/MAR/09 3 Restarting SAPinst aborts with error message
10/MAR/09 4 Delete usagetype.properties file manually due to security reasons
24/FEB/09 4 Dealing safely with installation directories
30/JAN/09 4 Uninstall Diagnostics Agent only: Manually delete the <smdsid>adm user
9/DEC/08 2 Dialog instance: Check entries in sapservices file and naming of profile backup files
17/DEC/08 2 Non-HA: Problems with local users and virtual host name
10/OCT/08 2 ABAP+Java,Java, Java Add-In: installation with virtual host name, exchange control.xml
09/OCT/08 2 Bootstrap error might occur during the installation with SAPinst
07/OCT/08 3 SAPinst Self Extractor error or APPCRASH error (Windows Server 2008) during logoff
22/SEP/08 3 Do not use an already existing SAPSID when installing a new SAP system
28/AUG/08 3 Error when using the “Media Browser” screen
13/AUG/08 5 Check that saploc share (if existing) points to local drive
24/JUL/08 4 ABAP+Java,Java: Keystore views are not created during the very first start
24/JUN/08 3 Java Add-In or dialog instance: gateway instance
with same <SAPSID> must not exist
19/JUN/08 4 Do not use <sapsid>adm user to delete the SAP system
03/JUN/08 3 (ABAP,ABAP+Java:) FJS-00003 TypeError: dir_instance.get is not a function
30/MAY/08 3 Windows Server 2008: Error when creating SAPstartsrv.exe service
21/MAY/08 1 SAP system installation except dialog instances on 64-bit operating systems only except for dialog instances
18/APR/08 3 SAPinst Self extractor error: file used by another process
16/APR/08 4 ABAP+Java: Individual passwords not assigned to ABAP UME users
10/APR/08 5 Unable to open …\packages.xml
03/APR/08 4 ABAP+Java, Java: Diagnostics Agent does not come up due to a bad CIM model
02/APR/08 4 BI Java: BEx Web Applications: Access denied
26/MAR/08 4 EPC, EP: “HTTP response: 500 – Internal Server Error” when accessing Forms Builder iView
25/MAR/08 3 SCM, ABAP: liveCache Client in SCM Installations
14/MAR/08 3 Java Add-In: Installation fails in phase ‘Create Java users’
05/MAR/08 4 EP: KM integration of CAF does not work
FEB/19/08 3 ABAP+Java, Java: Assign a unique User ID for the <smdsid>adm user
24/JAN/08 4 RAISE_EXCEPTION short dumps occur
29/OCT/07 3 SAPinst GUI: Close buttons (’X') of message boxes do not work
23/AUG/07 3 Using “Back” button with “Typical” Mode
12/JUN/07 3 Uninstall: Error message FCO-00011
15/APR/07 3 (ABAP, ABAP+Java:) Deadlock occurs Database error -60 at SEL access
27/SEP/06 4 Error when uninstalling first/install second system with the same <SAPSID>.
24/MAY/06 3 Multiple entries for the same parameter(s) on “Parameter Summary” screen
04/APR/06 4 (PI): Apply patch before running the Template Installer
28/MAR/06 4 (PI): Increase number of dialog work processes
22/MAR/06 4 (x64, Java, ABAP+Java): J2EE Engine reboots permanently
16/MAR/06 3 (x64, ABAP+Java, Java): Error during “Prepare to install minimal configuration”
13/MAR/06 3 Installation of “LDAP Support” stops in last installation step
10/MAR/06 3 (Java): SDM deployment fails
———————————————————————
1 General
21/MAY/08
SAP system installation only supported on 64-bit operating systems, except for dialog instances
As of SAP NetWeaver 7.0 SR3 and Business Suite 2005 SR3, SAP only supports to install dialog instances on 32-bit operating systems. All remaining SAP system instances (central instance, database instance, central services instance (SCS), ABAP central services instance (ASCS)) must be installed on 64-bit operating systems. 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 might 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 also use 64-bit systems for these components, including the dialog instance.
If you want to install a non-productive SAP NetWeaver 7.0 SR3 based system (test systems or development are normally productive systems) on 32-bit, 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.

2 Pre-Installation
———————-<D027120, 18/MAY/09>—————————-
Use current version of SAPINST 7.00
Make sure that you use the current version of SAPINST 7.00, which is 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.
Proceed as follows:
1. Copy the installation master DVD locally on your PC.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.
———————<19/DEC/08, D034879>————————-
Dialog instance: Check entries in sapservices file and naming of profile backup files
If you want to install a dialog instance to an existing SAP system, note the following:
Make sure that the service definitions for the SAP start services are configured correctly and refer to the correct profile filesIn case you have a backup of the profile file, the name of this profile backup file must not have an underscore ‘_’. If so, you must replace the ‘_’ with a ‘.’.
Example:
Before rename: \usr\sap\S14\SYS\profile\S14_DVEBMGS20_wsi6408_12
After rename: \usr\sap\S14\SYS\profile\S14_DVEBMGS20_wsi6408.12
————<17/DEC/08, D034879>———————-
Non-HA: Problems with local users and virtual host name
If you install a SAP system with local users and a virtual host name, you run into errors. For more information, see SAP note 1282975, section “Troubleshooting”.
——————< 13/OCT/08, D019130 >—————————-
ABAP+Java,Java, Java Add-In: installation with virtual host name, exchange control.xml
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).
In this case, you have to replace the control.xml file of the installation master DVD with the modified control.xml file that is attached to this SAP Note.
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 <inst_master_DVD>/<your operating system>/<your product>/WEBAS/INDand 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 did not apply this workaround, 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 and you run into this error during the installation, you have to restart the installation with option “New Installation Option” on the “What do you want to do” screen) after having done the modifications described above.
————————-<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.
3 Installation

—————–<30/MAR/09, D027120>————————–
Restarting SAPinst aborts with error message
After restart, SAPinst aborts with an error message similar to this:
FKD-00049 XML parser error: error: no DTD specified, can’t validate in line 2, 2 in file F:\Install\statistic.xml.
To solve the problem, remove the file statistic.xml from the installation directory and restart SAPinst.
—————- <D027120, 07/OCT/08> —————————– SAPinst Self extractor error:
While logging off from SAPinst you get the SAPinst Selfextractor error message(s) like the following:
“The process cannot access the file because it is being used by another process.”
“iaextract.c:895: child has signaled an exec error. Keeping directory D: /DOCUME~1/emadmin/LOCALS~1/Temp/1/sapinst_exe.4524.1222275633″
Windows Server 2008: APPCRASH error
On Windows Server 2008, before you get the SAPinst Self extractor error, you also get an APPCRASH error message, after you have installed the SAP system successfully and you want to close SAPinst. You are asked whether you want to close the program or if you want to search online to find a solution.
You can ignore both the SAPinst Self extractor error and the APPCRASH error message(s).
——————— <22/SEP/08, D034879> ————————-
Do not use an already existing SAPSID when installing a new SAP system.
If, for example, you have already installed an ABAP system, and want to install for example, a Java system on the same host, make sure that you enter a SAP system ID (<SAPSID>) that is different from the <SAPSID> for the first (ABAP) system.
—————–<D027120, 26/AUG/08>—————————
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.
————–<D029385, 24/JUN/08 > ———————————
Java Add-In or dialog instance installation: gateway instance with same <SAPSID> must not exist
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. If so, you must reinstall the gateway with a different <SAPSID>.
———————–<D029385, 03/JUN/08 >—————————
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.
—————< 30/MAY/08, D022091 >———————————-
Windows Server 2008: Error when creating SAPstart service
When you install the SAP system with SAPinst on Windows Server 2008, you might get an error that the step to create the sapstart service (sapstartsrv.exe) was executed with status ERROR. If so, retry the installation step in SAPinst. If the problem persists, open a customer service message under BC-INS-NT.

——————–<D027120, 18/APR/08>———————–
SAPinst Self extractor error: file used by another process
Symptom:
You log off from SAPinst for some reason by the end of the installation
process. While logging off you get an SAPinst Selfextractor error message like the following: “The process cannot access the file because it is being used by another process.”
Solution:
You can ignore this error message.
——————–<D036661, 25/MAR/08>———————–
SCM, ABAP: liveCache Client in SCM Installations
When you install an SCM system, the liveCache client software is automatically installed, even if you choose not to install liveCache server during the installation.
Currently there is no solution availabe. However, this has no effect on the functioning of your SCM system.
——————–<D034406, 14/MAR/08>———————–
Java Add-In: Installation fails in phase ‘Create Java users’
You get the following warning:
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.
To solve the problem, apply SAP Note 1126481

———————–<I021802, 19/FEB/08>————————–
ABAP+Java, Java: Assign a unique User ID for the <smdsid>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 <sapsid>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:a) Check the entry in the “User ID” field for <sapsid>adm on screen “SAP System > Administrator Password”.b) On the “Parameter Summary Screen”, select “Diagnostics Agent > OS User Parameters”.c) Enter a user ID that is not already assigned to the <sapsid>adm user or to any other user in the “User ID” field for the <smdsid>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 <smdsid>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 <sapsid>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
…
——————– < 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.
———————–<D027120, 23/AUG/07>————————–
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. This also might happen, if you change a parameter with the “Revise” button on the Parameter Summary screen.
———————–<d023322, 12/JUN/07>————————–
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”.
————————-<D022642, 15/APR/07>————————–
(ABAP, ABAP+Java:) Deadlock occurs Database error -60 at SEL access to table REPOSRC
Symptom:
You see an error like the following in the system log:
Deadlock occurred
Database error -60 at SEL access to table REPOSRC
> POS(1) Work rolled back
Perform rollback
Run-time error “DBIF_REPO_SQL_ERROR” occurred
> Short dump “060907 165433 lsi111_Q E1_00 ” generated
Runtime Errors DBIF_REPO_SQL_ERROR
Date and Time 07.09.2006 16:54:33
Short text
SQL error “-60″ occurred when accessing program “%_CICON ”
part “SRC “.
Depending on the process having been reset due to the deadlock, the installation may either continue and finish successfully or abort with an error.
Solution:
If the installation has finished successfully, you can ignore this error in the system log.
If the installation aborts, increase the number of dialog processes in the profile of the central instance to 10 and restart the installation.
This profile is named <SAPSID>_DVEBMGS<instance_number>-<hostname> and can be found in the directory /sapmnt/<SAPSID>/profile.

———————<D027120, 24/MAY/06>—————————-
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.
16/MAR/06
(x64, ABAP+Java, Java): The installation of AS Java usage types aborts during “Prepare to install minimal configuration” with the following error message:
ERROR 2006-03-02 15:51:10CJS-30153 Java process server0 of instance J20/JC01 reached state STARTING after having state STARTING_APPS. Giving up.
ERROR 2006-03-02 15:51:10FCO-00011 The step startJava with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Call_Offline_CTC|ind|ind|ind|ind|7|0|startJava was executed with status ERROR .
To solve the problem, choose “Retry” to continue the installation.
13/MAR/06
Installation of “LDAP Support” stops during the last step of the
installation with the following error message:
ERROR 2006-03-01 08:43:26 [synxcgroup.cpp:431]
void CSyGroupImpl::addMember(PSyAccount pAccount)
FSL-01006 Unable to add account <#0> to group <#1>. <#2>
To solve the problem, you have to add group SAP_<SID>_GlobalAdmin to SAP_LDAP group manually.
There is no need to restart the installation.
———————<C5061499, 10/MAR/06>—————————-
(Java): SDM deployment fails
When installing 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
To solve the problem, configure the VM settings for release 700 as described in SAP Note 723909:
-XX:MaxPermSize 256
-XX:PermSize 256 and continue with the installation.

4 Post-Installation

———————<05/MAR/09, D041479>——————————
Delete usagetype.properties file manually due to security reasons
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.
Proceed as follows:
1. Change to directory <Drive>:\usr\sap\<SAPSID>\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.
—————-<30/JAN/09, I021802>—————————–
Uninstall Diagnostics Agent only: Manually delete the <smdsid>adm user.
You have uninstalled a Diagnostics Agent instance using SAPinst with the installation option “Software Life-Cycle Options -> Uninstall-> Uninstall – Solution Manager Diagnostics Agent”.
After the uninstall with SAPinst has finished successfully, the user <smdsid>adm is still existing. Therefore, delete user <smdsid>adm manually.
——————-<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#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:
To solve the problem, proceed as described in SAP Note 1230057.
19/JUN/08
Do not use <sapsid>adm to delete the SAP system
———————–<D029385 16/APR/08 >—————————
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.

——————– < D027171 03/APR/08 > ———————–
ABAP+Java, Java: Diagnostics Agent does not come up due to a bad CIM model
Symptom:
During the installation you chose to register the Diagnostics Agent in the SLD Server. The Diagnostics Agent does not come up at the end of the installation although the installation finished successfully. In log file (/usr/sap/<smdsid>/JXX/sapinst/log) you can see that the CIM model is not correct.
Solution:
Proceed as follows:
1. Update the CIM model to 1.5.26 or +2. Edit the smdsetup.bat file (/usr/sap/<smdsid>/JXX/script) and add the following at the send of the “SET” commands:
- SET jdk = “<your java_home>”3. Open a shell on /usr/sap/<smdsid>/JXX/script and execute the command: smdsetup managingconf hostname:”<SLD_HOSTNAME>” port:”<SLD_PORT>” user:”<SLDDSUSER>” pwd:”<SLDDSUSER_PWD>”
In addition, you may need to create the SAPService manually. Execute sapstartsrv.exe (<drive>:\usr\sap\<smdsid>\exe) and specify the following:
Start profile path: (<Drive>:\usr\sap\<smdsid>\SYS\profile\START_JXX_<hostname>)username: <smdsid>adm

———————–<02/APR/08, D027913>————————–
BI Java: BEx Web Applications: Access denied
You get a portal runtime error (Access denied) when calling a BEx Web
Application (Java).
To solve the problem, proceed as described in SAP Note 1155392.
————————<I043531, 26/MAR/08>——————-
EPC, EP: “HTTP response: 500 – Internal Server Error” when accessing
Forms Builder iView
You get an “HTTP response: 500 – Internal Server Error” when trying to
access the Forms Builder iView.
To solve the problem, proceed as described in SAP Note 1150307.
—————-<I028584, 05/MAR/08>——————————
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, apply SAP Note 1143603.
——————-<D029385, 24/JAN/08>——————————–
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.
————————<D034882, 27/SEP/06>————————-
Error when uninstalling a system and install a new system with the same SAP system ID <SAPSID>.
If you install an SAP system, then uninstall it, and afterwards install a new system with the same SAP system ID (SAPSID), you might get the following error message:
MUT-03001 Value of type HKeyClass has illegal value ‘0′.
The reason is that during the installation of the second SAP system, the user <sapsid>adm is created but not added to the local Administrators group.
If this problem occurs do the following:
1. Add the <sapsid>adm user manually to the Administrators group.2. Check the owner of <SAPSID>adm HKEY_CURRNET_USER\Environement user as follows:
Log on as the <SAPSID>adm user and call regedit.exe.
Go to HKEY_CURRNET_USER\Environement and right-click on it.
Choose “Permissions” -> “Advanced” -> “Owner”, and make sure that the owner is set to the <SAPSID>adm user or to the Administrators group.3. Log off as <SAPSID>adm user, and log on again as the installation user4. Restart the installation.
———–<D036851, 04/APR/06>———————————–
(PI): Before running the Template Installer, you need to apply patch LMTOOLS06P_2-10003486.SCA as described in SAP Note 938261.
———–<D041479,27/MAR/06>————————————-
(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.
22/MAR/06
(x64, 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.
5 High Availability (HA)

———–<15/JUN/09, I005831>————————————-
Problem:
Windows Server 2008 ONLY: Error when installing a Central Instance.
During the installation of a Central instance on Windows Server 2008 in MSCS, error occurs if saploc share is not defined for the usr\sap directory in the Shared drive. In Windows 2008, it is possible to define the shares in the local drive and shared drive with the same name.
In MSCS, the Central instance is installed in the local drive, but SAPinst checks for the existence of saploc share in the Shared drive. If the saploc share doesn’t exist in the shared drive (in addition to the saploc share in the local drive), then the SAPInst installation fails with the following message:
CJS-30129 Creating node $(DIR_CCMS) with type DIRECTORY failed. Original exception text was: syslib.filesystem.nodeCreationFailed: Unable to create node \\<VirtualSAPGroup>\saploc\ with type DIRECTORY: can’t create parent node…
…………………………………
Solution: Do the following steps in your Central Instance Installation:
1. Copy the control.xml attached to the OSS note 1152240 for your release to the Installation Master directory.2. Before starting the CI installation in your system, check whether the ’saploc’ share exists BOTH in the SHARED Drive(usr\sap) and in the LOCAL drive (usr\sap).
If the ’saploc’ share (in addition to the ’sapmnt share) in the shared drive doesn’t exist, then create the share ’saploc’ in the shared drive for the directory usr\sap using explorer. Note: The ’saploc’ share in the local drive is probably already created in your system by enqueue replication instance installation.3. Start the SAPInst installation again with the option ‘continue with the old installation’.4. After the CI installation is completed successfully, create the following directories in the local drive, where the CI instance is installed. ( local ’saploc’ share)
<Local drive>:\usr\sap\prfclog<Local drive>:\usr\sap\prfclog\procmon<Local drive>:\usr\sap\prfclog\grmg
Make sure the security access to these directories set to ‘Full Control’ for the following groups. You can do this by right-clicking on the directory from explorer and then select properties–>security
- SAP_LocalAdmin(<NodeHostName>\SAP_LocalAdmin)- Administrators(<NodeHostName>\SAP_LocalAdmin)
5. The same problem can happen during the dialog instance installation on the second node. In that case, after the installation, create the missing directories and the necessary permissions for these directories as specified above.6. After the successful completion of CI and DI instances installation in your system, delete the saploc share in the SHARED DRIVE created in the step 2.
———–<24/APR/09, D033923>————————————-
Windows Server 2008: Error when installing a central or dialog instance
During the installation of a central or dialog instance on Windows Server 2008 in MSCS, you might get an error similar to this:
Cannot open Profile
\\<VirtualHostName>\sapmnt\<SID>\SYS\profile\START_DVEBMGS <InstanceNumber>_<LocalHostName>. (Error 5 EIO*: Input/output error OR: Access is denied.) [ntservstart.cpp 1025]
In this case, check the sapmnt share security and the file permission on .\usr\sap. Make sure that the domain group SAP_<SID>_GlobalAdmin has full access. You might have to remove all permissions of local groups on the sapmnt share and the file folders, since on Windows Server 2008 the security settings for local groups are not allowed on the shared disks.
———–<13/AUG/08, D033923>————————————–
———–<Updated on 15/JUN/09, I005831>—————————
Windows 2003 Only:
Check that saploc share if it exists points to local drive.
If it points to the shared drive, delete the saploc share.
You have to check this before you install the ERS, central instance or the dialog instance.
Windows 2008: See the note above in the High Availability section.
———–<D020990, 10/APR/08>————————————–
Unable to open …\packages.xml
Problem:
You get an error message when you choose the following path on the Welcome Screen:
> <Product>
> Software Life-Cycle Options
> Post-Upgrade
> High-Availability System
> Enqueue Replication Server
The error message is:
ERROR 2008-03-26 19:45:11.287
FCD-00007 Unable to open URL file://D:\Program Files\sapinst_instdir\NW04S\LM\UPG\HA\REP\packages.xml.
Solution:
1. Manually copy the following files from the DVD to the installation directory:
For example, from:
<drive>:\IM_WINDOWS_<platform>\NW04S\WEBAS\IND\PD\*.*
to
<windrive>:\Program Files\sapinst_instdir\NW04S\LM\UPG\HA\REP\2. Restart the installation with the option “Continue old installation”.