Diagnostics Agent Installation of Software Provisioning Manager (SWPM)

FAQ: Diagnostics Agent Installation of Software Provisioning Manager (SWPM)

We have questions regarding the installation of the Diagnostics Agent with help of Software Provisioning Manager (SWPM).

Check the following Steps:

1. General Information

If you want to install or uninstall a Diagnostics Agent with SWPM (>=) 1.0 SP3, you should use the option accessible via:

SAP Installation Master
Generic Installation Options
Diagnostics in Solution Manager
Install - Diagnostics Agent
Uninstall - Diagnostics Agent

Installations are only supported with one of the following kernels (SWPM Kernel version must match your SWPM version):

SWPM 1.0 SP3 720 Kernel, unicode, 32-bit
SWPM 1.0 SP3 720 Kernel, unicode, 64-bit
SWPM 1.0 SP3 720_EXT Kernel, unicode, 64-bit

When performing installations as described here, SWPM will ask for a kernel with following label: UC Kernel NW731. The mentioned kernels are compatible to the requested one.

In addition, the Diagnostics Agent PAM information for SWPM (>=) 1.0 SP3 must be respected. This PAM information is documented in the PAM document for SL Toolset (>=) 1.0 SP8. This PAM documentation can be accessed via: http://service.sap.com/sltoolset, Software Logistics Toolset 1.0 and PAM.

2. New Features

2.1. SWPM 1.0 SP3

Compared to the also available Diagnostics Agent Standalone Installers, this SWPM integrated installer version offers following new features and advantages:

support for Windows Server 2012
three (above mentioned) different kernels are supported
more frequent (SWPM aligned) releases
all platforms covered by one installer (where the standalone version requires an older installer version for older platforms and the latest installer version for newer platforms)

This comes at the cost of:

having two download packages instead of one (SWPM and SWPM Kernel)
having somewhat bigger download volume and installation size

Question:

You install a Diagnostics Agent with SWPM 1.0 SP3 or an earlier installer version, and you want to connect to SAP Solution Manager on HANA.

An error Message Box gets displayed saying: Make sure that the JEE engine is deployed correctly. Choose "Cancel" to modify managing configuration or "OK" to continue. If you choose to continue you will have to execute the smdsetup script later on.

On the status bar it says: Task completed with status ERROR (12)

In the sapinst_dev.log you will find entries like displayed below:

The key deploy is not register in the JNDI registry. Please make sure that the SAPJ2EE engine is deployed.

2013.08.02 12:13:08

Task completed with status ERROR (12)

2013-08-02 12:13:08

NWDiagAgentInstance.checkPrerequisiteSetup done

Answer:

Despite the reported ERROR (12), and under the assumption that all provided parameters are correct, "OK" to continue must be selected here. The installation will continue and finish correctly. The Diagnostics Agent will connect to the Solution Manager system, and it can be used.

Alternatively, you can decide to not connect to the Solution Manager system during the installation phase, and use the smdsetup script to establish the connection instead.

Question:

During the installation the installer asks for SSL Libraries.

Answer:

This should not occur in recent installers (SWPM 1.0 SP2, Standalone Installer 7.30 SP3, and respective successors). Very likely (especially in the case of SWPM), the wrong kernel archives have been provided during the installation procedure. For SWPM SPs there usually is a matching SWPM SP specific kernel version that must be used. Details are documented in SWPM Master Question: 1680045.

Question:

On SOLARIS, after entering a virtual hostname on the respective screen, SAPinst reports following error: "The host with the name is not a virtual hostname on the local host."

Answer:

If the "DEPRECATED" flag is set for the network interface, SAPinst does not detect that a hostname is bound to a local network interface. Execute 'ipconfig -a' to analyze this. Proceed in one of the following ways:

Set following environment variable prior to starting SAPinst:

IS_HOST_LOCAL_USING_STRING_COMPARE=true

Start SAPinst with the following command:

./sapinst IS_HOST_LOCAL_USING_STRING_COMPARE=true

Question:

During the installation on Windows platforms, the installer warns that a reboot is required. The message is like: "Running msiexec finished with return code 3010: The requested operation is successful. Changes will not be effective until the system is rebooted."

The sapinst_instdir*sapmmc*.log (for example: sapmmcX64u.log) holds details about files that are in use and thus could not be updated.

For example:

MSI (s) (DC:98) [time]: Product: SAP MMC SnapIn. The file C:WINDOWSsystem32sapmmc.dll is being held in use by the following process Name: mmc , Id 4200.
Info 1603. The file C:WINDOWSsystem32sapmmc.dll is being held in use. Close that application and retry.
MSI (s) (DC:98) [time]: Product: SAP MMC SnapIn. The file C:WINDOWSsystem32sapmmcms.dll is being held in use by the following process Name: mmc , Id 4200.
Info 1603. The file C:WINDOWSsystem32sapmmcms.dll is being held in use.  Close that application and retry.
MSI (s) (DC:98) [time]: Product: SAP MMC SnapIn. The file C:WINDOWSsystem32sapmmcada.dll is being held in use by the following process Name: mmc , Id 4200.
Info 1603. The file C:WINDOWSsystem32sapmmcada.dll is being held in use.  Close that application and retry.
MSI (s) (DC:98) [time]: Product: SAP MMC SnapIn. The file C:WINDOWSsystem32librfc32u.dll is being held in use by the following process Name: mmc , Id 4200.
Info 1603. The file C:WINDOWSsystem32librfc32u.dll is being held in use.  Close that application and retry.
MSI (s) (DC:98) [time]: Product: SAP MMC SnapIn. The file C:WINDOWSsystem32sapmmcdb6.dll is being held in use by the following process Name: mmc , Id 4200.
Info 1603. The file C:WINDOWSsystem32sapmmcdb6.dll is being held in use.  Close that application and retry.

Answer:

This is caused by the fact that the SAP Management Console is already installed and running on the system, during the execution of the installation procedure. Make sure that the SAP Management Console is closed before you start the installation procedure.

Question:

For example:

MSI (s) (DC:98) [time]: Product: SAP MMC SnapIn. The file C:WINDOWSsystem32librfc32u.dll is being held in use by the following process Name: sapstartsrv , Id 8200.

MSI (s) (DC:98) [time]: Product: SAP MMC SnapIn. The file C:WINDOWSsystem32librfc32u.dll is being held in use by the following process Name: sapstartsrv , Id 8400. Answer:

This situation must normally not occur. It indicates an incorrectly configured system. Application sapstartsrv should not access librfc from the system32 directory. Please open a ticket on component on BC-OP-NT.

Question:

Compared to Diagnostics Agent standalone installer 730 SP2, the 730 SP3 standalone installer and SWPM based installers, do not allow you to install Diagnostics Agents with instance number 98.

CAUTION:

The here described solution must only be used for installing Diagnostics Agents. The instance number 98 can be used for Diagnostics Agent installations, but it is also strictly reserved for these. Installing SAP (Systems, Applications, Products in Data Processing) systems that are not Diagnostics Agents, based on the here described solution and with an instance number 98, may lead to serious problems with future Lifecycle Management, Software Logistics, Upgrade and Update procedures. The here described manipulation of the installation media must be reverted or deleted, as soon as the Diagnostics Agent installation has been completed.

Answer:

Unpack the installation media SAR-file (SMD730_INST_WINDOWS_X86_64.SAR, SWPM.SAR, etc.)
Identify and open the control.xml file with an editor capable of editing XML (there should be exactly one control.xml file in the unpacked SAR-file)
In the control.xml file search for the string "98" (there should be exactly two occurrences of this string)
The line containing the two strings "98" should
Look like: var forbidden = installer.onWindows() ? ["43", "89", "98", "99"] : ["98", "99"];
Be part of a function starting with: NWInstance.isForbiddenNumber = function(num) {
Delete the two strings (include the commas) from the line: "98",
Save the control.xml
Perform the installation and specify 98 as the instance number for the Diagnostics Agent

Question:

Running the smdsetup script generates an error like the one below.

SAP Solution Manager - Diagnostics Agent - Copyright (c) 2010 SAP AG Exception in thread "main" java.lang.NoClassDefFoundError: com/sap/smd/setup/SetupMaintenance
Caused by: java.lang.ClassNotFoundException: com.sap.smd.setup.SetupMaintenance
at java.net.URLClassLoader$1.run(URLClassLoader.java:255)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:243)
at java.lang.ClassLoader.loadClass(ClassLoader.java:372)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:344)
at java.lang.ClassLoader.loadClass(ClassLoader.java:313)
Could not find the main class: com.sap.smd.setup.SetupMaintenance. Program will exit.

Answer:

This error is generated when the smdsetup script is run right after the installation, during the phase where the Diagnostics Agent binaries are being updated. The latest version of the binaries are downloaded from the Solution Manager system to which the Diagnostics Agent is connected. This is the intended behavior.

Question:

After a restart of the Diagnostics Agent the sapcpe_sapjvm_6.log file holds an error message complaining that file sapjvm_6.lst does not exist.

This error message can be found in files named like:

usrsapDAASMDA97worksapcpe_sapjvm_6.log

The complete error message will look like:

Trace level (profile): 1 *** ERROR: File-List "C:usrsapDAASYSexejvmNTAMD64sapjvm_6.1.048/sapjvm_6.lst" does not exist, 2, No such file or directory, [sapxxcpe.c:1438] parameter "all" is also not defined. Exit.

Answer:

This is the intended behavior.

The usrsapSYSexejvm directory is emptied on all platforms, as part of the installation procedure.

Question:

When installing a Diagnostics Agent implicitly as part of a NetWeaver 7.40 installation, the Diagnostics Agent gets installed with a NetWeaver 7.40 kernel. In the "SMD Agents Administration => SAP Host Agent" tab, the "SAP Host Agent kernel release" will show a value of 720 though.

Answer:

This is the intended behavior.

Question:

With SWPM (>=) 1.0 SP3 you have installed a NetWeaver Java System with version 7.1 or 7.1 Enhancement Pack 1. The Diagnostics Agent was installed with SAP JVM 5 as runtime environment.

Answer:

If a Diagnostics Agent was installed already, uninstall it. Then, install the Diagnostics Agent as described in section 1., General Information.

Question:

With installations based on a NetWeaver 7.40 kernel, and a SAP Solution Manager Managing System with version <= 7.10 SP8, the profile parameters of the Diagnostics Agent must be manually modified at the end of the installation procedure. If this is not done, communication between SAP Solution Manager and the Diagnostics Agent will not be fully operational. For example, following will not work:

SMD Agents Administration
Agents
Connected Agents
SAP Management Console
(this will not work) Kernel version info
(this will not work) Get environment

Both calls will fail with an error message containing following text pieces:

Cannot retrieve env from url
Invalid Response Code: (401) Unauthorized.

In addition: SMD Agents Administration => Agents => Connected Agents => => => Agent checks

Will produce errors on older Solution Manager systems. This problem is solved with SAP Solution Manager 7.10 SP9.

In addition: "smdsetup supportlogs" may not work, if you have decided to not connect the Diagnostics Agent to an SLD, and to not connect the Diagnostics Agent to the Solution Manager system directly. Issues with "smdsetup supportlogs" will disappear when connecting the Diagnostics Agent to a Solution Manager 7.10 SP9 or higher, using the "smdsetup managingconf" command.

This behavior also occurs with SAP SOLUTION MANAGER ON HANA, which is derived from Solution Manager 7.10 SP8.

Answer:

If a Diagnostics Agent was installed already, uninstall it. Then, install the Diagnostics Agent as described in section 1., General Information.

Update to SAP Solution Manager 7.10 SP9 or higher.

Add below line to the profile file for the Diagnostics Agent. If this is the last line in the profile file, then make sure to have a newline at the end of the line. Then execute sapcontrol RestartService. See detailed instructions below. The line that you add here must be removed again, as soon as your SAP Solution Manager Managing System is on version 7.10 SP9 or higher. service/protectedwebmethods = DEFAULT

Prerequisites:

You have logged on to the host as user adm.

On Unix/Linux:

Add mentioned line to profile file /usr/sap//SYS/profile/_SMDA_

Then execute /usr/sap//SMDA/exe/sapcontrol -prot NI_HTTP -nr -function RestartService

Example:

Modify /usr/sap/DAA/SYS/profile/DAA_SMDA97_YourHostName

Execute /usr/sap/DAA/SMDA97/exe/sapcontrol -prot NI_HTTP -nr 97 -function RestartService

On Windows: Add mentioned line to profile file :usrsapSYSprofile_SMDA_

Then execute :usrsapSMDA< Instance_Number>exesapcontrol.exe -prot PIPE -nr -function RestartService

Example:

Modify C:usrsapDAASYSprofileDAA_SMDA97_YourHostName

Execute C:usrsapDAASMDA97exesapcontrol.exe -prot PIPE -nr 97 -function RestartService

Question:

When checking (activating) the "Use SSL Connectivity" checkbox, for installations that do not use the SWPM Kernel for your SWPM version (e.g. SAP NetWeaver 7.4 installation), you will get an error Message Box with following message: Unable to create JNDI environment. Choose "Cancel" to modify managing configuration or "OK" to continue. If you choose to continue you will have to execute the smdsetup script later on.

Answer:

If a Diagnostics Agent was installed already, uninstall it. Then, install the Diagnostics Agent as described in section 1., General Information.

Question:

During the installation, when selecting one of the following (with "Use SSL connectivity" checked or unchecked):

- P4 connection via SCS message server
- Direct P4 connection via Java EE dispatcher node and when not specifying the User and Password information at "Credentials (optional)", the installer will display a Message Box with following error message: An error occurred while processing option Solution Manager Diagnostics Agent > SAP Systems > Standalone Engines > Diagnostics agent in SAP Solution Manager > Diagnostics Agent( Last error reported by the step: TypeError: out has no properties (in script NW_DiagnosticsAgent|ind|ind|ind|ind, line 103856: ???)).

Answer:

When using the mentioned connections, user credentials must be specified.