SAPinst Troubleshooting Guide for SAP Web AS Java Installation

Transcription

1 Troubleshooting Documentation SAPinst Troubleshooting Guide for SAP Web AS Java Installation Version 1.00 (March 2004)

2 Copyright 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. SAP AG Neurottstraße Walldorf Germany T +49/18 05/ F +49/18 05/ JAVA is a registered trademark of Sun Microsystems, Inc. J2EE is a registered trademark of Sun Microsystems, Inc. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic Server TM are trademarks of IBM Corp. in USA and/or other countries. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. MaxDB is a trademark of MySQL AB, Sweden SAP, SAP o, R/2, R/3, mysap, mysap.com, xapps, mysap Business Suite, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. LINUX is a registered trademark of Linus Torvalds and others. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way. Documentation in the SAP Service Marketplace You can find this documentation at the following Internet address: service.sap.com/instguides

3 SAP AG Neurottstraße Walldorf Germany T +49/18 05/ F +49/18 05/ Typographic Conventions Icons Type Style Represents Icon Meaning Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Caution Example Note Cross-references to other documentation Recommendation Example text Emphasized words or phrases in body text, titles of graphics and tables Syntax EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools. Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key

4 Contents 1. How to Use this Documentation General Remarks on Error Analysis Help from SAP How to Proceed After Correcting the Error Identifying Errors and Solving Problems Technical Information January/2004

5 Document History SAPinst Troubleshooting Guide for J2EE Version V 1.00 (March 8, 2004) Important Changes First Version January/2004 5

6 1. How to Use this Documentation This documentation provides troubleshooting information for the J2EE installation procedures with the tool SAP Landscape Implementation Manager, known for short as SAPinst and referred to as SAPinst in the text. It is meant to be an additional information source beside the component (J2EE) installation guide. It provides the following information: General notes on error analysis How to get help from SAP Support What to do if an installation error occurs s to already known errors Technical information Although this documentation provides software component-specific troubleshooting, you must also refer to further component-specific troubleshooting guides and related SAP Notes, which may be referenced in the relevant component installation guide. We highly appreciate your feedback about SAPinst. You can enter your comments at: This documentation is updated as required to inform you about new concepts and solutions for the installation process with SAPinst. You can also find updates at: To help you recognize updated versions more easily, the hyperlink to this guide contains date and version information, for example (Version 1.10, updated 20/DEC/2001) Sections of this Documentation Section General Remarks on Error Analysis SAP Support Identifying Errors and Solving Problems Technical Information Summary Introductory notes for the handling of error analysis Advanced help by SAP Support. Overview of relevant processing components in SAP Service Marketplace. Procedure for identifying errors and solving problems and how to continue the installation Also describes known error situations with clearly defined error messages and possible solutions. Related information that could be useful during a troubleshooting phase, such as log file descriptions, command options, external support tools, and so on. Back to Contents 6 January/2004

7 2. General Remarks on Error Analysis If you encounter errors in the installation of a J2EE Engine (a J2EE Only installation or an Add-In installation with an ABAP system), always go to the SAPinst log file sapinst_dev.log first. Proceed as follows: 1. Choose the path: %ProgramFiles%\sapinst_instdir\<installation_specific> (Windows) or /tmp/sapinst_instdir/<installation_specific> (UNIX). 2. Check the log file sapinst_dev.log. The name of the subdirectory <installation_specific> depends on the installation scenario you chose. On Unix, the installation directory sapinst_instdir is created as standard as a subdirectory of the temporary directory. The temporary directory is determined by checking the following alternatives for the installation directory, one by one: $TEMP, $TMP, /tmp. However, this is done only if you start SAPinst from a directory of the CD or another Read Only directory. Alternatively, you can switch to another writable directory of your choice and start SAPinst from there with its absolute path on the CD: Example (Unix): cd /installations/myinstallation <mount point SAP master CD>/SAPINST/UNIX/HPIA64/sapinst We recommend that you keep all installation directories until you are fully satisfied that the system is completely and correctly installed. If SAPinst cannot find a temporary directory, the installation terminates with the error FCO In a J2EE Only installation on Windows, the directory %ProgramFiles%\sapinst_instdir\WEBAS_640_J2EE_ONLY is created, which contains all log files created by SAPinst during an installation. If, when you start SAPinst, you select an installation that has already started on this computer, SAPinst uses the same log directory as the first time. SAPinst determines January/2004 7

8 that an installation of the same type has already been started, and asks you whether you want to start a completely new installation. If you want to start a new installation, the existing directory is saved by appending a timestamp (for example, a backup of the J2EE Only installation directory on Windows could appear as follows: %ProgramFiles%\sapinst_instdir\WEBAS_640_J2EE_ONLY\CS_<timestam p>). A completely new installation is then started. You can also start a completely new installation by deleting the installation directory. When you restart an installation on Unix, you must make sure that you start SAPinst in exactly the same way as you did the first time. If you have chosen an alternative installation directory, then you must restart SAPinst from this directory again, with the same absolute path. Otherwise, SAPinst assumes that you want to start a completely new installation. You can find out the step and component in which the installation was stopped at the end of the log file sapinst_dev.log. The step SapdbInstaller_SDBINST with step key J2EE_EngineEnterprise_OneHost ind ind ind WebAS J2EE_Engi neenterprisedialogs ind ind ind WebAS J2EE_Engine ind ind ind J2EE_Engine J2EE_Engine_SAPDB_Client ind ind ind ind ind 0 SAPDB_DB_SOFTWARE ind ind ind ind ind 0 SapdbInstaller_S DBINST executed with status ERROR The step is stated explicitly (here, SapdbInstaller_SDBINST); the SAPinst component is under key and can be found seven attributes before the step (here, SAPDB_DB_SOFTWARE). If SAPinst is still running, it may mean that the log file has not yet been updated. You can do this by clicking View in the GUI, or by exiting SAPinst. If SAPinst finds files in the SAPinst log directory, it assumes that you want to continue an existing installation, and uses the existing xml files. Note that different components can have different runtimes, depending on the computer and the installation scenario. Also note that certain installation steps must be performed in parallel. Not all the programs used in the installation are SAP programs, nor are they always a part of the SAPinst installation framework. This means that there cannot always be an explicit cooperation with these programs. In rare cases, the SAPinst Controller might not receive the expected results from one of these components in time. The step is then flagged as having produced an error, even though it has only exceeded a time limit. This problem can often be solved by choosing Retry in SAPinst to repeat the installation step (this is particularly successful on Windows). Back to Contents 8 January/2004

9 3. Help from SAP On many occasions, errors are not caused by the installation itself, or are not caused directly by the installation. If you cannot solve the problem yourself, attempt to identify the source of the error, and open a message in the appropriate component in SAP Service Marketplace. To enable the support team to process your message more efficiently, include any relevant error messages from the appropriate log file in your message. Before you open a message in SAP Service Marketplace, read any related SAP Notes in the corresponding component. These notes may give you more information on your problem. The following table shows you which SAP Service Marketplace component to use for which SAPinst component. This speeds up the processing of your message. Use the general installation component BC-INS only if you cannot narrow down your problem any further. SAPinst Component StartJ2EE SAP Service Marketplace Component BC-JAS OraDbUser OraDatabaseCommonParameters1 DatabaseOraSW OraRedolog OraDatabaseServerDirectories1 OraDatabaseServerConfiguration1 OraDatabaseBuild1 OraDatabaseTablespaces OraRollbacksegments OraDatabaseSchema DatabaseNetworkConfiguration1 DatabaseOraPatch OraSidadmEnv ORA_JDBC_DRIVER CREATE_SECURE_STORE_FS BC-INS SAPDB_DB_SOFTWARE SAPDB_DB_OSUSER_UX SAPDB_DB_INSTALL SAPDB_DB_UPD BC-DB-SDB-INS January/2004 9

10 SAPDB_INSTANCE DatabaseSchemaOperations SapDbConnectivity4J2EE SAPDB_JDBC_DRIVER MssinInfo MssDatabaseInfo MssCreateDatabase MssCreateSchema MssSecuritySwitch MssProfileParams MssStartScript MSS_JDBC_DRIVER BC-DB-MSS-INS DB2DatabaseServerJ2EE DB2PrepareSchemaJ2EE DB2_JDBC_DRIVER BC-DB-DB2-INS J2EEDB-DB4 JDBCDriver_DB4 BC-DB-DB4 DB6_Prepare_CreateUser DB6_PropagatePasswords DB6_Prepare_CreateTablespaces DB6_Prepare_CreateBufferpools DB6_Prepare_UpdateDbmAndDbCfg DB6_Filesystem DB6_CreateUser DB6_ModifySapsidadm DB6_DirectoryPermissions DB6_CreatePort DB6_CreateInstance DB6_StartInstance DB6_CreateDatabase DB6_UpdateDb2Registry DB6_CreateNodegroups BC-DB-DB6-INS 10 January/2004

11 DB6_CreateBufferpools DB6_CreateTablespaces DB6_Prepare_GrantPrivileges DB6_GrantPrivileges DB6_UpdateDbmCfg DB6_UpdateDbCfg DB6_RestartInstance DB6_ExecuteSqlScript DB6_JDBC_DRIVER SDM Installation BC-CTS-SDM IGS Installation BC-FES-INS SAP Netweaver Developer Studio BC-DWB-JAV Back to Contents January/

12 4. How to Proceed After Correcting the Error SAPinst does not simply exit the installation after an error occurs. This means that you can continue an interrupted installation as follows: If the installation is waiting at the location of the error, choose Retry. The step with the error is then executed again. You have already canceled the installation (by choosing Cancel). In this case, restart the program sapinst.exe (Windows) or sapinst (Unix) and choose the canceled installation from the GUI. SAPinst logs the progress of the installation in the file keydb.xml, which means that you can resume the installation from where it was canceled. In this case, you are asked whether you want to resume the old installation. Answer by choosing Yes. When you restart an installation, you must make sure that you start SAPinst in exactly the same way as you did the previous time. Back to Contents 12 January/2004

13 5. Identifying Errors and Solving Problems This chapter gives you an overview of errors that can occur during an installation. In the table, click a symptom to go to the proposed solution. Area Symptom General errors Cannot start SAPinst GUI Error when entering password during installation dialog Cannot create profiles Cannot install SAP Software Deployment Manager (SDM) Cannot call SAP Software Deployment Manager (SDM) Cannot switch mode of SAP Deployment Manager (SDM) Restart after a canceled installation Operating system-specific errors Windows Cannot create Windows services Cannot stop a Windows service Cannot create Windows file system shares Cannot create port entries Cannot create plug-in for Microsoft Management Console Cannot start/stop SAP system in SAP MMC Unix Oracle Universal Installer error when installing Oracle software on Unix Cannot create SAP/database administration users on Unix Cannot install SAPCCMSR agent SAPinst archive Cannot unpack SAPinst archive to target directory Error when getting SAPinst archive January/

14 from CD Cannot access archive files of installation CD J2EE environment Cannot start J2EE instance Invalid JDK directory Java environment set incorrectly Error message in installation step Create a J2EE Database Error in installation step Prepare Oracle Server Configuration Database Database software not installed Incorrect version of database software installed Back to Contents General Errors Symptom: Cannot start SAPinst GUI FGE Attempt to open a communication port connection failed. Check whether the port is already in use. FCO An error occurred during the installation. Problem: error in GUI server subsystem. This error can occur when you want to exit a previous SAPinst session (for example, by choosing Cancel), but you have not closed the corresponding log window, possibly because it has been minimized and you have not seen it. This means that SAPinst instance is still active and using all required resources, in particular the communication port. 14 January/2004

15 1. Check whether another SAPinst installation has already been started. If so, exit this session by using the Task Manager (on Windows) or the kill command (on Unix). Close any old log windows that are still open. 2. If no previous SAPinst instances are still active, use the netstat command to check whether another application is already using the default SAPinst installation port In this case, you can choose another port number by specifying the SAPinst command line option SAPINST_DIALOG_PORT=<port_number>. Always make sure that only one SAPinst instance at a time is started on a computer. Symptom: Error when entering password during installation dialog Description The installation dialog queries the passwords of the SAP users (SAP system administrator and the SAP Service Account). You enter the passwords, but you get the following error message: Invalid password. DIAGNOSIS: The password you specified for user <host_name>\<user> is wrong. SOLUTION: Enter the correct password. Cause The SAP system administrator or SAP Service Account already exists with different passwords. 1 Make sure that you have used the correct password. If you cannot confirm this, choose User Management (on Windows) or the passwd command (on Unix) to change the password to the one specified in the SAPinst dialog. 2 Alternatively, you can delete the relevant accounts when you restart an installation. We recommend that you do this if these users have already been created by a previous canceled installation. Symptom: Cannot create profiles FSL Unable to create node %instance_dir%/sys/profile/default.pfl with type file: The system cannot find the path specified. January/

16 FSL Node %instance_dir%/sys/profile/default.pfl does not exist. 1. Check whether the profile directory exists with the correct rights (on Windows, user group Administrators with authorization Full Control; on Unix, user <sid>adm, user group sapsys, and directory access rights 755). 2. If you are in doubt, create the directory manually with the correct authorizations. Symptom: Cannot install SAP Software Deployment Manager (SDM) MUT Call of SDM API autoinstall ends with error code <rc>. file %sapinst_instdir%/sdmautoinstall.log 1. Check the specified log for more detailed messages. 2. Also check whether the SDM log files sdmlog<timestamp>.log or engine<timestamp>.log exist under <drive>:\usr\sap\<sid>\jc<nr>\sdm\program\log (on Windows) or /usr/sap/<sid>/jc<nr>/sdm/program/log (on Unix), and whether these log files contain more information on the error. 3. Find the newest log file. 4. To do this, enter dir /od (on Windows) or ls -ltr (on Unix) in the SDM log directory. The newest file is at the bottom of the file list. Symptom: Cannot call SAP Software Deployment Manager (SDM) SDM call of <...> ends with returncode <rc>, where <...> contains the various SDM commands. This is always an SDM command (shutdown, jstartup, autoupdate, autoinstall, registerjstartup, gettargetconfig, registertarget, savetarget, getsubstvar, addsubstvar, deploy, systemcomponentstate, registersecurestore) and any additional optional SDM parameters. During the installation, SAPinst calls the SDM several times using its command line 16 January/2004

17 interface. 1. If the SDM cannot be called, go to the SAPinst installation directory and check the log file callsdmviasapinst.log for any information on the error. 2. The directory drive>:\usr\sap\<sid>\jc<nr>\sdm\program\log (on Windows) or /usr/sap/<sid>/jc<nr>/sdm/program/log (on Unix) contains other SDM-specific logs for the J2EE Only installation. For an add-in installation, you can find more detailed information in the directory <drive>:\usr\sap\<sid>\dvebmgs<nr>\sdm\program\log (on Windows) or /usr/sap/<sid>/dvebmgs<nr>/sdm/program/log (on Unix). Go to the newest log file first. 3. If these log files do not contain any information on the cause of the problem, execute the relevant SDM command manually. The SDM command line is in the SAPinst log file sapinst_dev.log and has the following syntax: Windows: <SDM Install Dir>\sdm.bat <command name> <command parameters> Unix: <SDM Install Dir>/sdm.sh <command name> <command parameters> On Windows, you must place the command line parameters in double quotes, for example: sdm.bat <command> "<param_1>=<value_1>" "<param_2>=<value_2>"... The SDM can be called directly only if you have a correctly installed Java environment. This should be confirmed when SAPinst calls the SDM. If the errors still occur when you execute the command directly, you can isolate them from SAPinst. Example of calling the SDM on Windows: To switch the SDM to integrated mode, you use the following command (for a system with the SID C11, J2EE instance number 00, and the installation drive C): C:\usr\sap\C11\JC00\SDM\program\sdm.bat jstartup "mode=integrated" "sdmhome=c:\usr\sap\c11\jc00\sdm\program" For more details on the SDM, see the directory <drive>:\usr\sap\<sid>\jc<nr>\sdm\program\doc (on Windows) or /usr/sap/<sid>/jc<nr>/sdm/program/doc (on Unix). This directory contains the following information files: (1) SDMCommandLineDoc630_en_final.pdf: Meaning of the SDM error codes and explanations of the command line options. (2) SDM_Dokumentation_630_en.pdf: Information on the SDM (in particular, deployment) and its log files. To view this documentation, you must install Adobe Acrobat Reader (available at January/

18 Symptom: Cannot switch mode of SAP Deployment Manager (SDM) MUT SDM call of jstartup mode=integrated ends with returncode <rc> MUT SDM call of jstartup mode=standalone ends with returncode <rc> During the installation, the SDM is switched from integrated to standalone mode, and back. If this does not work, first check the log file callsdmviasapinst.log in the SAPinst installation directory. The directory %SDM_install_dir%program/log (for example, the Windows directory for system C11 is C:\usr\sap\C11\JC00\SDM\program\log) contains other SDM logs. If these log files do not contain more detailed information, execute the relevant SDM command manually. Before you can do this, you must have a correctly installed Java environment. In this way, if the errors still occur when you execute the command directly, you can isolate them from SAPinst. (1) To switch the SDM to integrated mode, execute the following (an example is shown here): C:\usr\sap\C11\JC00\SDM\program\sdm.bat jstartup "mode=integrated" "sdmhome=c:\usr\sap\c11\jc00\sdm\program" (2) To switch the SDM to standalone mode, execute the following (an example is shown here): C:\usr\sap\C11\JC00\SDM\program\sdm.bat jstartup "mode=standalone" "sdmhome=c:\usr\sap\c11\jc00\sdm\program" For more details on the SDM, see the directory <drive>:\usr\sap\<sid>\jc<nr>\sdm\program\doc (on Windows) or /usr/sap/<sid>/jc<nr>/sdm/program/doc (on Unix). This directory contains the following information files: (1) SDMCommandLineDoc630_en_final.pdf: Meaning of the SDM error codes and explanations of the command line options. (2) SDM_Dokumentation_630_en.pdf: Information on the SDM (in particular, deployment) and its log files. To view this documentation, you must install Adobe Acrobat Reader (available at Windo ws 18 January/2004

19 Symptom: Restart after a canceled installation Description The SAP Administrator Account and SAP Service Account have already been created in an earlier installation. The password is now queried. If you enter the wrong password, the following error message appears: Invalid password. DIAGNOSIS: The password you specified for user '<host>\<sid>adm' or <host>\sapservice<sid>'is wrong. SOLUTION: Enter the correct password. If you do not know the correct password, delete the user at the operating system level, and restart the installation from the beginning. Operating System-Specific Errors Windows Symptom: Cannot create Windows services MOS 'E:\usr\sap\J2E\JC00\exe/sapstartsrv.exe' returned with '-1' In the run directory of the installation, check the log file sapstartsrv.exe.log for any additional information on the error. 2. Open the Windows Viewer to get more information on the error. Also check the Event Viewer of the system for any messages that are related to creating the service. 3. In particular, check whether your password for the SAP service user SAPService<SID> has been set correctly in the Windows user administration Attempt to create the service in the interactive mode of the program sapstartsrv.exe. To do this, open a command window and switch to the exe directory of the instance that you want to install (for example, E:\usr\sap\J2E\SYS\exe\run). 2. Here, start the tool for creating the SAP services in interactive mode by entering sapstartsrv. 3. Enter the following information in the dialog boxes that now appear: Operation: Select Install Service + Register COM Interface. SID: System ID of your installation (for example, J2E). January/

20 NR: Instance number (between 00 and 99) Start Profile: Use the Browse button to find the start profile of the installation (for example, E:\usr\sap\J2E\SYS\profile\START_JC00_mysap12vm03). User: Enter the user under which you want the service to run (for the system J2E, for example, the existing local Windows user.\sapservicej2e). Password: Enter the password of the user. 4. Confirm your entries by choosing OK, and wait until the program displays a message (this can take some seconds). If you cannot create the service interactively, check whether an entry exists for the service SAP<SID>_<nr> in the service applet. Delete this entry by starting sapstartsrv.exe and then choosing Uninstall Service + Unregister COM Interface under Options. Finish by choosing OK. Then attempt to create the service again with the procedure described above. Symptom: Cannot stop an SAP Windows service Error 1053 (The service did not respond to the start or control request in a timely fashion.) in execution of a 'ControlService' function, line (281), with parameter (SAP<SID>_<nr>,SERVICE_CONTROL_STOP). MOS Could not stop the 'SAP<SID>_<nr>' service on host 'Local'. Open the service applet. Attempt to stop the service manually. If errors have occurred, you get more detailed information directly. Open the Event Viewer and look for the cause of the error. If you cannot find any obvious errors, use the Microsoft Management Console (MMC) to check whether the corresponding server is still running. Stop this server and choose Retry. Further Information Assignment of service to server in the MMC SAP_<SID>_<nr> corresponds to <host_name> <nr> 20 January/2004

21 Symptom: Cannot create Windows file system shares FSL Error when sharing file system export (share) saploc : Access is denied. 1. Check whether the shares have been created with incorrect security information. To do this, go to the Control Panel and choose Administrative Tools, then Computer Management. 2. Under Shared Folders, expand Shares and check whether the share specified in the message (saploc in the example) has been created here. 3. For this share, open the context menu and choose Properties. Under Security, check whether the groups Administrators, SAP_LocalAdmin, and SYSTEM have all the listed authorizations. If this is not the case, select the appropriate checkboxes under Allow. Symptom: Cannot create port entries on Windows FSL Unable to access file C:/WINNT/system32/drivers/etc/services: cannot get read access. FSL Unknown exception caught when trying to add an entry to the service file. 1. Check whether you can open and modify the file %WINDIR%\system32\drivers\etc\services. 2. If you cannot do this, find the application that has locked this file. 3. Check whether the access rights for this file permit the Administrators user group to have the Full Control authorization. Symptom: Cannot create plug-in for Microsoft Management Console MOS Unable to register SAP snap-in in the MMC. Check the log file SAPMMCU.log in the SAPinst installation directory for more information on the error. In particular, check whether you can create the file %WINDIR%\sapmmc.msc, and whether the Windows executable %WINDIR%\system32\mmc.exe exists. January/

22 Start the Microsoft Management Console %WINDIR%\system32\mmc.exe. From the console, open the file %WINDIR%\sapmmc.msc. Symptom: Cannot start / stop SAP system in SAP MMC Description The display is empty, even though the services SAPOSCOL and SAP<sid>_<instance_number> are active. The SAP system is also active. No Error entries are in the log; the installation was completed properly In the run directory of the installation, check the log file sapstartsrv.exe.log for any additional information on the error. 2. Open the Windows Viewer to get more information on the error. 3. Also check the Event Viewer of the system for any messages that are related to creating the service. 4. Attempt to create the service in the interactive mode of the program sapstartsrv.exe. To do this, open a command window and switch to the exe directory of the instance that you want to install (for example, E:\usr\sap\J2E\SYS\exe\run). 5. Here, start the tool for creating the SAP services in interactive mode by entering sapstartsrv. On Windows, you can start the program sapstartsrv.exe from the Explorer. 6. Enter the following information in the dialog boxes that now appear: Operation 1: Select Uninstall Service + Register COM Interface. SID: System ID of your installation (for example, J2E). NR: Instance number (between 00 and 99) Operation 2: Select Install Service + Register COM Interface. SID: System ID of your installation (for example, J2E). NR: Instance number (between 00 and 99) Start Profile: Use the Browse button to find the start profile of the installation (for example, E:\usr\sap\J2E\SYS\profile\START_JC00_mysap12vm03). User: Enter the user under which you want the service to run (for example, for the system J2E, the existing local Windows user.\sapservicej2e or the domain user, depending on which user you have chosen for the installation). Password: Enter the password of the user. 7. Confirm your entries by choosing OK, and wait until the program displays a message (this can take some seconds). 22 January/2004

23 2 Instead of using the SAP MMC, you can use the graphical tool SAP Service Manager to manage your SAP systems. You call this tool as follows: x:\usr\sap\<sid>\sys\exe\run\sservmgr.exe <SAPSYSTEMNAME>_<SAPSYSTEM> [<COMPUTERNAME>] The following errors can occur: The SAP Service Manager cannot connect to the SAP/R3 Service. Please check the following settings: General - Information about the pipe name is taken from the command line. Check Computer name and Pipe name of the error message. Correct the command line if necessary: sservmgr <SAPSYSTEMNAME>_<SAPSYSTEM> [<COMPUTERNAME>] Error code 2 - SAP Service not existing or not started. Use Windows Control Panel to check existence and start it if necessary. - SAP Service cannot read start profile: * Profile commandline parameter (pf=...) of SAP Service wrong. Use the SAP tool ntscmgr query <Service name> to check the command line. * Profile not existing. * "sapmnt" share on sapglobal host not existing or permissions wrong. Use Windows FileManager to check it. * Application server has been booted before sapglobal host was booted. Make sure that the sapglobal host is booted before any application server. Use Windows Control Panel to stop and restart the SAP Service. * SAP Service is running under wrong account. Use Windows Control Panel to check the account under which the service is running. Never use the System or Administrator account. - SAP Service cannot change to SAP working directory. "saploc" share on application server not existing or permissions wrong. Use Windows FileManager to check it. Error code 5 - Access to the pipe is denied. The pipe of the SAP Service is protected with the permissions of the service executable sapntstartb.exe. Check your authentication and log on as user with the correct permissions. Error code 53 - The network path in the pipe name does not exist. Check the Computer name of the command line and make sure that the computer is up and running. - If the SAP Service Manager and the SAP/R3 Service are running on different machines, check the network connection. January/

24 Unix Symptom: Oracle Universal Installer error when installing Oracle software on Unix Error message: Error in invoking target <target> of makefile <makefile>. You must not ignore this error (even though Oracle Installer gives you this option). Otherwise, other errors may occur in a later installation phase (for example, you might not be able to connect to the database with the TNS Listener, even though all connection parameters are correct, and the TNS Listener is working correctly; you might not be able to load SAP data into the Oracle database; you might not be able to start the J2EE Engine due to a failed DB connect). To solve this problem, proceed as described in SAP Note Symptom: Cannot create SAP/database administration users on Unix Various log entries: FSL Unable to create account user="<sid>adm" uid="<uid>". Cannot modify /etc/group file, /etc/passwd was modified (return code <rc>) FSL Unable to create account user="ora<sid>" uid="<uid>". UID <uid> is not unique (return code <rc>) FSL Unable to check password for account user="<sid>adm" uid="<uid>". FSL Unable to modify account user="ora<sid>" uid="<uid>". FSL Unable to create node /home/<sid>adm/.profile with type file: Permission denied. SAPinst must run under a system administrator (on Unix, a user with uid = 0). Therefore, the specified user actions can fail only if the user accounts are not managed exclusively locally. You are probably using the Network Information Service (NIS, also known as Yellow Pages). This service manages user configurations and network configurations centrally. The following files usually have centrally managed counterparts when you use NIS: 24 January/2004

25 /etc/passwd, /etc/group, /etc/hosts, /etc/protocols, /etc/netgroup, /etc/networks, /etc/services, /etc/rpc. 1. Check whether the NIS Binder has been started (for example, by using ps - ef grep ypbind), and whether your computer is a potential NIS client. 2. Since NIS is not supported by older SAPinst installations, stop the NIS services, and repeat the appropriate SAPinst step by choosing Retry. Example: On HP-UX, you can check the file /etc/rc.config.d/namesvrs to see whether your computer is configured as an NIS client. If this file contains the entry NIS_CLIENT=1, your computer is configured as an NIS client. Otherwise, this parameter has the value 0. Example: On HP-UX, the search order of local and/or remote configuration entries is specified in the file /etc/nsswitch.conf. The search order can be changed dynamically. 3. If you have deactivated the NIS services for the installation, restart the service after the installation has been completed. In the central NIS management, repeat the changes made by SAPinst at the local level. Do not create the Unix users and Unix groups manually at the local level when NIS is running. Otherwise, an error occurs later when the home directory of the SAP administration user <sid>adm is created. This is not noticeable until the central instance (SCS<nr>) cannot be started, and a log message such as the one below is created: CJS Could not start instance 'SCS<nr>' of SAP system <SID>. Symptom: Cannot install SAPCCMSR agent FSL Account user="undefined" does not exist. This is an error in the SAPinst Java script part of the installation. 1. Choose Retry to finish this step successfully. 2. Change the owner of the installation directory of the SAPCCMSR agent to the system administrator and this administrator s group with the Unix command chown <sid>adm:sapsys <dir>. January/

26 SAPinst Archive Symptom: Cannot unpack SAPinst archive to target directory FSL Unable to access file %instance_dir%/scs<nr>/exe/sapstartsrv.exe: cannot get write access. 1 For program files: Use the Task Manager to determine whether this file is being executed and is therefore protected from being overwritten. Stop this program with the Task Manager. For other files: Check whether you can delete the file manually (for example, with the Windows Explorer), or whether it is locked by an application. 2 Search the installation log to find out when the program SAPCAR.exe was called. The specific log file of this call is specified before the program is called. You can find entries such as the following: Output of C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/1/sapinst_exe /SAPCAR.exe is written to the log file SCS.log. Search this log file for more details on the extraction process and any other error messages. 3 Attempt to perform the extraction process manually by opening a command window and repeating the command from the log file sapinst_dev.log in the command line. Example of an entry in the SAPinst log file: Output of C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/1/sapinst_exe /SAPCAR.exe '-x' '-v' '-g' '-i' '-n' '-R' 'E:\usr\sap\J2E\SYS\exe\run' '-f' 'D:/j2eecd_sp3_os1_inst_indos_ind_630-j2ee-cd/SCS/NT/I386/SCS.SAR,': Copy the input to the command line and make sure that it results in a valid command line: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\sapinst_exe \SA 26 January/2004

27 PCAR.exe -x -v -g -i -n -R E:\usr\sap\J2E\SYS\exe\run -f D:\j2eecd_sp3_os1_inst_indos_ind_630-j2ee-cd\SCS\NT\I386\SCS.SAR Symptom: Error when getting SAPinst archive from CD MUT Execution of the command "C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/1/sapinst_exe /S APCAR.exe '-x' '-v' '-g' '-i' '-n' '-R' 'E:\usr\sap\J2E\SYS\exe\run' '-f' 'D:/j2eecd_sp3_os1_inst_indos_ind_630-j2ee-cd/SCS/NT/I386/SCS.SAR,'" finished with return code <rc>. 1 Check whether you can access the archive by entering the command in the command line (the command below is an example; for the exact command, see the log file or message): C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\sapinst_exe \SA PCAR.exe -t -f D:\j2ee-cd_sp3_os1_inst_indos_ind_630-j2eecd\SCS\NT\I386\SCS.SAR This command attempts to list the contents of the archive. The system gives you additional information on the archive and the state of the archive. 2 Search the installation log to find out when the program SAPCAR.exe was called. The specific log file of this call is specified before the program is called. You can find entries such as the following: Output of C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/1/sapinst_exe /SAPCAR.exe is written to the log file SCS.log. Search this log file for more details on the extraction process and any other error messages. 3 Attempt to perform the extraction process manually by opening a command window and repeating the command from the log file sapinst_dev.log in the command line. Example of an entry in the SAPinst log file: January/

28 Output of C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/1/sapinst_exe /SAPCAR.exe '-x' '-v' '-g' '-i' '-n' '-R' 'E:\usr\sap\J2E\SYS\exe\run' '-f' 'D:/j2eecd_sp3_os1_inst_indos_ind_630-j2ee-cd/SCS/NT/I386/SCS.SAR,': Copy the input to the command line: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\sapinst_exe \SA PCAR.exe -x -v -g -i -n -R E:\usr\sap\J2E\SYS\exe\run -f D:\j2eecd_sp3_os1_inst_indos_ind_630-j2ee-cd\SCS\NT\I386\SCS.SAR Symptom: Cannot access archive files on installation CD MUT Execution of the command "<exedir>/sapinst_exe.<nr1>.<nr2>/sapcar.exe '-x' '-v' '-g' '-i' '-n' '- R' '<inst.dir>/install' '-f' '<cd-drive>/<dir>/<archive>.sar,'" finished with return code <rc>. 1. Check whether you can access the CD at the operating system level. Attempt to execute the specified command with the specified file manually. Use the operating system user that started SAPinst. If this does not work, then there may be access errors on the CD, or the CD is not available. 2. Check whether you can remove the error at the operating system level. Pay particular attention to the return code of the command. This code may be generated by the operating system and can be helpful in finding additional information. On Windows, you can use the command net helpmsg <nr>, for example, to display additional information on the specified code. On Unix, the file errno.h contains a list of the system error numbers. The file with the error code is located in a directory under /usr/include. Find this file with the command find /usr/include -name errno.h. This command may find more than one file. Search all of these files for relevant information. J2EE Environment Symptom: Cannot start J2EE instance CJS J2EE engine JC<nr> of SAP system J2E did not come up after 800 seconds: giving up Use the Management Console (on Windows) or startsap as user <sid>adm in 28 January/2004

29 the command line (on Unix) to start the instance. 2. If this does not work, select Process List in the Microsoft Management Console (on Windows) for the instance that cannot be started. You can see the process jcontrol.exe. 3. Open the context menu and choose Developer Trace. 4. Search this file for information about the failed J2EE start Check the log files <instance-dir>/work/dev_jcontrol (for example, E:\usr\sap\J2E\JC00\work\dev_jcontrol on Windows) and <instancedir>/work\dev_jcmon (for example, E:\usr\sap\J2E\JC00\work\dev_jcmon on Windows) for any other reasons why the J2EE instance could not be started. 2. Other sources of information are the log file dev_bootstrap under work, and the vm_* files, particularly the file jvm_server<nr>.out. For example, if you find the following entry (or similar), you have probably installed an incorrect Java version: *** ERROR => invalid vm detection, please have a look the files [jstartxxi.c 1008] - java command ["C:\j2sdk1.4.2_01\bin\java.exe" -cp. JdkDetection_2376 >./JdkDetection_2376.txt 2>&1] - output file [./JdkDetection_2376.txt] - java file [./JdkDetection_2376.java] - class file [JdkDetection_2376] - used vm type [-server] - used vm type [] *** ERROR => can't get JDK information (rc=-1) [jstartxxi.c 1063] *** ERROR => node [bootstrap] not found [jstartxx.c 1304] The Java installation used by the Engine is specified in the file <instancedir>/j2ee/cluster/instance.properties. Here, search for the parameter ID<nr>.JavaPath and check its value to see which installed Java environment is being used by the J2EE Engine. Symptom: Invalid JDK directory Error message: Directory <jdk-directory> is not valid a JDK directory: JDK version is < version number 1> is lower then the minimum version <version-number 2>. January/

30 Cause No correctly installed Java Runtime found, or the minimum required Java version is missing. The dialog informs you which version you need to install and where you can find it. Install the required JDK version. Also consult the installation guide. You can download the current Java version for many platforms from If you cannot find the Java environment for your platform here, contact your system partner. Symptom: Java environment set incorrectly CJS Context error. DIAGNOSIS: The context parameter JAVA_HOME is empty. SOLUTION: Check your installation. or CJS The value C:\j2sdk1.4.2_01 for context parameter JAVA_HOME is not valid. Cannot find C:\j2sdk1.4.2_01\bin\java.exe. Check your installation. The Java environment is not installed correctly on your computer. Install the Java environment again or correct the current installation. For certain platforms, you can find a description of the installation at If your platform is not listed here, contact your system partner. Symptom: Error message in installation step Create a J2EE Database in dialog Description Error message: Cannot find the default profile for the SAP system T15 at the default location '\\<central instance host>\sapmnt\<sid>\sys\profile\default.pfl'. Make sure the installation step 'Preparation of Central Instance Host' has run successfully on host <central instance host> for SAP System ID <SID>. 30 January/2004

31 No error entries in the log. You must first perform the installation step Prepare a Central Host Instance on the central instance host. Only then can you proceed with the installation. Symptom: Error in installation step Prepare Oracle Server Configuration Description In the message box, the following message, or similar, appears (the exact message text depends on the component you are installing): An error occurred during the installation of component SAP Web AS > J2EE System -> Central System -> Install a J2EE Server in Custom Mode. To get more information, press "View ". You may now cancel the installation, retry the current action or ignore the error. files are written to C:\Program Files\sapinst_instdir\WEBAS_640_J2EE_ONLY\CS\CUS. FSL Unable to create node D:\oracle\ora92\database\initJ2E.ora with type file: The system cannot find the path specified. During the installation, the wrong Database Home Directory was selected under J2EE Database Parameters. This situation can occur if an old database installation has not been uninstalled, or has been uninstalled incompletely, or if the registry has not been cleaned up properly. In this case, clean up the registry or remove the old database components. Resume the installation and select the current Database Home Directory. Database Symptom: Database software not installed Oracle software not installed. Install Oracle software first. January/

32 Cause You selected a database in the dialog. However, the existence of the database software is not checked until a few steps later (including the step where the CD for the IGS software is specified). Install the database software as described in the installation guide and repeat the installation. Symptom: Incorrect version of database software installed CJS SQL statement or script failed. DIAGNOSIS: Error message: ORA-12560: TNS: protocol adapter error ORA-12560: TNS: protocol adapter error. SOLUTION: See ora_sql_results.log and the Oracle documentation for details. Cause The error does not occur until the installation step Oracle Database Build. There is no clear indication that the database software has an incorrect version. Install the correct version of the database software as specified in the installation guide. 32 January/2004

33 6. Technical Information This chapter provides information on: Extraction of the SAPinst Executables and Required Libraries Searching for a Suitable Java Environment Overview of the Most Important SAPinst Files Important XML Files Files External Support Tools Back to Contents January/

34 6.1 Extraction of the SAPinst Executables and Required Libraries SAPinst is shipped as a self-extracting package (known as a self-extractor or SFX) on SAP CDs. If you start this program (for example, <CD>:\SAPINST\NT\I386\sapinst.exe on Windows), the required executables and libraries (not the SAPinst control files and XML files) are extracted to a file system on the computer. The location of these executable files and libraries in the file system is defined as follows: On Unix and NT, the environment variables TEMP, TMP, and TMPDIR are checked one by one to see if they exist and point to a directory. If none of these variables are set, the variable %SystemRoot% is used on Windows, and the directory /tmp is used on Unix. In this directory, a subdirectory is created with the name sapinst_exe.<coded_timestamp>. The exact amount of space needed for this directory depends on the platform, but is generally between 100 and 200 MB. The SFX can process the following command line options: -trace <tracefile>: An SFX trace is written to the file <tracefile>. If this file is not defined, you can find the file dev_trace in the temporary directory (see below). <tracefile> can also be set to '-'; in this case, the trace is written to stdout (on Unix only). -extract <existing dir>: Extract executables to <existing dir>. If no directory is specified with this command line option, the defaults described above are used. Back to Chapter Overview Back to Contents 6.2 Searching for a Suitable Java Environment SAPinst uses the following schema to search for a suitable Java version. This is an installed Java version that meets a minimum release requirement (to display the version, use java - version): (1) The environment variable JAVA_HOME is checked. (2) The environment variable PATH (Windows) or path (Unix) is checked. (3) Windows only: The registry is read (the entry HKEY_LOCAL_MACHINE/Software/JavaSoft/Java Runtime Environment is checked). The Java version is used that meets the requirements for the SAPinst installation. If no version can be found automatically, you must specify the version in a SAPinst dialog. SAPinst then checks the version information in the output of java -version and accepts the directory only if the defined requirements are met. Back to Chapter Overview Back to Contents 34 January/2004

35 6.3 Overview of the Most Important SAPinst Files Files Not Specific to an Operating System *.xml: SAPinst command files *.dtd: DTD files that correspond to the command files *.log: files written during the installation *.jar: Java archive files (particularly important for the Java-based SAPinst GUI) Unix-Specific Files *.sl (HP-UX) / *.o (IBM) / *.so (other Unix variants): Shared libraries *.sh: Unix shell scripts Windows-Specific Files *.dll: Dynamic Link Libraries (shared libraries) *.cmd: Windows command files Back to Chapter Overview Back to Contents 6.4 Important XML Files The SAPinst command files determine how SAPinst performs the installation of the SAP System. All control flows, parameters, and other information are stored in XML documents. These are the most important documents and their contents. XML Document control.xml keydb.xml messages.xml dialog.xml packages.xml Contents Instructions for controlling the installation of SAP components Table containers for installation parameters. When you run SAPinst for the first time, the delivered default keydb.xml file is copied to keydb.1.xml. If you run SAPinst several times in your installation directory, the system copies keydb.xml to keydb.<no>.xml. However, keydb.1.xml always remains the original default keydb.xml delivered by SAP. Mapping of message IDs to message texts Description of the dialog form Required label pattern for CD ROM January/