SAP Basis Tech Supports

Symptom
Installation of an SAP NetWeaver 7.0 with Enhancement Package 1 (EHP1) based system, including the Business Suite 7, on Windows
Other terms
SAPinst, 7.0, enhancement package 1, Business Suite 7, ERP 6.0 EHP4, SCM 7.0,SRM 7.0, CRM 7.0
Reason and Prerequisites
Installation problems for an SAP system based on SAP NetWeaver 7.0 EhP1 on Windows discovered after the publication of the installation guide.
It also includes information for the Business Suite 7, which is based on SAP NetWeaver 7.0 EHP1.
The Business Suite 7 includes:
ERP 6.0 EhP4
SCM 7.0
SRM 7.0
CRM 7.0
For database-specific installation problems with SAP NetWeaver 7.0 EhP1/Business Suite 7, see the following SAP Notes:
1108857 SAP NetWeaver 7.0 EHP1/Business Suite 7: Win Oracle
1108827 SAP NetWeaver 7.0 EHP1/Business Suite 7: SQL Server
1135525 SAP NetWeaver 7.0 EHP1/Business Suite 7: SAP MaxDB
1171534 DB6: SAP NetWeaver 7.0 EHP1 / Business 7 – Windows
Solution
Contents
1 General
2 Pre-Installation
3 Installation
4 Post-Installation
5 High Availability (HA)
This note contains information relevant to installation of the following SAP systems and software units on Windows. Since the Business Suite 7 is based on SAP NetWeaver 7.0 EhP1, you can also install the NetWeaver 7.0 EhP1 usage types.
SAP NetWeaver 7.0 EHP1, including software units:AS ABAP (ABAP)AS Java (Java)AS ABAP and AS Java (ABAP+Java)Business Intelligence Java (BI Java)Development Infrastructure (DI)EP Core (EPC)Enterprise Portal (EP)Mobile Infrastructure (MI)Process Integration (PI)SAP ERP 6.0 EHP4, including 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 7.0, including software units:CRM Application Set (CRM-APP)CRM Java Components (JCRM)CRM Business Packages (BP-CRM)SRM 7.0 including:SRM Application Set (SRM-APP)SRM Live Auction Cockpit (SRMLAC)SRM Business Packages (BP-SRM)SCM 7.0 including 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 stacks (ABAP, Java, ABAP+Java), the information applies to. If there is no prefix, the information applies to all SAP systems.
Date Section Description
———————————————————————
08/JUN/09 1 CRM 7.0 is only Supported on Windows Server 2008
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
30/MAR/09 3 Changing Parameter mode “Custom” to “Typical” on the “Parameter Summary” screen does not work
19/MAR/09 4 CRM: Errors in sapinst_dev.log
05/MAR/09 4 Delete usagetype.properties file manually due to security reasons
26/FEB/09 3 Windows Server 2008: Error when creating SAPstartsrv.exe service
24/FEB/09 4 Dealing safely with installation directories
13/FEB/09 2 ABAP+Java, Java: Make sure that there is not an older version of the JCE policy zip file on the installation host
30/JAN/09 4 Uninstall Diagnostics Agent only: Manually delete the <smdsid>adm user
19/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
19/NOV/08 4 Java (EP, KM): KM icons are not visible and services do not start up
06/NOV/08 3 Windows Server 2008: Error when creating
SAPstartsrv.exe service
03/NOV/08 5 HA: SCM 7.0 ABAP: liveCache client software distribution to disks
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
05/SEP/08 4 SCM, ABAP: Error message in transaction SM21 after installation
04/SEP/08 3 Error message during log off when running SAPinst first time
02/09/08 5 HA: ABAP+Java, Java: Use a local user for the Diagnostics Agent
28/AUG/08 3 Error when using the “Media Browser” screen
24/JUL/08 4 ABAP+Java,Java: Keystore views are not created during the very first start
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
29/OCT/07 1 SAPinst GUI: Close buttons (’X') of message boxes do not work
12/JUN/07 3 Uninstall: Error message FCO-00011
27/SEP/06 4 Error when uninstalling first/install second system with the same <SAPSID>.
28/MAR/06 4 (PI): Increase number of dialog work processes
22/MAR/06 4 (x64, Java, ABAP+Java): J2EE Engine reboots permanently
———————————————————————

1 General

—————-<08/JUN/09>—————————————–
CRM 7.0 only: Due to technical reasons, CRM 7.0 is only supported on Windows Server 2008. For more information, see the Product Availability Matrix at http://service.sap.com/pam.
Ignore the references to Windows Server 2003 in the installation guide.
——————– < 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

———————<13/FEB/09, D039123 >————————-
ABAP+Java, Java: Make sure that 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 generates a java.lang.SecurityException during the Create Secure Store step stating the jurisdiction policy files are not signed by trusted signers.
———————<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 files.In 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
Non-HA only: 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”.
———————-<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.
——————<30/MAR/09, D027120>—————————
Changing “Custom” to “Typical” on the “Parameter Summary” screen does not work.
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, since in “Revise” mode, you can change all parameters that you can select from the “Parameter Summary” screen except for the parameter mode (”Typical” or “Custom”).
As a solution, restart the installation with option “Run a new option”.
————–< 26/FEB/09, 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. You might have to repeat this for other Windows services.
If the problem persists, open a customer service message under BC-INS-NT.
—————- <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).
————————<04/SEP/08, D027120>———————
Error message during log off when running SAPinst first time
When you run SAPinst the very first time, and you are asked to log off and log on again, you might get the following error message:
Application popup: drwtsn32.exe – DLL Initialization Failed: The application failed to initialize because the window station is shutting down. For more information, see Help and Support Center at http://go.microsoft com/fwlink/events.asp.
Ignore this message and continue with SAPinst.
—————–<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.
——————–<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.
———————–<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”.

4 Post-Installation

————————<19/MAR/09, I027641>———————
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 is sent to them. The reason of the error messages listed in the log file is, that the applications were requested before the deployment of all referenced applications had finished. When a Web Dynpro application tries to start, it 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.

———————<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.
————————-19/NOV/08, I047884>—————————
Java (EP, KM): If after the system installation, the KM icons are not visible and services do not start up, you need to adapt the path to the shared KM configuration folder.
On each host in a J2EE cluster, perform the following steps:
1. Log on to the portal.2. Choose “System Administration -> System Configuration -> Knowledge Management -> Content Management -> Repository Managers -> File System Repository”3. Select the etc repository and choose “Edit”.4. Set the parameter to the global directory to point to the UNC path:
\\<central_instance_host>\sapmnt\<SID>\SYS\global\config\cm\etc5. To make sure that the UNC path is used during an upgrade, also enter the path (without etc) in the cm.properties file.
The file is located on the host of the central instance.
Change the value of the parameter System.SharedFolder to:
\\<central_instance_host>\sapmnt\<SID>\SYS\global\config\cm6. Restart the J2EE Engine to activate the settings.
————————<05/SEP/08, I043270>———————
SCM, ABAP: Error message after installation.
You get the following error in transaction SM21 after the installation:
Database error -10709 at CON
> Connection failed (RTE:database not running: no request pipe
To solve the problem install a liveCache.
——————-<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.
————————<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.
————————<D023322, 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.
———–<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)
———–<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.
—————- <D022376, 03/NOV/08> —————————–
HA: SCM 7.0 ABAP: liveCache client software distribution to disks
If your system isnotinstalled with the database MaxDB and you are using liveCache in SCM 7.0, you have to decide on how to distribute the liveCache client software to the local and shared disks. You have the following options:
If the liveCache server isnotinstalled on the same host as the SCM server, you can install the liveCache client software completely on local disks.If you install the liveCache server on the same host as the SCM server, you have to install the independent data of the liveCache client software on a shared disk. If doing so, the dialog instance installation on the second cluster node aborts in step installClientSoftware.
To solve this problem move the file <disc>:\sapdb\data\config\install\INSTREG to <disc>:\sapdb\data\config\install\INSTREG_A and continue the installation.
———————-<02/09/08, I021802>—————————
NW 701 only: HA: ABAP+Java, Java: Use a local user for the Diagnostics Agent.
When you install a central or dialog instance in a high-availability environment, make sure to select “Local installation” on the “Windows Domain” screen for the Diagnostics Agent, which requires a local user.
If the <smdsid>adm user already exists and is a domain user, a pop-up appears asking you to choose another, local user. If you then do not choose “Local installation” but choose a domain installation instead, the installation throws an error. In this case, restart the installation of the dialog or central instance, and for the diagnostics agent choose a local installation.