Select to view content in your preferred language

RasterToGeodatabase: Error 999999

563
2
05-29-2013 03:45 AM
ClaudiaGeorgi
New Contributor
Hi guys,

I was trying to add quite big raster images (.tif) to a Raster Catalog in ArcCatalog via Import. Unfortunately the results say as follows:


Failed to convert (Dataname) ERROR 999999: Error executing function.
FDO error: -1
Failed to execute (Copy Raster)



I tried the process with and without building pyramids. I am using verison 10.1. Has anyone a clue what I did wrong?


Thank you!
Claudia
0 Kudos
2 Replies
JamesHood
Regular Contributor
Hi Claudia,

I had a similar issue and found your thread in my search.

My issue was converting multiple LiDAR .LAS files to a single multipoint file (LAS to Multipoint).

I received the following errors:
Error: 999999
FDO error: -1
FDO error:-1 [featureclass_name]
Failed to execute (LAStoMultipoint)

I can't speak to your issue specifically but I just got off of the phone with ESRI support and they told me that my issue is directly related to 10.1 Service Pack1.

I was told that many LiDAR errors are resultant of SP1.  I was directed to go to control panel / programs and features / installed updates /  
highlight ArcGIS SP1 / right click / remove.

This apparently reverts to 10.1 SP0 and the errors should go away.

Might be worth looking into.
0 Kudos
JamesHood
Regular Contributor
Hi Claudia,

I had a similar issue and found your thread in my search.

My issue was converting multiple LiDAR .LAS files to a single multipoint file (LAS to Multipoint).

I received the following errors:
Error: 999999
FDO error: -1
FDO error:-1 [featureclass_name]
Failed to execute (LAStoMultipoint)

I can't speak to your issue specifically but I just got off of the phone with ESRI support and they told me that my issue is directly related to 10.1 Service Pack1.

I was told that many LiDAR errors are resultant of SP1.  I was directed to go to control panel / programs and features / installed updates /  
highlight ArcGIS SP1 / right click / remove.

This apparently reverts to 10.1 SP0 and the errors should go away.

Might be worth looking into.


I followed the above steps and it did not resolve my error. 
I'll call dem folks back.
0 Kudos