Tool errors and warnings: 651-675 |
|
|
Release 9.3
Last modified April 24, 2009 |
|
Note:
This topic was updated for 9.3.1.
| Error code: | 000652: Error reading output spatial reference |
| Description: | There has been an error reading the output spatial reference. |
| Solution: | Ensure that there is a correct spatial reference for the dataset that you are importing to. |
| Error code: | 000653: Different spatial references in input |
| Description: | The input annotation classes have different spatial references. In order to import into the same annotation feature class the inputs must have the same spatial reference. |
| Solution: | Import the annotation into different feature classes or reproject the annotation into the same spatial reference system and then import. |
| Error code: | 000654: Only one raster field may be used on a feature class or table |
| Description: | A feature class or table can have a maximum of one raster field. |
| Solution: | Either make use of the existing raster field, or delete the existing one prior to adding a new one. |
| Error code: | 000656: A Shapefile is not supported by this tool. |
| Description: | The output of Create Replica Footprints must be a geodatabase feature class. Shapefiles are not supported. |
| Solution: | Ensure the output workspace represents either a personal, file, or ArcSDE geodatabase. |
| Error code: | 000658: Existing output must be an annotation feature class |
| Description: | A non-annotation feature class has been selected to append into. |
| Solution: | Select an annotation feature class. |
| Error code: | 000659: The replica does not exist in this geodatabase. |
| Description: | The replica does not exist in the specified geodatabase. |
| Solution: | Ensure you have correctly spelled the replica name. Also, ensure you have selected the correct replica geodatabase, and the replica specified exists and is valid. Use the replica manager to view all the replicas in a geodatabase. |
| Error code: | 000660: Invalid input: feature class is within a feature dataset. |
| Description: | The input specified is a feature class contained within a feature dataset. This is not a valid input. |
| Solution: | Individual feature classes in a dataset cannot have their spatial reference upgraded. All the contents of the feature dataset get upgraded at once when the dataset is specified as the inputof the Upgrade Spatial Renference tool. |
| Error code: | 000661: Invalid input. Input Dataset must be low precision. |
| Description: | The input of the Upgrade Spatial Renference tool must be a low precision feature class, feature dataset, or raster catalog contained in a high precision geodatabase. |
| Solution: | Select an input dataset that is low precision. For more information see the documentation for the Upgrade Spatial Renference tool, or the help on Migrating to high precision. |
| Error code: | 000662: Contains a duplicate annotation feature class. |
| Description: | A duplicate annotation feature class has been added to the list of inputs. |
| Solution: | Remove the duplicate annotation feature class from the list of inputs. |
| Error code: | 000663: Empty parameter |
| Description: | No input annotation feature classes have been specified. |
| Solution: | Select annotation feature classes to append. |
| Error code: | 000664: Invalid input: The type of dataset is not supported. |
| Description: | The input specified is invalid. |
| Solution: | See the documentation for the Upgrade Spatial Renference tool, or the help on Migrating to high precision. |
| Error code: | 000665: Invalid input. Release version of input database must be 9.2 or higher. |
| Description: | The specified input is not contained in a 9.2 or higher version of the geodatabase. |
| Solution: | Upgrade the geodatabase. For more information on how to do this see the help on Migrating to high precision. |
| Error code: | 000666: <value> does not have an OID. |
| Description: | The specified paramter does not have an OID. |
| Solution: | Consider using the Make Query Table tool to add a virtual OID field. |
| Error code: | 000668: Not a feature layer |
| Description: | The feature layer being used does not represent a valid feature data type for the tool. Every tool has specific feature data type which it can and cannot process. For example, a valid feature layer may represent points, lines or polygons. There are many other valid feature data types. |
| Solution: | Read the tool help to learn what feature data types are accepted for processing by the tool. |
| Error code: | 000669: output <value> is same as overlay <value> |
| Description: | The output parameter and the overlay parameter cannot share an identical path and name. The output must be unique from the overlay. |
| Solution: | Create an unique name for your output dataset. |
| Error code: | 000670: output <value> is same as input <value> |
| Description: | The output parameter and the input parameter cannot share an identical path and name. The output must be unique from the input. |
| Solution: | Create an unique name for your output dataset. |
| Error code: | 000671: <value> does not exist within table |
| Description: | The field specified does not exist within the table being used. |
| Solution: | Check that the field has been specified correctly and update the appropriate field parameter accordingly. |
| Error code: | 000672: Field is not permitted when constraining features are points |
| Description: | The tool does not accept a Field for number of points when the constraining feature class is of geometry type "point". |
| Solution: | Specify a positive integer for the number of points rather than a field. |
| Error code: | 000673: The inhibition distance cannot be negative |
| Description: | The inhibition distance specified is negative. |
| Solution: | Only use positive numbers in the inhibition distance parameter. Inhibition determines how close together randomly placed points can be. This distance can be thought of as a buffer around already placed points. Negative buffer distances do not make sense when the object being buffered is a point. |
| Error code: | 000674: multipoint count must be positive |
| Description: | The number of points per multipoint must be positive. |
| Solution: | This parameter allows you to specify the maximum number of points that can fall in each multipoint. A negative number would mean fewer than zero |
| Error code: | 000675: The units value is either invalid or not supported for record <value> |
| Description: | The specified unit is either invalid or not supported by UDUNUTS library. |
| Solution: | Specify a unit supported by UDUNITS library. |