FNMS SAP Agent synchronisation with Inventory Beacon server

[#1]

Summary

This article covers why you may not be able to connect or reach your SAP system

Symptoms

We are having trouble synchronising a few SAP servers with the FNMS agent installed back to the Beacon server.

A manual attempt at synchronisation is failing on some servers. A scheduled overnight run had been issued.

Can you please advise what information we can provide to help you analyse and help resolve?

2017-01-12 12:21:29,180 [INFO ] Connecting to system AS5/00/888
2017-01-12 12:21:31,462 [ERROR]
============================================================

2017-01-12 12:21:31,462 [ERROR] An error has occurred in the SAP Inventory Agent:
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner 'server.sap.net:3300' not reached
TIME Thu Jan 12 12:21:31 2017
RELEASE 720
COMPONENT NI (network interface)
VERSION 40
RC -10
MODULE nixxi.cpp
LINE 3285
DETAIL NiPConnect2: 10.10.10.99:3300
SYSTEM CALL connect
ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER 2

SAP.Middleware.Connector.RfcCommunicationException:
LOCATION CPIC (TCP/IP) on local host with Unicode

at SAP.Middleware.Connector.CpicConnection.ConnectAsClient(Dictionary`2 options, Boolean forRepository)
at SAP.Middleware.Connector.RfcConnection.ConnectAsClient(RfcDestination destination, Boolean forRepository)
at SAP.Middleware.Connector.RfcConnectionPool..ctor(RfcDestination destination, Boolean forRepositoryCalls)
at SAP.Middleware.Connector.RfcConnectionPool.GetPool(RfcDestination destination, Boolean forRepository, Boolean create)
at SAP.Middleware.Connector.RfcDestination.GetClient(Boolean forRepository)
at SAP.Middleware.Connector.RfcDestination.SetAttributeValues(RfcSystemAttributes attribs)
at SAP.Middleware.Connector.RfcDestination.get_SystemAttributes()
at SAPReader.SAPReader.SAPServerReader.GatherSAPInventory(SAPServerConnection server, String sapInventoryOutputFolder, String beaconUID, RFCTableList rfcTableList, DateTime consumptionEndDate, Int32 consumptionNMonth)

Resolution

First test the Telnet connection, If the Telnet test failed, it looks like it can't access the server via port 3300.

This could be a firewall issue or that the port is closed. Would you be able to ask you network admin to take a look at the firewall settings and also make sure the port is open?

These are the most common reasons for telnet to fail.