SAP Solution Manager 7.

1 SP05

Outside Discovery
User Guide
Troubleshooting Guide

Version 1.1 - March 2012

OUTSIDE DISCOVERY
USER GUIDE

Typographic Conventions Icons

Type Style Represents Icon Meaning
Example Words or characters quoted Caution
Text from the screen. These
include field names, screen Example
titles, pushbuttons labels,
menu names, menu paths,
Note
and menu options.
Cross-references to other Recommendation
documentation.
Example Syntax
Emphasized words or
text phrases in body text, graphic
titles, and table titles.
EXAMPLE Technical names of system
TEXT objects. These include report
names, program names,
transaction codes, table
names, and key concepts of
a programming language
when they are surrounded
by body text, for example,
SELECT and INCLUDE.
Example Output on the screen. This
text includes file and directory
names and their paths,
messages, names of
variables and parameters,
source text, and names of
installation, upgrade and
database tools.
Example Exact user entry. These are
text words or characters that you
enter in the system exactly
as they appear in the
documentation.
<Example Variable user entry. Angle
text> brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.
EXAMPLE Keys on the keyboard, for
TEXT example, F2 or ENTER.
 OUTSIDE DISCOVERY
USER GUIDE

Contents
1 Overview .............................................................................................................................................. 5
2 Pre-requisites ...................................................................................................................................... 6
2.1 SAPHostAgent .............................................................................................................................. 6
2.1.1 SAPHostAgent Version ............................................................................................................ 6
2.1.2 SAPHostAgent Porttype ........................................................................................................... 7
2.1.3 SAPHostAgent Trusted Connection ......................................................................................... 8
2.2 Diagnostics Agent ......................................................................................................................... 8
3 User Guide ........................................................................................................................................... 9
3.1 Host Discovery .............................................................................................................................. 9
3.1.1 Landscape Browser / Technical System Editor View ................................................................ 9
3.1.2 Host Discovery Process Status .............................................................................................. 11
3.1.3 Physical Host Data ................................................................................................................. 11
3.1.4 Logical Host Data ................................................................................................................... 12
3.2 Database Discovery .................................................................................................................... 13
3.2.1 Landscape Browser ............................................................................................................... 13
3.3 Microsoft IIS Discovery............................................................................................................... 14
3.3.1 Landscape Browser / Technical System Editor View .............................................................. 14
4 Support Tools .................................................................................................................................... 16
4.1 Landscape browser .................................................................................................................... 16
4.1.1 Landscape Tab Hosts View ............................................................................................... 16
4.1.2 Administration Tab Logs and Traces View ......................................................................... 16
4.2 Diagnostics Agent Administration ............................................................................................. 18
4.2.1 Agent Error Monitoring Tab .................................................................................................... 18
4.2.2 Agent Log Viewer ................................................................................................................... 18
4.3 Diagnostics Agent Support ........................................................................................................ 20
4.3.1 SMD Server Analysis View..................................................................................................... 20
4.3.2 Diagnostics Agent Runtime View ........................................................................................... 21
5 Troubleshooting Guide ..................................................................................................................... 22
5.1 Troubleshooting Roadmap ......................................................................................................... 22
Outside Discovery 4
User Guide SolMan 7.1 SP05

5.2 Common Issues .......................................................................................................................... 23

5.2.1 Diagnostics agent is not connected to solution manager server ............................................. 23
5.2.2 An exception occurred during the execution of the function
'FM_DIAGLS_PUSH_PHYSICAL_HOST' ............................................................................................ 23
5.2.3 Exception while parsing SapOsCol DataNo data allowed here ........................................... 24
5.2.4 Exception while parsing SapOsCol DataParsing an empty source ..................................... 24
5.2.5 Failed to open HW file ............................................................................................................ 24
5.2.6 CIM Request EnumerateInstances for classes Application failed: : Provider load failure .... 25
5.2.7 GetObject ADSi Object IIS://localhost/W3SVC failed: Error : Access is denied ...................... 25
5.2.8 java.net.SocketTimeoutException: Read timed out ................................................................ 25
5.2.9 Timeout waiting for saposcol answer ..................................................................................... 26
5.2.10 Error to perform http request cause Socket output stream shutdown by peer .................... 26
5.2.11 Unable to open connection to host "localhost:1128". The host is down or unavailable ........... 26
5.2.12 Cannot established a trusted connection to SAP host agent webservice................................ 26
5.2.13 Webservice port type not enabled .......................................................................................... 27
5.2.14 Webservice invocation error occurred Generic error .......................................................... 27
5.2.15 Check prerequisites failed on Software Component Version .................................................. 28

SAP AG 2008
Outside Discovery 5
User Guide SolMan 7.1 SP05

1 Overview
The purpose of the Outside Discovery is to automatically discover, collect and send information related the monitored
system to Solution Manager.
As of Solution Manager 7.1 SP06, Outside Discovery is able to collect following information:
Host: data related to Physical Host and Virtual Host (like Operating System type, version, cpu, memory
)
Database: data related to installed database (like database type, version, )
Microsoft Internet Information Service: data related to installed instance of Microsoft IIS (like .Net
version, IIS Applications, IIS Sites)
The Outside Discovery is packaged inside the Diagnostics Agent within the Agelet called DCC (agelet archive:
sap.com~tc~smd~agent~application~e2edcc.ear).
The Outside Discovery process relies on the SAPHostAgent Web Service process for collecting all raw technical
data related to monitored system.
The process is ready to push as soon as the running Diagnostics Agent gets connected to a Solution Manager
system. Data are:
o Collected from the SAPHostAgent Web Service.
o Filtered and cached on Agelet side.
o Sent to JAVA Bean Controller (SMD_DataEnrichment_Registrator) through P4 Connection.
o Stored in LMDB database (AI_DIAGSNOTICS_DATA_ENRICHMENT package).

SAP AG 2008
Outside Discovery 6
User Guide SolMan 7.1 SP05

2 Pre-requisites
Even if the Outside Discovery process itself do not require any specific setup in order to run some pre-requisites are
necessary.
Pre-requisites for the SAPHostAgent and Diagnostic Agent are detailed in the Solution Manager Guided Procedure:
SAP Solution Manager Configuration System Preparation Step 6.3: Prepare Outside Discovery
Implementation Guides (IMG) are available in Solution Manager.
Topic IMG ID

Diagnostics Agent Installation Guide SMCONF_LSC_DIAGAGT (SIMG)

SAP Host Agent Installation Guide SMCONF_LSC_HOSTAGT (SIMG)

SAP Host Agent Trusted Connection SMCONF_LSC_CREDENT (SIMG)

2.1 SAPHostAgent
All data discovered by the Outside Discovery process are collected from the SAPHostAgent installed on the physical
host.

2.1.1 SAPHostAgent Version

The SAPHostAgent should have the correct version the minimum required version is:

Version field Required version

Kernel Version 720

Patch Number See SAP Note 1365123

How to check the version of SAPHostAgent:

Using Self-Check Application:

A specific self-check for the SAPHostAgent version is implemented in within the Self-Check Framework. This
check verify that the current SAPHostAgent Patch Number is higher than the required Path Number defined in
following configuration:

SAP AG 2008
Outside Discovery 7
User Guide SolMan 7.1 SP05

Using Operating System command:

o Open directory where SAPHostAgent is installed (example: on Windows system C:\Program
Files\SAP\hostctrl\exe).
o Run following shell command:
saphostctrl.exe -function ExecuteOperation -name versioninfo
o Here is the output from the above command:

2.1.2 SAPHostAgent Porttype

The SAPHostAgent provides a Web Service access to some sub-services also called Porttype. The SAPHostAgent
should be configured in order expose those Porttype to the Web Service.
The configuration of those available services is defined in the following file host_profile located under of the binary
directory of the SAPHostAgent.
Following porttypes are mandatory for the Outside Discovery process:
o SAPHostControl
o SAPOscol

Example of host_profile file on Windows system:

SAP AG 2008
Outside Discovery 8
User Guide SolMan 7.1 SP05

2.1.3 SAPHostAgent Trusted Connection

Some methods within the SAPHostAgent are restricted. In order to allow the Diagnostics Agent to access protected
Web Service from the SAPHostAgent a trusted connection is necessary between the 2 parties.
Trusted connection is defined in the following file host_profile.
The Diagnostics Agent user should be entered in the specific field service/admin_users.

Example of host_profile file on Windows system:

2.2 Diagnostics Agent

In order to start the Outside Discovery process, the Diagnostics Agent should be connected to the Solution Manager
System:
o Either during the Diagnostics Agent installation procedure.
o Either using the following step in the System Preparation Guided Procedure:

SAP Solution Manager Configuration System Preparation Step 6.4: Connect Diagnostics Agents

SAP AG 2008
Outside Discovery 9
User Guide SolMan 7.1 SP05

3 User Guide
As soon as the Diagnostics Agent gets connected to a Solution Manager system, the Outside discovery agelet
starts running.
The Outside Discovery Agelet contains 3 different jobs:
Host Discovery: this job is retrieving data from physical and virtual host on the monitored system.
Database Discovery: this job is retrieving data for all installed database on the monitored host.
IIS Discovery: this job is retrieving data for installed Microsoft IIS on monitored host.

The Host Discovery process is the master process of the Outside Discovery Agelet. Database
Discovery and IIS Discovery processes are only started if Host Discovery has been able to
successfully push and create host entity on Solution Manager.

3.1 Host Discovery

The Host Discovery (aka PhysicalHostPushJob) is the master process and gets started first.
The Host Discovery is retrieving following data from the monitored system:
Physical Host this includes:
o Operating System Information
o Virtualized Solution used.
All Logical hosts defined on the monitored Physical Host.

3.1.1 Landscape Browser / Technical System Editor View

All hosts created by the Outside Discovery process are available in the Landscape Browser and the Technical
System Editor.

In the following example, Outside Discovery retrieved following information from a Diagnostics Agent installed
on physical host vml2262:
Landscape browser:

SAP AG 2008
Outside Discovery 10
User Guide SolMan 7.1 SP05

Physical Host vml2262 is using a Virtualization solution.

o Its Operating System is SUSE Linux Enterprise Server 10 (x86_64)
o its Full Qualify Domain Name is vml2262.wdf.sap.corp and its IP Address is 10.66.51.11
Logical Host ldai1sd7 is defined within this physical Host:
o Its Operating System is SUSE Linux Enterprise Server 10 (x86_64)
o its Full Qualify Domain Name is ldai1sd7.wdf.sap.corp and its IP Address is 10.66.51.53
More detailed data are available in the Technical System Editor like Alternative Hostnames, CPU Type.

Complete list of data is available using the Details button:

SAP AG 2008
Outside Discovery 11
User Guide SolMan 7.1 SP05

3.1.2 Host Discovery Process Status

The status of the Host Discovery Process is displayed within the Landscape Browser (column Host Status).

Here is a view of the Host Discovery Process running on Physical Host vml2262

Host Discovery run successfully for physical host vml2262

Version of the SAPHostAgent is Kernel version 720 and Patch Number 80.

3.1.3 Physical Host Data

Following data are retrieved for the Physical Host:
Physical Host fields Description

Name Short name of the physical host

Full Host Name Full Host name of the physical host
IP Address IP Address

Virtualized Solution Identify if the physical host is running inside a virtualized

solution.

List of fields retrieved from the monitored host:

Operating System data Example

OpSysUname Windows NT
OpSys WINDOWS_X86_32
OpSysRelease 5.2

SAP AG 2008
Outside Discovery 12
User Guide SolMan 7.1 SP05

OsSysBits 32
OpSysCategory Windows NT
OpSysReleaseName Windows NT 5.2
Manufacturer PC Vendor
PhysicalRAMinMB 3904
VirtualRAMinMB 12276
NumberofCPUs 4
CPURate 2799
CPUCache
CPUType Intel 801586 (Mod 2 Step 9)

3.1.4 Logical Host Data

The Outside Discovery process is retrieving all Logical Hosts from the installed SAP Product Instance: SAP J2EE
Engine, Diagnostics Agent, etc
Logical Host fields Description

Name Short name of the logical host

Full Host Name Full Host name of the logical host
IP Address IP Address

The Logical Host inherits from the same Operating System data as its Physical Host.

Logical Host for SAP Instances

Logical Hosts are retrieved from the SAPHostAgent which reads the SAP Profile. If the Full Qualified Domain
Name is not reported correctly then the property SAPLOCALHOSTFULL=<FQDN> in the SAP Profile should be
modified manually in order to match your network configuration.

Logical Host for non-SAP Instances

For non-SAP Instances, Logical Hosts are retrieved from the Diagnostics Agent.
This means installing a Diagnostics Agent on the Logical Host is necessary in order to get the logical host reported
correctly to LMDB by Outside Discovery. This is usually part of the installation when enabling the monitoring
rd
capabilities of the 3 Party Component.
The important point is that the host, FQDN and IP should be the one defined for the Logical Host.

SAP AG 2008
Outside Discovery 13
User Guide SolMan 7.1 SP05

3.2 Database Discovery

Database Discovery (aka DatabaseInfoPushJob) is started only after a successful push of the Host Discovery
process.
Database Discovery is retrieving following data from the monitored system:
Database List installed on the monitored system.
Database Type, Name and additional properties like vendor, version.

3.2.1 Landscape Browser

All Database instances created by the Outside Discovery process are available in the Landscape Browser.

Database in Landscape Browser

SAP AG 2008
Outside Discovery 14
User Guide SolMan 7.1 SP05

3.3 Microsoft IIS Discovery

IIS Discovery (aka IISInfoPushJob) is started only after a successful push of the Host Discovery process.
IIS Discovery is only running on Windows Operating System. The process is stopped if no IIS instance is found on
the monitored system.
IIS Discovery is retrieving following data from the monitored system:
IIS instance automatically created in LMDB
IIS version (supported version are IIS 6 and IIS 7)
All Installed .Net versions
All IIS Applications and IIS Pools

3.3.1 Landscape Browser / Technical System Editor View

All IIS instances created by the Outside Discovery process are available in the Landscape Browser and the
Technical System Editor.

In the Landscape Browser you can search for all IIS instances

SAP AG 2008
Outside Discovery 15
User Guide SolMan 7.1 SP05

IIS Instance overview in the Technical System Editor

MSIIS Application view:

SAP AG 2008
Outside Discovery 16
User Guide SolMan 7.1 SP05

4 Support Tools
Different tools are available in Solution Manager in order to identify problems during the Outside Discovery process.

4.1 Landscape browser

4.1.1 Landscape Tab Hosts View
As already seen in section 3.1.2, Landscape Browser is showing the status of the Host Discovery process.
Any error during the host discovery process is reported in the Host Status Technical System Status section
under the Application area Data Enrichment.

Example of error occurring during Host discovery process of Physical Host nced60165205a:
SAPHostAgent is too old Upgrade is necessary.

4.1.2 Administration Tab Logs and Traces View

Additional logs are available in the Logs and Traces view of the Landscape Browser. Logs are available for each
discovery jobs using following Search pattern:

Discovery job Search Pattern Description

Host Discovery Push Host <hostname> Search pattern for Host Discovery job on specific
hostname.

Database Discovery Push Database <SID> at <hostname> of Search pattern for Database discovery job on specific
type <database type> hostname.

IIS Discovery Push MSIIS IIS.SystemHome.<hostname> Search pattern for IIS discovery job on specific
hostname.

SAP AG 2008
Outside Discovery 17
User Guide SolMan 7.1 SP05

Example of Logs and Traces view for all discovery jobs:

Enter Search query according to pattern table here all discovery jobs PUSH*
Make sure current users is switch off

Additional details are available in the Log Details view:

The level of details (Error, Warning, Info and Debug) is managed in Administration Tab Configuration Log
Configuration.

SAP AG 2008
Outside Discovery 18
User Guide SolMan 7.1 SP05

4.2 Diagnostics Agent Administration

All logs written by the Outside Discovery Agelet are available through the SMD Agent Administration UI.

4.2.1 Agent Error Monitoring Tab

This view shows only exceptions reported by all SMD Agents.

Following locations are available for filtering the Outside Discovery jobs:

Discovery job Location

Host Discovery com.sap.smd.e2edcc.host

Database Discovery com.sap.smd.e2edcc.db

IIS Discovery com.sap.smd.e2edcc.iis

4.2.2 Agent Log Viewer

The Agent Log Viewer can be used to check raw data retrieved from the SAPHostAgent by the Discovery job.
Each discovery job has its own log file. In order to get the most detailed report of extracted data, the Log Level should
be switched to debug.

SAP AG 2008
Outside Discovery 19
User Guide SolMan 7.1 SP05

Available log files for Outside Discovery Jobs:

Discovery job Log file

Host Discovery e2edcc_host.*.log

Database Discovery e2edcc_db.*.log
IIS Discovery e2edcc_iis.*.log

Example of e2edcc_host.*.log file which contains detailed process information

SAP AG 2008
Outside Discovery 20
User Guide SolMan 7.1 SP05

4.3 Diagnostics Agent Support

The Diagnostics Agent Support Tool is available to check:
JAVA Bean Controller registration - SMD_DataEnrichment_Registrator.
Discovery jobs statistics.

4.3.1 SMD Server Analysis View

In this view section SMD JNDI objects auto-registered we can check that the JAVA Bean Controller is registered
correctly.

The JAVA Bean Controller is used to controlled callback performed by each Outside Discovery Agelet.

If the object is not registered correctly, use the objects Reinitialization button to re-create all objects.

SAP AG 2008
Outside Discovery 21
User Guide SolMan 7.1 SP05

4.3.2 Diagnostics Agent Runtime View

The Diagnostics Agent Runtime view is used to get statistics about the Outside Discovery Jobs.
You have to select the Diagnostics Agent and use the Agent Monitoring Tab.

This view shows:

Outside Discovery jobs running on the Diagnostics Agent
Average execution time per jobs
Total number of execution
Last execution date
Number of Exceptions
Number of Timeouts exceptions.

SAP AG 2008
Outside Discovery
User Guide SolMan 7.1 SP05
5 Troubleshooting Guide
5.1 Troubleshooting Roadmap
In order to troubleshoot a specific Outside Discovery process, following roadmap may be used this applies to any
discovery job running on a specific host.
Tool
Landscape Browser / Host View
Landscape Browser / Logs and
Trace view
Diagnostics Agent Administration /
Agent Error Monitoring Tab
Diagnostics Agent Administration /
Agent Log Viewer
Once the problem has been identified, please check in the Common Issues (section 5.2) for detailed description of the
root cause and possible solution.
If the problem is not listed in the Common Issues section, please create a Message attaching the logs file from the
Diagnostics Agent.
SAP AG 2008
22
Section
Check
reference
Check Host status for the Application Area Data
Enrichment.
4.1.1
The status should be green as the Host
Discovery process is the master process.
Use following search string push*<hostname>
to check logs for each discovery job.
4.1.2
If Exception is found then the problem is located
in the persist process.
Select relevant Diagnostics Agent
4.2.1
If an exception is found then the problem is
located in the discovery process.
Select relevant Diagnostics Agent set relevant
log file to debug
4.2.2
The log file should display all actions related to
the discovery process:
Outside Discovery 23
User Guide SolMan 7.1 SP05

5.2 Common Issues

5.2.1 Diagnostics agent is not connected to solution manager server

Diagnostics agent is not connected to solution manager server, connection status: CONNECTING
Diagnostics agent is not connected to solution manager server, connection status:
LAST_REGISTRATION_ON_ERROR

Description this message is displayed if:

Diagnostics Agent is not yet connected to the Solution Manager system.
o Please make sure the Agent is starting correctly and is connected to a Solution
Manager.
JAVA Bean controller SMD_DataEnrichment_Registrator is not available.
o It may happen during deployment of new LM_SERVICE that the JAVA Bean
Controller SMD_DataEnrichment_Registrator is not correctly registered
please refer to section 4.3.1 for instruction on how to reinitialize JAVA Bean
Controller.

5.2.2 An exception occurred during the execution of the function

'FM_DIAGLS_PUSH_PHYSICAL_HOST'

java.rmi.RemoteException:RfcExecutionException; nested exception is:

com.sap.sup.admin.abap.rfc.exception.RfcExecutionException:An exception occured during the execution of the
function 'FM_DIAGLS_PUSH_PHYSICAL_HOST': DBIF_RTAB_SQL_ERROR > com.sap.mw.jco.JCO$Exception:SQL error
-964 when accessing table VBMOD. <MiddlewareJRfc.java:516:g

Description an error occurs during the communication between the Java Bean Controller and the
persistence Function Module in ABAP (package AI_DIAGNOSTICS_DATA_ENRICHMENT).
This is a global exception from the AI_DIAGNOSTICS_DATA_ENTICHMENT package and
should be resolved on Solution Manager ABAP stack.

Additional Check SOLMANDIAG destination between SAP J2EE Engine and ABAP stack.
Checks
Check ST22 dumps for additional information

SAP AG 2008
Outside Discovery 24
User Guide SolMan 7.1 SP05

5.2.3 Exception while parsing SapOsCol DataNo data allowed here

com.sap.smd.agent.plugins.dcc.exc.SapOsColParsingException:Exception while parsing

SapOsCol Data. > com.sap.engine.lib.xml.parser.NestedSAXParseException:Fatal Error:
com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here(:main:,
row:951, col:1) > com.sap.engine.lib.xml.parser.ParserException:XMLParser: No data
allowed here (:main:, row:951, col:1) <XMLParser.java:2509:scanMisc()>

Description This exception occurs when the Host Discovery process is trying to parse SAPosCol data
retrieved from the SAPHostAgent.
In some situation the SAPHostAgent is partially creating the SAPosCol.xml file before
sending it to Web Service.

Solution Apply SAP Note 1587142 SAPOscol WS Returns malformed XML response.

5.2.4 Exception while parsing SapOsCol DataParsing an empty source

com.sap.smd.agent.plugins.dcc.exc.SapOsColParsingException:Exception while parsing

SapOsCol Data. > java.io.IOException:Parsing an empty source. Root element expected!
<XMLParser.java:2885:onEncodedDataReaderEOF()>

Description SAPHostAgent Web Service is returning an empty SAPosCol.xml file.

Additional SAPHostAgent log files should be analyzed in order to identify SAPHostAgent the issue.
Checks

5.2.5 Failed to open HW file

Failed to open HW file. <MimeHttpBinding.java:747:buildFaultException()>

Description This exception occurs when the SAPHostAgent process (Porttype SAPosCol) is not able to
provide the SAPosCol.xml file

Additional SAPHostAgent log files should be analyzed in order to identify SAPHostAgent exception.
Check

SAP AG 2008
Outside Discovery 25
User Guide SolMan 7.1 SP05

5.2.6 CIM Request EnumerateInstances for classes Application failed: : Provider load
failure

java.rmi.RemoteException:Webservice invocation error occured on stub

com.sap.smd.agent.wsclients.saphostcontrol.SAPHostControlStub@680a68e9; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: CIM Request EnumerateInstances for classes Application failed:
EnumerateInstances for Application failed: Provider load failure >

Description The issue is the restriction done by II 7.0 on Windows 2008 and higher while discovering IIS
Applications in WMI namespace. Additional information available at
http://learn.iis.net/page.aspx/162/managing-sites-with-iis-7039s-wmi-provider/.
You must be an administrator to connect to the Web Administration WMI namespace. This
means that you are logged in as one of the following:
The built-in Administrator account on Windows Server 2008
A member of the Administrators group and you have disabled User Account Control
(UAC)
A member of the Administrators group and UAC is enabled.

Solution Add the user sapadm to the Local Administrator Groups.

5.2.7 GetObject ADSi Object IIS://localhost/W3SVC failed: Error : Access is denied

java.rmi.RemoteException:Webservice invocation error occured on stub

com.sap.smd.agent.wsclients.saphostcontrol.SAPHostControlStub@16e3879; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: GetObject ADSi Object IIS://localhost/W3SVC failed: Error :
Access is denied.

Description SAPHostAgent user does not have authorization to access ADSi IIS object.

Solution Add the user sapadm to the Local Administrator Groups.

5.2.8 java.net.SocketTimeoutException: Read timed out

java.rmi.RemoteException:Service call exception; nested exception is:

java.net.SocketTimeoutException: Read timed out > java.net.SocketTimeoutException:Read timed out
<SocketInputStream.java:-2:socketRead0()>

Description A timeout exception occurred while accessing one of the SAPHostAgent Web Service
methods.

Additional SAPHostAgent log files should be analyzed in order to identify SAPHostAgent performance or read

SAP AG 2008
Outside Discovery 26
User Guide SolMan 7.1 SP05

check issue.

5.2.9 Timeout waiting for saposcol answer

Timeout waiting for saposcol answer. <MimeHttpBinding.java:747:buildFaultException()>

Description A timeout exception occurred while accessing the SAPHostAgent Web Service (Porttype
SAPosCol)

Additional SAPHostAgent log files should be analyzed in order to identify SAPHostAgent performance or read
check issue.

5.2.10 Error to perform http request cause Socket output stream shutdown by peer

java.net.SocketException: Socket output stream shutdown by peer. >

java.net.SocketException:Socket output stream shutdown by peer. <Response.java:481:initialize()>

Description The SAPHostAgent has closed the communication channel with Diagnostics Agent.

Additional SAPHostAgent log files should be analyzed in order to identify SAPHostAgent performance or read
check issue.

5.2.11 Unable to open connection to host "localhost:1128". The host is down or

unavailable

java.rmi.RemoteException:Error to perform http request cause by java.io.IOException: Unable to

open connection to host "localhost:1128". The host is down or unavailable...;

Description The SAPHostAgent or port 1128 is not accessible.

Additional Please check that SAPHostAgent is running correctly.

check

5.2.12 Cannot established a trusted connection to SAP host agent webservice

Cannot established a trusted connection to SAP host agent webservice. (SAP Host agent version
installed doesn't support trusted connection method)
<SAPHostAgentTrustedConnectionConfigurator.java:117:setupTrustedConnection()>

Description SAPHostAgent do not support trusted connection.

SAP AG 2008
Outside Discovery 27
User Guide SolMan 7.1 SP05

Required Upgrade SAPHostAgent to latest version.

Action

Cannot established a trusted connection to SAP host agent webservice. (Cannot find the file
/usr/sap/hostctrl/work/sapcontrol_logon/logon5.)
Cause: It means that the SMD Diagnostics agent does not have enough permissions to read the folder
"/usr/sap/hostctrl/work/sapcontrol_logon/logon5"

Description The Diagnostics Agent does not have enough permissions to read the folder
"/usr/sap/hostctrl/work/sapcontrol_logon/logon5"

Required Change the agent OS user so that it can read the folder.
Action

5.2.13 Webservice port type not enabled

Webservice port type not enabled <MimeHttpBinding.java:747:buildFaultException()>

Description One of the service Porttype of the SAPHostAgent is not available or not setup correctly.

Additional Check Porttype configuration (see section 2.1.2).

Check

5.2.14 Webservice invocation error occurred Generic error

java.rmi.RemoteException:Webservice invocation error occured on stub

com.sap.smd.agent.wsclients.saphostcontrol.SAPHostControlStub@46b8c77f; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: Generic error. Check the trace file C:\Program
Files\SAP\hostctrl\work\dev_sapdbctrl for more details. Increasing the trace level may provide further
details. > javax.xml.rpc.soap.SOAPFaultException:Generic error. Check the trace file C:\Program
Files\SAP\hostctrl\work\dev_sapdbctrl for more details. Increas

Description Generic exception in SAPHostAgent process

Additional SAPHostAgent log files should be analyzed in order to identify SAPHostAgent performance or read
Check issue.

SAP AG 2008
Outside Discovery 28
User Guide SolMan 7.1 SP05

5.2.15 Check prerequisites failed on Software Component Version

When running the Managed System Wizard, the following error is displayed:
The definition of Technical System SYS~XXX is not correct: SYS~XXX: Operating System <Any operating
system> of Host hostXXX must have at least one Software Component Version.

Description The Software Component Version of the Operating System is mandatory for some setup
steps.
This information is retrieved by the Host Outside Discovery Process. All pre-requisites action
regarding the Outside Discovery process should be completed before running the Setup.

Required In order to check that the Host Outside Discovery Process runs successfully, please check
Action the status of the host within the Landscape Browser at section 3.1.2 - Host Discovery Process
Status.

SAP AG 2008