Drone2Map Error 160281 "A requested row object could not be located"

[PeterLarsen]

Version: 2023.1.0

The problem is not with the images or GCP. I have processed data in a previous version, but in the new version I get this error. The error appears in the "Adjust Images" category.

[Anonymous User]

Hello, I'm also having the same error and using a Sony camera on a Skyfish drone. Attaching the camera parameters for info. 

[PeterLarsen]

Try to change the focal length to 0.55 mm and process everything again.

[EricElizondo]

Sadly, that didn't change anything. Keeps coming up with that error. Ever since I updated to the latest version. Trying to render a tower with about 2100 images. Not sure if this is the best app to do it with but trying anyways.

[EricElizondo]

The Coordinate System my images are using is just WGS 1984 where as the Project Coordinate System is set to WGS 1984 UTM Zone 14N which is the zone the pics were taken. Not sure if the difference in the two is significant.

[MarkBarker1]

Hi @EricElizondo ,

If you are open to sharing the data I can have a look and see if I can reproduce the problems you are seeing. Feel free to email me directly (mbarker@esri.com) and I can setup a data share.

Regards,

Mark

[RyanWilkie_apca]

Has anyone found a clear source for this error? 
I had this error constantly in 2023.1, and now have 2024.1 and I'm still getting this same error regardless of the drone platform I'm using. CS's are correct, the "language" settings have done nothing, image metadata is correct, I've imported photos from both direct import images and import image folder. Images are stored locally. I get this error with Dji Ph4, Mavic3, Mavic3M, M200 with x4s. Esri support has emailed that "the bug will be fixed in new ArcGIS update, but with no clear answers as to what the problem is and their only feed back was to make sure images are sorted by file type and all in the same folder on the local harddrive. 
....so 6 months of troubleshooting and I still don't have an answer. 

[GadallaGadalla]

The issue got resolved once i copied all the images to a local drive and not on a network remote drive. I was connected to my office via a VPN, spent hours trying different solutions... Once I copied the files to the local drive and disconnected the VPN, all worked out fine.