Client Fails to Complete Login (DNN 4.x)

Last post 04-16-2010, 1:51 PM by Eric. 2 replies.
Sort Posts: Previous Next
  •  04-14-2010, 2:29 PM 60101

    Client Fails to Complete Login (DNN 4.x)

    I downloaded the "Cute Live Support for DotNetNuke 4.x and 5.x" today (for evaluation).
     
    I have followed the installation instructions and everything seems to be in the right place.
     
    When I login on the client, the login itself succeeds (I attached the Visual Studio 2005 debugger to the process and traced
      
    DNNChatProvider.ValidateUser() which is returning true after setting the AuthCookie ).
     
    At that point the Login screen disappears for a longish while, then I get the following error:
     

     
    Any Ideas?
     
  •  04-14-2010, 4:20 PM 60111 in reply to 60101

    Re: Client Fails to Complete Login (DNN 4.x)

    I've done a little further investigation,
     
    I navigated to 
    http://my.site.com/DesktopModules/CuteSoft_Client/CuteChat/SupportService.asmx
    using IE on the actual server and invoked  SupportLogin
     
    It hasn't timed out using this method (after 20 minutes or so).
     
    Debugging reveals that repeated calls are being made to DNNChatProvider.GetUserInfo for users that are NOT currently on the site.  This is a development server and, at the moment, I'm the only one using it.
     
    Currently DNN_Users contains  5478 rows and DNN_SiteLog contains 2,082,999 rows.  (This database is a copy of a production database that has been active for about 3 years).
     
    I really, really hope that DNN_SiteLog is not being processed here.

    Ah, It just ended with <int xmlns="http://tempuri.org/">0</int>
     
    I did a quick Client Login and still timed out - so it's not a one-time deal.
     
     
     
     
     
     

  •  04-16-2010, 1:51 PM 60182 in reply to 60111

    Re: Client Fails to Complete Login (DNN 4.x)

    Dear astewart,
     
    I have tested DNN 04.09.05 and Cute LiveSupport, I cannot reproduce this issue.  Please follow steps:
    1. Open sql server profiler, and then login from operator client, copy the sql log and send it to [email protected] .
    2. Extract related DNN_Users and DNN_SiteLog  and also send it to me.
    We will investigate this issue.
     
    Regards,
    Eric
View as RSS news feed in XML