Last post Jan 31, 2019 10:52 PM by jzero
Jan 29, 2019 11:36 PM|Gatwick|LINK
I am trying to start one legacy project and faced wit the following issue. It is a classic WebForms app with classic ASP.NET membership tables in the DB. To manage users & roles I start
"C:\Program Files\IIS Express\iisexpress.exe" /path:c:\windows\Microsoft.NET\Framework\v4.0.30319\ASP.NETWebAdminFiles /vpath:"/asp.netwebadminfiles" /port:8089 /clr:4.0 /ntlm
Then I start this url in the browser:
It shows then the start screen but when I click on "Security" tab I get this error:
There is a problem with your selected data store. This can be caused by an invalid server name or credentials, or by insufficient permission. It can also be caused by the role manager feature not being enabled. Click the button below to be redirected to
a page where you can choose a new data store.
The following message may help in diagnosing the problem: Access to the path 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\1472b2f8\d4121b9a\hash' is denied.
In the DB role manager feature has been enabled fore a while. What am I doing wrong?
Jan 30, 2019 12:24 AM|jzero|LINK
ASP.NET Web Site Administration Tool was created to be used with Visual Studio (i think until VS2012), and not to be hosted by a server.
In old times it was just to help you learn about Membership, Roles and Profiles and create some users during development. On production WebSite, we had to create our own User Management interface, to deal with users.
Anyway you should have a file named aspnetdb.mdf on App_Data folder used to store all Users, Roles & Profiles. If not may be all Membership tables are integrated to your main database, in this case look for tables starting with names like "aspnet_"
But, I suggest you forget about ASP.NET Web Site Administration Tool for a moment and check if you can load your site just using
http://localhost:8089 it should at least load a login page if Membership is in place.
If it loads, look for a User Management Interface, it is supposed to have one, (it was expected developer made one).
Jan 31, 2019 11:52 AM|Gatwick|LINK
The link http://localhost:8089 is available, the underlying DB has full set of tables for Aspnet Membership, but when I click on "Security" link this error comes up.
Jan 31, 2019 01:44 PM|jzero|LINK
Just a guess, in past sometimes we had to cleanup Temporary files.
Go to C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files and delete all files under it if any exist.
Also look at %temp%\Temporary ASP.NET Files, and delete files and folder under it
In your case message is pointing to "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET" and is expected to have a subfolder name "root" (as you can see on msg)
In my case when I do same, temporary is in %temp%\Temporary ASP.NET Files
These files should be recreated due to Dynamic Compilation as soon you load URL
To know more about Dynamic Compilation
Jan 31, 2019 01:54 PM|Gatwick|LINK
I purged all folders & files in "Temporary ASP.NET" , issued IISRESET but no luck, still getting this "access denied" message
Jan 31, 2019 07:24 PM|jzero|LINK
Sorry if I missed "access denied" on initial msg.
The fact of all temp been removed exclude any possible corrupted file.
So we back to "access denied", check permissions on Temporary ASP.NET files, subfolder and files
I checked here (default permissions) on same path as you have they are
Administrator : Full Control
Users : Read & Execute, List Folders, Read
IIS_IUSRS : Modify, Read & Execute, List Folder, Read, Write <--- Is this permissions in place for group IIS_IURS
Trusted Installer : List Folder
Jan 31, 2019 09:41 PM|Gatwick|LINK
For my instance of "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files" I have these users explicitly enlisted there:
All of them were granted "Full Control" or" Write & Modify" at least. But the error still appears...
Jan 31, 2019 10:52 PM|jzero|LINK
Everything point to User Permission, "defaults" was supposed to work, but if for "some reason" the user is not one in permissions.
My last choice would be try to discover which user is getting "Access Denied", I mean Current User, Application Pool user, or any other.
Perhaps this article help you to discover which user is getting "Access Denied" on the process.
By the way I used exact same command line here and no error, it worked fine.