We recently upgraded out Avaya IC environment to version 7.3.4, and now our desktop folks are pushing out upgrades to Microsoft Office 2016. I now have several desktops that Avaya IC won't connect and log in anymore. We get the "Database Login Failed" error almost immediately after clicking ok to proceed with the login, like its not even trying. Avaya IC engineer can't find anything in the log files, so we are all scratching our heads right now. We've tried reinstalling IC, ran the 'regrichclient.bat' file in the bin directory (which did fix a couple desktops that were getting the 'cannot add control' error messages). We've also has this MS Office upgrade kill a lot of our Avaya CMS Supervisor installations. We determined that this was due to a shared .dll file (msvbvm60.dll) that the upgrade for Office was messing with. By re-registering this file, it repairs the CMS Supervisor issue.
Has anyone seen anything similar to this with Avaya IC? Could I be looking at another shared file issue?
Has anyone seen anything similar to this with Avaya IC? Could I be looking at another shared file issue?