Published the app, no one can log on

[dgk]

Using the default SQLExpress provider for membership and profiles, I
published an app and moved the current development ASPNETDB files to
the production machine. It works great, the login page is presented,
but all the users are invalid.

Anyone know what I'm supposed to do to make it work? If it matters,
I'm using the default provider but changed the application name in the
provider section(s) of web.config to give the app a name other than
"/", but that is the only thing that is non-standard.

[Karl]

If you changed the Application name in web.config, dont you have to
change in the aspnet_application table too?

dgk wrote:

Using the default SQLExpress provider for membership and profiles, I
published an app and moved the current development ASPNETDB files to
the production machine. It works great, the login page is presented,
but all the users are invalid.

Anyone know what I'm supposed to do to make it work? If it matters,
I'm using the default provider but changed the application name in the
provider section(s) of web.config to give the app a name other than
"/", but that is the only thing that is non-standard.

[dgk]

On 15 Sep 2006 13:10:52 -0700, "Karl" <go**********@tlbsolutions.com>
wrote:

>If you changed the Application name in web.config, dont you have to
change in the aspnet_application table too?

But I added all the users after changing the name of the app. It
works fine on the development machine.

>dgk wrote:

>Using the default SQLExpress provider for membership and profiles, I
published an app and moved the current development ASPNETDB files to
the production machine. It works great, the login page is presented,
but all the users are invalid.

Anyone know what I'm supposed to do to make it work? If it matters,
I'm using the default provider but changed the application name in the
provider section(s) of web.config to give the app a name other than
"/", but that is the only thing that is non-standard.