Winhost does not have a file manager.
I also set the <trust = "Full"...> in the web.config.

But I ran the query and got this... sorry for bad formatting:

FolderIDPortalIDFolderPathAllowAccessRoleNamePermissionKey
1   28   0   Gallery/397/   1   Administrat…   READ
2   30   0   Gallery/397/_source/   1   Administrat…   READ
3   29   0   Gallery/397/_thumbs/   1   Administrat…   READ
4   31   0   Gallery/397/Pour House Photos/   1   Administrat…   READ
5   33   0   Gallery/397/Pour House Photos/_sourc…   1   Administrat…   READ
6   32   0   Gallery/397/Pour House Photos/_thum…   1   Administrat…   READ
7   34   0   Gallery/398/   1   Administrat…   READ
8   36   0   Gallery/398/_source/   1   Administrat…   READ
9   35   0   Gallery/398/_thumbs/   1   Administrat…   READ
10   40   0   Gallery/401/   1   Administrat…   READ
11   42   0   Gallery/401/_source/   1   Administrat…   READ
12   41   0   Gallery/401/_thumbs/   1   Administrat…   READ
13   43   0   Gallery/401/Baseball/   1   Administrat…   READ
14   45   0   Gallery/401/Baseball/_source/   1   Administrat…   READ
15   44   0   Gallery/401/Baseball/_thumbs/   1   Administrat…   READ

Perhaps the READ permission key is the culprit.

Thanks again... and... nice dog!

Dan

Dan,

The trust setting in web.config will have no affect on this issue and most likely your hosting provider has limited trust level to "medium" anyway.

The DotNetNuke permissions shown in the query which you ran look OK and match those of several other working Gallery installs and also show that the various Gallery folders have been properly registered in the DotNetNuke database. Since this version of the Gallery writes directly to the filesystem, DotNetNuke folder WRITE permissions are not needed.

I also see that you either have or did have three separate Gallery modules added to various pages of your site. Am I correct that you are having the same problem uploading to ANY of the Gallery modules.

Regarding checking the ASP.Net worker process permissions - there should be some way in your hosting provider's control panel to set file system permissions. If not, I would suggest submittting a trouble ticket or otherwise requesting support from your hosting provider - something to the effect of "Please ensure that full filesystem permissions including modify have been granted to the ASP.Net worker process account (IIS Identy Account _____________) on this website's root install folder and that those permissions propagate to all child folders of the root." Fill in the blank with the ASP.Net Identity User information from the Host --> Host Settings page.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

Dan,

Congratulations on finding the problem. The cause makes sense in that the original file that is uploaded is placed unaltered in the _source folder but those in the album folder (the preview image) and the _thumbs folder are manipulated to create the resized versions. I would very much like to try one of your jpg images in a development environment so that I can debug step through the section of code which creates the rediced size image files to see where it is failing. You may send one or more to me via email to bill (at) wesnetdesigns (dot) com.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner