{"id":365,"date":"2014-07-08T16:04:27","date_gmt":"2014-07-08T20:04:27","guid":{"rendered":"http:\/\/www.amixa.com\/blog\/?p=365"},"modified":"2014-08-19T15:59:51","modified_gmt":"2014-08-19T19:59:51","slug":"aspmaker-v11-image-resizer-not-working-under-iis","status":"publish","type":"post","link":"https:\/\/www.amixa.com\/blog\/2014\/07\/08\/aspmaker-v11-image-resizer-not-working-under-iis\/","title":{"rendered":"ASPMAKER v11 Image Resizer not working under IIS"},"content":{"rendered":"

If you are using ASPMAKER by HKVSTORE to build web admin interfaces, and you’ve arrived at this page, it’s likely because the Image Resizer ASP.NET add-on is not working for you.<\/p>\n

Does this look familiar to you?<\/p>\n

Warning: ASP.NET 2.0 or later is required but ASP.NET script is not executed properly on this server:<\/strong><\/p>\n

see this screenshot:\"2014-07-08_15-47-49\"Here is the solution to the issue.<\/p>\n

    \n
  1. You need to have a HOSTS file entry on the server that will allow the server to resolve the domain name for the website you are using ASPMAKER and the Image Resizer on.\u00a0 This is because the ASP.NET resizer uses MSXML2.ServerXMLHTTP\u00a0to locally fetch and resize the image.\u00a0 If there is no HOSTS file entry on the local server, there is no way for the resizer to work.<\/li>\n
  2. Open the HOSTS file and add an entry like this<\/li>\n
  3. \u00a0X.X.X.X\u00a0\u00a0 your.domain.name<\/li>\n
  4. \u00a0Make sure the upload folder\u00a0is set properly\u00a0in ASPMAKER here:\"file<\/li>\n
  5. \u00a0This path will be relative to the folder you have deployed the ASPMAKER files to on the server.\u00a0 For example, if the ASPMAKER files are in the directory \/123\/ then the upload folder (pictured above) will be \/123\/upload-temp\/<\/li>\n
  6. set the permissions properly on the \/upload-temp\/ folder.\u00a0 this means adding machinename\\IUSR and granting full control.<\/li>\n
  7. Inside ASPMAKER, make sure the destination folder is correct.\u00a0Note I had to use “..\/” to get ASPMAKER to upload to the correct path off the root.\u00a0 It is NOT necessary to grant this folder any special permissions.<\/strong><\/em>\"correct-path\"<\/li>\n
  8. Make sure the base site itself has a valid application pool assigned.\u00a0 Here’s what mine looks like (It is not necessary to have an application for the subdirectory where the ASPMAKER app). \"app\"<\/li>\n
  9. NOTE: depending on your setup, it may be necessary to set the .NET CLR version to v.2.X above.\u00a0 (I HAD TO USE v.2.X for my setup…)<\/strong><\/em><\/li>\n
  10. Adjust the maximum file upload size in ASP.\u00a0 ASP->Limits Properties ->Maximum Requesting Entity Body Limit.\u00a0 The default value is 200,000 (200000) which is 200,000 bytes.\u00a0 I upped mine to 20,000,000 (leave out the commas here).<\/li>\n
  11. Launch the ASPMAKER web admin and try uploading an image.\u00a0 The above should take care of all the issues.<\/li>\n<\/ol>\n

    Let me know if this saves you a headache!<\/p>\n

     <\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    If you are using ASPMAKER by HKVSTORE to build web admin interfaces, and you’ve arrived at this page, it’s likely because the Image Resizer ASP.NET add-on is not working for you. Does this look familiar to you? Warning: ASP.NET 2.0 or later is required but ASP.NET script is not executed properly on this server: see this screenshot:Here is the solution<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[33,4],"tags":[98,97,103,5],"class_list":["post-365","post","type-post","status-publish","format-standard","hentry","category-classic-asp","category-iis-tips-n-tricks","tag-asp-net","tag-aspmaker","tag-classic-asp","tag-iis"],"_links":{"self":[{"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/posts\/365","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/comments?post=365"}],"version-history":[{"count":4,"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/posts\/365\/revisions"}],"predecessor-version":[{"id":376,"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/posts\/365\/revisions\/376"}],"wp:attachment":[{"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/media?parent=365"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/categories?post=365"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/tags?post=365"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}