BUG – Permissions removed from an application root folder
Last post Apr 23, 2012 01:08 PM by GrZeCh
Jul 31, 2011 06:19 AM|LINK
Below is a copy of Jeremy’s email. Because he didn’t contact me,
I ASSUME THEY WERE ABLE TO REPRODUCE THE ISSUE.
Sent From: Jeremy Phelps
Subject: BUG - Permissions removed from an application root folder
I'm Jeremy with the Escalation Services team for WebDeploy and WebMatrix and I wanted to follow up with you and let you know that we are still
investigating it. We have not yet reproduced this. If we are unable to get a repro soon, would you be available to run some tools to collect more data from your system?
Aug 03, 2011 10:14 AM|LINK
I am still sending one or two emails per day. No response so far …
Aug 05, 2011 06:01 AM|LINK
Microsoft has published the solution on ‘Microsoft Connect’:
Unfortunately, I can’t test it before the end of the next week.
GrZeCh, could you test this solution and post the result here, please?
Sep 04, 2011 10:51 AM|LINK
have you tested fix from connect.microsoft.com website? I've applied id and so far it works.
Sep 04, 2011 11:31 AM|LINK
Not yet. Will try next week.
Nov 07, 2011 08:25 PM|LINK
have you maybe checked mentioned solution? For me it looks like it is nor working correctly. Today one of my clients published Umbraco project and all of files located in wwwroot folder of application had removed permissions. I had to take ownership for
whole directory to make it browsable again.
Nov 08, 2011 07:17 AM|LINK
Nov 09, 2011 07:54 PM|LINK
Wow, I think that I have finally found the source of great frustration! I have been troubleshooting my IIS folder permissions for months. Everything would be working fine, and then I would check something, and boom, no more website. I even told one of
the MS Website spark hosting providers to shove it, cause they kept blaming it on me.
Here's my situation: I have an existing Wordpress Site that I host locally. I had the great idea of making it faster by moving the site to a Website Spark hosting provider and then using webmatrix to make code edits and develop plugins and themes. Every
time I would turn around, the site would go down, and i could never track down the reason. Apparently it was because I uploaded my locally tested code, and it changed all of my site permissions. I knew it was a permissions issue, and tried to work with the
hosting provider to resolve, but they insisted it wasn't their problem. I thought that the hosting provider was to blame, bad hardware or something, but after reading this thread I am sure that it's webmatrix. Moreover, I have recently had the SAME exact
issue after I tried to view my site code locally in webmatrix. It sounds like I'll be having the same trouble in VS which sadly brings me back to notepad or dreamweaver to do all of my site code.
Nov 10, 2011 05:31 AM|LINK
I have received a private message from
harshmittal (see below). Because I am really tired of the incompetence of
Microsoft I think that I will abandon the Microsoft hosting solution an offer to my customers only LAMP solution. Anyone interested in continuing this thread is welcome.
My name is Harsh Mittal and I am Senior Program Manager with Web deploy team. First of all, I apologizethat solution provided by Microsoft did not resolve the issue.
Beforeposting the solution to connect, team verifies that solution actually works forthe repro we have in house. But many a times our in house repro may not be the best representation of your environment.
In order to proceed further and resolve the issuesyou are still facing, we will need detailed explanation of the current issue.
Can you pleaseprovide us detailed repro steps and problem you are facing with current workaroind, so that WebDeploy team can work towards solving this issue?
Nov 14, 2011 04:33 PM|LINK
If anyone else is still experiencing the issue after applying the workaround, please share the description of the problem, either by re-opening the issue through connect or by directly messaging me. As I communicated to Maciej and few others privately that
Webdeploy team is fully committed to resolve the issue.