Troubleshooting for Empirum connector

Last updated
Save as PDF

Empirum Connector is out of support with availability of Empirum Inventory Data Provider (Migration from Empirum Connector (legacy) - Matrix42 Self-Service Help Center)

Error	Solutions
Import failed with message: Could not connect to net.tcp:// empirumserver:9100/Services/Matrix42.CoreService/CoreService. The connection attempt lasted for a time span of 00:00:01.0156510. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.22.10:9100.	Check whether the Empirum Interface Hosting Service Windows service is run on the Matrix42 Empirum server. Check that the port number of the API services in Matrix42 Empirum is identical to the settings that are defined in Matrix42 Software Asset & Service Management for the connector. In the network settings, instead of the host name, enter the IP address or FQDN of the Matrix42 Empirum server.
Import failed with message: The socket connection was interrupted. This could be caused by an error when processing your message or a receive timeout that is being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'.	Check that the encryption settings of the API services in Matrix42 Empirum are identical to the settings that are defined in Matrix42 Software Asset & Service Management for the connector.
There was no endpoint listening at net.tcp://empirumserver:9100/Services/ Matrix42.Empirum.PLF.EmpirumAPI.Service.CoreService/CoreService that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.	Check whether the correct Empirum version is defined in the location settings of the connector in Matrix42 Software Asset & Service Management.
The requested upgrade is not supported by 'net.tcp://empirumserver:9100/Services/ Matrix42.CoreService/CoreService'. This could happen because of mismatched bindings (for example, security enabled on the client and not on the server).	Check that the encryption settings of the API service in Matrix42 Empirum are identical to the settings that are defined in Matrix42 Software Asset & Service Management for the connector.