Messages

Here you can find the most frequent messages the GISconnector for Excel returns. Additionally you will receive a description and a possible solution for the message.

Message text	Description & Solution
ArcGIS licence could not be called up.	Description Check in the ArcGIS Administrator (Windows 7: Start → All Programs → ArcGIS → ArcGIS Administrator; Windows 8: Search → Apps → ArcGIS Administrator), whether a licence is available for the chosen software product (Advanced, Standard, Basic). Solution If applicable, choose a different sofware product, or a different licence server (in a case of concurrent licences).
The table / feature-class is blocked by a different process.	Description There is an ArcGIS block (common or exclusive block) that is preventing access to the data. A possible scenario for this can be when · the same data are being accessd in a different MXD · the data are being displayed in ArcCatalog in the preview · a different user is editing the data or requesting it Solution Ensure that your application has exclusive use of the data.
The file "<Value>" has an invalid format and cannot be loaded.	Description With the creation of each connection, a configuration file is generated in which the connection characteristics are saved. The configuration file of the chosen connection is damaged or has been manually altered. Solution Delete the connection and create a new one.
The creation of the data set has failed.	Description A unspecified error has occured. Solution Please contact your distribution partner or GI Geolabs GmbH.
The column name <Value> occurs more than once in the table. Column names must be distinct within a table.	Description Field names must be distinct within a table. For example, it is not permitted for two columns both to have the name "ABC". Solution Rename one of the columns.
Inconsistent number format in the column <Value>.	Description All cells of one column in the connected Excel spreadsheet must have the same format (e.g. text). In the case of columns with cells containing numbers, all such cells must have numbers with the same number of places after the decimal point. For columns with cells that are formatted with the date, the date format must be the same in all cells. Solution Adapt the format of the column(s) appropriately.
Invalid number format in the column <Value>.	Description The format that has been defined for this column cannot be interpreted as text, number or date. Generally this error message occurs with number- and date formats. Solution Adapt the format of the column appropriately.
Invalid format for title in column <Value>.	Description To enable a correct functioning of the GISconnector, the column title must be defined as text or as standard. Solution Change the format of the column title appropriately.
The cell content of <Value> is not compatible with the format of the table column.	Description The contents of the cells clashes with the format of the column. Cells in Excel, for example, can be defined as a number though the cell can contain text. Solution Make corrections to the contents of the cells such that they fit the format of the cell.
The primary key <Value> cannot be applied to the table.	Description The GCEX_ID column contains no distinct key values. Values that are in duplicate, missing or negative are not permitted. Solution You can either rework this column (not recommended) or carry out a new Export to generate this column correctly.
The cell <Value> is not a valid table origin.	Description On setting up a connection, no table can be found at the assigned cell. Solution Choose a different table origin.
The table schema contains invalid columns.	Description All columns that are managed by GISconnector for Excel must meet with specific conventions, especially those for the creation of new fields submitted by Esri. Solution Check the column names for invalid characters or formats.
Duplicated column name	Description Field names must be distinct within a table. For example, it is not permitted for two columns both to have the name "ObjectID". Solution Rename one of the columns.
Invalid character string in column name	Description Depending on the data format used (Shapefile, Geodatabase, etc.) only specific characters are permitted in column titles. Field names must also begin with a letter and may not contain either spaces or reserved words. Further information can be found in the ArcGIS Help. Solution Change or delete invalid characters in the column name (e.g., .: ! " § $ % & / ( ) = ? ´ ´ * ' ' ; : , . -). Replace each with an underscore.
Invalid length of the column name	Description Depending on the data format used (Shapefile, Geodatabase, etc.), column titles may only contain a specific number of characters. Further information can be found in the ArcGIS Help. Solution Field names are restricted to a length of 64 characters for File- and Personal-Geodatabases, and to 10 characters in dBASE/shape-file.
Reserved SQL definition	Description Depending on the data format used (e.g., Personal-Geodatabase), certain definitions are reserved and may not be used as column titles. Further information can be found in ArcGIS Help. Solution Reserved definitions are: Text, Left, Right, Upper, Lower, etc.
Unknown error	Solution Without further information we regret that no solution can be offered.
No product licence could be called up.	Description Check in the Geolabs Administrator whether the GISconnector for Excel has been authorized. Solution Go to the license management chapter and proceed as described.
The primary key column <Value> was not found in the table.	Description The GCEX_ID column is missing. Solution Carry out the Export again to generate the column correctly.
A cell in the Excel spreadsheet <Value> is currently being edited. Please finish the editing process before proceeding.	Solution If a cell in Excel is currently being edited, this can be recognized by the active icons in the input bar: If the data entry has been concluded (either click on button or select a different cell), these buttons are no longer displayed:
The Excel worksheet <Value> cannot be edited.	Description An attempt is being made to access a write-protected Excel table. Solution Close the Excel workbook and open it without write-protection. Check wether other users in your network are accessing this workbook at the same time. If so, ask them to close the file.
The table name <Value> already exists.	Description Within a File- or Personal-Geodatabase, the name of a feature-class or table may only occur once (irrespective of saving within a feature-dataset). The same applies in a directory with dBase-tables. Solution Use a different table name.
The workspace <Value> could not be opened.	Description The ArcGIS workspace specified for this connection in the Edit connection settings-dialogue could not be opened Solution Verify that the ArcGIS workspace is available.
A new task can not be started while another task is still running.	Description The GISconnector is currently not able to perform multiple operations simultaneously. Solution Please wait until the GISconnector has completed the first task and start the next one afterwards.
The workbook <Value> does not exist.	Description The Excel workbook which was specified for this connection in the Edit connection settings-dialogue is not available. Solution Please correct the path to the workbook in the “Edit connection settings“.
The worksheet <Value> does not exist in the workbook <Value>.	Description The Excel worksheet which was specified for this connection in the Edit connection settings-dialogue is not available. Solution Please select the worksheet in the Edit connection settings-dialogue.
The feature-class/table could only edited with an edit session	Description For certain feature-classes or tables, f.e. if they are connected to a relationship class, data can only be transferred during an editing session. Solution Start an editing session and restart the operation.
The data types of the following columns are not identical:	Description To enable a correct functioning of theGISconnector for Excel, the columns that are managed by the GISconnector must have the same data types in ArcGIS and in Excel. Solution Ensure that the data types in ArcGIS and Excel are the same.
The review of the tables resulted in an error:	Solution Take note of the Error message received and follow the suggestion for the solution given by the corresponding error message.
The review of the tables resulted in errors. The following errors occurred:	Solution Take note of the Error messages received and follow the suggestions for the solutions given by the corresponding error messages.
The GCEX_ID has an invalid format (<Value>), it must be a whole number (integer).	Description The GISconnector requires a GCEX_ID for all tasks and this must be available in ArcGIS and in Excel. The data-type for this GCEX_ID must be an integer (short or long integer). Caution: Short integer permits only value ranges from -32.768 to 32.767. Solution Change the format of the GISconnector-ID appropriately.
The GCEX_ID could not be found:	Description The GISconnector for Excel requires a GCEX_ID for all tasks and this must be available in ArcGIS and in Excel. The data-type for this GCEX_ID must be in integers (short or long integer). Caution: Short integer permits only value ranges from -32.768 to 32.767. Solution Repeat the Export so that the GCEX_ID is automatically generated.
The dataset <Value> in workspace <Value> could not be opened.	Description The directory of the feature-class/table is stored in the connection properties of a connection. If this directory is deleted or renamed, the GISconnector for Excel can no longer access it. Solution Enter a new location of the feature-class/table into the connection properties.
Table data are loaded. Data could could not be loaded from the data source. ...defective network connection.	Description This error message appears due to an error in ArcGIS. If a feature-class and a stand-alone table are connected to each other and a field is then deleted in the stand-alone table, ArcGIS is no longer able to access the attribute table. Solution Remove the connection and then recreate it.
At least one column could not be added/deleted because the target table is part of one or multiple joins.	Description The reason for this mistake is a limitation of ArcGIS. Solution Remove the joins or close all map documents (MXDs) containing those joins if you want to apply schema changes to the table. You have the choice to continue without the schema changes and just transfer data modifications.