Operator App Crashes on Support Requests

  •  09-29-2006, 12:31 PM

    Operator App Crashes on Support Requests

    Hello!
     
    I am going through a trial of the Cute Live Support, and when I tested in a standalone VPC everything worked.  I have moved it into a test environment that has the operator console (currently only installed on my machine) and the server separated.
     
    I can start the console and say that "I am ready".  I can then open a browser on another machine, hit the server, and see that I can get support (so it recognizes that I'm logged in).  I can request support, and the chat applications come up on both machines.  But after a second or two (it's a very short period of time), the operator app crashes with a message saying that it's sorry but something has gone wrong and it must close.
     
    One of the more interesting aspects of this "crash" is that as long as I don't click "OK" and instead just leave the crash box there, I can continue with the two-way chat.  The "crash" doesn't impact my ability to chat until I click OK to let it close the application.
     
    I have a development environment on my machine, so I am able to click "Debug" and see what it has to say.  Each crash has the following error: The remote server returned an error: (407) Proxy Authentication Required.  We do have a proxy environment, but you're only prompted if you're trying to go outside the network to the Internet.  My best guess is that perhaps the server is trying to "phone home" and verify the license?  Something else entirely perhaps?
     
    A more detailed stack trace shows the following:
       at System.Net.HttpWebRequest.GetResponse()
       at LiveSupport.IPInfo.GetIpData(String ipAddress, String& country, String& city)
       at LiveSupport.IPInfo.LoadAsync(Object state)
       at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
     
    The "Status" value is: System.Net.WebExceptionStatus.ProtocolError
     
    Are there proxy settings I need to configure either on the server or on the operator client to get it to work?  Any assistance on this matter would be greatly appeciated.  We're fairly certain we're going to purchase a 10 domain license, so if the only way around the problem is to have a fully-licensed product, we can go that route as well.
     
    Thank you!
    Jason W. Pegg

    Jason W. Pegg
    Application Architect
    Telect
View Complete Thread