nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Failure or Kriging Tool

RoyHewitt

Hello all,

A field biologist has point data from sampling locations. He has used the kriging tool in the past (Spatial Analyst), but now every time he runs it, it returns error: 999999, which tells you absolutely nothing about why the tool failed.

I took his data across the office over to my desk, and the tool ran fine -- twice. Now I'm getting the same error 999999 with no understanding as to why.

Has anyone else experienced this or someone with a suggestion??

Thank You

Find more posts tagged with

Accepted answers

All comments

deleted-user-ntyckxP5KpJO

I had the same issue. I'm running ArcGIS 10.3.1 with the Spatial Analyst extension.

I copied all files I needed to a local folder and built a new mxd. I also made new scratch and workspace gdbs and directed my ArcGIS environments to use these.

Seems to have all worked. Simple enough.

Thanks

JJHarding

I'm running 10.1 and I got the 999999 Error (aka ye olde Error of Utter Uselessness) trying to run Kriging as well. The only thing that worked was moving all my files to my local drive instead of the shared company network drive. This has become my go-to troubleshooting technique since python REALLY seems to hate working with files that are not on my local drive.

ColinMurray

Hello
I recieved the same error 999999 when Kriging through the Spatial Analyst Extension in ArcMap ArcGIS 10.
I tried a few of the suggestions above including: deleting my default.gdb, creating new workspace and scratch directories (regular folders), ensuring file pathways didnot have odd characters and such, restarting ArcMap a few times, and watching raster file name character size. In the environments I also set the raster cell size to 100. I also tried the tool through the 3D Analyst Extension in ArcMap as well with the same error given.
It would still give the error in ArcMap however it worked fine when I ran the tool in ArcCatalogue.
Unsure why.
I was interpolating a point shape file of just over 160,000 elevation points.
Any ideas why this was occuring? Probably something silly.
Colin

SteveLynch

Roy

Delete you Windows temp folder and your default file GDB.
If this does not work (along with Jeff Swain's suggestions above in this thread) then please contact Esri Support.

BTW, can you run Slope or Aspect and what happens if you use .shp input to IDW and output to Esri GRID?

Regards
Steve

RoyHewitt

Can you run IDW using this data?
What version of ArcGIS are you using?
Input data format - .shp, file or P geodatabase or ?
Output format - grid, fGDB raster or ?

Just tried to run IDW -- returned the same error message 999999

ArcInfo Desktop 10
Input data format: multiple feature classes in a feature dataset within a file geodatabase.
Output format: Raster (default, seems to be the only option).

Thanks,
Roy

SteveLynch

Roy

Can you run IDW using this data?
What version of ArcGIS are you using?
Input data format - .shp, file or P geodatabase or ?
Output format - grid, fGDB raster or ?

Thanks
Steve

RoyHewitt

Data is local, I've changed the scratch workspace: Generic Error: 999999 instead of 999998.
File names do not start with numbers, and do not contain symbols.

The inexplicable failure of this tool is extremely frustrating.

JeffreySwain

If it worked once, but subsequent runs fail, I would consider moving the scratch space directory. As ArcMap and Spatial Analyst processes data, the working directory fills up with data from the processes. If changing that directory does not solve the analysis, I would consider running the tool locally, to avoid sporadic network differences with Esri GRIDs across the network. If that does not solve the issue, then placing a Support call to check out the differences in your processing syntax. I would recommend against names that have symbols or start with numbers and paths with too many spaces or special characters.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.