Αναζήτηση στην υποστήριξη

Προσοχή στις απάτες! Δεν θα σας ζητήσουμε ποτέ να καλέσετε ή να στείλετε μήνυμα σε κάποιον αριθμό τηλεφώνου ή να μοιραστείτε προσωπικά δεδομένα. Αναφέρετε τυχόν ύποπτη δραστηριότητα μέσω της επιλογής «Αναφορά κατάχρησης».

Learn More

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 έχουν αυτό το πρόβλημα
  • 2 προβολές
  • Τελευταία απάντηση από 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.