Upgrade wizard problems

[flexphil]

I'm using Manager 5.2.53. I've got a lot of problems with the upgrade wizard. The IpOffice's are blocked and I've had to use the serialcable for a couple off times.

The same with the digital phone's. I've updated (fw_on.bat)them, closed the updating program (fw_off.bat), disconnected my pc and when I unplug the phone's and plug them in again, they are still trying too update.

Can anyone help me?????

Thx

 

[colpot]

I too had a lot of problems with 3.2.53 which led to us sticking to 3.1.65 on new installs. However we now use 3.2.54 and have not had any problems so far

Colpot
(Remember - If it aint broke - fix it till it is.)

 

[kwing112000]

I have had alot of issues with the 3.2 releases as well and what i have found is that you need to make sure the working directory file paths are set right for what you are doing. I am not sure this helps you but worth a mention.

 

[jakason]

Sometimes it´s needed to turn windows firewall off, it helped me a couple of times.

 

[intrigrant]

Most likely the batch file fw_off did not do what it supposed to do.
The problems you have must be related to a firewall or virus protector on your PC

 

[jconrad0305]

I think it is an ipo issue. i have had a lot of porblems even on the 3.2.54 with it being blocked and having to use the dte port. also when i install a vcm card i alwas have to resend the bin via dte or the system will stay in the reboot cycle. it really sucks because it takes the normal time to install a card to even longer and i will no longer do remote upgrades because if the unit gets into the reboot cycle that i have to go out anyways.

 

[tlpeter]

it is not an ip office issue
i only had problem one time and that was the first time i used 3.2
upgrading to 3.2 takes a little more time
like intrigrant said firewall or virus scanner can do a lot of harm

 

[jconrad0305]

i beg to differ. how can an ipo work fine on 3.2.54 with no vcm installed. i install the vcm and the system stays in reboot state. i then have to resend the bin file via the dte port to get it come back to life. logic will tell you that it is the ipo

 

[tlpeter]

this has nothing to do with the software version
this will happens with older versions too

 

[jconrad0305]

so it sounds like an issue with the ipo.

 

[intrigrant]

In 3.2.53 there is a issue with the LAN wich gets blocked on a 406V2, upgrading to 3.2.54 will help. It is obvious that the network of the IPO must work otherwise a upgrade is a bit difficult.
My experience is that the IPO-LAN after some time suddenly starts working again and then do the upgrade right away.