I implemented Pure ASP Upload 3 and smart image processor 2, tested and ran dozens of images without any problem, then went live, only to find that the customer gets an error

System.ArgumentException: Item has already been added. Key in dictionary: '59932' Key being added: '59932' at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add) at System.Collections.Hashtable.Add(Object key, Object value) at DMXzone.ImageProcessor.ImageProcessor.ReadExif(Image src, Boolean keepThumb, Boolean keepICC) at DMXzone.ImageProcessor.ImageProcessor..ctor(String filename, Boolean autoOrient) at DMXzone.ImageProcessor.ImageProcessorWebService.Load(String filename, Boolean autoOrient)

This error is generated by images that come from the client's camera, but never from my images.
I took one of the client images, and stripped the EXIF data and then tried the exact same upload and it works fine.
Bottom line, the exif data seems to generate the error.
I would be happy to supply an image from their camera so you can reveiw the EXIF data if you wish, just let me know where I can send it. Thanks for looking into this.

Page developed using ASP, Dreamweaver CS4 on Vista Home Premium, server is Windows 2003, ASP.NET version is 2.0.507.27
Problem appears totally dependant on EXIF data, can run the page 30 times with images from the web, or several of my cameras with NO issues, but will fail every time with the specific images supplied by the client, even if renamed, however if EXIF data is stripped using EXIFCleaner the same image works fine. So far I have only found the one image that throws the error but would like to get to the bottom of it.
David

Edited by - David volle on 01 Mar 2010  19:12:51

Hi David,

This is an old bug that we have fixed already a couple of updates ago.

Just make sure you download and install the latest version of Smart Image Processor 2 from www.dmxzone.com/go?12607

Greetings,
George

Hi George,
Sorry to have troubled you! I looked at my version (It's the first thing I do), but somehow I thought that 2.5.1 was the current version.
Anyway, I'll update to 2.5.5 right away and carry on. Thanks again.
David