1

I'm using ArcMap 10.3.1, and I'm working with monthly precipitation raster data from 1995 - 2015. Currently, I'm trying to get all of these raster layers (252 in total) to a different projection by using Project Raster (I'm using UTM NAD 1983 13N). I was doing a batch process (R click tool > Batch) with all of these layers.

All was going well, but while on the 210th raster layer, processing stopped at 78% and timed out with an Error 999999: Error executing function.(I mention the percentage because the time out occurs at the same value each time I've restarted the process.) The message I received simply stated that it "failed to copy raster dataset." In addition, it continues to give this error for all of the remaining rasters, and I cannot continue the process.

I've checked the rasters I'm projecting from, to see if I can diagnose some error with the original, and nothing is out of the ordinary; the other rasters that I was able to successfully project are all the same as the ones that spark the error (i.e. their extent, rows, columns, initial projection, cell size, etc. are all the same. The only difference is the pixel data they hold). The successfully processed rasters (1 to 209) also appear fine. Does anyone have any idea for why this is occurring?

  • Is it always the same actual raster that it fails on? – Midavalo Oct 5 '16 at 23:01
  • 1
    Perhaps review these Q&As: gis.stackexchange.com/… but 999999 errors are notoriously difficult to debug – PolyGeo Oct 5 '16 at 23:03
  • @Midavalo Yes, although it does seem that each raster after the 210th one also has this error. – Tula Oct 5 '16 at 23:07
  • What happens if you do the first 209 and then start again from the 210th onwards? – Midavalo Oct 5 '16 at 23:08
  • 1
    What happens when you use the tool normally, not in batch, on just that 210th raster? – PolyGeo Oct 6 '16 at 2:07
2

I'm still not entirely sure what happened, but I ended up going through all of my steps from the beginning (prior to me Project Rastering the layers - I had Raster Clipped these rasters previously). I focused on just the sections that started the error (210th raster and above), and that somehow fixed the problem. Even though they all appeared to be the same when I looked at those layers' properties, I'm thinking some sort of glitch happened during the earlier batch Raster Clip that I couldn't determine. I'm still looking into it, but I'll edit my answer if I find something new to add.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.