A generic error occurred in GDI+. at System.Drawing.Image.Save(String filename, ImageCodecInfo encoder, EncoderParameters encoderParams)
at System.Drawing.Image.Save(String filename, ImageFormat format)
No other error information is provided. Are there perhaps some other support assemblies needed that may be needed on the server? This telerik upgrade is being tested on 2003 server, where all other telerik stuff works just fine for a number of sites. Is it possible the older server just doesn't support some GDI+ functionality that you require, and our only option is to move to server 2008?
We are in the process of switching our sites from rather ancient Windows Server 2003 to Windows Server 2008 so that's not a show-stopper. We just weren't quite ready to deploy this testing site there.
6 Answers, 1 is accepted
I believe that the following forum thread could be helpful for you to resolve this generic ASP.NET error:
http://stackoverflow.com/questions/1044085/a-generic-error-occurred-in-gdi.
Regards,
Kostadin
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
A generic error occurred in GDI+. at System.Drawing.Image.Save(String filename, ImageCodecInfo encoder, EncoderParameters encoderParams)
Was not Teleriks problem. I misinterpreted error and have resolved things with the usual privilege assignement related to GDI+ errors. Apologies for the blame-telerik-first.
Hi Support and John
Sorry to resurrect an old thread - We are having an identical problem in a production environment (generating and rendering a QR code), with the only difference being that the operation seems to work fine for some time, until we hit the above error.
Restarting the app pool temporarily resolves the problem, until it happens again after a while... possibly a build up, a concurrency issue, a clash with the temp filename where the QR code is saved?... could be anything, but we have no idea where to look for the next clue given that the behaviour is so inconsistent / sporadic, and we don't have access to the inner workings of the RadBarcode logic.
Would you be able to offer any pointers?
Thanks in advance, Paolo