Show Navigation
|
Hide Navigation
Tool errors and warnings: 401-425 |
|
|
Release 9.3
Last modified April 24, 2009 |
|
Related Topics
Note:
This topic was updated for 9.3.1.
| Error code: | 000401: No features were found for processing |
| Description: | No input features were found, which can result in an empty result. This warning commonly occurs when the Extent or XYDomain environment settings have been previously set for a specific geographical area and the values were inadvertantly used when running another tool. The Extent environment is used to limit the input features used, so an inappropriately set environment could exclude all features. Another possible cause is a layer with a selection set containing no selected features. Tools honour layer selections as their input. A query returning zero features is valid, but will result in no features in the layer being used by a tool. |
| Solution: | If this is an unexpected message, check the Extent and XYDomain environment settings to ensure they are appropriate for the data and the tool being used. If they are not, reset them by emptying their values or set them to suitable values. If the input is a layer, make sure the definition or selection query used on the layer is correct. If it is not, clear the layer's selection set and run the tool again. |
| Error code: | 000402: No input fields found. |
| Description: | An input field, used to populate the XData field, needs to be selected. |
| Solution: | Select one or more input fields to be added to the newly created XData field, which is a XML string containing the values of the selected fields. The XData field may be used to provide ArcGIS attribution within AutoCAD. |
| Error code: | 000403: No output file name specified |
| Description: | A name for the output CAD file has not been specified. It is required. |
| Solution: | Specify an output file name when running the Export CAD tool. |
| Error code: | 000404: No parent version. |
| Description: | The specified version does not have a parent. |
| Solution: | This is only possible with the Default version. Switch to a non Default version and repeat operations. |
| Error code: | 000405: No records within table |
| Description: | There were no records available in the table on which to perform the operation. This warning can obviously occur when using an empty feature class or table, but it may also occur when working with a layer or table view containing an empty selection set. If a selection was applied against the layer or table view (e.g., Select Layer By Location, Select Layer By Attribute) and it resulted in no records being selected, this warning will result. |
| Solution: | Use Get Count to return the number of available records or features within the input dataset. If the inout is a layer or table view and there is a selection, it will return the number of selected records or features. Reexamine the query used to create the selection to ensure it is correct. |
| Error code: | 000406: No replicas in Check-in from workspace |
| Description: | There were no replicas in the Check-in from workspace. The check-in from workspace must have a valid check-out. |
| Solution: | Ensure you have specified the correct replica workspace. Use the replica manager to determine if there is a valid checkout in the workspace. For more information on Check out/Check in Replication see Replication Types. |
| Error code: | 000407: No fields selected in <value> |
| Description: | Select at least one of the fields from the list. |
| Solution: | If you are using a tool dialog, choose a field from the list of field names. If you are running a tool from a script or the command line, specify a field name, using a semi-colon to seperate multiple field names, if more than one field name is supported. |
| Error code: | 000408: No valid frequency fields |
| Description: | The specified frequency fields are invalid. |
| Solution: | Make sure the field(s) you specified exists in the input. This message usually occurs when an mistaken field name is used. |
| Error code: | 000409: No valid inputs... |
| Description: | No acceptable inputs have been provided. Feature Class To Coverage accepts feature classes and feature layers as valid input. |
| Solution: | Check that the inputs provided exists and are valid. |
| Error code: | 000413: <value> not found in <value> |
| Description: | The field you have chosen does not exist within the table. |
| Solution: | Choose a valid field from the input table. |
| Error code: | 000414: <value> not found. |
| Description: | The specified field does not exist in the Relationship Table. |
| Solution: | Check the list of attribute fields and remove any fields that don't exist and correct any spelling mistakes. |
| Error code: | 000415: Relationship Table not found. |
| Description: | The relationship table provided does not exist. |
| Solution: | Provide an existing relationship table. Check the path to the table and its name for spelling mistakes. |
| Error code: | 000416: Relationship Table or Fields not found. |
| Description: | The relationship table or specified fields do not exist. |
| Solution: | Review the parameters you provided and make sure they exist. To learn more about relationship classes, please see the Relationship Class Properties. |
| Error code: | 000417: Field does not exist |
| Description: | The specified field does not exist in the dataset. |
| Solution: | Check that the field name is correctly entered. Also check that the field does in fact exist in the dataset. |
| Error code: | 000422: The number is less than one |
| Description: | A newly created raster dataset must contain one or more raster bands. |
| Solution: | Specify the band number you want the output to be within the newly created raster dataset. |
| Error code: | 000423: Only single band integer raster dataset is a valid input |
| Description: | Certain tool operations can only be applied to a raster dataset containing a single integer band. Creating a colormap or raster attribute table for a raster dataset are examples of this. |
| Solution: | Select a single band raster dataset as input. |
| Error code: | 000424: Opposite corner coordinate is needed |
| Description: | When using the Create Fishnet tool, the Opposite corner of Fishnet parameter should be set if any of the following parameters are not set, or have a value of zero:
|
| Solution: | Set the Opposite Corner of Fishnet parameter to a valid coordinate pair or specify a value greater than zero for all of these parameters:
|
| Error code: | 000425: Failed to create ortho-corrected raster dataset |
| Description: | The output raster dataset can not be created. It is possible that the output raster dataset format does not support the output ortho-corrected raster data type. |
| Solution: | Select a proper output raster format for the ortho-corrected raster output. When storing a raster dataset in a file format, you need to specify the file extension: .bmp for BMP, .gif for GIF, .img for an ERDAS IMAGINE file, .jpg for JPEG, .jp2 for JPEG 2000, .png for PNG, .tif for TIFF, or no extension for GRID.
When storing a raster dataset in a geodatabase, no file extension should be added to the name of the raster dataset. A raster dataset stored in a geodatabase can be compressed; you can specify a compression type and compression quality within your environment settings. |