Search

You searched for the word(s):
< 1 second(s)
  • Re: Login Form return OK, but lgoin failed!

    Thanks Terry!&nbsp; This fix corrects the problem.
    Posted to Cute Live Support (Forum) by wakkinen on September 3, 2009
  • Re: Login Form return OK, but lgoin failed!

    Hey, &nbsp; No, I've not yet fixed the issue, If I remove if (System.Web.Security.Membership.Provider.Name == ''AspNetSqlMembershipProviderLiveSupport'') then it trys to use the default provider to get the authentication, and I need it to use AspNetSqlMembershipProviderLiveSupport for the users that can use the LiveSupport tools. &nbsp; Still ...
    Posted to Cute Live Support (Forum) by wakkinen on September 1, 2009
  • Re: Login Form return OK, but lgoin failed!

    The problem happens for both... ''Login Form return OK, but login failed!''&nbsp; it doesn't matter what user type I try to login with... the key is to use the alternate application because the website already has an application name... so there needs to be a way to pass the application name along with the connection attempt.&nbsp; &nbsp; I ...
    Posted to Cute Live Support (Forum) by wakkinen on August 31, 2009
  • Re: Login Form return OK, but lgoin failed!

    Hey Adam, &nbsp; I did as you suggested: &nbsp; isAdmin = true; // System.Web.Security.Roles.Providers[''AspNetSqlRoleProviderLiveSupport''].IsUserInRole(user.UserName, ''Admin''); However the same problem persists...&nbsp;&nbsp; another suggestion? &nbsp; Thanks, &nbsp; Michael
    Posted to Cute Live Support (Forum) by wakkinen on August 31, 2009
  • Re: Login Form return OK, but lgoin failed!

    I'm having the same problem ''Login Form return OK, but login failed!'', here is my&nbsp;chat provider code:&nbsp; (when I use the default provider in the web.config and alter the code to use the default one instead of the secondary one, I can connect fine but this provider using an admin instance doesn't work.)&nbsp; What am I missing ...
    Posted to Cute Live Support (Forum) by wakkinen on August 29, 2009