Ingest Aborts with Error -- Unable to Copy

[jldodge]

I recently had to replace one of the CPUs in my computer. As a result, the technician had to reformat the "C" drive and reinstall Windows. I then re-installed the remainder of the applications, including Photo Mechanic. Before the CPU went bad, Photo Mechanic worked fine, no problems with the ingesting process even when using hot codes. However, following the reinstallation of Photo Mechanic, I continue to get errors after 4, 6, or 8 files are ingested. Attached is a screen shot as well as a log file. The files that are ingested are solid black, no picture even when I used other applications to view them. The files sizes are similar to the original files despite no picture. Also, even though I start the numbering sequence at 00001, the sequence number on the ingested files starts at some randomly higher number, e.g. 03275. I have increased the size of the cache but that has not helped the situation. I need help at this point. Thanks in advance ...

[Kirk Baker]

For a problem like this, I suggest contacting our support folks at:

By email: support@camerabits.com

By phone: +1 503.547.2888

Hours: Mon-Fri, 9:00am-5:00pm [PST/PDT]

[jldodge]

Just to keep everyone updated in case my situation is similar to other user's experiences ... 


Camera Bits Support via freshdesk.com
Mon, Oct 7, 7:38 PM (2 days ago)
to me

Hi Jeffrey,

It looks like, over the past few days, you've tried increasing the size of Photo Mechanic's various caches, I assume as a troubleshooting step for this issue. I'm not sure what is causing the problem, but I can assure you that the issue is not due to the sizes of the various caches, and setting the caches too large can have adverse affects in other areas. 

What happens if, instead of Ingesting, you use Windows Explorer to try to copy the contents of the source to the destination? If that works, what happens if you try to Ingest to a different destination than the drive where you are seeing errors?

Best regards,
Andrew H.,  Senior Manager of Technical Support
Camera Bits, the makers of Photo Mechanic®
Hours: Monday through Friday, 9am to 5pm Pacific Time
503-547-2888
www.camerabits.com
Subscribe To Our Newsletter

My Reply:

A couple of corrections from my initial comments. The files that did not display (i.e. all black) turned out to be the same as the originals. Somehow, I had forgotten to delete them from my originals. So, I deleted them before performing the additional tests. Second, the only difference between "before" (when everything worked fine) and "now" (which is my current dilemma) is that my operating system changed from Windows 10 to Windows 11.

I am able to copy files to the NAS device using Windows Explorer. They copy fine and are visible in Windows Explorer and "other" applications, e.g. FastRawViewer. When I ingest the files and route them to a destination folder on my C drive (i.e. not a NAS drive), Photo Mechanic seems to work fine. I aborted the ingestion process after a significant number of files had been correctly ingested and were viewable in the contact sheet. However, I do not have the capacity on any connected drive for all of my ingested photos. Also, I access these photos with other computers so I need to use a network configuration.
After that, I tried to ingest my original photos to a different NAS. The ingestion process aborted with the same error message as before although the ones that were ingested were viewable in the contact sheet.
I then went back to my original settings and ingested from one NAS drive (which contains the originals) to another NAS drive (which contains all of my ingested photos). As before, I received the same error message (attached is the screen shot of that process).
I should also note that photos which were previously (Photo Mechanic + Windows 10) ingested are viewable in the contact sheet. Also, I have other applications which read and write to all of my NAS and remote/external drives without any problems.

I checked for software updates to Photo Mechanic and am told that my software is up to date.

Thanks again ... in advance.