Cannot fix web pages / firmwware mismatch popup error message

[rygh]

I get this error in the network config on Apex classic:
"The Dashboard version does not match the firmware version. Update the web pages using the Apex Flash Utility."

I upgraded to the new firmware version 4.40_3A16
That worked fine, and I see that in the network page.

I then clicked update web pages, and it seemed to do its thing properly. Green bar -> ready, no errors.
But it did not really seem to update.
In the network page, Dashboard version is 4.34_4F15

I tried the usual rebooting, disabling anti-virus, clearing web cache, etc.
Port is 80, no communication issues between flash utility and apex.

Everything is working fine. I just get that error message going to netsetup.sht page.

[RussM]

Try the web update again. In the log window, you should see messages about each file being uploaded. Do you see that?

[rygh]

Try the web update again. In the log window, you should see messages about each file being uploaded. Do you see that?

Ahh, I had to expand the app to see the error log.

ERROR:
>Uploading file: aihost.bin...
>
>Operation failed with the following error information:
>
>The underlying connection was closed: The connection was closed unexpectedly.

[rygh]

Ok, fixed it.
Thanks RussM
Once I had the error message, I could search forums more.

I tried the turn apex off ... attempt update so it times out .... turn apex on ... update again.
And it worked.
Why?? Who knows...

[RussM]

After you update the firmware, the Apex restarts, which takes about 45 seconds. My guess is that you started the web page update too soon. It's best to wait a minute or two.

[rygh]

After you update the firmware, the Apex restarts, which takes about 45 seconds. My guess is that you started the web page update too soon. It's best to wait a minute or two.

No, definitely not that. I logged in between reboots / tries a few times to look at the version number.

That thread I found described exactly what to do. Something to do with the flash utility needing to time out then retry.
I am an engineer, and it makes little sense why, but it worked.