Dell NetWorker 19.9 Administration Guide

PDF

NMC error messages and corrective actions

The following table provides a list of NMC error messages or symptoms and corrective actions to take.

Table 1. Error messages or symptoms
Error message or symptom	Possible cause	Corrective action
If the Console server fails to load and instead displays a Save As... dialog box.	JavaScript is not enabled on the host. The security level in Internet Explorer is set to High, which disables JavaScript, which is needed to launch the product, or JavaScript has been disabled by some other means.	In Internet Explorer, ensure that the security level is lower than high, which disables JavaScipt, or enable Active Scripting.
The NetWorker Server does not accept the authorization code.	A temporary enabler code has already expired.	Log out, then stop and restart the NMC Server services.
An application window is unresponsive.	Insufficient disk space on the file system where the NMC database is installed.	Ensure that the NMC Server is running. If it is not, close all application windows and check the gstd log file for errors. Back up and move the Console database, if required. On a Windows system, run InstallShield with the Repair option to move the database to a different drive.
	Application ran out of memory.	Close all instances of the application and restart it.
	Another dialog box is open in the NMC window or Administration window.	Close any open dialog boxes or error messages.
Connection refused: no further information. or Problem contacting server server_name:	NMC Server is in the process of crashing or has already crashed.	Check to see if the NMC Server is running. If it is running, stop and restart the NMC server. If it is not, close all application windows and check the gstd log file for errors.
	Console server has been started within the previous few minutes.	Wait a couple of minutes and retry.
Failed to bind to port `port_mumber` message appears in the gstd.raw log file.	Another process is using the gstd service port (default 9001) or the port is in a timeout (TIME_WAIT/FIN_WAIT) state.	Close any running NMC GUIs or any processes that may be using the gstd service port. Wait until the timeout period passes so that the operating system can free up the port. The timeout period may differ between operating systems.
Database fetch operation failed messages appears in the gstd.raw log file.	The NMC database is corrupt.	Recover the database.
Display problem: In Internet Explorer: The page cannot be displayed.	The gstd service is not running on the NMC server.	Restart the NMC server.
	Browser is not pointing to the correct URL.	Check the install log file to determine the HTTP port that is used by the NMC Server.
	Network connection is down.	Ping the NMC Server to confirm the network connection. If it is available, contact the system administrator.
Enabler code not accepted.	Temporary enabler code has expired.	Close the NMC Server and log in again. Repeat the procedure of typing the enabler code. If the enabler code is still not accepted, log out, then stop and restart the NMC Server.
Database delete operation failed: Reference object does not exist.	Another user has already deleted that user or folder.	None
Database store operation failed: An object with pathname “`pathname`” already exists.	Another user is trying to add a folder to the same location in the Enterprise simultaneously. An object was added with the same name as an existing object.	Wait a few moments and try again. Check whether there is an existing object with the same name.
Invalid Object ID.	Another user deleted that host.	None
Could not contact License Manager on `hostname`. - or - Program not registered.	License Manager hostname has not been assigned or License Manager is not running or installed.	If you are using the License Manager and a hostname has not been assigned: Select the Software Administration task. Click Licensing. Click Software Administration on the menu bar. Click Change LLM Server. Type the new License Manager hostname. Click OK. If License Manager is installed, but not running, start it. The NetWorker License Manager server Installation and Administration Guide provides details.
	NetWorker Client was stopped, but the License Manager was not stopped, and then the NetWorker Client was restarted. Although both services are now running, NetWorker Client must be started before License Manager is started. If the services are not started in the correct order, an error condition occurs.	Stop the NetWorker software. Stop License Manager, if it is running. Restart License Manager. Restart the NetWorker software.
License allocation failed.	Temporary license for NetWorker software is expired.	Enter enabler codes and register the product.
License managed event indicates that license is expiring/expired even though it has been authorized.	License has been authorized within the last 24 hours.	None needed. To remove the managed event from the display, dismiss the event or it is deleted within 24 hours.
Logging of troubleshoot messages has stopped. alloc /opt: File system full.	Disk space on the /opt file system is nearly full.	Allocate more disk space.
Event disappears from the Events window.	Another user dismissed it, or the problem that was causing the event no longer exists.	None
Dialog box: "Java Web Start –Download Error" with the message, "Unable to launch NetWorker Console".	Java Web Start preferences are set to something that is incompatible with the rest of the environment. (For example, a proxy server has been set up that stops Java Web Start from downloading the Console client software from the Console web server.) This error message may also occur if the Console is being launched on a localized operating system and the Java Web Start cache path contains non-English characters.	Check the Preference settings in the Java Web Start Application Manager for compatibility with the environment. Change any settings that prohibit the download of the Console client software. In the proxy server example, go to the General tab of the Preferences dialog box and select None, for Proxies. If the Java Web Start cache path contains non-English characters, change the path to contain no non-English characters.
gstd.log file error: internal error: could not end transaction	When you move the system time ahead, the NMC Server starts a time out event and closes database client connection for the gstd process.	None
GC overhead limit exceeds	This error message appears when you are performing tasks in NMC and there is insufficient Java memory, or heap.	Increase the Java heap size to 1400MB. Start the Java Control Panel application: `javaws -viewer`. Close the Java Cache window. On the Java tab, click View. On the Java Runtime Environment Settings window, double-click in the Runtime Parameters cell for the Java version that you use with NMC. In the Runtime Parameters field, specify a heap size of 1400 MB: `-Xms1400m` Click OK. Click OK to close the Java Control Panel. Close the NMC and NetWorker Administration windows and reconnect to the NetWorker.