为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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.