I'm trying to figure out why my FBA keeps breaking down on me. It has happened on two servers now. I've gotten FBA up and running, added users, etc. Then after a day or two users begin to not be able to log in. The aspnetdb seems to be fine, the users are not showing signs of being locked out. If I try to log in, I get a '..check your user name and password.." type error shown on the fba login screen. The first time in a group of login attempts seems to throw an error to the event log, but after that, subsequent attempts do not log an error. I have seen both 4005 and 4006 errors in the log on these occasions.

I've checked my web.config, the timeouts seem fine and the application names are all set to "/".

I've tried deleting the aspnetdb and recreating it, though after the recreation, Central Administration can no longer find any users to add them to the web application administrators group. Therefor I can't update the site settings or give anyone access to the site.

I'm not sure if this has anything to do with using SPCommands for Powershell to set up the FBA. Please let me know if anyone has experienced similar issues using this setup package. I'm using it because in the production environment we will not be able to install visual studio to get the aspnetdb initial user created. Are there any other ways of getting the db setup without VS

That sounds like exactly what I've been looking for. I'll check it out now and see if it solves my users becoming disabled problem.

Thanks,

Evan

Make a *.bat file e.g. StartAdmin.bat

Add the following lines to it:

@echo off
SET FrameWorkFolder=C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
SET VFolder=Asp.NetWebAdminFiles
SET Port=8099
SET App=/
SET AppPath=C:\Inetpub\wwwroot\wss\VirtualDirectories\81

explorer "http://localhost:%Port%/%VFolder%/default.aspx applicationPhysicalPath=%AppPath%&applicationUrl=%App%"

%FrameWorkFolder%\WebDev.WebServer.EXE /port:%Port% /path:%FrameWorkFolder%\%VFolder% /vpath:/%VFolder%

Where AppPath is the physical path to your WSS-web adn select any free Port you like. In the example above a WSS-web running on port 81. The WebDev-Webserver will start on port 8099.

Greetings, Peter

<membership defaultProvider="yourprovidername">

<providers>

<remove name="yourprovidername" />

This is really helpful... much better than having to install visual studio.

Thanks,

Evan

Well this has solved my problem of being able to create the database and first user without having visual studio installed, but does anybody know anything about why the users are losing access to the site It being a progressive issue, it may take a few days to take affect, but I still don't know how I can fix it if it happens at the client site, or sometime in the future here in development. Let me know if you have any suggestions.

Thanks,

Evan