By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,740 Members | 844 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,740 IT Pros & Developers. It's quick & easy.

Website Administrator writes two instances of each user into the database

P: n/a
I applied aspnet_regsql to SQL2K which was working fine throughout Beta 2
development. After installing Visual Studio and SQL Express RTM my
application has blown up. Logging in to the application became
realllllllllllly slow. Content in LoginView Role Groups was not displaying
even after a user in a role had logged in.

It was taking about 15 seconds or so for the login control to display when
the login link was selected on the homepage. I would hear two page clicks
after selecting the Login link. hearing two clicks made me wonder if the
page was posting back twice. Furthermore, entering text into textbox
controls on a page now throws a stack overflow at line: 0 in a windows
dialog. This is the oddest page behavior I have ever experienced. Hello 2.0.

So this all made me suspicious and I went into the database and observed
there were two instances of each user in the aspnet_Users table, a table
that is created by aspnet_regsql when setting up Membership, Roles and
Profiles.

After observing the redundant records I then used the Website Administration
tool to delete all users and confirmed no user could login to the
application. It was interesting to note the login control would then load
without waiting when trying to login from the homepage. The performance
problem seemed to have been resolved. I hoped I had resolved the entire
problem but stack overflows persisted when entering text into textboxes
displayed by an instance of the Wizard control.

What is interesting to observe is the stack overflow does not happen until
the second step in the Wizard control and the value is always at line zero
for all subsequent steps in the Wizard control each of which will throw the
error into a dialog when selecting the Wizard's next button. I really have
no experience with overflow circumstances in a web page so I went back into
the database to look around.
Lo and beholdski the aspnet_Users table still contained records populated
with user data. The same redundant instances (two of each user) were still
present in the database even though I had used the Website Administrator to
delete users. So I used Enterprise Manager and deleted all aspnet_* tables
and ran aspnet_regsql on the database thinking a fresh install of Membership
would resolve this problem and get rid of the redundant records and all
users which was okay because the users were proxy test dummies.

After applying aspnet_regsql I confirmed the aspnet_ tables were installed
into the database restoring a fresh instance of Membersghip. The
aspnet_Users table was empty and I started feeling I would not see anymore
stack overflows. So I then used the Website Administration tool and created
two users. Tried to login and the same thing all over again.

Each user is being created in the database twice and the stackI applied
aspnet_regsql to SQL2K which was working fine throughout Beta 2. After
installing 2.0 RTM I'm having all kinds of problems. Logging in became
realllllllllllly slow. Content in Role Group sections was not displaying
even though a user with a role had logged in after waiting for 15 seconds or
so for the login control to display when the login link was selected. I
would hear two page clicks when selecting the Login link. Furthermore,
entering text into textbox controls now throws a Stack overflow at line: 0
error.

This made me suspicious and I observed there were two instances of each user
in the aspnet_Users table.

I used the Website Administration tool to delete the users and confirmed no
user could login and the display of the login control appeared snappy as one
would expect yet stack overflows persisted. I then observed the aspnet_Users
table still contained the users including redundant instances (two of each
user). So I used Enterprise Manager and deleted all aspnet_* tables and ran
aspnet_regsql on the database thinking a fresh install of Membership would
resolve this problem.

After applying aspnet_regsql I confirmed the aspnet_* tables were installed
into the database and the aspnet_Users table was empty. I then used the
Website Administration tool and created two users. Tried to login and the
same thing all over again.

Each user is being created in the database twice and the stack continues to
overflow.

What the fugowi could be going on here?
<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/

Nov 22 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.