XMLHTTPRequest Open Failed

[twhiting9275]

Ok, so I'm really, really not trying to spam new threads (I promise), but another one that came up yesterday, completely and totally boggled me.

For 2 weeks my LR setup had been running just fine, no changes, no problems, no server moves, nothing at all. All of the sudden, I received the following error (see attachment)

I went to the admin side of things, copied the URL, pasted it into the LR application, saved, applied, all that jazz (it hadn't changed, mind you), and restarted the application, only to get the same error. This repeated for a good 30,45 minutes.

What could have caused this instant problem, when nothing had changed at all on the server (or application) side, and why did it persist. Better yet, why did it suddenly stop acting up?

Like I said, nothing had changed, so, it makes no sense that the application would suddenly just do this.

[Varun Shoor]

The error you receive is independent of the actual application. That error is actually thrown up inside IE.

For some reason internet explorer is rejecting the AJAX request or is unable to reach your host (connection issues?)

Regards,

Varun Shoor

[eger]

I just starting getting this error all of a sudden today. It's happening when trying to reply to a ticket only.

Did it eventually go away or did you do something to fix it?

[Ryan Lederman]

eger, it's probably coincidental that it appeared and then vanished. I'd guess that maybe your connection had some latency issues for a while there.

If it continues, run a tracert to your server and see what the connection looks like.

[acenetryan]

I'm also having this problem. Another thread reported it can be fixed within main.js. We have had this problem on multiple machines.

OS: Windows XP
Browsers: IE 7 and FF 2

Symptoms:

While trying to post a reply, the Javascript error mentioned by the OP pops up while typing. I can still submit a reply, but I have to continuously close the error popup.

While trying to add notes, the screen shows "Loading" and does not show the form fields to add notes.

[eger]

Originally Posted by acenetryan

I'm also having this problem. Another thread reported it can be fixed within main.js. We have had this problem on multiple machines.

OS: Windows XP
Browsers: IE 7 and FF 2

Symptoms:

While trying to post a reply, the Javascript error mentioned by the OP pops up while typing. I can still submit a reply, but I have to continuously close the error popup.

While trying to add notes, the screen shows "Loading" and does not show the form fields to add notes.

Try restarting apache on the server and then reloading the LiveResponse client. For me this was likely something hung up on my server end. I was never able to reproduce it.

[supportskins]

Make sure you are accessing your helpdesk using the same domain name as used in the software's Admin CP > Settings > General > Product URL

If you access the software using any other URL, you will encounter this error.

[acenetryan]

The solution to my problem was essentially supportskins's suggestion, but I didn't realize it at first. Our Helpdesk is configured to be accessible only over https. I was visiting the Helpdesk using http. Along the lines of supportskin's suggestion, make sure you're not only visiting the correct domain, but also using the correct protocol (http vs https).

[Jamie Edwards]

Originally Posted by acenetryan

The solution to my problem was essentially supportskins's suggestion, but I didn't realize it at first. Our Helpdesk is configured to be accessible only over https. I was visiting the Helpdesk using http. Along the lines of supportskin's suggestion, make sure you're not only visiting the correct domain, but also using the correct protocol (http vs https).

If you'd like to ensure this happens automatically (and you are running Apache, as far as this tip is concerned), use a .htaccess file in your installation directory containing the following to rewrite the URL containing a http request to https:

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

It can also be done using IIS, I believe (but for that you'll need to Google ).

Thanks,