No inventory gathering on device 'Device_Name' because the discovery did not find the server type
The following FlexNet Manager Suite On-Premises error can be seen in the VMWareInventory.log files:
No inventory gathering on device 'Device_Name' because the discovery did not find the server type.
This is a known issue when the Inventory Beacon is not able to verify that the VMware vCenter/Host Server has an SDK open on the target port.
The VMware vCenter/Host inventory scan goes through three processes when it is targeted: STEP 1: Discover the device information, IP to Host resolution, Host to IP resolution, and its open ports while scanning the provided list
STEP 2: Discovering the existence of a VMware SDK using the IP Address
STEP 3: Taking inventory of the vCenter/Host using credentials from the Inventory Beacon's Password Store, targeting by IP Address
The above error refers to the failure of Step 2. The best way to test if the Inventory Beacon Server has access to the VMware vCenter/Host is through a Web Browser with the following link, while having any Internet Proxies disabled (vimService.wsdl is case sensitive!):
. If you get an xml-formatted page or a login screen, then the test passed. If you get a "page not found" error, try the following to make sure it's not a firewall issue which this link should ask you for a login if it passed the firewall:
Possible causes are as following, sequenced by the most common:
A firewall is blocking the port between the vCenter/Host and the Inventory Beacon Server (above browser tests will both fail)
The target vCenter/Host does not have a SDK enabled/fully-enabled (above SDK browser test will fail)
The Local_Machine registry keys have forced policy to use an Internet Proxy, which would apply to the Inventory Beacon since it by default runs as the Local System account (above browser tests might succeed)
The current mgsipcan (Flexera's port scan tool) reported 443 as "filtered" not "open" which prevented inventory to proceed. (above browser tests will succeed).
This can be resolved by identifying which of the 4 common causes and contacting the proper internal department (e.g. Network Security, Firewall Team).
If the issue is not due to the first three issues, then it could be due to cause #4. This can be resolved by downloading the attached MGSIPScan.zip to the inventory beacon server and unzip it to the following directory: Program Files (x86)\Flexera Software\Inventory Beacon\RemoteExecution\MgsIPScan\ - overwriting the current contents.
on Oct 24, 201809:25 PM - edited on Sep 15, 202112:28 PM by tjohnson1