DOCUMENTATION: Listing of VBR Status Codes with an explanation of each.
| Article:TECH68034 | | | Created: 2009-01-19 | | | Updated: 2010-01-12 | | | Article URL http://www.symantec.com/docs/TECH68034 |
Problem
DOCUMENTATION: Listing of VBR Status Codes with an explanation of each.
Solution
Codes are prefixed with "A" when they originate from the
agent and an "S" when they originate from the server. For example, "A217"
is an agent error. "S3003" is a server
error.
VBR Log Files:
Note: "X" indicates an incrementing log file number.
VBR Server Status Codes:
Note: Server status codes are displayed with an "S" prefix. Agent status codes are displayed with an "A" prefix.
VBR Agent Status Codes:
VBR Log Files:
Note: "X" indicates an incrementing log file number.
VBR Server Status Codes:
Note: Server status codes are displayed with an "S" prefix. Agent status codes are displayed with an "A" prefix.
VBR Agent Status Codes:
VBR
status code: A1
Message:
Cannot resolve version
Explanation:
The agent and management server software installed are not
compatible.
Recommended
action: Verify that you have installed the same version of software for the
agent and the management server.
VBR
status code: A2
Message:
Invalid agent home directory
Explanation:
The agent's home directory is invalid or not present.
Recommended
action: Verify that the file path specified for the agent is
present:
1. In the
management console menu choose Settings > Global Settings > Agent
Configuration.
2. Choose a
configured agent and then select a configured module.
3. Verify
the home directory path to the actual installation path of the agent, as it
appears in the operating system of that agent.
VBR
status code: A3
Message:
Could not load configuration
Explanation:
The agent configuration file is missing or invalid.
Recommended
action:
- Verify
that agent.conf exists.
- In Solaris
the default path is "/opt/VRTSccsva/conf/agent.conf".
- In Windows
the default path is "<install path>\Veritas Backup
Reporter\agent\conf\agent.conf.
- Open
agent.conf and review the entries for invalid information.
VBR
status code: A4
Message:
Could not save configuration
Explanation:
The agent was unable to save its configuration file after authentication of
the agent with the management server.
Recommended
action: If authentication is successful then the agent.conf file must be
manually updated:
1. Open
agent.conf.
2. Add or
edit the entry "serverName =" with the correct hostname of the server that the
agent is installed on.
3. Restart
the agent.
VBR
status code: A5
Message:
Fatal Authentication Exception
Explanation:
The agent is not able to authenticate with the management server.
Recommended
action:
- Verify
that the arguments provided to "agentauth.exe" are correct.
- Verify
that the Symantec Authentication service is running
- Review
"Resolving agent authentication failures manually on Solaris and Windows" in the
VBR 6.5 Installation Guide.
VBR
status code: A6
Message:
Fatal Scheduler Error
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A7
Message:
Network error
Explanation:
The IP address or host name of the agent could not be determined.
Recommended
action:
- Verify
that the agent is running.
- Verify
that the agent module is configured with the correct location.
- Check name
resolution and the hosts file on the management server.
VBR
status code: A8
Message:
Agent not authenticated with the server
Explanation:
The VBR agent could not authenticate with the management server
Recommended
action: Review "Resolving agent authentication failures manually on Solaris
and Windows" in the VBR 6.5 Installation Guide.
VBR
status code: A9
Message:
Invalid Arguments passed on the command line
Explanation:
Invalid arguments were passed on the command line while starting the agent
from the command prompt.
Recommended
action: Review "Stopping and starting the Veritas Backup Reporter Agent on
Solaris and Windows" in the VBR 6.5 Installation Guide.
VBR
status code: A10
Message:
The EventQueueElement already exists
Explanation:
The data collection event to be performed already exists in the data
collection event queue.
Recommended
action: Do not click on "Force Poll" until all of the running data
collection events complete.
VBR
status code: A11
Message:
Fatal invalid configuration
Explanation:
The VBR agent is unable to start.
Recommended
action:
- Verify
that the agent is not already running.
- Verify
that the agent home directory is present.
- Verify
that the agent is authenticated with the management server
- Check file
and logon permissions.
VBR
status code: A200
Message:
Invalid date range
Explanation: The
date range, i.e. either start time or end time, is invalid (null) for Job or
Image data collection.
Recommended
action: This is an internal error from the agent and should not occur under
normal usage. The date range used by the agent is dependent on the data
collection interval, but this could be magnified by incorrect OS date and time
settings. Collect all agent logs and error information and then contact Symantec
support.
VBR
status code: A201
Message:
Invalid communication method
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A202
Message:
Data collection event was improperly initialized
Explanation:
Data collection event is not initialized properly
Recommended
action: Check to see that all of the VBR software (agents, management
server, view builder) have been upgraded to the same version level.
VBR
status code: A203
Message:
Failed to transmit data
Explanation:
Error while transmitting data from the agent to the management
server.
Recommended
action: Do the following steps:
1. In the
management console choose from the menu Settings > Global Settings > Agent
Configuration, Show All Agents Status.
2. Click on
the appropriate agent and choose "Show Agent Data Transmission
Problems".
3. Click on
"Force Load".
VBR
status code: A204
Message:
The data collection event is already in the queue
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A205
Message:
Cannot get session
Explanation:
Cannot get a CORBA session with the VBR Corba server.
Recommended
action:
- Verify
that Veritas Backup Reporter Corba Server service is running.
- Verify
that Symantec Private Branch Exchange service is running.
VBR
status code: A206
Error
Message: Invalid connection parameters
Explanation:
An invalid connection parameter was used while an agent was connecting to
management server.
Recommended
action: Verify that the server name is valid in agent.conf.
VBR
status code: A207
Message:
Cannot contact server
Explanation:
The agent cannot communicate with the VBR Corba server.
Recommended
action:
- Verify the
VBR Corba server is running.
- Verify
that agent.conf has valid configuration parameters
- Verify
agent authentication using the steps described in the VBR Installation
Guide.
- Verify the
network path between the agent and the VBR management server is
working
- Verify
that the ports used by VBR are not blocked by a firewall
VBR
status code: A208
Message:
Cannot update meta data
Explanation:
The agent cannot update its configuration.
Recommended
action:
- This is
usually a VBR server-side exception. Check the VBR management server's
logs.
- Verify
file permissions of the VBR directories and files.
VBR
status code: A209
Message:
Cannot send heartbeat
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A210
Message:
Cannot get data from server
Explanation:
The agent is not able to get VBR server version information from the VBR
management server.
Recommended
action: Verify that the VBR management server processes are running and that
the correct version is present in the version file.
VBR
status code: A211
Message:
The requested action is not supported
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A212
Message:
Improper use of method
Explanation:
This is an internal message.
Recommended
action: Upgrade to the latest maintenance release. Save all error
information and contact Symantec Support if the issue persists.
VBR
status code: A213
Message:
Invalid module instance
Explanation:
The agent is expecting to gather data for a non-existent module.
Recommended
action:
- Verify
that agent.conf has valid module entries.
- Stop the
VBR agent. Remove problematic module entries from agent.conf. Start the
agent.
- Check the
agent log for further messages.
VBR
status code: A214
Message:
Invalid data collection event
Explanation:
The agentdatacollectionutility.exe command line utility provides the ability
to run an immediate poll of any of the seven data collection types within a VBR
module. The agent tried to collect data using invalid options.
Recommended
action: Upgrade to the latest maintenance release. If manually running
commands verify that the correct options are being used.
VBR
status code: A215
Message:
Log Configuration Error
Explanation:
Database transaction logs are not in the format expected during an
upgrade.
Recommended
action:
- Verify
that any release dependencies have first been installed.
- Close any
open VBR consoles before upgrading.
- Upgrade
the management console before upgrading the agents or ViewBuilder.
- Ensure
that you have administrative rights
- For
Symantec Backup Exec:
- Verify
that all operating system patches have been applied
- Install
the redistributable package for Microsoft Visual C++ 200
VBR
status code: A216
Message:
Cannot send alert
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A217
Message:
Data rejected by server
Explanation:
The data received by VBR could not be loaded.
Recommended
action:
- Examine
the VBR Corba Server logs for more details
- Windows
default path: c:\program files\symantec\veritas backup
reporter\server\corbaserver\logs
- Solaris:
/var/VRTSccsvs/log/
- Increase
the maxheap setting
- Disable
automatic reboot if the maxheap setting is configured
VBR
status code: A218
Message:
Could not initiate data collection event
Explanation:
The agent is not getting any data returned from a query
Recommended
action:
- Verify the
path to the binary location for NetBackup
- Check the
Agent logs, /opt/VRTSccsva/logs, to see what is reported as a problem when
trying to collect information from this module. (Specifically, check
agent-core-0.log.)
- Check to
see how the problematic module was configured. Look in the
/opt/VRTSccsva/conf/agent.conf config file.
-
For UNIX, confirm that the homeDirectory value is set to the UNIX path.
The homeDirectory refers to the location of Net Backup binaries on the
Agent.
- For
Windows, check C:\Program Files\Symantec\Veritas Backup Reporter\Agent\Logs and
C:\Program Files\Symantec\Veritas Backup Reporter\Agent\conf.
VBR
status code: A219
Message:
The module has thrown an error.
Explanation:
A module has experienced a Java error. The message can also be related to
memory (e.g. Java heap space)
Recommended
action: Check which module has the error condition and correct or recreate
the module.
VBR
status code: A220
Message:
Invalid null data
Explanation:
The backup product sent invalid or null data to the agent.
Recommended
action:
In the
NetBackup master server:
- Check
images using bpimagelist command for "no entity found"
- Upgrade
the master server to the latest maintenance release
VBR
status code: A221
Message:
Invalid state transition
Explanation:
VBR data collection event is in invalid state.
Recommended
action: Restart the VBR agent
VBR
status code: A222
Message:
Internal communication error
Explanation:
The agent has determined that it has no space to create a file in the
spooler directory.
Recommended
action:
- Verify
that the file path specified for the agent is present.
- Verify
that the file path specified for the spooler directory is present and on same
computer as the agent.
- Stop the
agent service.
- Edit the
MaxMemoryUsage value in agent.conf. By default the value is set to 500
- Note:
value must be set lower than the amount of available disk space on the server
hosting the agent.
- Start the
agent service.
VBR
status code: A223
Message:
Invalid parameter
Explanation:
A module configuration parameter is not valid while updating agent module
configuration.
Recommended
action: Review the agent module configuration for correctness. Check VBR
logs for more details.
VBR
status code: A224
Message:
Communication Queue does not exist
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A225
Message:
Communication Queue does not exist
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A226
Message:
Module does not exist
Explanation:
The module for the specified instance identifier does not exist
Recommended
action: Verify that the module configuration is present with said instance
number in the agent.conf file.
VBR
status code: A227
Message:
Event already exists
Explanation:
The data collection event already exists.
Recommended
action: Wait for the data collection event to finish. No further
action should be needed.
VBR
status code: A228
Message:
Invalid event schedule
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A229
Message:
Event does not exist
Explanation:
An attempt was made to remove an event that does not exist.
Recommended
action: Review the agent logs for more details.
VBR
status code: A230
Message:
Module already exists
Explanation:
The agent module has already been instantiated. This status can occur if a
new module is configured that is identical to an existing one or if agent.conf
has more than one entry with the same instance ID.
Recommended
action: Verify that the module configuration is correct. Verify that
agent.conf does not have a duplicate instance ID.
VBR
status code: A231
Message:
<no message is displayed>
Explanation:
The requested Corba object does not exist.
Recommended
action: This is an internal status code. Verify that the VBR Corba Server
service is running. Check the VBR management server log core-0.log for more
details.
VBR
status code: A232
Message:
<no message is displayed>
Explanation:
The Corba session times out.
Recommended
action: This is an internal status code. Verify that the VBR Corba Server
service is running. Check the VBR management server log core-0.log for more
details.
VBR
status code: A2000
Message:
Parameter passed is NULL
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2001
Message:
Data stream is NULL
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2002
Message:
Module configuration is NULL
Explanation:
The agent module configuration is invalid.
Recommended
action: Correct the agent module configuration. Review the VBR documentation
for correct installation and usage. Save all error information and contact
Symantec Support if the issue persists.
VBR
status code: A2003
Message:
Module configuration is invalid
Explanation:
The home directory in the agent module configuration was not specified or is
invalid while configuring a TSM agent module.
Recommended
action: Review the agent module configuration and correct the home
directory. This can also be reviewed in agent.conf.
VBR
status code: A2004
Message:
Collection method is NULL
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2005
Message:
Invalid value for collection method
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2006
Message:
Collection request is not supported.
Explanation:
The data collection for the configured event and configured product is not
supported. Review the VBR documentation for correct installation and usage. Save
all error information and contact Symantec Support if the issue
persists.
Recommended
action: Verify that the agent module was correctly created.
VBR
status code: A2007
Message:
Module configuration is invalid
Explanation:
The home directory in the agent module configuration was not specified or is
invalid while configuring a Networker agent module.
Recommended
action: Review the agent module configuration and correct the home
directory. This can also be reviewed in agent.conf.
VBR
status code: A2008
Message:
Home directory of the product does not exist
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2009
Message:
The master server is NULL
Explanation:
The product host specified while configuring a CommVault module is
invalid.
Recommended
action: Correct the agent module configuration.
VBR
status code: A2011
Message:
IOException happened when executing external process
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2012
Message:
Command array for external process is NULL or empty
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2013
Message:
External process interrupted
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2014
Message:
External process terminated because of not returning data in a timely
manner
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2015
Message:
External process exited abnormally
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2020
Message:
Data source file not found
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2021
Message:
IOException happened when using data source file
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2022
Message:
Invalid data source
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2030
Message:
Unexpected problem encountered when parsing command output
Explanation:
An unexpected problem was encountered.
Recommended
action: Review the agent logs for more information.
VBR
status code: A2031
Message:
Incorrect named value count
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A2032
Message:
File not found
Explanation:
The Networker messages file couldn't be located using the provided
information.
Recommended
action: Verify that the location of the messages file in the Legato
Networker installation and compare it to the agent module configuration. Default
paths for the messages file:
- Windows:
c:\program files\nsr\logs\messages
- Solaris:
/usr/sbin/nsr/logs/messages
VBR
status code: A2033
Message:
File name invalid
Explanation:
The Networker messages file couldn't be located using the provided
information.
Recommended
action: Verify that the location of the messages file in the Legato
Networker installation and compare it to the agent module configuration. Default
paths for the messages file:
- Windows:
c:\program files\nsr\logs\messages
- Solaris:
/usr/sbin/nsr/logs/messages
VBR
status code: A3000
Message:
Netbackup host name is NULL
Explanation:
The NetBackup host name that was configured is invalid.
Recommended
action: Verify the NetBackup product host name used in agent.conf.
VBR
status code: A3001
Message:
Failed to initialize NBU job data collector for master server
Explanation:
The job data collection could not be initialized because the NetBackup
product host name was not recognized.
Recommended
action: In Global Settings, Agent Configuration, open the configured agent
and check that the product host is the hostname of the NetBackup server from
which data is to be collected.
VBR
status code: A3002
Message:
Failed to get the slot count information from vmchange
Explanation:
An error was experienced trying to execute the vmchange command.
Recommended
action:
- Verify
that the agent has access to the vmchange command if the agent is not installed
on the NetBackup master server.
- Verify
that the vmchange command being executed is of the same version as the NetBackup
master server.
- Windows
default location: <install path>\volmgr\bin\vmchange.exe
- Unix
default location: /usr/openv/volmgr/bin/vmchange
- Verify
that vmchange has not been replaced with some other file.
- Verify
that in the operating system's search path a vmchange file does not get executed
before reaching NetBackup's vmchange.
- Check the
agent module configuration in agent.conf.
VBR
status code: A3003
Message:
Media data collection failed.
Explanation:
Tape library information is not available for the media.
Recommended
action: Check the agent module configuration in agent.conf.
VBR
status code: A3004
Message:
Failed to get the volume database host information for the agent product
host
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A3005
Message:
Failed to get the master server hostname for the agent product
host
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A3006
Message:
Failed to fully qualify host name: Please contact System
Administrator
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A3007
Message:
Failed to initialize NetBackup agent: Local NetBackup version does not match
with Remote NetBackup version
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A3008
Message:
Failed to initialize NetBackup agent: Could not determine the product
version
Explanation:
Unable to determine the version of the remote NBU product host.
Recommended
action:
- Verify
that NBU product host name is valid in agent.conf.
- Verify
that the NetBackup product server is accessible from the agent.
- Note: the
agent is trying to run the command "bpclntcmd -get_remote_host_version
<product host name>"
VBR
status code: A3009
Message:
Failed to initialize NetBackup agent module
Explanation:
Unable to determine the version of the remote NBU product host.
Recommended
action: Check the values provided in agent module configuration or in
agent.conf, such as Server name, Collection method, and Home
Directory.
VBR
status code: A4000
Message:
BE host name is NULL
Explanation:
BE server host name is invalid in module configuration.
Recommended
action: Verify that correct host name is provided while configuring the
agent module for BE.
VBR
status code: A4001
Message:
Failed to initialize BE agent
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A4002
Message:
Failed to connect to BE master server
Explanation:
The agent was unable to connect to BE master server.
Recommended
action: Verify that the BE server is up and running. Ensure that BE Server
is accessible from the agent host.
VBR
status code: A4003
Message:
Failed to connect to BE master server using BEMSDK
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A4004
Message:
Failed to initialize BE Job data Collector
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A4005
Message:
Invalid BE Job data Collector
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A4006
Message:
BE Job data parsing error
Explanation:
An error occurred during data collection.
Recommended
action: Review the agent module logs for more detail.
VBR
status code: A4007
Message:
Parsing error in BE Job data from BEMSDK
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A4008
Message:
BE Policy data parsing error
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A4009
Message:
Parsing error in BE Policy data from BEMSDK
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A4010
Message:
Failure determining the BE version
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A4011
Message:
Error while Policy data collection
Explanation:
An error occurred collecting policy data.
Recommended
action: Review the agent module logs (module-XXX-backupexec-<BE Server
Name>-X.log) for specific details.
VBR
status code: A4012
Message:
Error while Job data collection
Explanation:
An error occurred collecting job data.
Recommended
action: Review the agent module logs (module-XXX-backupexec-<BE Server
Name>-X.log) for specific details.
VBR
status code: A4013
Message:
Error while Tape Drive collection
Explanation:
An error occurred collecting tape drive data.
Recommended
action: Review the agent module logs (module-XXX-backupexec-<BE Server
Name>-X.log) for specific details.
VBR
status code: A4014
Message:
Error while Media data collection
Explanation:
An error occurred collecting media data.
Recommended
action: Review the agent module logs (module-XXX-backupexec-<BE Server
Name>-X.log) for specific details.
VBR
status code: A4500
Message:
Invalid user name specified
Explanation:
Invalid user name specified while configuring CommVault agent
module.
Recommended
action: Verify the username provided while configuring the CommVault agent
module.
VBR
status code: A4501
Message:
Invalid password specified
Explanation:
Invalid password specified while configuring CommVault agent
module.
Recommended
action: Verify the password provided while configuring the CommVault agent
module.
VBR
status code: A4502
Message:
Invalid port specified
Explanation:
Invalid port number specified while configuring CommVault agent
module.
Recommended
action: Verify the port number provided while configuring the CommVault
agent module.
VBR Error
Code: 4503
Message:
Could not determine the product version
Explanation:
The CommVault version could not be determined.
Recommended
action: Verify that a supported version of CommVault is installed. Verify
the agent installation. Check the CommVault product host name used.
VBR
status code: A4504
Message:
Could not connect to the CV database
Explanation:
Could not connect to the CommVault database.
Recommended
action: Verify that CommVault database is up and running.
VBR
status code: A4505
Message:
Could not find the database driver
Explanation:
Could not find the CommVault database driver
Recommended
action: Verify that CommVault version is supported.
VBR
status code: A4506
Message:
Could not get data from the result set
Explanation:
Could not get data from the result set
Recommended
action: Review the agent module logs (module-XXX-commvault-<CommVault
Server Name>-X.log) for specific details.
VBR
status code: A4507
Message:
Invalid data returned by the commvault db query
Explanation:
Invalid data returned by the commvault db query
Recommended
action: Review the agent module logs (module-XXX-commvault-<CommVault
Server Name>-X.log) for specific details.
VBR
status code: A4508
Message:
Problem with the properties file
Explanation:
Properties file containing CommVault sql queries is invalid.
Recommended
action: Review the agent module logs (module-XXX-commvault-<CommVault
Server Name>-X.log) for specific details.
VBR
status code: A5001
Message:
Could not instantiate report manager stub
Explanation:
Initialization failure of PureDisk agent module. Secure port may not be
available/open to connect.
Recommended
action: Verify secure port "1044
VBR
status code: A5002
Message:
Could not add header to report manager stub
Explanation:
Internal connectivity issues between internal objects.
Recommended
action: Increase cache sizes, verify that the server is not overburdened by
cpu or memory usage.
VBR
status code: A5003
Message:
Error in retrieving policy data
Explanation:
There was an error in retrieving the policy data.
Recommended
action: Typically this exception occurs after creating the PureDisk agent
module. Restarting the agent module works in most of the cases. If it doesn't
work then delete and recreate agent module.
VBR
status code: A5004
Message:
Error in retrieving completed job data
Explanation:
There was an error in retrieving the completed job data.
Recommended
action: Typically this exception occurs after creating the PureDisk agent
module. Restarting the agent module works in most of the cases. If it doesn't
work then delete and recreate agent module.
VBR
status code: A5005
Message:
Could not connect to the PD database
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A5006
Message:
Could not find the database driver
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A5007
Message:
Could not get data from the result set
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A5008
Message:
Error in executing the query
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A5009
Message:
Problem with the properties file
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A5010
Message:
Data iterator is already destroyed.
Explanation:
Occurs if the PureDisk agent module tries to process an expired job/policy
data iterator.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A5011
Message:
Invalid configuration for PureDisk.
Explanation:
An invalid configuration was provided while creating a PureDisk agent
module
Recommended
action: Check the specified PureDisk SPA host is valid and
running.
VBR
status code: A5012
Message:
Report Manager is not responding for given request.
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A5013
Message:
Failed to load queries from file.
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A6000
Message:
Resource type invalid
Explanation:
CLI output validation failed.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A6001
Message:
Failed to load resource
Explanation:
Unable to load an event data class, e.g. "NetworkerMedia" class for the
event "Media".
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A6010
Message:
IOException encountered when parsing message log file
Explanation:
The message file location is incorrect or the message file is
missing.
Recommended
action: Verify that the message file is in its location. Take corrective
action if it is not there or the location is invalid.
VBR
status code: A6020
Message:
The command passed to 'nsradmin' is not supported
Explanation:
This error will occur when trying to run a command that is unsupported or
invalid.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A6030
Message:
Error while date parsing, possibly unsupported locale
Explanation:
The date returned in the CLI output is different than the default date
format. This may be due to an different locale than the local of the
server.
Recommended
action: The date format should be in the default locale format. Verify that
the locale is supported by VBR. Verify that the date format of the
Operating System has not been customized.
VBR
status code: A8000
Message:
TSM Product Host Name is NULL
Explanation:
The TSM server name is not specified in the agent module
configuration.
Recommended
action: Verify that the TSM agent module configuration is correct and that
the TSM server name is present.
VBR
status code: A8001
Message:
Failed to connect to TSM Server
Explanation:
Failed to connect to the TSM server.
Recommended
action: Verify that the TSM server is running.
VBR
status code: A8002
Message:
Failed to initialize TSM Agent Module
Explanation:
Failed to initialize the TSM agent module.
Recommended
action: Review the agent module logs (module-XXX-tsm-<TSM server
name>-X.log) for specific details.
VBR
status code: A8003
Message:
Error while executing TSM query
Explanation:
An error occurred while executing the TSM query.
Recommended
action: Review the agent module logs (module-XXX-tsm-<TSM server
name>-X.log) for specific details.
VBR
status code: A8004
Message:
TSM Header-Check error
Explanation:
The header of the output from a TSM command line query does not match the
expected header.
Recommended
action: Verify that data is being collected from a supported version of TSM.
Verify that the TSM agent module is correctly configured. Review agent module
logs for more details, with the log level set to ALL.
VBR
status code: A8005
Message:
Error while Policy data collection
Explanation:
An error occurred while collecting TSM policy data.
Recommended
action: Review the agent module logs (module-XXX-tsm-<TSM server
name>-X.log) for specific details.
VBR
status code: A8006
Message:
Error while Job data collection
Explanation:
An error occurred while collecting TSM job data.
Recommended
action: Review the agent module logs (module-XXX-tsm-<TSM server
name>-X.log) for specific details.
VBR
status code: A8007
Message:
Error while Skipped File data collection
Explanation:
An error occurred while collecting TSM skipped files data.
Recommended
action: Review the agent module logs (module-XXX-tsm-<TSM server
name>-X.log) for specific details.
VBR
status code: A8008
Message:
Error while Error / Log data collection
Explanation:
An error occurred while collecting TSM errors and logs data.
Recommended
action: Review the agent module logs (module-XXX-tsm-<TSM server
name>-X.log) for specific details.
VBR
status code: A8009
Message:
Error while Tape Drive / Library data collection
Explanation:
An error occurred while collecting TSM tape drive and library
data.
Recommended
action: Review the agent module logs (module-XXX-tsm-<TSM server
name>-X.log) for specific details.
VBR
status code: A8010
Message:
Error while Media data collection
Explanation:
An error occurred while collecting TSM media data.
Recommended
action: Review the agent module logs (module-XXX-tsm-<TSM server
name>-X.log) for specific details.
VBR
status code: A9000
Message:
Generic agent host name is NULL
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9001
Message:
Invalid utility location for Generic agent
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9002
Message:
Failed to initialize Generic agent
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9003
Message:
Failed in running utility specified for Generic agent
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9004
Message:
Failed to initialize Generic data Collector
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9005
Message:
Invalid Generic data Collector
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9006
Message:
Generic data parsing error
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9500
Message:
Failed to create API object
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9501
Message:
Failed to collect single host data from CCMM API
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9502
Message:
Failed to collect hosts data from CCMM API
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9503
Message:
Failed to collect filter data from CCMM API
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9504
Message:
Failed to collect sample data from CCMM API
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9505
Message:
Failed to check for more elements from CCMM API
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A9506
Message:
Failed to get the next element from CCMM API
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A10001
Message:
SQL Server driver not loaded
Explanation:
SQL Server driver not loaded
Recommended
action: Install the SQL Server driver and check the database access from the
module to the VaultDirectory.
VBR
status code: A10002
Message:
Error during collection of event data
Explanation:
Error during collection of event data
Recommended
action: Check the EV agent module logs for more specific details.
VBR
status code: A10003
Message:
Error during collection of VaultPartition data
Explanation:
Error during collection of event data
Recommended
action: Check the EV agent module logs for more specific details.
VBR
status code: A10004
Message:
Error during collection of event data
Explanation:
Error during collection of event data
Recommended
action: Check EV agent module logs for more specific details.
VBR
status code: A10005
Message:
Error during collection of event data
Explanation:
Producer thread for savesets failed with an exception
Recommended
action: Check EV agent module logs for more specific details.
VBR
status code: A10007
Message:
Invalid data port
Explanation:
An invalid port was specified during collection of event data
Recommended
action: Check the EV agent module logs for more specific details.
VBR
status code: A10008
Message:
Producer thread for savesets failed with an exception
Explanation:
Invalid database port
Recommended
action: Check the database port configured in the agent module
configuration.
VBR
status code: A10009
Message:
Error querying SQL Server database
Explanation:
I/O Error saving EV spooler files
Recommended
action: Check the systems free space
VBR
status code: A10010
Message:
I/O Error saving EV spooler files
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A10011
Message:
I/O Error reading EV spooler files
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A10012
Message:
Error querying SQL Server database
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A10013
Message:
I/O Error saving EV spooler files
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A10014
Message:
Producer thread for targets failed with an exception
Explanation:
This error should not occur through normal use of VBR.
Recommended
action: Review the VBR documentation for correct installation and usage.
Save all error information and contact Symantec Support if the issue
persists.
VBR
status code: A10015
Message:
I/O Error reading EV spooler files
Explanation:
An error occurred while querying SQL database
Recommended
action: Check the database access from agent host to Vault Store
Database.
VBR
status code: A10016
Message:
Producer thread to vault capacity failed with an exception
Explanation:
An error I/O error occurred while saving EV spooler files
Recommended
action: Check the file system space.
|
|
Related Articles
Legacy ID
319722
Article URL http://www.symantec.com/docs/TECH68034
Terms of use for this information are found in Legal Notices
Thank you.