Error 999999 аркгис

Troubleshooting Error 999999 in ArcMap and ArcGIS

If you’ve worked with ArcGIS, you’ve certainly had your fair share of errors while running geoprocessing tools – many of them are quite descriptive and tell you exactly what’s wrong, while some are specific but cryptic. But one error message, with error code 999999, is painful to get because it means something went wrong, and even the software isn’t sure what it is. It is usually accompanied by misleading messages such as “the table was not found” or something else. So we have to figure it out ourselves. In this article, I’ll lay out some places to look for the most common solutions to this problem.

Here’s the summary of steps (followed by detailed explanations for each one), in an approximate order of how I try them – though circumstances will vary and you may have a hunch that one of these will work.

1. Restart ArcMap/Your Computer
2. Try the operation in a blank map document or in ArcCatalog
3. Check your input and output workspaces
4. Check the names of your inputs and outputs
5. Disable Background Geoprocessing
6. Check your projections/coordinate systems
7. Check your environment settings for anything unusual
8. Look for any tool specific settings that could create problems – try simplifying your options until the tool runs, which will help you ID the problem
9. Try Repair Geometry

Restart ArcMap/Your Computer

Troubleshooting 101, but we all need a reminder sometimes. Turning it off and back on again can work! If you want to just reboot the software and not your computer, make sure to kill all ArcGIS programs – you can open your task manager and find ArcROT, ArcGIS Connection Manager, and ArcGIS Cache Manager – make sure to kill each of those processes if they are running. The easiest way is to often reboot your whole computer. Then try the operation again.

Try the operation in a blank map document or in ArcCatalog

If you’ve been working with the data in ArcMap, try running it in ArcCatalog instead, or try running it in a new, blank map document. Map documents can occasionally accumulate problems or small issues related to environment settings you’ve changed, and attempting the operation in a new map document can help rule out these issues.

Check your input and output workspaces

To put this another way, check the formats of the data you’re providing as inputs or choosing for outputs, as well as the locations they are stored. While ArcGIS has become much more consistent in the last 5-10 years, occasionally a tool may have trouble working with file geodatabase rasters when an Esri GRID format raster works just fine (for example). You can try copying the data to a new version of the same workspace – so if it’s already in a file geodatabase, try copying it to a brand new file geodatabase as the only item – or you can try converting it to a different format (export a GeoTIFF, GRID, etc). The same rules can apply for outputs – try writing out the results as a different format to see if it resolves the issue. Finally, check the workspace environment settings. For many years, certain raster operations wanted to use folder workspaces rather than geodatabases, though this has also improved.

Check the names of your inputs and outputs

One thing that occasionally creates error 999999 for me is starting a feature class or raster name with a number – this most often happens when I try to start the name with the year the data represents (2016_imagery, for example). This isn’t allowed in a name, but it doesn’t have a specific error message to tell you that, so you just have to know. Another common naming problem in the past was any file path that had spaces – this is less of a problem today than it had been, but it’s often still good to avoid spaces. It’s worth checking the naming rules of whatever workspace you’re reading from and writing to in order to ensure you don’t have any other invalid characters or names. Here are some naming rules for rasters in Spatial Analyst.

Check your inputs for joins and relates

If one of the layers involved in your geoprocessing operation has an active join on it to attach values in the attribute table, that could be the cause of the error. If you need those values attached, one option is to export a copy of that dataset, which permanently writes those values to the attribute table, and then try running your geoprocessing operation again. If you do not need those values, simply remove the joins or relates and try running the operation again.

Disable Background Geoprocessing

Background geoprocessing sends your data to another process on your computer, freeing up ArcGIS to let you do more work while it’s running – occasionally, it has side effects that don’t occur when running “in the foreground” (where a window pops up and blocks you from doing anything else while it runs). You can disable background geoprocessing by going to the Geoprocessing menu in ArcMap, then Geoprocessing Options and unchecking the box next to Enable in the Background Geoprocessing section. Click OK to save your settings, then try running the process again. If this solution works, you might want to reenable background geoprocessing later since there error might still be specific to your current data, or you can choose to leave it disabled.

Check your projections/coordinate systems

ArcGIS is usually great with projections and coordinate systems, and handles reprojecting data into a common coordinate system in the background for each analysis, if they don’t already share one. But occasionally this can go wrong (maybe if a geographic transformation is required to shift datums), so reprojecting the data manually to a common coordinate system will remove this as a factor and can make the tool succeed. I’ve personally seen this be a problem with rasters in geographic coordinate systems, but it applies elsewhere too.

Check your environment settings for anything unusual

This step is less than straightforward – environment settings can make a big difference in your processing, but you might not always be clear on when and how to use them. The first step is to check the tool’s help document and look near the bottom of the page – it will tell you which environment variables apply. If you are getting an error when you set variables, it’s possible that removing them and running it will succeed. That doesn’t fully solve your problem since the environment variable may be important, but it might help you narrow in on the set of parameters that are causing the problem. One example might be setting an invalid extent for the analysis – if I remove the extent environment setting and the analysis succeeds, I may then know that I need to check on the value I was providing for the extent variable and make sure it’s correct and applicable to the data at hand.

Look for any tool specific settings that could create problems

In a similar realm to checking the environment settings, try only setting the minimum number of options in the main geoprocessing tool. For example, I’ve had troubles when running the Buffer tool if I use the dissolve option – leaving it as its default helped me realize my problem was with that option – at which point I could read up on the details of what setting that option does and whether I need it. If you can get it running after setting the minimum set of options (basically, just the required options) you can narrow in what’s wrong with your tool run by selectively setting the remaining options and reading the documentation, then determining if you’re setting appropriate values for those remaining options.

Try Repair Geometry

It’s also possible that there might be something wrong with your data. Running the Repair Geometry tool, if your data is a feature class, will check the data’s spatial information for errors and repair them if they are found. If all else fails, this one can be an important factor.

OK. That’s my list of things to try if you’re getting error 999999 in ArcGIS. If you think I missed something or have other suggestions for what to try, leave it in the comments below!

Источник

999999: Инструмент не сработал по неожиданной причине. Для отчета об ошибке свяжитесь со службой технической поддержки Esri (http://esriurl.com/support) и обратитесь к справке по ошибке для возможных решений или обхода ошибки.

Описание

Инструмент не сработал по неожиданной причине, а (режим) Без обработки исключений обеспечил создание специального сообщения об ошибке. В некоторых случаях эта ошибка может включать в себя другие сообщения, которые могут помочь понять проблему.

Решение

Это считается ошибкой, поскольку в инструменте отсутствует обработка исключений. Свяжитесь с техподдержкой Esri и проинформируйте ее об этой ошибке и обстоятельствах ее возникновения. После того, как вы сообщите об этой ошибке в техническую поддержку, вы можете выполнить следующие шаги для ее устранения:

1. Причиной этой ошибки могут стать нулевая геометрия, осколки сегментов, самопересечения и другие геометрические проблемы в классе пространственных объектов. Запустите инструмент Восстановить геометрию , чтобы исправить имеющиеся ошибки геометрии.
2. Проверьте имя, которые вы пытаетесь использовать для создания выходных данных. В базе геоданных не поддерживаются символы, кроме букв и цифр. Имена данных базы геоданных не могут начинаться с цифры. Следующие слова зарезервированы в качестве ключевых слов для базы геоданных, и поэтому сами по себе их нельзя использовать в качестве имени набора данных, а только как часть более длинного имени набора данных:
   • ADD, ALTER, AND, BETWEEN, BY, COLUMN, CREATE, DELETE, DROP, EXISTS, FOR, FROM, GROUP, IN, INSERT, INTO, IS, LIKE, NOT, NULL, OR, ORDER, SELECT, SET, TABLE, UPDATE, VALUES, WHERE
   • Более подробно о правилах присвоения имен данным базы геоданных
   • Более подробно об ограничении размеров и имен файловых баз геоданных
3. Проверьте местоположение, в котором вы пытаетесь создать выходные данные. Можете ли вы переместиться к этому месту в Windows Explorer? Можете ли вы скопировать и вставить файлы в это место вне ArcGIS? Если появится диалоговое окно Windows с сообщением о том, что для копирования файлов в этом местоположении требуется разрешение, это с большой вероятностью и является причиной отказа инструмента.
4. Если вы работаете с очень большим набором данных, этой ошибки можно избежать, разбив данные на более мелкие части. Используйте инструмент Вырезать (растры) или Вырезать (объекты) , чтобы сделать поднабор данных меньшего размера, и запустите этот инструмент, используя созданный поднабор. Если это удастся, можете дополнительно создать поднаборы исходных данных и запустить инструмент, используя все эти поднаборы.
5. При работе с входными и выходными шейп-файлами используйте файловую базу геоданных. Возможно, вы столкнулись с проблемой, характерной для шейп-файлов. Вы также можете сделать обратное — экспортируйте свой класс объектов файловой базы геоданных в шейп-файл и попробуйте использовать этот шейп-файл. Для растровых данных, если вы работаете с растрами на основе файлов, такими как файл .tif или Esri GRID, попробуйте экспортировать его в базу геоданных. Можно сделать наоборот: экспортировать растр в файл .tif и попробовать снова выполнить этот процесс.
6. Если путь выходных данных слишком длинный (содержит множество подпапок или длинное имя), можно попробовать создать папку с выходными данными в расположении ближе к корню диска с именем покороче. Не пытайтесь создать папку с выходными данными в корне диска, поскольку современные операционные системы обычно не разрешают создавать файлы и данные в этом расположении без специального разрешения администратора.
7. Попробуйте запустить ArcGIS Pro в режиме администратора. Щелкните правой кнопкой мыши ярлык приложения и выберите Запустить от имени администратора . Выполните ранее не удавшуюся задачу. Если ошибка вызвана разрешениями доступа, запуск от имени администратора может позволить выполнить операцию успешно.
8. Большинство инструментов геообработки могут успешно использовать нулевые атрибуты данных, но иногда эти нулевые значения могут стать причиной возникновения проблемы. Для проверки сделайте копию своих данных, а затем с помощью инструмента Вычислить поле замените все нулевые значения на 0 или на другое выбранное значение (некоторые используют -1 для обозначения нулевых значений). Если вы работаете с растровыми данными, то для замены нулевых значений на 0 или другое выбранное значение можно использовать инструмент Условие .
9. Временные или промежуточные данные часто записываются в местоположение C:Users\AppDataLocalTemp (оно будет доступно, если в окне Проводник Windows ввести %localappdata%temp ). Закройте ArcGIS Pro , очистите папку Temp, перезапустите приложение и повторите попытку неудавшегося процесса.

Источник

Проблема: Сбой инструмента Копировать растр с ERROR 999999 в ArcGIS Pro

Description

В ArcGIS Pro, при попытке запуска инструмента Копировать растр, происходит сбой и возвращается сообщение ERROR 999999.

Cause

Проблема возникает при выборе более одного процессора в поле Коэффициент параллельной обработки параметров среды геообработки. Это известное ограничение. Дополнительные сведения см. в BUG-000129060.

Solution or Workaround

Для решения этой проблемы используйте только один процессор при запуске инструмента Копировать растр. Выполните указанные ниже шаги:

1. На верхней ленте ArcGIS Pro щелкните вкладку Анализ и выберите Инструменты.
2. На панели Геообработка найдите и откройте инструмент Копировать растр (Управление данными). Откроется окно Копировать растр.
3. В окне Копировать растр щелкните Параметры и заполните все обязательные поля.
4. В окне Копировать растр щелкните Параметры среды. В разделе Параллельная обработка удалите значение в поле Коэффициент параллельной обработки.
5. Щёлкните Выполнить.

Last Published: 6/14/2021

Article ID: 000024626

Software: ArcGIS Pro 2.8, 2.7.3, 2.7.2, 2.7.1, 2.7, 2.6.5, 2.6.4, 2.6.3, 2.6.2, 2.6.1, 2.6, 2.4.3, 2.4.2, 2.4.1, 2.4, 2.3.3, 2.3.2, 2.3.1, 2.3, 2.2.4, 2.2.3, 2.2.2, 2.2.1, 2.2, 2.1.3, 2.1.2, 2.1.1, 2.1, 2.0.1, 2.0

Download the Esri Support App on your phone to receive notifications when new content is available for Esri products you use

Download the Esri Support App on your phone to receive notifications when new content is available for Esri products you use

Источник

I am iterating through ~300 raster tiles, using a polygon feature class to extract by mask. The model successfully processes the first ~100 tiles and then I get the following error on the same tile each time:

ERROR 999999: Error executing function.
The table was not found. [VAT_T2001]

ERROR 010092: Invalid output extent.
Failed to execute (ExtractByMask).

I changed the extent parameter of the extract by mask tool from default to «intersection of inputs» and got the same error for the same tile. The tool seems to work fine when I change the extent parameter to «union of inputs» but it takes an extremely long time to process each tile.

I thought that the error might be occurring because there is no overlap between the error tile and the mask feature class, but I confirmed that the tool successfully processes other tiles where there is no overlap.

The tiles and the feature class have the same spatial reference. The error also occurs for a handful of other tiles in the data set.

Does anyone know how to resolve these errors while maintaining efficient processing?

The model is just an iterator sitting in front of the extract by mask tool. So this is a question about why extract by mask works for some raster datasets and not others when the datasets have the same attributes and the tool has the same parameters.

If you’ve worked with ArcGIS, you’ve certainly had your fair share of errors while running geoprocessing tools – many of them are quite descriptive and tell you exactly what’s wrong, while some are specific but cryptic. But one error message, with error code 999999, is painful to get because it means something went wrong, and even the software isn’t sure what it is. It is usually accompanied by misleading messages such as “the table was not found” or something else. So we have to figure it out ourselves. In this article, I’ll lay out some places to look for the most common solutions to this problem.

Here’s the summary of steps (followed by detailed explanations for each one), in an approximate order of how I try them – though circumstances will vary and you may have a hunch that one of these will work.

1. Restart ArcMap/Your Computer
2. Try the operation in a blank map document or in ArcCatalog
3. Check your input and output workspaces
4. Check the names of your inputs and outputs
5. Disable Background Geoprocessing
6. Check your projections/coordinate systems
7. Check your environment settings for anything unusual
8. Look for any tool specific settings that could create problems – try simplifying your options until the tool runs, which will help you ID the problem
9. Try Repair Geometry

Restart ArcMap/Your Computer

Troubleshooting 101, but we all need a reminder sometimes. Turning it off and back on again can work! If you want to just reboot the software and not your computer, make sure to kill all ArcGIS programs – you can open your task manager and find ArcROT, ArcGIS Connection Manager, and ArcGIS Cache Manager – make sure to kill each of those processes if they are running. The easiest way is to often reboot your whole computer. Then try the operation again.

Try the operation in a blank map document or in ArcCatalog

If you’ve been working with the data in ArcMap, try running it in ArcCatalog instead, or try running it in a new, blank map document. Map documents can occasionally accumulate problems or small issues related to environment settings you’ve changed, and attempting the operation in a new map document can help rule out these issues.

Check your input and output workspaces

To put this another way, check the formats of the data you’re providing as inputs or choosing for outputs, as well as the locations they are stored. While ArcGIS has become much more consistent in the last 5-10 years, occasionally a tool may have trouble working with file geodatabase rasters when an Esri GRID format raster works just fine (for example). You can try copying the data to a new version of the same workspace – so if it’s already in a file geodatabase, try copying it to a brand new file geodatabase as the only item – or you can try converting it to a different format (export a GeoTIFF, GRID, etc). The same rules can apply for outputs – try writing out the results as a different format to see if it resolves the issue. Finally, check the workspace environment settings. For many years, certain raster operations wanted to use folder workspaces rather than geodatabases, though this has also improved.

Check the names of your inputs and outputs

One thing that occasionally creates error 999999 for me is starting a feature class or raster name with a number – this most often happens when I try to start the name with the year the data represents (2016_imagery, for example). This isn’t allowed in a name, but it doesn’t have a specific error message to tell you that, so you just have to know. Another common naming problem in the past was any file path that had spaces – this is less of a problem today than it had been, but it’s often still good to avoid spaces. It’s worth checking the naming rules of whatever workspace you’re reading from and writing to in order to ensure you don’t have any other invalid characters or names. Here are some naming rules for rasters in Spatial Analyst.

Check your inputs for joins and relates

If one of the layers involved in your geoprocessing operation has an active join on it to attach values in the attribute table, that could be the cause of the error. If you need those values attached, one option is to export a copy of that dataset, which permanently writes those values to the attribute table, and then try running your geoprocessing operation again. If you do not need those values, simply remove the joins or relates and try running the operation again.

Disable Background Geoprocessing

Background geoprocessing sends your data to another process on your computer, freeing up ArcGIS to let you do more work while it’s running – occasionally, it has side effects that don’t occur when running “in the foreground” (where a window pops up and blocks you from doing anything else while it runs). You can disable background geoprocessing by going to the Geoprocessing menu in ArcMap, then Geoprocessing Options and unchecking the box next to Enable in the Background Geoprocessing section. Click OK to save your settings, then try running the process again. If this solution works, you might want to reenable background geoprocessing later since there error might still be specific to your current data, or you can choose to leave it disabled.

Check your projections/coordinate systems

ArcGIS is usually great with projections and coordinate systems, and handles reprojecting data into a common coordinate system in the background for each analysis, if they don’t already share one. But occasionally this can go wrong (maybe if a geographic transformation is required to shift datums), so reprojecting the data manually to a common coordinate system will remove this as a factor and can make the tool succeed. I’ve personally seen this be a problem with rasters in geographic coordinate systems, but it applies elsewhere too.

Check your environment settings for anything unusual

This step is less than straightforward – environment settings can make a big difference in your processing, but you might not always be clear on when and how to use them. The first step is to check the tool’s help document and look near the bottom of the page – it will tell you which environment variables apply. If you are getting an error when you set variables, it’s possible that removing them and running it will succeed. That doesn’t fully solve your problem since the environment variable may be important, but it might help you narrow in on the set of parameters that are causing the problem. One example might be setting an invalid extent for the analysis – if I remove the extent environment setting and the analysis succeeds, I may then know that I need to check on the value I was providing for the extent variable and make sure it’s correct and applicable to the data at hand.

Look for any tool specific settings that could create problems

In a similar realm to checking the environment settings, try only setting the minimum number of options in the main geoprocessing tool. For example, I’ve had troubles when running the Buffer tool if I use the dissolve option – leaving it as its default helped me realize my problem was with that option – at which point I could read up on the details of what setting that option does and whether I need it. If you can get it running after setting the minimum set of options (basically, just the required options) you can narrow in what’s wrong with your tool run by selectively setting the remaining options and reading the documentation, then determining if you’re setting appropriate values for those remaining options.

Try Repair Geometry

It’s also possible that there might be something wrong with your data. Running the Repair Geometry tool, if your data is a feature class, will check the data’s spatial information for errors and repair them if they are found. If all else fails, this one can be an important factor.

OK. That’s my list of things to try if you’re getting error 999999 in ArcGIS. If you think I missed something or have other suggestions for what to try, leave it in the comments below!

In ArcGIS Desktop 9.3 I have 3 features I’m trying to use to extract by mask a DEM raster layer. After I extract by mask the layers visually don’t line up. When I try to do further analyses (e.g., extract to point, slope, summary stats, etc.) it is clear that my mask does not line up with my features because I get -999999 as values in further analyses.

What went wrong? and what can I do to fix it?

I’ll also note that my features were originally drawn polygons that I converted to features — could this have anything to do with the problem?

STEPS

1. Create New layer

2. Draw Polygon

3. Manually adjust polygon length & width

4. Rotate polygon

5. Copy polygon 2x so that I have 3 identical polygons

6. Place polygons where they belong on map (using road features layer as guide)

7. Convert Graphics to features (using DEM as source data for coordinate system)

   • Selected all 3 drawn polygons at once and then selected to convert graphics to features

8. Add new features as layer

   • Agreed to the menu that popped up asking to add my converted features as a layer

9. Extract by Mask using new layer features as input and DEM for raster input

Properties of both Layers (I didn’t manually define or adjust)

DEM Raster:

Spatial Reference: NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
linear Unit: Foot_US (0.304801)
Angular Unit: Degree (0.017453292519943295)
False_Easting: 2000000.002616666
False_Northing: 0
Central_Meridian: -79
Standard_Parallel_l: 34.33333333333334
Standard_Parallel_2: 36.16666666666666
Latitude_ Of_ Origin: 33.75
Datum: D_North_American_1983

Polygon Features:

Projected Coordinate System:     NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
Projection: Lambert_Conformal_Conic
False_Easting:  2000000.00261667
False_Northing: 0.00000000
Central_Meridian:   -79.00000000
Standard_Parallel_1:    34.33333333
Standard_Parallel_2:    36.16666667
Latitude_Of_Origin: 33.75000000
Linear Unit:    Foot_US

Geographic Coordinate System:   GCS_North_American_1983
Datum:  D_North_American_1983
Prime Meridian:     Greenwich
Angular Unit:   Degree

Overall Data Frame properties:

NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
Projection: Lambert_Conformal_Conic
False_Easting: 2000000.002617
False_Northing: 0.000000
Central_Meridian: -79.000000
Standard_Parallel_1: 34.333333
Standard_Parallel_2: 36.166667
Latitude_Of_Origin: 33.750000
Linear Unit: Foot_US

GCS_North_American_1983
Datum: D_North_American_1983

Picture demonstrating alignment issue (2 of 3 drawn features shown)

Black/grey = DEM mask layer; Red outline = polygon feature outline; Blue = rivers; Green = roads

In ArcGIS Desktop 9.3 I have 3 features I’m trying to use to extract by mask a DEM raster layer. After I extract by mask the layers visually don’t line up. When I try to do further analyses (e.g., extract to point, slope, summary stats, etc.) it is clear that my mask does not line up with my features because I get -999999 as values in further analyses.

What went wrong? and what can I do to fix it?

I’ll also note that my features were originally drawn polygons that I converted to features — could this have anything to do with the problem?

STEPS

1. Create New layer

2. Draw Polygon

3. Manually adjust polygon length & width

4. Rotate polygon

5. Copy polygon 2x so that I have 3 identical polygons

6. Place polygons where they belong on map (using road features layer as guide)

7. Convert Graphics to features (using DEM as source data for coordinate system)

   • Selected all 3 drawn polygons at once and then selected to convert graphics to features

8. Add new features as layer

   • Agreed to the menu that popped up asking to add my converted features as a layer

9. Extract by Mask using new layer features as input and DEM for raster input

Properties of both Layers (I didn’t manually define or adjust)

DEM Raster:

Spatial Reference: NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
linear Unit: Foot_US (0.304801)
Angular Unit: Degree (0.017453292519943295)
False_Easting: 2000000.002616666
False_Northing: 0
Central_Meridian: -79
Standard_Parallel_l: 34.33333333333334
Standard_Parallel_2: 36.16666666666666
Latitude_ Of_ Origin: 33.75
Datum: D_North_American_1983

Polygon Features:

Projected Coordinate System:     NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
Projection: Lambert_Conformal_Conic
False_Easting:  2000000.00261667
False_Northing: 0.00000000
Central_Meridian:   -79.00000000
Standard_Parallel_1:    34.33333333
Standard_Parallel_2:    36.16666667
Latitude_Of_Origin: 33.75000000
Linear Unit:    Foot_US

Geographic Coordinate System:   GCS_North_American_1983
Datum:  D_North_American_1983
Prime Meridian:     Greenwich
Angular Unit:   Degree

Overall Data Frame properties:

NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
Projection: Lambert_Conformal_Conic
False_Easting: 2000000.002617
False_Northing: 0.000000
Central_Meridian: -79.000000
Standard_Parallel_1: 34.333333
Standard_Parallel_2: 36.166667
Latitude_Of_Origin: 33.750000
Linear Unit: Foot_US

GCS_North_American_1983
Datum: D_North_American_1983

Picture demonstrating alignment issue (2 of 3 drawn features shown)

Black/grey = DEM mask layer; Red outline = polygon feature outline; Blue = rivers; Green = roads

Перепечатано на: https://www.cnblogs.com/dowtowne/p/3466866.html