News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

XML Parsing Error: no element found

Started by PortableTech, September 27, 2012, 09:13:03 AM

Previous topic - Next topic

PortableTech

Greetings All,

I have noticed over the last couple firmware revisions, and I am on the latest 2721 now, that when I go into the local web interface on the OBi110 that when using the "System Status" screen I sometimes get a yellow screen with one of the following several messages on it

XML Parsing Error: no element found
Location: http://10.130.0.4/default.xsl
Line Number 761, Column 10:         
---------^

or

XML Parsing Error: no element found
Location: http://10.130.0.4/default.xsl
Line Number 888, Column 2:
-^

or

XML Parsing Error: no element found
Location: http://10.130.0.4/default.xsl
Line Number 654, Column 4:   
---^

or even

XML Parsing Error: unclosed token
Location: http://10.130.0.4/default.xsl
Line Number 528, Column 17:                <xsl:value-of select="value//@de
----------------^

At the end of the day the error is never the same twice, and if I load the System Status screen a few times it will eventually give me the correct info, usually, but 80%-90% of the time I just get one of the above errors.  Now all other options and menus on the side work perfectly fine, and the OBi110 seems to work just fine as well.

I have also tried doing a full factory reset on the device and that did not change matters any either.

Any thoughts from those Guru's out there?

--PortableTech

crbc

Judging from all the posts in these forums, it appears this problem proliferates throughout the latest firmware releases.

I wanted to post and give this a bump in the hopes that Obihai will pay attention and get it resolved soon.  Discovered it myself (and hence the discovery of these threads) after upgrading to latest (2744).  My local Obi displays correctly, but those I access via VPN do this.  It's a real pain, because now I can't continue tweaking the configurations 'til their right.  Uuuuurgh!!

Please, Obihai, get this resolved.  Will try another browser (as some others have suggested), but don't think I should have to.