Yes, the path is correct.
c:\>cd "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files"
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files>
The double quotes are required because of the spaces in the folder name.
As a test, make sure that the command prompt is dragged wide enough to fit the command in one line before pasting it in case the command is carrying over to the next line and not being properly executed.
Please go ahead and post a screenshot showing the command prompt after using the attrib command to see if anything may stand out.
Thanks Brink.
I didn't know that might cause a problem. I will store that in one of my brain cells.As a test, make sure that the command prompt is dragged wide enough to fit the command in one line before pasting it in case the command is carrying over to the next line and not being properly executed.
Back to watching.
The read only attribute is in almost every case totally irrelevant and always ignored.
Look again at the error message, I'm pretty sure it clearly refers about permissions and not to "read only". The usual cause of this error is that the web server cannot write to that temporary location, so you must give its user account write permissions there. This often happens when deploying in a real web server, as opposed in development with the Visual Studio toy dev server.
In response to Brink's suggestion, the command was run again in an expanded command prompt to prevent wrapping of the command. The result was the same though.
C:\>attrib -r +s "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NETFiles"
File not found - C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NETFiles
In response to Alejandro85's comment about the permissions, the scenario I've encountered seems to be identical to that described in the MS Tech Note (https://support.microsoft.com/en-us/kb/326549). Their recommendation is to run the command shown above as an Administrator.
I'll have to find a work-around for the time being and hopefully can address this at a later date. If I come upon a solution, I'll check back and will post the solution on this forum.
Brink - thanks for all of your help on this.
If you like, you might see if taking ownership of the folder may help.
Take Ownership Shortcut
Quote