SAPTechno

Note 1439013 - SAP Systems based on SAP NetWeaver 7.3: Windows

Header
Version / Date 19 / 2012-05-18
Priority Correction with high priority
Category Installation information
Primary Component BC-INS-NT Installation Windows
Secondary Components

Summary
Symptom

You install the following SAP systems based on SAP NetWeaver 7.3 on Windows:

  • SAP NetWeaver 7.3
  • SAP Business Suite 7i 2011 (SAP ERP 6.0 EHP6, SAP CRM 7.0 EHP2, SAP SRM 7.0 EHP2) on SAP NetWeaver 7.3 Java Hubs
  • SAP Business Suite 7i 2010 (SAP ERP 6.0 EHP5, SAP CRM 7.0 EHP1, SAP SRM 7.0 EHP1) on SAP NetWeaver 7.3 Java Hubs
  • SAP Business Suite 7 (SAP ERP 6.0 EHP4, SAP CRM 7.0, SAP SCM 7.0) on SAP NetWeaver 7.3 Java Hubs

Other terms

SAPinst

Reason and Prerequisites

Installation problems for an SAP system based on SAP NetWeaver 7.3 on Windows that were discovered after the publication of the installation guide.
Always use the latest documentation version on SAP Service Marketplace of the installation guide at: http://service.sap.com/instguides

Solution

Contents

1     General
2     Pre-Installation
3     Installation
4     Post-Installation
5     High-Availability


Each entry is marked with a prefix for the NetWeaver software units abbreviations as mentioned above, and for the technical stacks (ABAP, Java, ABAP+Java). Entries for a high-availability system with MSCS (Microsoft Cluster Service) are marked with the prefix MSCS. If there is no prefix, the information applies to all types and software units.

Date      Section   Description

-----------------------------------------------------------------------
18/MAY/12   2       Apply SAP Note 1697164 before you install the SAP system
20/MAR/12   3       ABAP+Java, Java: Installation fails while 'jlaunch' is started
21/FEB/12   4       CRM 7.0 EHP1 on NW 7.3 Java Hubs: Wrong entries in tables BC_SL_SWFEATURE and  BC_SL_SWFEATUREINC
NOV/21/11   4       ABAP+Java, Java: Additional application server
19/JAN/12           Error while Installation on non-english Windows Server 2008/2008R2
02/DEC/11   3       FSL-01005  Unable to set password for account ... error code = 2147944645
21/NOV/11   3       ABAP+Java, Java: Additional application server installation: Ensure that updated SAPJVM of existing system is not overwritten by the older SAPJVM on the kernel medium.
12/OCT/11   2       PI, ABAP+Java: Problem with NW 7.3 Installation Media
11/OCT/11   4       PI, ABAP+Java: Check SAP Note 1638667
11/OCT/11   3       PI, ABAP+Java: Do not change change selection on 'Usage Types' screen
19/MAY/11   4       Caution with SAPinst Uninstall option with regard to SAP profiles
17/FEB/11   3       SAPinst Media Browser prompts folder JAVA_J2EE_OSINDEP_SAPLUP
01/DEC/10   3       Do not use the built-in or renamed built-in Administrator account to install the SAP system
13/JUL/10   3       Do not use Japanese characters in SAP system profiles
06/MAY/10   3       32-bit: Additional application server instance installation fails
29/APR/10   1       MSCS: Use of virtual host names
29/APR/10   3       Japanese Windows version: Error in step: changeUserInstall
30/MAR/09   3       Restarting SAPinst aborts with error message
26/FEB/09   3       Windows Server 2008: Error when creating SAPstartsrv.exe service
-----------------------------------------------------------------------

1     General

2     Pre-Installation


----------------------<18/MAY/12, D025095>---------------------------
Before you install the SAP system with SAPinst, apply SAP Note 1697164.

------------------<19/JAN/12, D054186>---------------------------
An error in the SAPinst framework on the current Installation Master media causes the following error when installing an SAP system based on SAP NetWeaver 7.3 on non-english Windows Server 2008/2008R2:

"Modifying the USER 'NT Authority\LocalService' failed.
SOLUTION: Modify the account manually and choose OK to continue.
If you choose Cancel, the installation will be aborted.
The detailed error message is as follows:
ind-rel.ind-os.ind-db.j2ee-eng.emptyPassword:
Password for user 'NT Authority\LocalService' is empty."

[OK] [Cancel]

Note that the USER "NT Authority\LocalService" is shown in the Windows operating system installation language.

In the latest SAP NetWeaver 7.3 SAPinst version from SAP Service Marketplace this framework error is solved. Therefore, use this SAPinst executable (version 7.20-2) for the installation of SAP NetWeaver 7.3 on a non-english version of Windows Server 2008 or Windows Server 2008 R2. The corrected SAPinst executable is available at:
http://service.sap.com/patches -> A-Z Index -> S -> SAPINST -> SAPINST 7.20-2 -> OS-version -> database independent
Proceed as follows:

    1. Download the current 7.20-2 SAPinst executable from SAP Service Marketplace at:
    http://service.sap.com/patches -> A-Z Index -> S -> SAPINST -> SAPINST 7.20-2 -> OS-version -> database independent
    2. Extract the downloaded SAR-file with SAPCAR to a local working directory on your computer, e.g. c:\tmp.
    3. Copy the SAP NetWeaver 7.3 installation Master media locally and replace sapinst.exe on the Installation Master with the previously extracted SAPinst executable.
    4. Start the installation from the modified Installation Master media.


You can ignore the warnings about the wrong OS installation language after the Prerequisites Check and continue the installation.

------------------<12/OCT/11, I031908>---------------------------
PI, ABAP+Java, Java: Problem with NW 7.3 Installation Media (Mat. No. 51039309)
Wrong Java usage types (CE-APPS, COMP-ENV, BPM) are installed together with selected usage type, although those were not selected to be installed.
To solve the problem, proceed as follows:

    5. When making installation media available, ensure that you do the following:
  • If you downloaded installation media from http://service.sap.com/swdc, make sure that you extract all individual media to separate folders.
    For example, extract 51039309_JAVA to a folder that is different from the folder to which you extract 51039309_ABAP_INST_EXP.
  • If you use physical installation media, make sure that you copy the content of all JAVA_* folders from the medium to your local disk and make them visible in the LABELIDX.ASC file.
    6. Before starting the installation, make sure that the <media>\DATA_UNITS folder contains both folders JAVA_EXPORT_JDMP and JAVA_EXPORT_JDMP_BPM, and that both folders are listed in the <51039309 media>\LABELIDX.ASC file.
    7. After the installation has finished, check if the wrong Java usage types were installed. Proceed as described in SAP Note 1641258 to resolve the problem.

3     Installation


--------------------<20/MAR/12, D056915>-------------------
ABAP+Java, Java: Installation fails while 'jlaunch' is started.
The installation fails when the program 'jlaunch' is started.
In the installation log file, you see an error message like the following:

Critical Error
Can't read program properties
-> Internal program error (rc = -1)

In the 'dev_jlaunch' tracefile, you see an error message like the following:

<os/platform> is not supported with this startup framework

To solve the problem, apply the latest kernel patch archives SAPEXEDB.SAR and SAPEXE.SAR.
For more information about how to download kernel patches, see SAP Note 19466.

-------------------<02/DEC/11, D037196>---------------------------
FSL-01005  Unable to set password for account ... error code = 2147944645
When you install your SAP system, and you get this error message, the passwords of the operating system users do not comply with the Windows password policy.
Restart the installation and set the passwords so that they comply with the Windows password policy.

-----------------<21/NOV/11, <D037196>---------------------------
ABAP+Java, Java: Additional application server installation:


You want to install an additional application server instance for an existing SAP system based on SAP NetWeaver 7.3. The SAP JVM version of the existing SAP system is more up-to-date than the SAP JVM version on the kernel medium that you use for the additional application server installation.
To avoid that the more up-to-date version of the SAPJVM from the existing system is overwritten by the older SAPJVM version on the kernel medium, ensure that you do the following when you install the additional application server instance with SAPinst:

    1. When you reach the "Unpack Archives" screen, deselect the "Unpack" flag for SAPJVM6.SAR .
    2. Choose "Next".
    3. Choose "Confirm" when SAPinst prompts you to unpack SAPJVM6.SAR manually.
    4. Choose "Cancel" on the next UI screen.
    5. Restart SAPinst with the additional command line argument SAPINST_SKIP_ERRORSTEP=true

If you do not perform these steps, you will get an error message like the following when SAPinst executes step "Install Instance basics":

********************************
CJS-30023  ,,
ERROR 2011-07-20 13:08:41.099
CJSlibModule::writeError_impl() CJS-30023 Process call
'/usr/sap/QE1/J10/exe/jstart pf=/usr/sap/QE1/SYS/profile/QE1_J10_plx040
-file=/usr/sap/QE1/J10/exe/startup.properties -nodename=bootstrap
-launch' exits with error code 2. For details see log
file(s)jstart_bootstrap_J10.log.
*********************************

Error message in log file jstart_bootstrap_J10.log:

*********************************************************************

F  [Thr 47550871018560] *** ERROR => SfCJvmConfig::testJava: Java VM
info collection failed.
- checked JVM type 'server'
- checked JVM type ''
Please check the following files:
- Java launcher    : /usr/sap/QE1/J10/exe/sapjvm_6/bin/java
- Java info output :
/tmp/sapinst_instdir/NW73/ADA/AS/APPS/JvmInfo_10790.txt [sfxxcfg.hpp
1265]
F  [Thr 47550871018560] *** ERROR => SfEStartupError: Java VM detection
failed.  [sfxxcfg.hpp  664]
F  [Thr 47550871018560] *** ERROR => Initialization failed:
SfEStartupError: Java VM detection failed.
[sfxxmain_mt. 998]
F
F  F  *** ERROR => Java VM info collection failed.

**********************************************************************

In this case, perform the following steps:

    1. Restore the SAP JVM as follows:
      a) Log on to the SAP global host as user <sapsid>adm
      b) Change to the central SAPJVM directory:
      <drive>\usr\sap\<SAPSID>\SYS\exe\jvm\<platform>\sapjvm_<version>
      where <version> is the major release of the SAP JVM, for example 6
      c) Delete the contents of the central SAP JVM directory.
      d) Unpack the SAR archive of SAP JVM for the version currently used by the system by executing the following command:
      SAPCAR -xvf <SAPJVM SAR file>
    2. Log on to the host of the additional application server instance being installed and execute the following command to distribute the updated central SAP JVM to the additional application server instances:
    sapcpe pf=<application server profile> list:<central SAPJVM dir>/sapjvm_<version>.lst source:<central SAP JVM dir>
    3. Continue with the additional application server installation.


-------------------------<10/OCT/11, D042421>-------------------------
PI, ABAP+Java: Do not change change selection on 'Usage Types' screen
You are installing the primary application server instance of a High-Availability SAP Process Integration System
Due to a bug in SAPinst, the 'Usage Types' screen is displayed. Make sure that you do not change the default selection of usage types in the table 'SAP NetWeaver Usage Types' on the 'Usage Types' screen.
The following usage types must be selected:

  • Application Server ABAP
  • Application Server Java
  • NW Product Description
  • Process Integration Adapter Engine
  • Application Server Java Extensions
  • Enterprise Services Repository
  • Process Integration


----------------<17/FEB/11, D042421>-------------------
SAPinst media browser prompts folder JAVA_J2EE_OSINDEP_SAPLUP
When you install your SAP system, SAPinst might ask you for the location of the following media:
Java component NW73 (folder JAVA_J2EE_OSINDEP_SAPLUP).
SAPinst is looking for the LUP.SAR archive in the folder JAVA_J2EE_OSINDEP_SAPLUP. However, this folder is not located on the SAP NETWEAVER 7.3 OS-DB independent components media (#51039309), but in the folder SL_CONTROLLER_720 on the SAP NetWeaver 7.3 OS-DB dependent media (#51040410) (or relevant kernel DVD).

-------------------<01/DEC/10, D020904>--------------------------
Do not use the Windows built-in user 'Administrator' or the renamed built-in user to install your SAP system with SAPinst. The built-in user only has restricted network access rights that are required by SAPinst. Instead, use an user who has the required user authorization.
For a domain installation, this is normally a user who is a member of the domain Admins group; for a local installation this is a user who is a member of the local administrators group. For more information, see the chapter "Required User Authorization for Running SAPinst" in the installation guide for your SAP system.
For security reasons, Microsoft recommends to rename the Windows built-in user 'Administrator'. If you rename this user into e.g. NTAdmin, then make sure that you do not create a new user with the original name 'Administrator' and you use this new 'Administrator' user for the installation with SAPinst. Otherwise, SAPinst does not assign the correct rights to this newly created user 'Administrator' and permanently asks you to log off and log on again. The problem only occurs if you create a new user with exactly the same name as the old renamed 'Administrator' user. It does not exist if, for example, you call the new user 'Administrator1'. However, in any case you should neither use the built-in Administrator user nor the renamed built-in Administrator user to install your SAP system.

---------------<13/JUL/10, D029385>---------------------------
Do not use Japanese characters in SAP system profiles
You made entries (for example, comments) in SAP system profiles in \usr\sap\<SAPSID>\profile.
You get an error message that a profile parameter is not set.
To solve the problem, proceed as follows:

    1. Remove all Japanese characters from the SAP system profiles.
    2. Restart the installation.
    On the "What do you want to do?" screen, choose "Run a new option".


----------------<06/MAY/10, D035306>----------------------------------
32-Bit Windows: The additional application server instance installation fails when starting disp+work.exe at the end of the installation phase.
Before you install an additional application server instance on a host different from the database instance host, you need to install the Microsoft Visual C Runtime 7.1 library attached to SAP note 684106. Otherwise, the installation fails. Also read SAP note 1280759.

-------------------<29/APR/10, D033923>--------------------------------
Japanese Windows version: Error in step: changeUserInstall
With the Japanese Windows version, you might get the following error in step: changeUserInstall
To solve this problem, skip this step as follows:

    1. Stop the installation.
    2. In the installation folder, open the "keydb.xml " file.
    3. Search for the table "tDialogStatus"
    4. Look for the last row where it says: "changeUserInstall step"
    5. Edit the field STATUS and write OK like this:
    <strval><![CDATA[OK]]>
    </strval>
    6. Save the changed "keydb.xml" file.
    7. Restart the installation, choose the same installation option as before, and choose "Continue the 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.

---------------< 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. If the problem persists, open a customer service message under BC-INS-NT.

4     Post-Installation


---------------------<21/FEB/12, D025095>------------------------
CRM 7.0 EHP1 on NW 7.3 Java Hubs: Wrong entries in tables BC_SL_SWFEATURE and BC_SL_SWFEATUREINC
There is an error in the file "ppms_data.xml" on the installation master medium. This results in wrong entries in the tables BC_SL_SWFEATURE and BC_SL_SWFEATUREINC.
To solve the problem, apply SAP Note 1687048.

-----------------------<10/OCT/11, D031385>----------------------
PI, ABAP+Java: Check SAP Note 1638667

------------------------<19/MAY/11, D050445>----------------------
Before you use the SAPinst 'Uninstall' option, make sure that the profile directory of the relevant SAP system to be deleted only contains profiles that belong to this  SAP system. Otherwise, if there are valid profiles of other SAP systems available in this profile directory, there might be the risk of data loss for these systems.

5    High Availability


-------------------------<29/MAR/10, D0339223>------------------------
MSCS: Use of virtual host names Only use virtual host names in an MSCS environment, if this is explicitely stated in the MSCS-specific parts of the installation guides. Otherwise, use the physical host name, for example, when starting SAPinst.

Affected Releases
Software Component Release From Release To Release And subsequent
SAP_BASIS71730730

Related Notes
1716962HA: Error with special characters in cluster resource name
1641258Problem with NW 7.3 Installation Media
1617021Inst. SAP NetWeaver 7.3: Windows / SAP HANA Database
1613306Installation of SAP NetWeaver 7.3 EHP1 - Developer Workplace
1600846JSPM/SUM calls sapcontrol without user credentials
1503070Inst. Systems Based on NW 7.3 on IBM DB2 for z/OS
1492391Installation of SAP NetWeaver 7.3 Developer Workplace
1489836SAP NetWeaver 7.3 for IBM DB2 for i
1482555DB6: Inst. of SAP NetWeaver 7.3 - Windows
1460151Web Dispatcher SAP Systems based on SAP NetWeaver 7.3