OpsCenter Error Messages

Following table lists OpsCenter error messages with the possible root cause of the problem and details about the solutions that can be applied.

Table: OpsCenter Error codes with Description

Error Code	Description	Root Cause	Solution
401	The user does not have permissions of the selected view.	This error occurs when user 'A' saves the report with a given view 'V' (master/media/client) in public folder. Later in time, if administrator changes permission on the view 'V' for user 'A', then next time on running the report by user 'A', will raise this exception.	Make sure that user running the report has permission on the view selected. If no permission for the view then user can edit the report and re-run by selecting available views.
402	Provided user details are invalid.	This error occurs when user 'A' saves the report 'S' in public folder and later in time if administrator delete user 'A' , and if User 'B' or Admin runs the saved report 'S' , will fail to run because the original user does not exists.	`There is no direct way to solve this problem. Best way is to re-create the report and re-run it.`
10500	OpsCenter Database Error	This error signifies OpsCenter database related generic issue. (Connectivity, Timeouts . . .etc.)	Check Database is up and running. Do basic sanity around database. Contact Support with screenshot and relevant log-files.
10501	OpsCenterDb PK Violation around:{<table/entity>} while executing {<add/delete-API>}	Primary Key violation / Duplicate entries were tried to insert in the same table.	Contact Support with screenshot and relevant log-files
10502	OpsCenterDb FK Violation around:{<table/entity>} while executing {<add/delete-API>}	This error signifies Foreign Key violation or Reference records do not exist.	Contact Support with screenshot and relevant log-files.
10503	OpsCenterDb Column value issue around:{<table/entity>} while executing {<add/delete-API>}	This error occurs when NULL value is added for Non-Nullable columns in database.	Contact Support with screenshot and relevant log-files.
10504	OpsCenterDb Column Truncation around:{<table/entity>} while executing {<add/delete-API>}	This error occurs when a value is too large, and does not fit into database column.	Contact Support with screenshot and relevant log-files.
10505	OpsCenterDb Constraints failed around:{<table/entity>} while executing {<add/delete-API>}	This error occurs when database constraints failed. This can occur under multiple reasons. Eg.Entity based constraint or trigger based constraints.	Contact Support with screenshot and relevant log-files.
10506	OpsCenterDb SQL Parsing Error around:{<table/entity>} while executing {<add/delete-API>} DBAL component consists of generated code from the database.	This error resembles that the generated code has a problem and is a serious issue.	Contact Support with screenshot and relevant log-files.
10507	OpsCenterDb Query Execution failed around:{<table/entity>} while executing {<add/delete-API>} DBAL component consists of generated code from the database.	This error resembles that the generated code has a problem and is a serious issue.	Contact Support with screenshot and relevant log-files.
Messages related to Reporting Services
10802	The selected view for this report is not available. The view that was associated with this report might have been deleted.	A view which is used in the saved report has been deleted. View can be deleted without validating that it is associated with a report.	Edit the saved report and select the views which are currently available and try again.
10804	You have no permissions to see the report {0}.	The user accessing the report may not have permission to run/view the report. User is actually trying to access the private reports of other user by modifying the URL parameters.	User can see reports created by that user itself or the reports from a public folder.
10805	Filter {0} is not defined in XML definition file. Please define the filter in FilterAttributeList.xml.	Incorrectly or undefined filter may cause the problem.	Undefined filter should be defined properly in filter definition xml file.
10806	Failed to load the XML definition file {0}. Please contact customer support for assistance.	Each report is associated with xml definition file. This error occurs when there is no corresponding definition file for a report.	Make sure that OPS_INSTALL_DIR/definitions/reports.zip file is not corrupted or modified.
10807	Failed to read the XML file.	XML definition file may be in use and therefore cannot be read.	Make sure that no process is using the XML definition file.
10808	Failed to execute stored procedure {0}.	Stored procedure may fail due to formation of invalid query inside the procedure.	Based on stack trace message, it is possible to figure out where the problem exists in the stored procedure.
10809	Failed to get the database connection.	DBAL component exposes connection to reporting.	Stack trace helps in finding the root cause.
10810	Definition mapping for report ID {0} is failed to load from the database. Please check report_cannedReportMapping table for the mapping.	Each report has an entry in report_cannedReportMapping table. This table keeps the mapping between report ID and XML file. If there is no mapping for the running report, then this error occurs.	Make sure that the table has entry for the running report.
10811	Failed to fetch the schedule workflow details from the database.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10814	Failed to fetch the report condition list from the database for report ID {0}.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10815	Failed to fetch the saved report details from the database for report {0}.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10816	Failed to fetch the user details from the database for report {0}.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10817	Failed to fetch the custom saved report details from the database for report {0}.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10818	Failed to fetch the custom template category mapping list from the database.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10819	Failed to fetch the custom template from the database for {0} category.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10820	Failed to fetch saved report list from the database for user {0}.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10821	Failed to fetch the information for upgrade report from the database for user {0}.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10822	Failed to process the query result for report {0}.	Each result set is processed before sending to the GUI. This error message conveys that the logic that is written to process the result is broken.	This should be escalated to CFT/engineers to understand the problem.
10823	Failed to execute the query at the database for report {0}.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10824	Failed to execute the query for report {0}.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10825	Failed to update report {0}.	Exception occurred while updating the report at the database level.	Stack trace helps in finding the root cause.
10826	Failed to save report {0}.	Exception occurred while saving the report at the database level.	Stack trace helps in finding the root cause.
10828	Failed to delete report {0}.	Exception occurred while deleting the report at the database level.	Stack trace helps in finding the root cause.
10830	Failed to update the schedule workflow in the database.	Exception occurred while updating the workflow at the database level.	Stack trace helps in finding the root cause.
10831	Failed to update the Finish Time of schedule workflow in the database.	Exception occurred while updating the schedule finish time at the database level.	Stack trace helps in finding the root cause.
10832	Failed to create report schedule {0} in the database.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10833	Failed to delete schedule workflow in the database.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10834	Failed to delete reports from schedule workflow.	Exception occurred while running the query at the database level.	Stack trace helps in finding the root cause.
10835	No report schedule is found.	This error occurs while adding reports to a report schedule which does not exists in the database.	Re-create the report schedule and try to add reports to this newly created schedule.
10836	Tree ID and Tree Type information is missing from saved report {0}.	This can be an upgrade issue. Each report that is migrated should have a tree ID and tree type information (if it is view based report) in report_savedreport table.	Re-create the saved report and re-run it.
10837	Time column ID {0} used in definition is not present in the database.	Either the time filter is wrongly defined in the definition .xml file or reports.zip file under OPS_INSALL_DIR/definitions folder is corrupted.	Make sure reports.zip file is not corrupted. If the problem still persists, escalate to engineering/CFT.
10838	Time condition column ID {0} used in the definition file is not present in the database.	Either the time filter is wrongly defined in the definition .xml file or reports.zip file under OPS_INSALL_DIR/definitions folder is corrupted.	Make sure reports.zip file is not corrupted. If the problem still persists, escalate to engineering/CFT.
10839	You do not have permissions to run any report with the specified view. However, you can edit the view filter for which you have permissions and can re-run the report.	The report with selected view cannot be run because the user does not have permission to access the selected view.	Edit the report and select the view available from the drop down menu and re-run the report.
10840	View filter is not applicable for the report.	This error is due to inconsistency in the definition. Example: Suppose user has created and saved a report with some view. In the next release, if the support for the view is removed from the definition, then there is a mismatch in saved definition versus XML definition. If there is a mismatch in the saved definition and XML definition, then it means that database is not updated properly to reflect the new change.	In such cases, edit the report and re-run by applying any valid views that are applicable.
10841	Vault view is not applicable for the report.	The report does not support the vault view filtering.	Edit the report and select the view available from the drop down menu and re-run the report.
10842	Policy view is not supported for this report. However, you can edit the view filter and re-run the report.	The report does not support the policy view filtering.	Edit the report and select the view available from the drop down menu and re-run the report.
10843	Exchange view is not supported for this report. However, you can edit the view filter and re-run the report.	The report does not support the exchange view filtering.	Edit the report and select the view available from the drop down menu and re-run the report.
10844	Master Server view is not supported for this report. However, you can edit the view filter and re-run the report.	The report does not support the Master Server view filtering.	Edit the report and select the view available from the drop down menu and re-run the report.
10845	Client view is not supported for this report. However, you can edit the view filter and re-run the report.	The report does not support the Client view filtering.	Edit the report and select the view available from the drop down menu and re-run the report.
10846	File system view is not supported for this report. However, you can edit the view filter and re-run the report.	The report does not support the file system view filtering.	Edit the report and select the view available from the drop down menu and re-run the report.
10848	No definition of report {0} is found.	Missing XML definition for the report.	Make sure that OPS_INSTALL_DIR/definitions/reports.zip file is not corrupted or modified.
10849	Please upload the .csv file with client name, to run the report.	This error can occur while running client coverage report, if user runs the report without uploading the .csv file.	The .csv file with client names should be uploaded while running the client coverage report.
10850	Report {0} does not have support to run with {1} view. View in this context refers to Distribution/Ranking/Historical/Tabular.	This error can occur in case of upgraded reports Or when reports.zip file is corrupted.	Make sure that OPS_INSTALL_DIR/definitions/reports.zip file is not corrupted or modified. If problem persists, upgraded report needs to be re-created.
10851	Report {0} does not have correctly defined java type.	This error can occur while running any Java based reports. This can occur if reports.zip file is corrupted.	Make sure that OPS_INSTALL_DIR/definitions/reports.zip file is not corrupted or modified. If problem persists, escalate to CFT/Engineering.
10852	Java type executor {0} for report {1} should be appropriately created and used for each java-based report.	This error can occur while running any Java-based reports. This can occur if reports.zip file is corrupted.	Make sure that OPS_INSTALL_DIR/definitions/reports.zip file is not corrupted or modified. If problem persists, escalate to CFT/Engineering.
10853	Report {0} already exists in the selected folder. Either save the report with a different name or overwrite the existing report.	User cannot save the report which already exists; else he needs to overwrite the existing once.	Save report with a different name.
10854	The folder does not exist for saving report {0}. Each report should be saved under the specific folder.	This error occurs when user tries to save a report in a folder while at the same time someone has deleted that folder.	Re-save a report under the existing folder.
10855	No node is present in view node for report ID {0}.	This error occurs when there is major problem with the data in the database. However, it will occur only in case of saved report.	Re-create the report and save it.
10856	Failed to execute report {0} at view level. Reporting component uses view layer component for view related queries.	This error signifies that there is an issue with the view component.	Stack trace helps in finding the root cause.
10857	Failed to fetch child nodes at view level. Reporting component uses view layer component for view related queries.	This error signifies that there is an issue with the view component.	Stack trace helps in finding the root cause.
10858	Failed to fetch the report tree.	Failed to execute the query, by the view component while fetching the view tree.	Stack trace helps in finding the root cause.
10859	Failed to delete a report.	Failed to execute the query, by the view component while deleting the report node from database.	Stack trace helps in finding the root cause
10860	Failed to add report to the view tree. .	Failed to execute the query, by the view component while adding the report to the report tree.	Stack trace helps in finding the root cause
10861	Failed to update report to the view tree.	Failed to execute the query, by the view component while updating the report to the report tree.	Stack trace helps in finding the root cause.
10862	Failed to fetch report details at view level.	Failed to execute the query, by the view component while fetching the report details from the report tree.	Stack trace helps in finding the root cause.
10863	Column {0} does not exist in the database.	This error occurs when an incorrectly defined column exists in the XML definition.	Make sure reports.zip file under {OPS_INSTALL_DIR}/definitions folder is not corrupted. If problem persists, escalate to CFT/Engineers.
10864	Report schedule {0} already exists. Please specify a different name.	Duplicate report schedule names are not allowed.	Save the report schedule with a different name.
10865	Data collection failed for selected Master Servers.	This error occurs only when we run explicit data collection for License report (Capacity and Traditional). It implies that agent is not able to collect the data from the Master Server.	Make sure that agent is configured correctly. Stack trace helps in finding the root cause.
10866	An error has occurred while running the licensing report.	This error occurs only while running license report (Capacity /Traditional). It resembles that an error has occurred while performing File IO operation.	Stack trace helps in finding the exact issue.
10867	Generating license report is failed due to {0}.	This error is caused while running nbdeployutil. Capacity license report is generated via nbdeployutil executable and any error thrown will be the root cause.	From the log file, check if any exception is thrown by nbdeployutil. Since this is an executable, it creates its own log file which is shown as a link in the License report GUI.
10868	Generating license report is failed. From the log file, check if any exception is thrown by nbdeployutil.	Capacity license report generation depends on nbdeployutil executable.	From the log file, check if any exception is thrown by nbdeployutil. Since this is an executable, it creates its own log file which is shown as a link in the License report GUI.
10869	No Master Server is configured for collecting the licensing data.	License report (Capacity /Traditional) can be executed only when at least one Master Server is configured in OpsCenter.	Configure Master Server for which license report needs to be generated.
10870	License Data Collection or Report Generation is already in progress.	This error occurs when user tries to run license report multiple times at the same time. User cannot run license report multiple times at any given point in time.	Make sure you run the report only when previous request for run is completed.
10871	Failed to fetch licensing details from the database.	This error occurs when Licensing report (Capacity /Traditional) fails to perform some of the database activity like fetching status of the failed master server.	Log file will help in finding the exact root cause.
10872	License report is not generated as none of the Master Server license data collections is successful.	License Report (Capacity /Traditional) will be generated only when at least one Master Server data collection (Licensing specific) is successful. Report is not generated if none of the Master Server collection is successful.	Make sure the data collection (Licensing Specific) is successfully collected for at least one Master Server.
10873	Unable to send the email. Please verify the email address, SMTP server settings and then try again.	Email component failed to send email because SMTP configuration might be incorrect or email ID specified might be incorrect.	If not specified, set SMTP configuration from Settings > Configuration > SMTP configuration page.
10875	Failed to create report {0}.	This error occurs when charting component fails to create the chart while exporting and emailing a report.	Log file will help in finding the root cause of failure.
10876	PDF format is not supported for report {0}.	This error occurs when a report not supported for PDF format is added in the scheduled report and expected to be exported in PDF format.	Remove the non-PDF format supported report from scheduled report if the export format expected is PDF.
10877	Only HTML export format is supported for report {0}.	This error occurs when a HTML format supported report is added in the scheduled report and expected to be exported other than HTML format.	If the export format selected (while defining the report schedule) is HTML, then make sure you add only HTML supported reports in the schedule.
10878	Query builder failed to build a query for report {0}.	Query Builder forms the metadata required to build actual SQL query. This meta data is then passed to DBAL component to get the actual query.	This error denotes serious problem in the Query builder forming SQL meta data. This problem needs to be diagnosed from the log file to find the root cause.
10879	One or more reports failed to execute and therefore cannot be sent by email.	This error will occur when dashboard is emailed and one or more reports failed to be exported in specified format (PDF/HTML/CSV). For eg, week at a glance report do not support PDF format.	While emailing the dashboard report, make sure that all the reports under dashboard supports the given export format.
10880	The selected combination of report parameters for this report is not valid. However, you can edit the report, change the parameters and then run the report.	Custom reporting allows user with a lot of combinations to create customized report. However, not all combinations are valid.	Example: Y1-axis Report data and Y2-axis Report data cannot be same. Edit the created custom report and specify valid parameters.
10881	Failed to execute specified SQL-- {0}. Please make sure the SQL syntax is correct.	This error signifies that SQL specified by the user is invalid.	Log file will help in finding the exact problem of the SQL.
10882	Failed to read file {0} from report.zip. Each report is associated with XML definition file.	This error is due to non-availability of particular XML file for a given report.	Make sure reports.zip file under {OPS_INSTALL_DIR/definitions} folder is not corrupted. If problem persists, escalate to CFT/Engineers.
10883	Invalid table join set ID {0} specified in the report {1}.	This error indicates that definition is incorrect for specified report.	This issue needs to be escalated to CFT/Engineers to get XML definition corrected.
10884	Failed to load chargeback definition XML file.	This error is due to invalid XML definition for chargeback reports.	Make sure the definition file reports.zip is not corrupted. If problem persists, escalate to CFT/Engineers.
10885	Failed to execute chargeback report {0}.	This error is due to failure to fetch chargeback variable/formulae from the database.	Log file helps in finding the exact root cause.
10887	Report {0} already exists in some other folder. Please save the report with a different name.	You cannot overwrite the report that exists in another folder. Duplicate report names are not allowed even across different folders. It should be unique across the saved report tree.	Save the report with a different name.
10888	Please select report-on parameter by editing the report as it is a mandatory field.	This error signifies that report-on parameter is mandatory field while creating custom report.	Select appropriate report-on parameter by editing the report.
10889	You do not have permission to execute the SQL-- {0}. Custom SQL allows user to fire any SQL as per choice.	This can be harmful if user fires delete/update query on OpsCenter database and thus getting corrupted. This error denotes that user do not have permission to execute the specified SQL. However he can fire update/delete on tables which he has created on OpsCenter Database.	User needs to fire only those queries which will NOT corrupt OpsCenter database
10890	Please select Y-axis report-data parameter by editing the report as it is a mandatory field.	This error signifies that Y-axis report data parameter is mandatory field while creating a custom report.	Select appropriate Y-axis report data parameter by editing the report.
10891	Please select Time-basis parameter by editing the report as it is a mandatory field.	This error signifies that Time-basis parameter is mandatory field while creating custom report.	Select appropriate Time-basis parameter by editing the report.
10892	Please select Y-axis function parameter by editing the report as it is a mandatory field.	This error signifies that Y-axis function parameter is mandatory field while creating custom report.	Select appropriate Y-axis function parameter by editing the report.
10893	Please select X-axis Report-data parameter by editing the report as it is a mandatory field.	This error signifies that X-axis Report data parameter is mandatory field while creating custom report.	Select appropriate X-axis report data parameter by editing the report.
10894	One or more selected columns are invalid. Please edit the report and remove invalid columns.	This error signifies that one or more columns in custom tabular report created are invalid. The label of the invalid columns is usually "-". Remove all such columns that are selected and re-run the report. This issue usually occurs in case of upgraded reports. If one or more columns are not mapped correctly while upgrading, then such issue occurs.	Remove all invalid columns and re-run the report.
Messages related to SCL
10901	An error has occurred. Please contact your system administrator.	This is an unknown error. This is the rarest scenario for which the root cause cannot be predicted. It is an unknown error for Opscenter.	Log will help in finding the cause.
10902	The specified master server already exists.	This error occurs when we try to add master server that already exists in OpsCenter.	Do not try to add same master server twice.
10903	Master Server with the same display name already exists.	Each master server should have a unique display name associated with it.	Try giving another display name.
10904	The specified Master Server is not a valid NetBackup Master Server.	Trying to add NetBackup media server to OpsCenter.	Try adding NBU Master Server, instead.
10905	Action not permitted. Please verify that the OpsCenter host is listed in NetBackup configuration file (host properties or bp.conf) and/or trust is established in case of NBAC.	This error occurs when you try to add a master server for which there is no entry of OpsCenter host in bp.conf file. The other problem could be insufficient trust between OpsCenter and NetBackup in NBAC case.	Make sure bp.conf file has proper entry for OpsCenter host. In case of NBAC, proper trust setup should be established.
10906	Deletion is already in progress for the specified Master Server.	This error occurs if user tries to delete Master Server for which the delete request is already in progress.	Do not perform delete operation multiple times. Wait till the previous delete operation completes.
10908	The specified Master Server could not be located. Please check if the machine is reachable and the NetBackup services are running.	This error occurs while adding a Master Server which is not reachable from the OpsCenter.	Make sure NetBackup host is reachable from OpsCenter and vice-a-versa via ping command.
10909	The specified Master Server could not be located. Please check if the machine is reachable and the NetBackup services are running.	This error occurs while adding a Master Server which is not reachable from OpsCenter and vice-a-versa. Or when NBSL service on NBU master is not running. Or there might be firewall configuration blocking OpsCenter-NetBackup communication.	Make sure NetBackup host is reachable from OpsCenter and vice-a-versa via ping command. Also check if NBSL service on NetBackup Master is running. And if firewall is configured, check TCP port 1556 is opened on OpsCenter and NetBackup machine.
10910	Unable to connect with NetBackup event channel. Please check if the NetBackup services are running.	If nbevtmgr (NetBackup Event Manager) service is not running.	Make sure that nbevtmgr is up and running on NetBackup Master Server.
10911	Unable to create consumer for the event.	This can occur, when OpsCenter Server process is out of resources. This is a symptom of OpsCenter going out of resource.	Root cause might be Object leak/Thread leak.
10912	The specified Master Server is currently disabled.	This is only in case of reconnection master server task is present and at the same time someone disabled and enabled the Master Server.	This is just a safe guard.
10913	Invalid GUID found for NetBackup Master Server.	NBSL is not getting the GUID from the NetBackup.	Check the NBSL logs.
10914	NetBackup is not initialized. Please check if the NetBackup services are running and NetBackup is correctly initialized.	NBSL is not passing the Product Name.	Ensure that NBSL service are up and running. Also verify there is no error during start-up of service.
10915	OpsCenter machine is not reachable from the specified Master Server.	This error occurs when OpsCenter is not reachable from NBSL/NetBackup Or there might be firewall configuration blocking OpsCenter- NetBackup communication. This indicates that OpsCenter is able to communicate to NBSL but reverse communication is not working.	Make sure OpsCenter is reachable from NetBackup via ping command. Also check if firewall is configured, check port 1556 is opened on NetBackup machine.
10916	The specified agent already exists.	This error is caused when we try to add same agent host, twice.	Do not add agent host multiple times.
10917	The specified data collector already exists.	Each agent is associated with one or more data collector that user can create. This error occurs when data collector with existing data collector name is created.	Save each data collector with a unique name.
10925	The specified agent is already deleted.	This occurs when one user is editing the agent and another user deleted the same agent from another session. Basically one user is working on stale data.	User will see the refreshed list by again accessing the agent home page.
10926	The specified data collector is already deleted. Come back to agent home page and user will see the refreshed list.	This occurs when one user is editing the data collector and another user has deleted the same data collector from another session. Basically one user is working on stale data.	User will see the refreshed list by again accessing the agent home page.
10927	The specified agent has been updated by other user. Please try again.	While updating agent information, there are chances that multiple users try to modify the same agent at the same time. This can make database inconsistent and hence the error message.	Try updating after some time assuming that other user has completed updating.
10928	The specified data collector has been updated by other user. Please try again.	While updating data collector information, there are chances that multiple users try to modify the same data collector at the same time. This can make database inconsistent and hence the error message.	Try updating after some time assuming that other user has completed updating.
10929	The specified platform is not supported. Agent is supported on Windows platform.	This error signifies that agent is not installed on the supported platform.	Install agent on Windows platform.
10930	Unable to connect with specified target host.	This error occurs while adding a point product host which is not reachable from OpsCenter. Or there might be firewall configuration blocking OpsCenter,-NetBackup communication.	Make sure Point Product host is reachable from OpsCenter and vice-a-versa via ping command.
10931	The specified product is not licensed.	This occurs when product is not licensed for data collection.	Install the appropriate license for point product data collection.
10932	Unable to connect with agent. Please check if the machine is reachable and the agent service is running.	This error occurs when OpsCenter is unable to connect with agent host.	Make sure that agent host is reachable from OpsCenter host and vice-a-versa.
10934	The specified data collector is disabled.	This is only in case of reconnection server task is present and at the same time someone disabled and enabled the Master Server.	This is just a safe guard.
10935	Deletion is already in progress for the specified data collector.	This error occurs when deleting the agent data collector while another delete request is already in progress.	Wait till the previous delete request is completed.
10936	The specified install or volume directory is invalid.	This error occurs when an invalid path to "Volume Manager Directory" or "Install Directory" is specified while defining Advanced Data Collection Properties in Add Master Server.	While defining advanced data collection properties, make sure you specify proper path of NetBackup install directory and volume manager directory.
10937	The specified install directory of the product does not exist.	This error occurs when "Install Directory" path (under Configuring Advanced data collection properties of Add Master Server) is incorrect or does not exist on the NetBackup host.	Make sure NetBackup is installed on the host and specify proper path of NetB ackup home directory.
10938	The specified volume directory of the product does not exist.	This error occurs when "Volume Manager Directory" path (under Configuring Advanced data collection properties of Add Master Server) is incorrect or does not exist on the NetBackup host.	Correct the Remote Admin Console installed path (installed on Agent box). Or install the NetBackup Remote Admin Console on the Agent.
10939	The specified username or password is not valid.	This occurs when UserName/Password is not valid to connect to Master Server through BPJava.	Provide correct user name and password of Master Server.
10943	A database error has occurred. Please contact your system administrator.	This error occurs when any database related exception occurs.	Log file helps in finding the exact root cause.
10944	Deletion is in progress for the same Master Server. Connection to this master server will occur once deletion is completed.	This error occurs when a Master Server delete request is in progress and user tries to add/locate Master Server at the same time.	Before you add/locate Master Server, make sure that the previous request for delete Master Server is complete.
Messages related to Schedules
20800	Failed to get the next schedule time for schedule {0}. The schedule information in the database might be corrupted. Please re-create the schedule and try again.	For each schedule, the next schedule time is calculated based on the type of schedule (daily, weekly, monthly, etc). The problem can occur when data for schedule in database is corrupted.	You can delete the schedule for which you are facing the problem and re-create it so that proper data is stored for schedule. Such problem may occur in case of upgraded schedule where data is not migrated properly for schedule.
20801	Failed to execute the query at the database.	This error can occur when Time schedule crud operations such as add/delete/update/fetch are performed. This error is due to a problem at the database level when the corresponding query is fired.	Log helps in finding the cause of failure at the database level.
20802	Schedule cannot be deleted as it is referred in one or more report schedules.	When Time schedule is referred by one or more Report Schedules, then user cannot delete the Time schedule since it is in use.	If you want to delete the Time Schedule, make sure it is not referred in any of the Report Schedule.
20803	Schedule {0} already exists. Please save the schedule with a different name.	You cannot save a Time schedule with same name that already exists.	Save the schedule with a different name.
Messages related to Chargeback
20850	Failed to load the chargeback definition file {0}. Chargeback definitions are stored in XML format.	If any problem exists in XMLfile, then this error message is shown.	Make sure reports.zip file present in {OPS_INSTALL_DIR}/definitions folder is not corrupt. If problem still persists, escalate to CFT/Engineers.
20851	Failed to execute the query at the database.	This error can occur when chargeback crud operations such as add/delete/update/fetch chargeback variable, chargeback formula or chargeback currency are performed. This error is due to problem at the database level when we fire the corresponding query.	Log helps in finding the cause of failure at the database level.
20852	Cannot delete the formula as it is referred in one or more chargeback reports.	Chargeback formula created can be used in chargeback based reports. If such reports are saved with a given formula, then that formula cannot be deleted until we remove the reference of the formula from all the saved reports.	Before you delete chargeback formula, make sure you remove all references to the formulae from all saved report.
20853	Cannot delete the variable as it is referred in one or more chargeback reports or chargeback formulae.	Chargeback variable created can be used in chargeback based reports and in chargeback formula. If such reports/formulae are saved with a given variable, then that variable cannot be deleted until we remove the reference of the variable from all saved reports/formulae.	Before you delete a chargeback variable, make sure you remove all references to the variable from all saved report and all saved formulae.
20854	Chargeback variable {0} already exists. Please save the variable with a different name.	This error occurs due to saving chargeback variable with the same name that already exists.	Save the variable with a different name.
20855	Chargeback formula {0} already exists. Please save the formula with a different name.	This error occurs due to saving chargeback formula with the same name that already exists.	Save the formula with a different name.

OpsCenter Error Messages

Feedback

Feedback