CiscoSecure GRS System Messages

This appendix contains a list of system messages, an explanation of their meanings, and a recommended action to resolve any problems.

Error Message    Cannot connect to local ACS.

Explanation    CiscoSecure GRS cannot talk to the local ACS.

Recommended Action    Make sure the local ACS is running before starting CiscoSecure GRS.

Error Message    Cannot get read lock for the data store: Some other process is writing to the data store.

Explanation    You tried to run one of the CiscoSecure GRS utilities with the GUI running.

Recommended Action    Exit the GUI before running the utilities.

Error Message    Cannot open file for reading: filename.

Explanation    CiscoSecure GRS is unable to open the file named for reading.

Recommended Action    Check the file's read permissions.

Error Message    Cannot open file for writing: filename.

Explanation    CiscoSecure GRS is unable to open the file named for writing.

Recommended Action    Check the file's write permissions.

Error Message    Config file name is NULL.

Explanation    The CiscoSecure GRS file name is empty.

Recommended Action    Make sure GRSHOME is set properly and the grs.ini file exists in the $GRSHOME/etc directory.

Error Message    Data store type not known.

Explanation    The data store type is not specified.

Recommended Action    Make sure that either an Oracle database or a flatfile data store is specified in the grs.ini file.

Error Message    Error in getting the summary information.

Explanation    CiscoSecure GRS could not get the summary information for the domain, NAS, or translation in the GUI.

Recommended Action    Restart the GUI.

Error Message    Error initializing the flatfile data store. Refer to log.

Explanation    The flatfile data store cannot be initialized. There are several possible causes for this message.

Recommended Action    See the grsdb.err file in the $GRSHOME/logfiles directory.

Error Message    Error opening log file.

Explanation    The log file cannot be opened for writing or reading.

Recommended Action    Check the read/write permissions in the $GRSHOME/logfiles directory. Check to make sure you have enough free disk space for the log files to be created.

Error Message    Error parsing the grs.spc file.

Explanation    The grs.spc file is corrupted.

Recommended Action    Copy the $GRSHOME/etc/.grsspc.bak file to $GRSHOME/etc/grs.spc and retry the operation.

Error Message    Error parsing the MwFieldInfo vector.

Explanation    The grs.spc file is corrupted.

Recommended Action    Copy the $GRSHOME/etc/.grsspc.bak file to $GRSHOME/etc/grs.spc and retry the operation.

Error Message    Error parsing the specification file.

Explanation    The grs.spc file is corrupted.

Recommended Action    Copy the $GRSHOME/etc/.grsspc.bak file to $GRSHOME/etc/grs.spc and retry the operation.

Error Message    Error parsing the .spc file.

Explanation    The grs.spc file is corrupted.

Recommended Action    Copy the $GRSHOME/etc/.grsspc.bak file to $GRSHOME/etc/grs.spc and retry the operation.

Error Message    Error retrieving AttributeID from: tablename.

Explanation    There is an internal JDBC error.

Recommended Action    If you are using an Oracle database, make sure the Oracle server is running. If you are using a flatfile data store, restart CiscoSecure GRS.

Error Message    Error retrieving data.

Explanation    There is an internal ODBC error.

Recommended Action    If you are using an Oracle database, make sure the Oracle server is running. If you are using a flatfile data store, restart CiscoSecure GRS.

Error Message    Error rolling back flatfile data store. Refer to the log file.

Explanation    An attempt to write to the flatfile data store failed.

Recommended Action    See the log file for an explanation and perform the necessary action.

Error Message    Failed to load the properties.

Explanation    The grs.ini file cannot be read properly.

Recommended Action    Make sure $GRSHOME is set properly and the read permission is set properly for the grs.ini file in the $GRSHOME/etc directory.

Error Message    Fatal error. Error initializing the flatfile data store.

Explanation    The flatfile data store cannot be initialized. There are several possible causes for this message.

Recommended Action    See the grsdb.err file in the $GRSHOME/logfiles directory and perform the necessary action.

Error Message    Fetch Data

Explanation    There is an internal JDBC error.

Recommended Action    If you are using an Oracle database, make sure the Oracle server is running. If you are using a flatfile data store, restart CiscoSecure GRS.

Error Message    File name: filename is not recognized.

Explanation    The file indicated by filename passed an invalid argument to grsfile2db.

Recommended Action    Check for valid usage of filename. Enter grsfile2db -h.

Error Message    grs.spc file is corrupted. Fatal error.

Explanation    The grs.spc file is corrupted.

Recommended Action    Copy the $GRSHOME/etc/.grsspc.bak file to $GRSHOME/etc/grs.spc and retry the operation.

Error Message    grsdbadd: syntax error. Illegal command-line option.

Explanation    The options entered for grsdbadd are incorrect.

Recommended Action    Check for valid usage of grsdbadd. Enter grsdbadd -h.

Error Message    Mismatch between the record classes and the schema.

Explanation    The grs.spc file is corrupted.

Recommended Action    Copy the $GRSHOME/etc/.grsspc.bak file to $GRSHOME/etc/grs.spc and retry the operation.

Error Message    No authorization to modify the table.

Explanation    The flatfile data store file does not have write permission enabled.

Recommended Action    Change the write permission of the flatfile data store file in the $GRSHOME/etc/.working directory.

Error Message    No authorization to read the table.

Explanation    The flatfile data store file does not have read permission enabled.

Recommended Action    Change the read permission of the flatfile data store file in the $GRSHOME/etc/.working directory.

Error Message    No matching record found.

Explanation    The particular record does not exist.

Recommended Action    Check your command line options.

Error Message    No print command configured.

Explanation    The print command has not been configured.

Recommended Action    Use the Properties tab in the GUI to configure the print command.

Error Message    Stripping string must be substring of domain or ENTIRE DOMAIN

Explanation    The string you entered in the GUI Properties tab is not a configured domain or a subset of a configured domain.

Recommended Action    Enter the correct string or configure the domain correctly.

Error Message    Unable to create the acs table.

Explanation    Unable to create the table in the Oracle database.

Recommended Action    Make sure the Oracle username and password are correct and the Oracle server is running.

Error Message    Unable to create the attribute table.

Explanation    Unable to create the table in the Oracle database.

Recommended Action    Make sure the Oracle username and password are correct and the Oracle server is running.

Error Message    Unable to create the domain table.

Explanation    Unable to create the table in the Oracle database.

Recommended Action    Make sure the Oracle username and password are correct and the Oracle server is running.

Error Message    Unable to create the ipaddressrange table.

Explanation    Unable to create the table in the Oracle database.

Recommended Action    Make sure the Oracle username and password are correct and the Oracle server is running.

Error Message    Unable to create the IP pool table.

Explanation    Unable to create the table in the Oracle database.

Recommended Action    Make sure the Oracle username and password are correct and the Oracle server is running.

Error Message    Unable to create the NAS table.

Explanation    Unable to create the table in the Oracle database.

Recommended Action    Make sure the Oracle username and password are correct and the Oracle server is running.

Error Message    Unable to create the vendor table.

Explanation    Unable to create the table in the Oracle database.

Recommended Action    Make sure the Oracle username and password are correct and the Oracle server is running.

Error Message    Unable to get GRSHOME.

Explanation    The GRSHOME variable is not set.

Recommended Action    Set the GRSHOME variable. See your UNIX documentation for more information.

Error Message    Unable to get an OPERATION lock.

Explanation    Another application is trying to write to the data store.

Recommended Action    Ensure that no other applications, such as the GRS GUI or Command Line Utilities, are trying to modify the datastore.

Error Message    Unable to get a WRITE lock.

Explanation    Another application has locked the data store and is preventing CiscoSecure GRS from writing to it.

Recommended Action    Ensure that no other applications, such as the GRS GUI or Command Line Utilities, are trying to modify the datastore.

Error Message    Unable to load the JdbcOdbc driver.

Explanation    LD_LIBRARY_PATH is not set properly.

Recommended Action    Source the $GRSHOME/etc/grs.sh file.

Error Message    Unable to print.

Explanation    Unable to print the summary from the GUI.

Recommended Action    Make sure the printer name is correct.