Tool errors and warnings: 976-1000 |
|
|
Release 9.3
Last modified April 24, 2009 |
|
Note:
This topic was updated for 9.3.1.
| Error code: | 000976: A non-zero value for Number of Neighbors is required for this conceptualization of spatial relationships. |
| Description: | Invalid entry for the Number of Neighbors parameter. Expecting a non-zero, positive number. |
| Solution: | Specify an integer value greater than zero for the Number of Neighbors parameter, or else select a different option for the Conceptualization of Spatial Relationships parameter. |
| Error code: | 000977: Error reading spatial weights header information from <value>. |
| Description: | Problems were encountered while reading the spatial weights matrix file. The file could not be processed. |
| Solution: | Rebuild the spatial weights matrix file using the Generate Spatial Weights Matrix or Generate Network Spatial Weights tools, and then re-run the analysis. |
| Error code: | 000978: Unexpected error creating ellipse geometry. |
| Description: | An unexpected error occurred while constructing the ellipse feature. |
| Solution: | Try running the analysis again. If the problem continues, please contact Tech Support. |
| Error code: | 000979: Cannot copy between different workspaces. |
| Description: | An unexpected error occurred trying to copy data to the output workspace. |
| Solution: | Make sure you have write access to the output workspace, that the disk is not full, and that no other application is holding the output file or folder. |
| Error code: | 000980: Domain value <value> description <value> already exists as description <value>. |
| Description: | The specified coded value already exists within the workspace. The field representing the code value may also containing duplicate values. |
| Solution: | Check for duplicates between the input table and the new code values that will be imported and existing code value already in the geodatabase. Also, check for duplicate values in the field in the input table that will be used for the code values.
Learn more about attribute domains |
| Error code: | 000981: The <value> conceptualization of spatial relationships is inappropriate for data measured in a Geographic Coordinate System. |
| Description: | For accurate distance measurements you should always project your data prior to analysis. The option you've selected for the Conceptualization of Spatial Relationships is invalid for data measured in a Geographic Coordinate system. |
| Solution: | Project your data to a Projected Coordinate System and re-run the analysis. Alternatively, set the output coordinate system to project your data on the fly. |
| Error code: | 000982: The spatial reference for the spatial weights matrix (<value>) does not appear to match the defined output coordinate system (<value>). |
| Description: | The spatial reference associated with the spatial weights matrix file is different than the spatial reference specified by the output coordinate system. This could potentially lead to unexpected results. Spatial weights matrix files are tied to the input feature class, the Unique ID field, and to the output coordinate system settings used when the .swm file was created. |
| Solution: | To avoid confusion and to ensure accurate results, consider projecting your input feature class to match the output coordinate system settings and then recreating the spatial weights matrix file prior to running your analysis. |
| Error code: | 000983: The specified number of points could not be created in all cases due to restrictions from the minimum allowed distance. |
| Description: | This error occurs when the feature cannot contain the specified number of points while also maintaining the minimum allowed distance between points. When the constraining feature class is a polygon, or when using a constraining rectangle, the tool will not always try to place the maximum number of points, as this would greatly slow processing speed. |
| Solution: | Try reducing the number of points, the minimum allowed distance, or a combination of the two. |
| Error code: | 000984: The spatial reference for the input feature class (<value>) does not appear to match the defined output coordinate system (<value>) |
| Description: | The spatial reference associated with the spatial weights matrix file does not match the spatial reference for the input feature class. This could lead to unexpected results. Spatial weights matrix files are tied to the input feature class, the Unique ID field, and to the output coordinate system settings used when the .swm file was created. |
| Solution: | To avoid confusion and to ensure accurate results, consider projecting your input feature class to match the output coordinate system settings and then recreating the spatial weights matrix file prior to running your analysis. |
| Error code: | 000985: The spatial reference used to create the spatial weights matrix file does not match that of the input feature class. |
| Description: | The spatial reference associated with the spatial weights matrix file does not match the spatial reference for the input feature class. This could lead to unexpected results. Spatial weights matrix files are tied to the input feature class, the Unique ID field, and to the output coordinate system settings used when the .swm file was created. |
| Solution: | To avoid confusion and to ensure accurate results, consider projecting your input feature class to match the output coordinate system settings and then recreating the spatial weights matrix file prior to running your analysis. |
| Error code: | 000986: <value> contains the full list of non simple features. |
| Description: | When more than 25 geometry problems are encountered, instead of printing more messages to the screen this message will be printed. This is done to avoid having very large number of messages in the geoprocessing results which can lead to slowdown in application startup and shutdown. |
| Solution: | This is an informational message, no further action is necessary. As stated in the message, the txt file contains the full list of geometry problems encountered, and what action was taken on each one. |
| Error code: | 000987: Visually self intersecting geometry was created for feature <value>. |
| Description: | Using the specified option, a self-intersecting geometry was detected and turned into valid multipart geometry. The feature may still look self-intersecting when displayed |
| Solution: | Manual editing would be necessary to reconstruct the feature and to avoid self-crossing. |
| Error code: | 000988: A raster field is not a valid field type in a raster attribute table. |
| Description: | Raster fields are not a valid field type in raster attribute tables. |
| Solution: | A raster field cannot be added to a raster attribute table. Check the help for AddField for a list of appropriate field types.
Learn more about raster datasets as attributes |
| Error code: | 000989: Python syntax error: <value> |
| Description: | The code block used by the Calculate Field or Calculate Value has a syntax error. This error message provided will list the specific Python syntax error. |
| Solution: | This error code covers a number of Python syntax errors.
Example: Parsing error : unindent does not match any outer indentation level (line 3) The above is a Python syntax error. Line 3 has invalid indentation. For specific Python issues, consult the Python help for more information, normally listed under c:\Python24\Doc, or consult the Calculate Field or Calculate Value help for more information on these tools. |
| Error code: | 000990: <value> is already joined |
| Description: | The same table cannot be joined to the same layer more than once at a time. |
| Solution: | Remove the joined table using the Remove Join tool and then re-join the table using the Add Join tool. |
| Error code: | 000991: Scale Factor must be greater than zero. |
| Description: | The scale factor is not greater than zero. Rescale tool requires the scale factors for both x and y be greater than zero |
| Solution: | Enter value greater than zero for scales. |
| Error code: | 000992: You cannot administer 9.2 or older versions of ArcGIS Server using ArcGIS Desktop version 9.3. |
| Description: | Caching tools require administrative access to the ArcGIS Server. You cannot adminster 9.2 or older versions of ArcGIS Server using the ArcGIS Desktop version 9.3 and therefore you will see this message. |
| Solution: | Use ArcGIS Desktop version 9.2 to work with services on ArcGIS Server version 9.2 |
| Error code: | 000995: Resampling failed. The reason could be that the specified cell size is too large or too small. |
| Description: | The cell size that was specified in the is either too large or too small. |
| Solution: | Use a more moderate cell size in the resampling operation. |
| Error code: | 000996: Cell size must be greater than zero. |
| Description: | The cell size specified was a negative number. |
| Solution: | Enter a positive value for the cell size. |
| Error code: | 000997: The 'Reduce Study Area' Boundary Correction Method is invalid with a 'User Provided Study Area'. |
| Description: | The 'Reduce Study Area' Boundary Correction option should not be used unless the Study Area Method is Minimum Enclosing Rectangle. |
| Solution: | Use another boundary correction method, or select Minimum Enclosing Rectangle for the Study Area Method. |
| Error code: | 000998: Barriers are too complex. |
| Description: | The outline of the barriers are too complex. |
| Solution: | Eliminate or simplify some of the barrier features. |
| Error code: | 000999: Failed to get raster. Please check if the input parameters is correct. |
| Description: | The input raster is empty or invalid. |
| Solution: | Select a valid raster as input. |
| Error code: | 001000: <value>: Field <value> does not exist. |
| Description: | The field name specified does not exist within the table. |
| Solution: | Check in the table for existing field names and update the field used as appropriate. |