Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Release 11.0.4.1 - 400 Bad Request 9

Status
Not open for further replies.

splittingcodec

Technical User
Feb 21, 2018
51
US
Hello,

I'm currently experiencing an issue with upgrading IP500V2 Control Units to 11.0.4.1, where the HTTP Session terminates with a 400 Bad Request in the process of uploading the Web Management Files.

I have all TFTP and HTTP Settings set to the Manager PC on the same subnet as the IPO, and have tried each option for file upload wihout success. What I am finding is that the files that cause the error are 0KB in size. Here is a trace of the error:

2019-08-12T16:21:19 316252082mS HTTP: 192.168.10.232(63201) ~HTTPEmbeddedFileServerSessionIO
2019-08-12T16:21:19 316252083mS HTTP: Rx Src: 192.168.10.232(63201)-(80)
PUT /memorycard/system/primary/WebMgmtEE/selfadmin_help/Cloud/de/GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map__a_t_t_r_.txta HTTP/1.1
Last-Modified: Wed, 06 Feb 2019 06:33:04 GMT
Content-Type: application/octet-stream
User-Agent: IPOManager/11.0
Host: 192.168.10.230
Content-Length: 0
2019-08-12T16:21:19 316252084mS HTTP: Content type doesn't match the file type: content type=application/octet-stream filename=GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map__a_t_t_r_.txta
2019-08-12T16:21:19 316252084mS HTTP: 192.168.10.232(63201)-(80) HTTPServerSessionIO: stCreationCallback(7)
2019-08-12T16:21:19 316252084mS HTTP: Public IP=192.168.10.232 Private IP=Not set
2019-08-12T16:21:19 316252085mS HTTP: 192.168.10.232(63201)-(80) HTTPSession: SendErrorResponse Code: 400, Entity: Content Length Header is required to be non-zero for PUT
2019-08-12T16:21:19 316252085mS HTTP: 192.168.10.232(63201)-(80) HTTPServerSessionIO: SetState GracefulClose
2019-08-12T16:21:19 316252089mS HTTP: Tx Dest: 192.168.10.232(63201)-(80)
HTTP/1.1 400 Bad Request
Connection: close
Date: Mon, 12 Aug 2019 23:21:18 GMT
Expires: Mon, 12 Aug 2019 23:22:18 GMT
Cache-Control: private,max-age=60
Server: IPOffice/
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: text/plain
Content-Length: 56


I've upgraded SE nodes without issue. Seems like an Avaya bug to me, anybody else run into the same kind of issues?

Thanks in advance for any replies.
 
I got the same error. The only thing that worked for me was to format and recreate the SD Card.
 
It looks like I was able to resolve this one:

- I found that there were several files that were 0KB in size giving the syntax error, all in the WebMgmtEE directory of system/primary on the new Manager Installation:
1)Version.json which is located in the WebMgmtEE directory of the Manager installation
2)GUID-D34E8070-85A7-4267-8637-7277A9001AE4.MAP which is a self help file that is located in WebMgmtEE\selfadmin_help\Cloud\(all languages)directory
2)GUID-353430D7-191F-4115-BFB4-C329139187AA.MAP which is another file in the WebMgmtEE\selfadmin_help\Premise\(all languages) directory

I reviewed it with a few engineers and found that these were non essential files. I didn't exactly want to just delete them, so i made new files simply containing the name of the file in text (i.e Version.json was made as a text file stating "Version 11.0.4.1") and saved that as a .json file, then replaced each file in the Manager directory. After that, file management upload worked fine for both systems in the recently upgraded SCN.

Let me know if anybody else finds any alternate solutions.

 
I have just done 2 of these and both failed to load all the files correctly. This is a known issue with Avaya.
Per Avaya
You can either upgrade by following the Upgrade process of recreating the SD card, or you can delete the file C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\Version.json then go back into file embedded file management and upgrade system files again.
Title : IP Office: Upgrade to Release 11.0 FP4 SP1 System File Upload Fails at Version JSON File
Article ID : SOLN342353
Article Link : Just thought you should know before doing any upgrades.
Mike
 
Avaya says it is related to the Version.json file. But they only offer SD card recreation as a workaround. Bad if you can't go on site...

I am pretty sure [ponder] that Avaya from now on checks for 0 byte files in their tests.

Need some help with IP Office? IP Office SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
 
It appears to be these files in particular
The file - C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\Version.json being empty is the cause of the issue.
delete the 0 kb file create a new one named Version.json
I stuck this in the file "Version 11.0.4.1" Put it in the path above
then
C:\Program Files\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Cloud\de
edit the GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map file put the word nothing in it
make sure you save the files back to the same extension (no .txt)
Still uploading will let you know if it bombs any more but I think this is it.
Nope -
C:\Program Files\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Cloud\es
file: GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map
Put something in that one too
Next it bombed on Fr (French)
so I went through each language found the 0KB file and edited it.
is the last of them
Each language has a 0kb map file
put anything in it so it will copy [can't copy a 0kb fileust a name]
GUESS WHAT
C:\Program Files\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Premise
each language folder here too
just look for the 0kb file and edit
splitting codec above had the right idea i just didn't totally understand his post
When he said all languages he means all those sub directories (de to zh)

 
OK I've been wrestling with this issue as well and I wanted to post a list of every single bad file with this new release. All you have to do with these files is open them in notepad and put literally any text in there, then save. I put "Version 11.0.4.1"

List follows:
Code:
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\Version.json
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Cloud\de\GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Cloud\en\GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Cloud\es\GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Cloud\fr\GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Cloud\it\GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Cloud\pt\GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Cloud\ru\GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Cloud\zh\GUID-D34E8070-85A7-4267-8637-7277A9001AE4.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Premise\de\GUID-353430D7-191F-4115-BFB4-C329139187AA.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Premise\en\GUID-353430D7-191F-4115-BFB4-C329139187AA.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Premise\es\GUID-353430D7-191F-4115-BFB4-C329139187AA.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Premise\fr\GUID-353430D7-191F-4115-BFB4-C329139187AA.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Premise\it\GUID-353430D7-191F-4115-BFB4-C329139187AA.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Premise\pt\GUID-353430D7-191F-4115-BFB4-C329139187AA.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Premise\ru\GUID-353430D7-191F-4115-BFB4-C329139187AA.map
C:\Program Files (x86)\Avaya\IP Office\Manager\MemoryCards\Common\system\primary\WebMgmtEE\selfadmin_help\Premise\zh\GUID-353430D7-191F-4115-BFB4-C329139187AA.map

So long as each of these files is greater than 0KB, the upgrade will proceed normally.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top