The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Dell Chat Problems

    Discussion in 'Dell' started by 640k, Jan 9, 2008.

  1. 640k

    640k Notebook Evangelist

    Reputations:
    35
    Messages:
    305
    Likes Received:
    2
    Trophy Points:
    31
    Anyone ever get this error?

    HTML:
    <?xml version="1.0" encoding="utf-8" ?> 
    - <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP-ENV:Header /> 
    - <SOAP-ENV:Body>
    - <SOAP-ENV:Fault>
      <faultcode>SOAP-ENV:Server</faultcode> 
      <faultstring>Unable to Connect to Talisma Server at 143.166.82.15</faultstring> 
    - <detail>
    - <e:faultdetails xmlns:e="urn:netagent600fault">
      <message>Request exceeds maximum size</message> 
      <errorcode>99999</errorcode> 
      </e:faultdetails>
      </detail>
      </SOAP-ENV:Fault>
      </SOAP-ENV:Body>
      </SOAP-ENV:Envelope>
    I get this error everytime I try to connect to Dell Chat. No matter which option I choose. No matter which computer I use. Are the servers just that full? Is that all the message is? Because 9 times out of 10, the wait queue is under 10 minutes.
     
  2. ThePug

    ThePug Notebook Consultant

    Reputations:
    13
    Messages:
    161
    Likes Received:
    0
    Trophy Points:
    30
    It's on their end. Nothing you can do.
     
  3. 640k

    640k Notebook Evangelist

    Reputations:
    35
    Messages:
    305
    Likes Received:
    2
    Trophy Points:
    31
    I figured, but I haven't been able to use Dell Chat in like a month.
     
  4. sinstoic

    sinstoic Notebook Deity

    Reputations:
    214
    Messages:
    1,028
    Likes Received:
    0
    Trophy Points:
    55
    Well as you can see SOAP in the code, you can assume the representative has gone for a bath! :rolleyes:

    You could try:
    Refreshing the page.
    Closing the browser and opening again.
    Clearing cookies, closing the browser and opening again.

    If all else fails, try after sometime as their servers could be busy or shutdown.

    Hopefully, the representative will be back at the system after a refreshing bath! :rolleyes: