Hi,
I have followed Sue's tutorial on how to upload and configure my website. I am still having an issue when I try to configure permissions/roles using the ASP. Net configuration tool.
I am able to start it but when I click Security I get the error below. Also below is my web.conf file. I am hosting with gate.com, incase someone is with them as well and has had a similar experience.
If someone has maybe they can explain to me what some of those xml values mean. I can follow a tutorial but I am poor at troubleshooting because I don't know what all those valuse mean; provider, rolemanager etc.. Thank you.
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: EXECUTE permission denied on object 'aspnet_CheckSchemaVersion', database '695746_default', schema 'dbo'.
*****************************************************************************
WEB.CONFIG
*****************************************************************************

 

1    
2    <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
3      <connectionStrings>
4        <add name="Personal" connectionString="Data Source=sql002.whp.server-hosting.com;Initial Catalog=695746_default;Persist Security Info=True;UID=****;PWD=****" providerName="System.Data.SqlClient" />
5      </connectionStrings>
6      <system.web>
7        <pages styleSheetTheme="Black"/>
8    		<customErrors mode="RemoteOnly"/>
9    		<compilation debug="true"/>
10   		<authentication mode="Forms">
11   			<forms loginUrl="Default.aspx" protection="Validation" timeout="300"/>
12   		</authentication>
13   		<authorization>
14   			<allow users="*"/>
15   		</authorization>
16   		<globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
17   		<!--<roleManager enabled="true"/>-->
18       <membership>
19         <providers>
20           <remove name="AspNetSqlMembershipProvider" />
21           <add name="AspNetSqlMembershipProvider"
22           type="System.Web.Security.SqlMembershipProvider,System.Web, Version=2.0.0.0, Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a"
23           connectionStringName="Personal"
24           enablePasswordRetrieval="false"
25           enablePasswordReset="true"
26           requiresQuestionAndAnswer="true"
27           applicationName="/"
28           requiresUniqueEmail="false"
29           passwordFormat="Hashed"
30           maxInvalidPasswordAttempts="5"
31           minRequiredPasswordLength="7"
32           minRequiredNonalphanumericCharacters="1"
33           passwordAttemptWindow="10"
34           passwordStrengthRegularExpression="" />
35         </providers>
36       </membership>
37       <profile>
38         <providers>
39           <remove name="AspNetSqlProfileProvider" />
40           <add name="AspNetSqlProfileProvider"
41           connectionStringName="Personal"
42           applicationName="/"
43           type="System.Web.Profile.SqlProfileProvider,System.Web, Version=2.0.0.0, Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" />
44         </providers>
45       </profile>
46       <!--<roleManager enabled="true">
47         <providers>
48           <remove name="AspNetSqlRoleProvider" />
49           <add name="AspNetSqlRoleProvider"
50           connectionStringName="Personal"
51           applicationName="/"
52           type="System.Web.Security.SqlRoleProvider,System.Web, Version=2.0.0.0, Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" />
53         </providers>
54       </roleManager>-->
55   		<siteMap defaultProvider="XmlSiteMapProvider" enabled="true">
56   			<providers>
57   				<add name="XmlSiteMapProvider" description="SiteMap provider which reads in .sitemap XML files." type="System.Web.XmlSiteMapProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" siteMapFile="web.sitemap" securityTrimmingEnabled="true"/>
58   			</providers>
59   		</siteMap>
60   	</system.web>
61   	<location path="Admin">
62   		<system.web>
63   			<authorization>
64   				<allow roles="Administrators"/>
65   				<deny users="*"/>
66   			</authorization>
67   		</system.web>
68   	</location>
69   </configuration>
70   

 

Got it fixed, kind of
I went into the database on the server and gave explicity permissions for each of the stored procedures, including the one above, for the user I was trying to login with the ASP configuration.
I hope this was the right way. Maybe this is something that I was supposed to configure in the web.config file.
If someone knows, can they let me know if I did this correctly.
Thanks.

So it appears to be working. I've been trying to setup the permissions/roles and I'm a little confused. Is it possible to set permissions on individual files: for example if I only want certain users to access resume.aspx how do I set it?
Secondly, for some reason Allow for all user/roles is enabled and I cannot delete it. How do I disable this so that no one except for the users I specify have access?
Thanks.

If you put the resume.aspx in the admin folder or in a seperate folder you can then control who has access through their role in the configuration tool

On the seocnd part, do you mean access to the site or to an individual page?

Please check your database user roles.
It's necessary the database user to be owner.
Only it.

I fixed this by adding the following role memberships to the users:

aspnet_Membership_BasicAccess

aspnet_Membership_FullAccess

aspnet_Membership_ReportingAccess

Please kindly advise detailed steps of what you have done. Thanks.

 

ViniciusCamara:

Please check your database user roles.
It's necessary the database user to be owner.
Only it.

Assigning db_owner to your user will give them more access than they need.

What you should instead do, is grant the user the following Roles:

• aspnet_Membership_FullAccess
• aspnet_Roles_FullAccess
• etc. depending on what features you have enabled/installed into this database

1. Connect to the database you are working with
2. Open Databases
3. Open the database you are working with
4. Open Security
5. Open Users
6. Double-click the user who is accessing the database
7. In the list of Owned Schemas, check off the roles indicated above

Hi,

I was Also Facing Same Problem

I got the solution

By executing this queries in Query Analyzer

 

GRANT EXECUTE ON dbo.aspnet_CheckSchemaVersion TO "myUserName"

GRANT EXECUTE ON dbo.aspnet_Membership_CreateUser TO "myUserName"

GRANT EXECUTE ON dbo.aspnet_Membership_GetPasswordWithFormat TO "myUserName"

 

 

 Thanks

Hi,

I was Also Facing Same Problem

I got the solution

By executing this queries in Query Analyzer

 

GRANT EXECUTE ON dbo.aspnet_CheckSchemaVersion TO "myUserName"

GRANT EXECUTE ON dbo.aspnet_Membership_CreateUser TO "myUserName"

GRANT EXECUTE ON dbo.aspnet_Membership_GetPasswordWithFormat TO "myUserName"

 

 

 Thanks

I tried everything above which is working fine when its in local system. but not for development server where we dont have permission for the database user.

finally i have got solution its very simple.

in SQL Server>
   Database>
        <My database Name>
                Security
                       Schemas

Select dbo Schemas > properties > Select Permission >
In that users and role section
Add your login User Name [given user name for your database in development server]

It works fine.

I tried everything above which is working fine when its in local system. but not for development server where we dont have permission for the database user.

finally i have got solution its very simple.

in SQL Server  
   Database
        My database Name
                Security
                       Schemas

Select dbo Schemas - properties - Select Permission
In that users and role section
Add your login User Name [given user name for your database in development server]

It works fine.

Thank you for the time you took to write this.

 

umbyersw:

Do this by using Microsoft SQL Server Management Studio or Microsoft SQL Server Management Studio Express

1. Connect to the database you are working with
2. Open Databases
3. Open the database you are working with
4. Open Security
5. Open Users
6. Double-click the user who is accessing the database
7. In the list of Owned Schemas, check off the roles indicated above