The login control used on the login web page has an option for creating an account.  Use that to create the administrator account, then go to your GoDaddy account, navigate to the aspnet_Membership table and mark the IsEnabled box for the record you created.

Use ' not "

Tim Stover

Ok to add Admin locally In VWD, click website, click asp.net configuration and create administrator in the asp.net configuration page. When you close that page VWD will ask if you want to save the changes made, click yes.

Everything in this statement makes no sense

That might work, but if you have a much more sophisticted SQL database, do this

Open your "Creatalltables.sql" or whatever it's named in your club kit, replace all "dbo" with the godaddy sql database login name.

Execute query and you've created all tables. 

1.Then SELECT RoleId FROM aspnet_Roles WHERE RoleName = 'Administrators'

Click Submit and save the return value

2.Copy the following T-SQL statement into the Query Analyzer window:
SELECT UserId FROM aspnet_Users WHERE UserName = '<username>'

Replace <username> with the user name of the account to which administrator privileges will be granted.

Click Submit and save the return value

Copy the following T-SQL statement into the Query Analyser window:
INSERT INTO aspnet_UsersInRoles (RoleId, UserId) VALUES ('<roleID>', '<userID>')

Replace <roleID> with the return value from step 1. Replace <userID> with the return value from step 2.

Click Submit

You're now admin

For this step i'm gettin really confused. With the replaced text, do i have to put my public website information for the ClubSiteDB? I'm not sure which one to modify and which one stays default. or just what to modify in general. can someone put their modifed replaced example with a fictitious public website? Would really appreciate it. Thanks for the walkthru btw!

1. Replace original text

   1. <add name="ClubSiteDB" connectionString="Data Source=.\SQLExpress;
            Integrated Security=true;
            AttachDBFileName=|DataDirectory|Club.mdf;
            User Instance=True" providerName="System.Data.SqlClient"/>

2. With new text

   1. <add name="ClubSiteDB" providerName="System.Data.SqlClient"
            connectionString="server=whsql-v04.prod.mesa1.secureserver.net;
            database=DB_12345;
            uid=myusername;
            pwd=mypassword"/>

      <remove name="LocalSqlServer"/>
      <add name="LocalSqlServer" providerName="System.Data.SqlClient"
            connectionString="server=whsql-v04.prod.mesa1.secureserver.net;
            database=DB_12345;
            uid=myusername;
            pwd=mypassword"/>

Also. I've tried redoing these steps over and over. and something that is tripping me up is when i do the club-add sql query. It won't add the other tables like asp_UserInRoles table. I don't see it at all especially in the sql statement. The first time it worked, but then i backed up my SQL Server DB and tried it again, and don't see it anymore.

Pls help. I feel i'm just tryin' way too hard then is needed. and it sucks to be an MIS Grad and struggle with this.

Ok You posted a question about connection strings to a posting concerning granting admin rights in the SQL databse. Here's how to do your web.config file connection strings

<connectionStrings>
<add name="ClubSiteDB" connectionString="Data Source=pswhsql-v.shr.phx.secureserver.net;Initial Catalog=XXXXXX;User ID=XXXXXX;Password=XXXXX;Trusted_Connection=False" providerName="System.Data.SqlClient" />
<remove name="LocalSqlServer" />
<add name="LocalSqlServer" connectionString="Data Source=pswhsql-v.shr.phx.secureserver.net;Initial Catalog=XXXXXX;User ID=XXXXX;Password=XXXXX;Trusted_Connection=False" providerName="System.Data.SqlClient" />
</connectionStrings>

Godaddy sucks in a huge way, you'll need to jump thru hoops to grant Admin in the SQL database.

I've jumped thru all godaddy's hoops and have managed to get all my sites working

in spite of godaddy being a bunch of near do wells. I feel bad for people who've signed up with godaddy

thinking they actually got a discount  server host when really it's a bait and switch.

Good luck

Create your tables then do this:

exec aspnet_Roles_CreateRole '/', 'Administrator'

houstonman89@yahoo.com:

Godaddy sucks in a huge way, you'll need to jump thru hoops to grant Admin in the SQL database.
I've jumped thru all godaddy's hoops and have managed to get all my sites working
in spite of godaddy being a bunch of near do wells. I feel bad for people who've signed up with godaddy
thinking they actually got a discount  server host when really it's a bait and switch.

I hope you can find time to write an FAQ for those using GoDaddy. From the many posts I have seen concerning problems with hosting at GoDaddy, such an FAQ would be greatly appreciated.

Where is the FAQ section?

 You will not be able to post directly to the FAQ, so I suggest that you start with a post to http://forums.asp.net/158.aspx

Eventually the FAQ moderator will see the value of the thread and move it to the FAQ forum.

when I do my last query, trying to get admin role for a few users, I enter this,

INSERT INTO aspnet_UsersInRoles (RoleId, UserId) VALUES ('110c5802-bc08-4e09-9263-97263ca8d44b', '110c5802-bc08-4e09-9263-97263ca8d44b')

and get this error,

The INSERT statement conflicted with the FOREIGN KEY constraint "FK__aspnet_Us__UserI__37A5467C". The conflict occurred in database "dbname", table "dbo.aspnet_Users", column 'UserId'. The statement has been terminated.

 Yea this is a really big problem that GoDaddy doesn't bother to let thier customers know. It's because you need to execute a query to name a table of your DB name, for instance; If your DB name is spectrum then execute a query and create table "spectrum.aspnet_Users". The easiest way is to open your SQL database in VWD 2008 and find & replace all your "dbo" to your database name. I still have the dbo tables in the database as well.

Good luck

Hi,

  I have exactly same issue as you have. Hope you would have solved this issue earlier. Can you help me out to solve this?

For Your Note: "I have Windows Server 2003 , And I deployed in this Server's IIS. "

I am waiting for your response. Your help in this would be highly appreciated.