For whatever reason I seem to be unable to access my /images/products folder on all 4 of my sites. I have set permissions, had the host confirm permissions and all seems to be in order but still can't access the images via the BVC image browser. Oddly enough I can access anything within the /images folder itself, just not the /products sub-folder.

This is the response I got from my host support and am wondering if it is a web.config issue with IIS7

***********************************************
I tried to access one of the images directly that are listed in the image browser:
http://www.yourticketzon...ages/products/qtlogo.jpg

and it gives a 'File Not Found error'. The image is physically there, but permissions seem fine on the file and it's folder.

At the same time I ran Sysinternals ProcessMonitor, which showed:

---

Process Name w3wp.exe
Operation: CreateFile

PATH NOT FOUND

---

(notice the web.config file at the end of the path?)

It seems that something in your settings is causing this. As a test, for a brief moment I renamed your web.config file so that it wasn't active, and then I was able to directly access http://www.yourticketzon...ages/products/qtlogo.jpg

So this appears to be something in your settings in web.config. You may want to ask BV Commerce about this.

*******************************************************

Any ideas?

Thanks,
Derekl[orange] [/orange][b][i][b][i]

Hi Andy,

No I haven't found a solution....except to move the images out of the /products folder and into the /images folder.

Thanks,
Derek

We identified the problem as a conflict with the URL rewriter. By default, the urls for products are written as /Products/SKU-Name-etc.aspx and the URL rewriter is looking at the tail of the /images/products url and causing it to redirect incorrectly.

For now, you can change the /images/products folder to another name like /images/products2 or you can change the URL rewriter default settings under Options->Performance.

Also, make sure that you have given the correct user accounts permissions to read/write files. The application pool in IIS 7 may be running under a different user account than your IIS 6 site.

Change the app pool to run in classic mode. Seems to work without any other changes.