Guys/Gals,
System is IP500 with 200 stations (dig and IP), SIP trunks VMPRO, few expansion modules, etc.
Windows 2008 Server running VMPro.
Recently upgraded IP500v2 from R9.1.5 to 9.1.11. Attempted VMpro to 9.1.11 and ended up w/ vmpro at 9.1.9.
There are 2 errors that showed up. I do see a little on this on this forum but no resolution.
When installing Admin Suite I get and error referencing America.cab. This file is fine as it installed correctly on 2 different PCs (Win7 and Win8).
When installing VMPro on 2008 Server I get an error about Chinese.cab being corrupt. I ended installing VMPro 9.1.9 for now.
All Microsoft updates were installed and 2008 server rebooted.....still same errors about American.cab and Chinese.cab.did create new user on 2008 server and same result.
I believe this is possibly .Net related but not sure. I searched Avaya support site with no results.
Anyone have a workaround or solution for this? If not, I will open up a trouble ticket with Avaya as I am sure we are not the first for encounter these errors with R9.1.11.
System is IP500 with 200 stations (dig and IP), SIP trunks VMPRO, few expansion modules, etc.
Windows 2008 Server running VMPro.
Recently upgraded IP500v2 from R9.1.5 to 9.1.11. Attempted VMpro to 9.1.11 and ended up w/ vmpro at 9.1.9.
There are 2 errors that showed up. I do see a little on this on this forum but no resolution.
When installing Admin Suite I get and error referencing America.cab. This file is fine as it installed correctly on 2 different PCs (Win7 and Win8).
When installing VMPro on 2008 Server I get an error about Chinese.cab being corrupt. I ended installing VMPro 9.1.9 for now.
All Microsoft updates were installed and 2008 server rebooted.....still same errors about American.cab and Chinese.cab.did create new user on 2008 server and same result.
I believe this is possibly .Net related but not sure. I searched Avaya support site with no results.
Anyone have a workaround or solution for this? If not, I will open up a trouble ticket with Avaya as I am sure we are not the first for encounter these errors with R9.1.11.