Diagnostics Agent 7. Troubleshooting SAP Solution Manager Setup. This article describes how to troubleshoot the Diagnostics Agent and provides a brief overview of the most common know issues and how to solve these. In case of Outside Discovery issues go to the section Outside Discovery. In case of connectivity issues between the Diagnostics Agent and the Solution Manager see section Connectivity. If the Diagnostics Agent is not starting at all or has a high CPU or memory consumption go to the section Troubleshooting Booting and Ressource Consumption Issues of the Diagnostics Agent. For troubleshooting the Outside Discovery identify the issue and proceed accordingly Acquiring the Log Files. But do tailor your answer to your audience. My Lifehacker colleagues choose the title blogger or journalist depending on how much theyre ready to get. For troubleshooting the Outside Discovery, check the debug log of the Outside Discovery. The logs can be downloaded as described in the SAP Note 1. Compendium In the Agent Administration application, tab Agent Log Viewer, link Log Configuration, set the levels of the log files e. Diagnostics Agent on the physical host with the issue to Debug. In case of issues with an agent node on a logical host, you need to identify the related physical host and change the log configuration of this host. Consolidate orders and maximize the return on your transportation spend with our transportation management system for freight, shipping, and logistics. UpdateStar is compatible with Windows platforms. UpdateStar has been tested to meet all of the technical requirements to be compatible with Windows 10, 8. Windows 8. Give business users anytime, anywhere insights to improve decision making with SAP BusinessObjects Business Intelligence, our BI analytics platform. Deployment Guide for Cisco HyperFlex for Virtual Server Infrastructure 2. All Flash Storage. TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/99/05/metablogapi/2553.image_420AB578.png' alt='Configure Windows Security Event Log Sizer' title='Configure Windows Security Event Log Sizer' />Test drive the latest security and management features in the Windows 10 Fall Creators Update free for 90 days. Discover new ways to deploy and manage devices, dig. Acquiring the Log Files. For troubleshooting the Outside Discovery, check the debug log of the Outside Discovery. The logs can be downloaded as described in the SAP. In case you havent noticed, we here at Lifehacker have spent the day gleefully reveling in fullblown Eclipse Madness. But now that the blessed event is behind us. Press Save in the Log Configuration dialog. Restart the Diagnostics Agent and the SAP Host Agent. Wait for 12 hour. Again under Agent Log Viewer, use the link Download logs for downloading the logs of the Diagnostics Agent. Again under Agent Log Viewer, reset the log levels to their previous values. Analysing the Log Files. As the Outside Discovery is only executed on Diagnostics Agent nodes associated to a physical host, the log files located at SMDAgentlt logical. Host log with lt logical. Host being a logical hostname can be ignored. Identify the most recent SMDAgentloge. Debug log entries. Check the log for the following entries and proceed accordingly Hostname Switching On a physical host the Outside Discovery asks the SAP Host Agent for the logical hosts of the SAP System Instances on this host and reports these to the LMDB as logical hosts, not checking whether there is actually such a logical host in the network configuration. The Solution Manager processing the Outside Discovery data then apparently stores these as logical hosts in the LMDB, even if the respective host name is not among the alternative host names. An association of a logical host that keeps switching between multiple physical hosts in the LMDB is most likely caused by a wrong network setup 1. The logical host is switching because it is defined on various physical hosts e. SAPLOCALHOST property, or by defining the logical host on various technical systems running on different physical hosts. Thus, this logical host is independently reported by the Outside Discovery of each physical host it is associated to. As this is not allowed according to SAP Note 9. If the two physical hosts are thought to be a high availability setup according to High Availability Installation Strategy System Switch Over keep in mind that the fallback host must only be created once the other host crashed by a switch over software 2. Furthermore, SAP System Instances on different physical hosts must not have be associated to the same logical host name or IP. This association is declared in the profiles of the SAP System Instances and is not related to the existence of configured network addresses. Ensure that SAP System Instances on different physical hosts have different logical host names as claimed in the Net. Weaver installation guide 2. If there is DCCService. DCC DISABLED entries in the SMDAgentloge. Outside Discovery is disabled. To enable the Outside Discovery open the Agent Administration, go to the Application Configuration tab, click on com. SAP Host Agent Does not Provide FQDN of the Physical Host. If there is one of the following entries in the SMDAgentloge. SAP Note 9. 62. 95. Physical. Host. Push. Job Could not find hostname in Hostnames list. Using Name as fallback full hostname. Debug Physical. Host. Push. Job get. Computer. System resolve. FQDNand. IP failed Using fallback method. Debug Physical. Host. Push. Job get. Computer. System Get. First. Valid. FQDNand. IP Fallback Method. The FQDN of a Logical Host is Missing. Search the log files for the foloowing Physical. Host. Push. Job 3 SAP instances found. Physical. Host. Push. Job SAP instance 1. Physical. Host. Push. Job FQDN my host name. Physical. Host. Push. Job hostname my host name. Physical. Host. Push. Job IP address 1. Physical. Host. Push. Job SID XYZ. Physical. Host. Push. Job System number 0. Physical. Host. Push. Job adding agent node Agent. Hostname mmis. Agent. Node true, mmsaplocalhostmy host name, mmresolved. FQNmy host name. SQNmy host name, mmresolved. IP1. 0. 1. 0. 1. SMD, mmpath. InstanceusrsapSMDSMDA9. Number9. 8Here the FQDN of the SAP instance on my host name is corerct my host name. LMDB shows a different FQDN, namely my host name. FQDN of the related DIagnostics Agent node resolves to my host name. To fix this, ensure that the host name can be resolved correctly by adjusting your network settings. The Outside Discovery always prefers the FQDNs and IP addresses of the Diagnositcs Agent nodes to the information provided by the SAP instances, i. The Host Name Associated to a Database Does not Exist. Error Database. Info. Push. Job Exception calling Data. Enrichment Manager Bean. Remote. Exception Rfc. Execution. Exception nested exception is. Rfc. Execution. Exception An exception occured during the execution of the function FMDIAGLSPUSHDATABASE The Host my. Host. Name does not existnullnullnull. The log files of the Outdise Discovery contain the error message stated above, if the Outside Discovery tries to report a database installation to the LMDB which is rejected because the host name that is associated to this database is not know to the LMDB. The Database Outside Discovery can only report a database if the associated host name has been previously reported by the Host Outside Discovery. The latter only reports host names that are either the physical host name the Diagnostics Agent is installed on, a logical host name associated to an SAP System Instance, or a logical host name associated to a Diagnostics Agent node. A host name that is neither associated to a Diagnostics Agent node nor an SAP System Instance is considered as irrelevant an will not be reported to the LMDB. To fix this issue, reconfigure the managed system such that the host name is reported by the Host Outside Discovery. The Host Name Associated to a Database is Wrong. If a database instance is associated to a unintended host name in the LMDB or if the association between a database and the desired host name gets deleted automatically every once in a while, access the Outside Discovery log files as described in section Aquire the Outside Discovery Logs, search for Database. Info. Push. Job. get. Database. List and detect the dedicated database instance. You will find log entries similar to the following Database. Info. Push. Job. get. Database. List Property DatabaseInstance. NameDBX. Database. Info. Push. Job. get. Database. List Property DatabaseHostmy host name. Database. Info. Push. Job. get. Database. List Property DatabaseVendorsap. Database. Info. Push. Job. get. Database. Airtel 3G Data Card Software Free Download there. List Property DatabaseTypesap. Database. Info. Push.