IP500V2 Upgrade fails with HTTP error “400 Bad request”

Seite auf Deutsch öffnen

In the Tek-Tips IP Office forum I recently read about an issue with the latest update of an IP500V2 to the latest 11.0 FP4 SP1. Upgrade fails and during file transfer you can see a HTTP error message “400 Bad Request”.

User splittingcodec found the reason for the issue and posted a workaround. He found out that some files in the Manager’s MemoryCards folder are empty. The solution was to just add some content to those files. For example just use the file name as content and save the files.

The files mentioned by splttingcodec were:

  • GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map within the Common\system\primary\WebMgmtEE\selfadmin_help\Cloud\<all language folders> directory
  • GUID-353430D7-191F-4115-BFB4-C329139187AA.map within the Common\system\primary\WebMgmtEE\selfadmin_help\Premise\<all language folders> directory
  • Version.json within the Common\system\primary\WebMgmtEE directory

Then start the update again and you should be fine.

Thanks again splittingcodec for posting this under https://www.tek-tips.com/viewthread.cfm?qid=1796408

Update: Avaya published a document describing the issue: https://support.avaya.com/ext/index?page=content&id=SOLN342353

Sadfully their workaround is to do the update by recreating the SD card. I like this way to update IPO but it’s not possible if you are remote…

Update: Avaya now updated the informations and offers the wrong files to download: https://support.avaya.com/ext/index?page=content&id=SOLN342353

If you need further help with IP Office you can contact me through my main website: https://www.fwilke.com/home

Do you want to get information about new posts? Subscribe to my Newsletter

1 thought on “IP500V2 Upgrade fails with HTTP error “400 Bad request”

  1. Pingback: IP500V2 Update schlägt fehl mit dem HTTP Fehler “400 Bad request” - Blog: Florian Wilke

Leave a Reply

Your email address will not be published.