NetWorker: VMware View Refresh Fails "Dispatcher Request Timed Out"

Summary: Error fetching vCenter information for ESXi vCenter hostname: Reason Dispatcher Request timed out NetWorker

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

The NetWorker Management Console's (NMC) VMware View times out with the following error.

NetWorker Management Console Time Out Error Message
Figure 1: NetWorker Management Console Time Out Error Message 

A similar error may be observed when performing NetWorker VMware Protection (NVP) Virtual Machine (VM) backups or restores.

The NetWorker server's daemon.raw reports: 

Inventory session returned err: Inventory session status returned with a failure. 
Error: 'Failed to load inventory from 'VMWARE-HYPERVISOR-FQDN'. Failed to load Category/Tagging metadata.

Cause

  • The vCenter inventory operation is exceeding the max Java heap size (default 2 GB) on the NMC client.
  • Default timeout parameters used by NetWorker processes are exceeded.
NOTE: There are other causes for this type of issue. This KB focuses on symptoms that only seem to impact the NMC functions. Such as the VMware View refresh and NMC recovery wizard. Typically VMware backup operations are not impacted. The settings outlined in this KB may be beneficial; however, for other potential causes, see the Additional Info section.

Resolution

NetWorker Management Console Heap Size:

Increase the Java heap size of the NetWorker Management Console.

  1. Open the gconsole.jnlp file from the NMC installation folder. Default:
Windows: C:\Program Files\EMC NetWorker\Management\GST\web\gconsole.jnlp
Linux: /opt/lgtonmc/web/gconsole.jnlp
  1. The max heap setting is identifiable by -Xmx, for example:
<j2se version="1.8+"  java-vm-args="-Djava.locale.providers=COMPAT -XX:+IgnoreUnrecognizedVMOptions --add-modules=java.se.ee  -Xms256m -Xmx2048m"/>
NOTE: In this example, the max heap size is 2048m (2 GB). This means that the NMC client (host accessing the NMC) only allows up to 2 GB for the NMC's "Java(TM) Web Launcher" process. In larger environments, or when querying large amounts of data, it is possible to exceed the default 2 GB limit.
  1. Increase the max heap size to 4096m (4 GB):
<j2se version="1.8+"  java-vm-args="-Djava.locale.providers=COMPAT -XX:+IgnoreUnrecognizedVMOptions --add-modules=java.se.ee  -Xms256m -Xmx4096m"/>
  1. Save the file.
  2. Restart the NMC server service. This closes any NMC sessions which remain open:
Windows: 
net stop gstd
net start gstd
Linux: 
systemctl restart gst
  1. Relaunch the NMC.
  2. Perform a VMware View refresh and monitor for completion.
NOTE: Open Task Manager and monitor "Java(TM) Web Launcher" memory usage. If it exceeds 4 GB, wait for inventory refresh to complete before increasing heap size further.

 

Environment Variables:

Add the following two system variables on the NetWorker server:

GST_VBA_TIMEOUT=7200
NSR_HYPERVISOR_QUERY_REQUEST_TIMEOUT=3600
NOTE: If the NetWorker Management Console (NMC) server is installed on a separate host, the settings must be applied on the standalone NMC server as well.

For Windows:

Use one of the following methods to apply the recommended system variables.

 

Command-Line:

  1. Open an Administrator command prompt.
  2. Run the following commands:

setx /m GST_VBA_TIMEOUT 7200
setx /m NSR_HYPERVISOR_QUERY_REQUEST_TIMEOUT 3600

 

For NetWorker 19.10 (or later) add the following (optional):

setx /m NSRVIM_TIME_INTERVAL 60

This setting changes the frequency in which nsrvim runs (in minutes). The minimum (default setting) is 15. The maximum setting is 60. This change can help reduce load on the vCenter Server Daemon (VPXD).

 

NOTE: The following article includes additional kernel and TCP optimizations for Networker servers. The above parameters are included. NetWorker: Best practices for networking configuration
  1. Reboot the host.
  2. When the host comes back up, validate the system variables using from a new Administrator command-prompt: set

System Properties UI Method:

  1. From the dashboard, select Server Manager > Local Server.
  2. Click the hyperlink for the Computer Name.
  3. Select System Properties > Advanced > Environment Variables > New.
Server Manager Dashboard for Windows
Figure 2: Server Manager Dashboard for Windows 
NOTE: The following article includes additional kernel and TCP optimizations for Networker servers. The above parameters are included. NetWorker: Best practices for networking configuration
  1. Reboot the NetWorker server operating system.

For Linux:

  1. Create or edit the /nsr/nsrrc file using a text editor:
vi /nsr/nsrrc
NOTE: The nsrrc file is a variable file used by NetWorker processes, the variables are applied during NetWorker daemon startup.
  1. Add the following lines:
GST_VBA_TIMEOUT=7200
export GST_VBA_TIMEOUT
NSR_HYPERVISOR_QUERY_REQUEST_TIMEOUT=3600
export NSR_HYPERVISOR_QUERY_REQUEST_TIMEOUT
  1. The finished changes should look similar to:
[root@networker]:~# cat /nsr/nsrrc
JAVA_HOME=/opt/nre/java/latest/
export JAVA_HOME
GST_VBA_TIMEOUT=7200
export GST_VBA_TIMEOUT
NSR_HYPERVISOR_QUERY_REQUEST_TIMEOUT=3600
export NSR_HYPERVISOR_QUERY_REQUEST_TIMEOUT
# For NetWorker 19.10 and later add the following line (optional)
NSRVIM_TIME_INTERVAL=60 
# This value changes the frequency in which scheduled nsrvim runs (in minutes). Minimum (default): 15, maximum:60. This setting can help reduce load on the vCenter server daemon.
export NSRVIM_TIME_INTERVAL
NOTE: The following article includes additional kernel and TCP optimizations for Networker servers. The above parameters are included. NetWorker: Best practices for networking configuration
  1. Restart the NetWorker services:
systemctl restart networker
systemctl restart gst

Additional Information

If the issue persists after applying the environment variables defined in this KB, see:

Affected Products

NetWorker

Products

NetWorker Family, NetWorker Series
Article Properties
Article Number: 000211688
Article Type: Solution
Last Modified: 30 Dec 2025
Version:  11
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.