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

bugaya.com foundation: some bugs found on IP Office installations.

Status
Not open for further replies.

ZebrAYA

IS-IT--Management
Mar 16, 2007
198
CO
bugaya.com foundation: some bugs found on IP Office installations.

The following bugs (errors) are commonly found in IP Office installations:

And they are somewhat desperating.

I am posting it here, to check certain tricks that may be applied to fix them (at least temporarily)

I am posting it here, also, to found a channel for some partners to make escalation to Avaya itself.

They vary by operating system, version of the application, and some other causes.

Code:
<hr>please paste it into excel, this is a table separated by commas

sorry to post this with commas, but can't upload my table.

Application, Release, event, PC platform, error, severity, Reported, Fixed
Call Status, 4.0, start application, Windows XP, SP2, Resource TMainForm not found, high, can’t start application., Not known until now, ?
Phone Manager, 3.2 - 4.0 – 4.0.15 – 4.0.20, Login after application startup, Windows XP, SP2, List index out of bounds (10), Mid, applications starts with limited functionality, On tech bulletin , ?
Phone Manager, 3.2 - 4.0 – 4.0.15 – 4.0.20, Login after application startup, Windows server 2003, List index out of bounds (5), Mid, applications starts with limited functionality, On tech bulletin , ?
Call Status, 4.0, start application, Windows server 2003, EAccessViolation, high, can’t start application, On ipoffice.info, Add the program to the “execution prevention menu”
, , , , , , ,
 
What's the point?
You can check the Avaya caveats list, if it is not in there then report your problem to Avaya, we cannot solve bugs here....

NIHIL NOVI SUB SOLE
 
Hmmmm

i'm not asking the community to solve avaya bugs.
Just to check tricks and tips to overcome this nuissances.

look over and you'll see that i'm posting a solution for running call status on win 2003 server systems, and the solutions works great!

My intention is that somebody could post "reinstall the .net framework to the 2.0.1.4 version" or "erase this line on your windows register" or things alike.

Thanks!
 
Ok, the releases supported on Vista are also supported on win2k3 server SR2. Previous versions were not supported on this version of Windows 203 server SR2.

NIHIL NOVI SUB SOLE
 
intrigantt
any idea to avoid phone manager error windows of "List index out of bounds (10)"?
I got it in winxp sp2, and with 4.0 and 4.0.20 updates as well.
 
stuff like that in phone manager are usually cleared by clearing the user profile. Delete the Avaya folder from the users My Doc's folder and reconfigure.

This will clear any Speed dials the user has so make a note of these first.

I have had alot of corupt profiles in the last few months. Not sure if Bill Gates' Auto Updates are doing it or not.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office


Fooball is not a matter of life and death-It is far more important!!!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top