Well, I know I am a little late, but I had the same problem last week, it was extremly frustrating. I found a solution, so I thought I'd share it here for people, that get this error in the future.
Just the facts first, I tried to import a whole bunch of images and videos from my iPhone in the Photos app on my Mac. It always started importing, successfully imported a couple of pictures, and then stopped, showing the same error message seen on the screenshot of zblom. Whenever the error occurred, my iPhone wasn't displayed in the Photos app anymore, and I had to replug it. I rebooted my mac, rebooted my iPhone, fixed the Photos database, but it just happened again and again. I am using an iPhone 6 running on iOS 9.3.2 and a Mid-2014 MacBook Pro Retina 15" running on OS X El Capitan 10.11.5.
Since I hate wiping my phone and wanted a quick solution, I just went for the Genius Bar at the Apple Store here in Tokyo. What came out in the end is pretty interesting. When I tried to import the same set of images I was trying to import the last days, it actually worked. So we selected another set of images and started a new import, and boom, the error came back. What the Genius Bar guy suggested right away, was that there might be some issues with the lightning cable. So we tried two different cables from the store, and both imports were successful. Then he used my cable to import photos and videos from an in-store-iPhone to an in-store-Mac, and he got the error message as I did. What we did next, was twist the cable a little bit, and just play around with the ends a little bit, and started another import on my mac, and it started working again, the import was successful.
I think, this being a primitive hardware issue, is the reason, why the space where the file name is supposed to be shown stays blank. Also, twisting and rearranging the cable helped, which makes it pretty obvious.
I ended up purchasing a new lightning cable, hoping to avoid this problem from now. I don't think that the cable is always the source of the issue as it was in my case, but you should definitely try another lightning cable if you get this error, possibly it solves the problem.
