본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

What to do to solve this error ?XML Parsing Error: no element found Location: https://localhost:13443/weblct/openExplorerServlet?neid=1 Line Number 1, Column 1:

  • 2 답장
  • 2 이 문제를 만남
  • 1 보기
  • 최종 답변자: Tonnes

more options

Hi , i recived this error :XML Parsing Error: no element found Location: https://localhost:13443/weblct/openExplorerServlet?neid=1 Line Number 1, Column 1: anyone know how to solve this problem ?

Hi , i recived this error :XML Parsing Error: no element found Location: https://localhost:13443/weblct/openExplorerServlet?neid=1 Line Number 1, Column 1: anyone know how to solve this problem ?

모든 댓글 (2)

more options

The error should indicate some missing content in external software which is accessible through the link provided (and probably in any browser), so not internally from Firefox or one of any installed add-ons.

I’m not familiar with the product, but you could try uninstalling and reinstalling the latest software for the Web LCT component as found here. You could also uninstall what you no longer need.

more options

The above may not be right.

This is not entirely my area of expertise but when searching for the error message, several threads and possible causes can be found - one of them describing them is this thread.

Quotes: "I figured a little bit out - turns out the error is a FireFox error when it gets an empty document and is expecting XML." "i believe it's a firefox caching issue. but the underlying problem is that the page is not rendering anything." "this actually is a firefox issue. if you view source, you'll see that there's no output. If you were to view the site in another browser, you wouldn't see this error."

So my bet is some server software (Web LCT?) isn’t running properly or unreachable for some reason (port busy) and you get no data, resulting in the error. As posted in the thread, it’s a side effect.

If you search Bugzilla for "XML parsing error", you’ll find a number of open bugs that may be helpful.

Hope this helps.