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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

upgrade to R11.1.2.1 on IP500V2 - I have no luck with it 2

Status
Not open for further replies.

Westi

Programmer
May 14, 2007
10,541
Ontario
Hello All
I have gone with the IP Office through a lot of crap since R1.1 but THIS !!!

I have so far avoided to use 11.1 on anything I was not forced by customer requests and that was only a few of server editions.

So now I have a R9.1 that needs to be upgraded and I found that Manager crashed on upgrade showing the usual crash error every time I attempt it. Upgraded admin to 11.1.2.2 and still the same

Then I tried that on my home system, also 9.1 and the same happens here.
It works past that point if I attempt to upgrade a R11.0 system but then it fails on the upgrade attempt as it claims only that it fails when checking the same way as if the system password is wrong but takes longer.

Recreated the SD card and no go
I tried uploading the system files and http error
tried a different SD card and the same problem
tried a different IP500V2 and still the same

F@#$ING Avaya has dropped the ball on R11.1 to force people to pay them more money on their crappy hosted solution that costs so much more and is so much less flexible.

I know I can upgrade the system if I just recreate the SD card as 11.1 but do I want a crapshoot like this that bites me in the behind out there?

Here my actual question.

Has ANYONE successfully upgraded an IP500V2 to R11.1.2.1 or 11.1.2.2 ?

Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque
 
Without reading the upgrade instuctions, but are you allowed to do a direct upgrade from 9.1 > 11?

Or do you need to upgrade to 10.0 first?

 
the upgrade instructions are mostly for server edition.
but even 9.1 - 11.0 then 11.1 fails

Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque
 
I've done quite a few upgrades from 9.1 to 11.1, 11.1.2, 11.1.2.2 and have had headaches left and right. Usually with manager being a POS and crashing when trying to upgrade, but eventually it got there.
So far I've found the only "good" way is to upgrade to 11 with 11 manager (like 11.0.4.7). Then completely uninstall manager and delete the directory and then install 11.1 or 11.1.2/2 and upgrade again.

However, all the issues have been with manager/wizard. We have started just using new SD cards and setting them up as 11.1/.2/.2.2 and throwing them in the system with the 9.1 config and the pldskeys file. Takes about 20ish mins to upgrade then.

-Austin
I used to be an ACE. Now I'm just an Arse.
qrcode.png
 
Thanks AACon

I am so glad to hear that Avaya is to blame with their lack of testing and diligence and not that I am completely useless and incompetent.

uninstalling and re-installing was in the early 1.x and 2.x the normal way and really painful because you had to use CD's that you had to carry. Seems they unpacked old business models.
I guess the move to a new SD card will be the way to go which means no more remote upgrades after hours without the customer being on site switching the SD card for me.

I will try the uninstall / reinstall locally here on my test systems.

Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque
 
It is clear as can be that Avaya has decided they will "force" people to hosted by making onprem unusable... whoever thought this up needs to be fired immediately. If you get frustrated to the point you want to move on from Avaya's onprem what in the world makes them think you would turn around and buy Avaya's hosted solution? You would find a different onprem offering or a different hosted offering. The only thing Avaya has (or had) going for it was it's name power and they are dragging it through the mud (and it seems to be on purpose?!)

I bought one LG phone and it was an absolute turd. I didn't decide "oh Ill buy a more expensive LG phone" I decided I will NEVER buy LG again.

The truth is just an excuse for lack of imagination.
 
words have never been more along my thought process critchey
if you have a bad product then that is it.
For me that is HP laptops, bought one and it was an absolute lemon. Lenovo all the way now.


We have even started promoting our own hosted solution over the ACO too as we don't want to lose the customer base that it took 30 years to build up just so that Avaya RingCentral comes and takes them laughing all the way to the bank.



Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque
 
AACon
that worked on my spare desktop but my laptop is still FUBAR'd

Hey half way there, now I have tried this on the customer machine and the same as my laptop, no go.

I uninstall Admin suite and see still the Manager and SSA icons on the desktop and when I click on them they still work but Admin suite is no longer in the list of programs installed.
Avaya paid a big stinky egg with this one. I might just be a prick and open a case with Avaya on this one. Let them feel the pain but that only gets the wrong people at Avaya.

So I guess I have to ask the customer now to spin me up a brand new Win10 incidence and try from that one.

Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque
 
I just had a similar issue but with voicemail pro. I had R11.1 vmpro client installed but when I tried to connect to a R9.1 system it looked like it would connect but I couldn't access the settings. Fine, just uninstall R11.1 and install R9.1 vmpro client right? Can't be that easy.... the R11.1 errored out during uninstall and then wouldn't run. When you tried to run R9.1 it would be like it was still installed and if you tried to do anything it would then say "this product isn't installed". I had to go muck around in the registry and delete everything vmpro related to get it to work.

R11.1 is just an unmitigated disaster.... again leading to either on purpose and just blatant incompetence.

The truth is just an excuse for lack of imagination.
 
I have the same problem too !
Trying to upgrade a R9.0 system, the embedded file management does not show any contents in the SD and the online upgrade wizard give back a Manager application error with the following details (WTF !!):

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at UpgdWiz.WISystems.get_Version11p1p2AndHigher()
at UpgdWiz.WISystems.get_IsSecureHTTPOnly()
at UpgdWiz.UpgradeWiz.btnUpgrade_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4420.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Manager
Assembly Version: 13.1.0.0
Win32 Version: 11.1.2.2.0 build 20
CodeBase: file:///C:/MyPrograms/Avaya/IP%20Office/Manager/Manager.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
UpgdWiz
Assembly Version: 12.0.0.0
Win32 Version: 11.1.2.2.0 build 20
CodeBase: file:///C:/MyPrograms/Avaya/IP%20Office/Manager/UpgdWiz.DLL
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4455.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
SecurityManager
Assembly Version: 12.0.0.0
Win32 Version: 11.1.2.2.0 build 20
CodeBase: file:///C:/MyPrograms/Avaya/IP%20Office/Manager/SecurityManager.DLL
----------------------------------------
CoreServices
Assembly Version: 12.0.0.0
Win32 Version: 11.1.2.2.0 build 20
CodeBase: file:///C:/MyPrograms/Avaya/IP%20Office/Manager/CoreServices.DLL
----------------------------------------
Manager.resources
Assembly Version: 13.1.0.0
Win32 Version: 11.1.2.2.0 build 4
CodeBase: file:///C:/MyPrograms/Avaya/IP%20Office/Manager/it-IT/Manager.resources.DLL
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Manager.resources
Assembly Version: 13.1.0.0
Win32 Version: 11.1.2.2.0 build 4
CodeBase: file:///C:/MyPrograms/Avaya/IP%20Office/Manager/en-US/Manager.resources.DLL
----------------------------------------
WhoIs2
Assembly Version: 12.0.0.0
Win32 Version: 11.1.2.2.0 build 20
CodeBase: file:///C:/MyPrograms/Avaya/IP%20Office/Manager/WhoIs2.DLL
----------------------------------------
AvailabiltyValidationVisability
Assembly Version: 12.0.0.0
Win32 Version: 11.1.2.2.0 build 20
CodeBase: file:///C:/MyPrograms/Avaya/IP%20Office/Manager/AvailabiltyValidationVisability.DLL
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4455.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
UpgdWiz.resources
Assembly Version: 12.0.0.0
Win32 Version: 11.1.2.2.0 build 4
CodeBase: file:///C:/MyPrograms/Avaya/IP%20Office/Manager/en-US/UpgdWiz.resources.DLL
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------

************** JIT Debugging **************
Application does not support Windows Forms just-in-time (JIT)
debugging. Contact the application author for more
information.


 
I have had only a few issue going from 9.1 to 11.1. I have only done V2 control units. Main issues is system shows it's upgraded but it is not because it did not transfer all the files over. After an upgrade I always reboot. Than I get into "embedded file management" & upload the system files. It normally uploads only 2 files but incase where it shows the system is upgraded it transfers several 100 files. Make sure to reboot & run again. If you have not uploaded system files this way do not freak out when manager sits there for 5 minutes before another screen pops up & starts transferring files.

Avaya also change the default directory for the manager files. It was in the IP Office folder & they changed it to IP Office Admin Suite. The problem is when you tried to upgrade the directories still pointed to the old folder so it would fail. The fix was to uninstall manager & reinstall manager. The only problem is since the IP Office folder was still there manager would still point to the wrong directories. You either had to change the directories in manager or run a program that uninstalls & deletes all the program files & the registry keys. I believe Avaya has since fixed manager so it points to the correct directory folder.

If your not going to it right don't bother doing it at all!
 
The source folder problem is well known, that's why I check it all every time I upgrade/re-install a new version's manager. With this Manager Release I am allowed to upgrade from 11.0 to 11.1 with no trouble, viceversa if I try upgrading a R9.x version to R11.1 the upgrade process crashes and the SD card seems missing. If I use a previus version of manager (still R11.x) in the same environment no problem at all.
 
Everything about this release is a mess. From upgrades to fresh installs and everything in between. This is the release that will end the on prem IPO line and I'm pretty sure that's as designed.

It's a shame cause it was really starting to reach it potential before this. Time to start looking in new directions in my opinion.
 
Had manager 11.1 on my laptop, would not upgrade a 9 to 11.1. Ended up defaulting the laptop to factory. Reloading manager 11.0. No problems. the laptop I use is only for onsite programming so it was no big deal to reload windows. Something about 11.1 that loads permanent register values that don't go away when you just uninstall the software. I will NOT be running 11.1 on my systems!
 
We just had a system that would not allow J-series phones to register
defaulted the system - uploaded the same config - working

Avaya Management is apparently dumb enough to believe that we will put all their customers on ACO
WRONG
we put them on our on hosted platform or we sell them some old fashioned on-prem system other than Avaya if they only need a system with phones and voicemail

There are options - they may not be a slick in the programming as the IPO and we may not be used to it as much but there are options and Avaya Management will wake up one day - take their multi million dollar severance packages and leave Avaya to die in the phone system desert because they missed the signs of all the thousands of small and medium customers.

One of my previous companies I worked for thought they can do the same thing and concentrate on large size companies, then they lost 3 big ones and hundreds of neglected small and medium ones.
DONE and basically bankrupt now holding on to a few larger accounts that they are contractually bound to service. No more sales people and no techs there any more.

Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque
 
If installing 11.1 Manager on a PC with an older existing Manager you need to run a program that uninstalls all the registry settings. I use Revo Uninstaller Freeware version. Never use add/remove programs or you will have issues. Before running Revo Uninstaller make sure you save any config files or any other item you want in your Avaya & IP Office folders. The software is easy to run. When removing software most of the time it will pop up the windows modify - repair - remove screen. Remove as normal. After the software is removed Revo will give you an option box to scan for registry keys. Always select "Advanced". After it find the registry keys press "select all" then "delete". If it finds any additional registry keys it is the same process. When removing Avaya software it will most likely leave the Avaya folder. I manually delete that folder. I also empty the recycle bin. Then shut down not reboot.

Now you can install fresh. Just remember if you have vm pro client or any other software it will affect those when uninstalling manager.

If your not going to it right don't bother doing it at all!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top