I am using Classic ASP and receiving the message below when I run ckfinder on our live production server.
"Unable to find an image manipulation component"
I have everything working correctly on our developmemet server but not our live production machine. If I set the Thumbnail mode to None then it works correctly and I can upload and select files.
I am attempting to use the ASP.NET thumbnail system and we are able to successfully run ASP.NET scripts from this machine. ASP.NET appears to be correctly configured on IIS. I have also tried changing the config.asp and web.config files to use c:\mytmp\ as the communication folder as instructed but that makes no difference.
The site runs on a separate user account which I have given full premissions to the c:\mytmp folder, c:\windows\temp, and the UserFiles folder as well as full premissions to the IUSR_ and ASPNET accounts. Is there something I have missed?
Please help, I have spent about 6 hours trying to make this work now.
"Unable to find an image manipulation component"
I have everything working correctly on our developmemet server but not our live production machine. If I set the Thumbnail mode to None then it works correctly and I can upload and select files.
I am attempting to use the ASP.NET thumbnail system and we are able to successfully run ASP.NET scripts from this machine. ASP.NET appears to be correctly configured on IIS. I have also tried changing the config.asp and web.config files to use c:\mytmp\ as the communication folder as instructed but that makes no difference.
The site runs on a separate user account which I have given full premissions to the c:\mytmp folder, c:\windows\temp, and the UserFiles folder as well as full premissions to the IUSR_ and ASPNET accounts. Is there something I have missed?
Please help, I have spent about 6 hours trying to make this work now.
Re: "Unable to find an image manipulation component" -
IIS also didn't like having one web.config file in the root and another in a deeper folder which was blocking aspx further down the directory structure.
I think some better error reporting and a much better troubleshooting section would be helpful to others as this was not easy to get running.
Re: "Unable to find an image manipulation component" -
Sorry for the problems.
)
We are always trying to improve the setup process as well as the troubleshooting (ideally there should be no troubleshooting
Yes, the web server process needs write permissions for the UserFiles folder, but the only problem would be that an asp page will be able to write contents in that folder, so I guess that this is exactly what we want.
And for the web.config, it needs to be explained in the docs, but it just needs that entry without the rest of the settings available in a normal web.config, that way there are no conflicts about keys that can't be redefined further down.
Thanks for your feedback.