Overview
Error code 4097 means OneIQ Pulse hit a network error while communicating with a platform endpoint, such as vCenter. It is a network problem, not a login or permissions problem. Changing the endpoint's credentials will not fix it.
What the Error Looks Like
In the OneIQ Pulse console, the endpoint shows as Red. Click Details to see the full error. It will look similar to this:
ErrorCode: 4097
Message: An error occurred while sending the request.
InnerMessages: The response ended prematurely.
The message and inner message can vary. The error code is what identifies this issue.
Common Causes
Pulse cannot reach the endpoint at all. A firewall, routing rule, DMZ or VPN is blocking traffic between the Pulse machine and the endpoint.
Pulse reaches the endpoint, but the connection is closed partway through. This usually happens during larger data requests. It is typically caused by a firewall that applies SSL inspection, intrusion prevention (IPS) or session timeouts, by a proxy, or by an endpoint service that isn't responding properly.
Step 1 — Test Connectivity to the Endpoint
On the machine running OneIQ Pulse, open a PowerShell window.
Run the following command, replacing the placeholder with the address used for the endpoint in Pulse:
Test-NetConnection -ComputerName <endpoint address> -Port 443Check the TcpTestSucceeded result:
False — the Pulse machine cannot reach the endpoint. Ask your network team to allow TCP port 443 from the Pulse machine to the endpoint. If the Pulse machine connects over a VPN or sits in a DMZ, check that it has access to the endpoint's network.
True — basic connectivity is working. Check that the address is the endpoint you intended to add, then continue to Step 2.
Step 2 — Check for Connections Being Closed
If the connectivity test succeeds but the error remains, something is closing the connection during collection.
On the Pulse machine, check the proxy settings:
netsh winhttp show proxy
If a proxy is configured, see OneIQ Pulse with a Proxy.For vCenter, confirm that Pulse can retrieve a response from the vCenter API:
curl.exe -vk https://<vCenter address>/sdk/vimServiceVersions.xmlIf there is a firewall between the Pulse machine and the endpoint, check whether it applies SSL inspection, IPS, or session or idle timeouts to HTTPS traffic. Its logs may show dropped or reset sessions from the Pulse machine at the time of the error.
Check whether any network, firewall or endpoint changes were made around the time the error started.
For vCenter, also confirm that:
the vCenter services are running and healthy. You can check this in the vCenter Management Interface on port 5480.
the vCenter appliance isn't low on disk space.
the vCenter certificate hasn't been replaced recently.
Step 3 — Remove Duplicate Endpoints
If the same endpoint has been added to Pulse twice, for example once by IP address and once by hostname, remove one of them and keep the one that uses the hostname. Two collections running against the same endpoint add unnecessary load and can contribute to timeouts.
Step 4 — Resume Collection
After fixing the cause, click Resume on the endpoint in the Pulse console, or restart the OneIQ Pulse service. Data should appear in the OneIQ Portal within about 30 minutes.
If the Issue Persists
Collect the Pulse logs from the following locations and contact OneIQ Support. Include a description of what you have already tried.
Pulse Service Logs: %windir%\ServiceProfiles\NetworkService\AppData\Local\OneIQ\OneIQ Pulse\Logs
Pulse Deputy Logs: C:\ProgramData\OneIQ\OneIQ Pulse Deputy\Logs
Pulse Console Logs: %userprofile%\AppData\Local\OneIQ\OneIQ Pulse Console\Logs
Related Articles