In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary

  • Configuration Exceptions
    These exceptions relate to errors which may occur while configuring QXI. These exceptions are displayed on the UI when configuring the system; details are available in outbound-ui.log and qdocInstall.log.

    Configuration Exceptions
     
    Exception Code
    Description
    Notes
    ConfigurationException001
    Receiver specified is not valid
    While adding a new schema, the receiver assigned does not exist.
    ConfigurationException002
    Receiver directory not present
    While deleting a receiver, the receiver directory does not exist.
    ConfigurationException003
    Reloading managers failed
    QXtend launches managers that carry out specific functions, for example, Queue Manager to allow QDoc processing through a queue and Configuration Manager to configure QXI. If QXI is restarted using the Tomcat admin functionality or the restart option in QXtend, these managers are reloaded. If some configuration has changed prior to reloading which invalidates any of the managers, then the QXtend UI link displays red and this exception appears in qdocInstall.log with more information.
    ConfigurationException004
    Schema descriptor info incorrect
    When modifying a schema, the schema details are retrieved from a configuration file. If the details are unavailable, this error is raised. This occurs if the configuration file is directly modified and that record deleted. Review the configuration for this schema and reinstall if necessary.
    ConfigurationException005
    Events directory not found
    While adding or updating a schema, the events directory does not exist.
    ConfigurationException008
    Events file not found
    When adding or modifying a schema, the events file must exist in the specified location. If not, this exception is raised.
    ConfigurationException009
    Error occurred configuring the system
    An exception occurred on QXtend startup related to the configuration of QXtend. The QXtend link displays red. The error is logged in qdocInstall.log.
    ConfigurationException010
    Error getting API configuration details
    This error displays on the UI if an error occurs removing API support for a specified schema. This should only occur if the configuration files were manually updated. Contact the system administrator or QAD Support.
    ConfigurationException011
    Duplicate entries for an API
    QADQdocs.xml or implementationQdocs.xml were incorrectly modified. View logs for details and contact the system administrator or QAD Support.
    ConfigurationException012
    Referenced node missing in descriptor file
    See ConfigurationException004.
    ConfigurationException013
    Error loading configuration details
    An error occurred loading a configuration file. The file may have been manually moved or deleted, or manually updated with invalid data. View logs for details. Also verify the path and file permissions.
    ConfigurationException014
    Schema files do not exist in specified directory
    While adding or deleting a schema, the schema files cannot be located. Verify path and permissions.
    ConfigurationException016
    File already exists
    While creating or modifying a schema, the descriptor file already exists. Verify path and permissions.
    ConfigurationException017
    Problem writing to new file
    While adding a new schema, the schema files already exist.
    ConfigurationException018
    Duplicate nodes exist in descriptor file
    You cannot create an entry in a descriptor file for a node that already exists.
    ConfigurationException019
    Schema directory not found
    While adding a schema, the schema directory does not exist or is read-only. Verify path and permissions.
    ConfigurationException020
    Deleting receiver directory failed
    While deleting a receiver, the write to the backup directory failed.
    ConfigurationException021
    Receiver name cannot be null
    While adding a receiver, the receiver name is blank or null. The null state may be raised if an error occurs recovering the value from the UI. Refresh and restart.
    ConfigurationException022
    Version not installed
    While adding a receiver, the schema directory does not exist, could not be created, or the receiver version is blank.
    ConfigurationException024
    Receiver already supported
    You cannot add a new receiver that already exists for that version. Specify a different receiver or edit existing receiver.
    ConfigurationException025
    Receiver details not found
    While deleting a receiver, cannot find the receiver node in receivers.xml.
    ConfigurationException026
    Parsing descriptorInfo failed
    Building a hashmap of nodes from a descriptor file failed. Verify that the file exists.
    ConfigurationException027
    Updating descriptorInfo failed
    This error occurs while creating a new receiver structure, path directory, or subdirectory for requests. It can also occur while updating global or receiver descriptor files with a new node.
    ConfigurationException028
    Specified configuration file not found
    The configuration files qxtendalertconfig.xml, qxtendalertgroupconfig.xml, and qxtendalertuserconfig.xml are missing from
    WEB-INF/emailAlerts. Replace the files.
    ConfigurationException029
    Alert recipient must be assigned a value
    The Alert Recipient field is blank. Enter a valid e-mail address.
    ConfigurationException030
    Alert recipient’s
    e-mail address is invalid
    The specified e-mail address uses an incorrect format. The correct format is username@domain.
    ConfigurationException031
    Alert recipient already exists
    The alert recipient entered already exists. Enter a different recipient.
    ConfigurationException032
    A problem occurred when updating the configuration file
    The configuration files qxtendalertconfig.xml, qxtendalertgroupconfig.xml, and qxtendalertuserconfig.xml cannot be updated. Check that the
    WEB-INF/emailAlerts directory exists and file permissions.
    ConfigurationException033
    Cannot map schema and XML files to ProDataGraph
    Check the log file.
    ConfigurationException035
    Cannot create menu XML
    Check the log file.
    ConfigurationException036
    Problem occurred when reading XML
    The configuration files qxtendalertconfig.xml, qxtendalertgroupconfig.xml, and qxtendalertuserconfig.xml are not well-formed or contain incorrect data. Check the files.
    ConfigurationException037
    Alert group must be assigned a value
    The Alert Group field is blank. Enter an alert group name.
    ConfigurationException038
    Alert group already exists
    There is already an alert group with the alert group name just entered. Enter a different name.
    ConfigurationException039
    Cannot find alert receiver
    The alert receiver specified may have been deleted or modified by another user. Refresh the screen to get the latest information.
    ConfigurationException040
    Domain name must be assigned a value
    The Alert Domain field is empty. Enter a domain name.
    ConfigurationException041
    Domain name already exists
    There is already a domain using the domain name just entered. Enter a different name.
    ConfigurationException042
    Problem occurred removing receiver in alert
    The receiver may have been deleted or modified by another user. Refresh the screen to get the latest information.
    ConfigurationException043
    Problem occurred creating a session to send mail
    There was a JavaMail error.
    ConfigurationException044
    Problem occurred creating a mime to send mail
    There was a JavaMail error.
    ConfigurationException045
    Problem occurred setting mail subject
    The e-mail subject is incorrect. If the alert group is using the default message configuration, check the qxtendalertconfig.xml file in the WEB-INF/emailAlert directory. If it is not using the default message configuration, check the e-mail subject setting in the Group Configuration Parameters page.
    ConfigurationException046
    Problem occurred setting mail body
    The e-mail body is incorrect. If the alert group is using the default message configuration, check the qxtendalertconfig.xml file in the WEB-INF/emailAlert directory. If it is not using the default message configuration, check the e-mail body setting in the Group Configuration Parameters page.
    ConfigurationException047
    Problem occurred adding mail attachment
    Cannot add the attachment. Check the log for more details.
    ConfigurationException048
    Problem occurred setting the e-mail “From:” in the mail header
    The e-mail “From:” is incorrect. Check the setting in the Email Configuration Parameters screen.
    ConfigurationException049
    Problem occurred setting the
    e-mail “To:” in the mail header
    The e-mail “To:” is incorrect. Check the setting in the Email Configuration Parameters screen.
    ConfigurationException050
    Problem occurred sending mail
    An error occurred when sending the
    e-mail. Check the SMTP setting, e-mail body, e-mail subject, and attachments.
    ConfigurationException051
    SMTP server must be assigned a value
    The SMTP Server field is blank. Enter the name of an SMTP server.
    ConfigurationException052
    The “From:”
    e-mail address is invalid
    The specified “From:” e-mail address is incorrect. The correct e-mail address format is username@domain.
    ConfigurationException053
    Cannot find alert domain
    The specified alert domain may have been deleted or modified by another user. Refresh the screen to get the latest information.
    ConfigurationException055
    SMTP settings are invalid
    The SMTP settings are incorrect. Check the SMTP server, port number, and authentication details in the Email Configuration Parameters screen.
    ConfigurationException056
    Recipient must be assigned a value
    The Alert Recipient field is blank. Enter a valid e-mail address.
    ConfigurationException057
    Recipient’s
    e-mail address is invalid
    The format of the e-mail address entered for the recipient is incorrect. The correct format is username@domain.
    ConfigurationException058
    No recipients
    There are no recipients specified for the
    e-mail. Check the alert recipients setting in the Group Configuration Parameters screen.
    ConfigurationException059
    The “From:” must be assigned a value
    The Email From field is blank. Enter a valid e-mail address.