Sorry to hear you're having problems with ImageGen.
You'll need to allow the server to display the actual error message to know what the problem is. In the web.config, temporarily set this:
<customErrors mode="Off"/>
(that's a capital 'O' in Off)
Then you should see the full details of the error, which will give a hint about what is going wrong. Alternatively, you can look at the server's event log.
My guess is that your site isn't running in a full-trust environment, which ImageGen requires.
The only problem is that i can't debug it from here, but my friendly hostprovider had a go at it and it was due to webconfig settings that were not cleared after uninstalling imageGen.
So when i reinstalled the package i got duplicate entries in the webconfig and the site "broke" down.
Don't know whether or not your are familiar with this behaviour?
Uninstall and the reinstall 2.5.2 results in 500 - Internal Error
Headline says it all.
Currently not able to debug as i am in germany away from my machine and ftp details.
Sorry to hear you're having problems with ImageGen.
You'll need to allow the server to display the actual error message to know what the problem is. In the web.config, temporarily set this:
(that's a capital 'O' in Off)
Then you should see the full details of the error, which will give a hint about what is going wrong. Alternatively, you can look at the server's event log.
My guess is that your site isn't running in a full-trust environment, which ImageGen requires.
Let us know what you find out.
cheers,
doug.
Hi Douglas
The only problem is that i can't debug it from here, but my friendly hostprovider had a go at it and it was due to webconfig settings that were not cleared after uninstalling imageGen.
So when i reinstalled the package i got duplicate entries in the webconfig and the site "broke" down.
Don't know whether or not your are familiar with this behaviour?
Thanks for the bug report and glad you could resolve the problem.
Uninstalls are 'manual' with regard to the web.config changes unfortunately. It's something the package developers are continuing to work on.
cheers,
doug.
Alrighty then, thanks for the info and especially the package!
is working on a reply...