202 and the new update

[Lavarock7]

I just updated my 202 today with the pending update (3.0.1) (Build: 3722). I went to configure SP3 in the ObiTalk interface and get a blank screen. Can anyone else verify this? I tried clearing cache on the PC and power cycled the unit.

[giqcass]

I can't confirm this yet as I have not done that update but you can install the old firmware manually or reinstall the current firmware manually.  I have had multiple failed installs due to corrupt files I downloaded directly from the Obi website. 

[giqcass]

I just did the update and the only thing I see that has changed is support for multiple BT adapters.

[CoalMinerRetired]

I did the update, no issues on SP3 or on any SPx screen. Note: I'm using the web interface directly to the device with this 202.

[giqcass]

I'm using the direct interface as well.

[Lavarock7]

Thanks, who knows. I'll just chalk it up to gremlins. As I daid, I just deleted the one service provider and re-entered it and it worked. Strange that one screen would just disappear though. I used ***6 to update.

[MikeHObi]

When I performed the update, I didn't see the same problem, but I did notice something.

After restarting my SP3 - anveo was showing failure to authenticate.  So I went into the sp, checked the settings and hit save.  after the save, it showed connected.

[giqcass]

I have had a little weirdness when I was messing around with dial plans.  I got some kind of error page as the OBi rebooted but it would go away after a few seconds and a page refresh.  I have done all updates manually.  I have also been backing up my settings but I have not had to use a backup yet.  I feel like the boot time is a little longer on this firmware but it might just be my impatience as I never actually timed it.

[CoalMinerRetired]

As of this morning I'm getting this error on the System > System status pages:

XML Parsing Error: not well-formed
Location: http://192.168.1.xxx/DI_S_.xml
Line Number 283, Column 58:

<value hash="417db31c" type="input" default=" " current="" >
---------------------------------------------------------^

For the record, this error was not present last week when I first applied the update. And it also means one cannot see or get into the main system status page.

[giqcass]

That is the error I was getting at reboot when I was adjusting dial plans.  As I said before it just went away on its own for me.

[CoalMinerRetired]

I've since deduced this only happens in certain browsers.  And I suspect it only occurs in browsers with Java disabled due a recent (last week) security warning.

[Felix]

Actually, this XML malformed usually happens when the page times out. XML is partially retrieved, without closing </xml> tag. Unlike html parser, where you can have missing closing tag, xml parser is strict - so you get malformed xml error.

Obviously, why page times out is a completely separate question.

[CoalMinerRetired]

That's odd, because I consistently get it in one browser, FF.  On the same machine in IE and Chrome I do not get it.