CMS Supervisor Error 429

Resolving CMS Supervisor Error 429 issue.

Error 429 typically occurs when code tries to instantiate an object. This error can be caused in many ways. The following list includes some of the most common scenarios that could cause this error:

  • License information for a particular component is not present.
  • A component is missing or is not registered.
  • A DCOM issue exists.
  • A Packaging and Deployment Wizard (PDW) issue exists.

1. Clear the log under CMS directory
2. User ID has insufficient right to access the directory
3. Goto Services->Telephone, set it to automatic

Another solution but not tested
1. create on your desktop a text file “test.txt”
2. Rename it to “test.avsup”
3. if Avaya supervisor is installed properly, you can double-click on this file and CMS with prompt you to enter your credentials.


From the CentreVu “readme” file:

If an “Error 48” or “Error 429” message is displayed the first time you
run Avaya CMS Supervisor, or if a component fails to start, it may be a
result of some elements not being properly entered into the Windows
registry. To fix this problem, complete the following steps:

1) Navigate to the CMS Supervisor installation directory.
(by default,the installation directory is C:\Program Files\Avaya\CMS Supervisor R16)

2) Run the RegistryDefaults.bat file.

CentreVu/Supervisor/CentreVu Supervisor/CMS Supervisor, all same thing.

Author: Darren Adams

The Avaya Engineer

32 thoughts on “CMS Supervisor Error 429”

  1. Nice post. I learn something more challenging on different blogs everyday. It will always be stimulating to read content from other writers and practice a little something from their store. I’d prefer to use some with the content on my blog whether you don’t mind. Natually I’ll give you a link on your web blog. Thanks for sharing.


  2. Manually register the Visual Basic 6.0 run-time DLL (msvbvm60.dll) by following these steps.

    1. Click the Windows Start button, and then click Run.

    2. In the Open box, type the following, and then click OK.

    regsvr32 c:\windows\system32\msvbvm60.dll

    You should receive the message “DLLRegisterServer in msvbvm60.dll succeeded.”


    1. Outstanding! Registering that DLL fixed my The operation could not be completed. Error -2147221163 – Colum Info Location: Main_DoAction issue! Only difference is that I had to execute the command from an elevated Command Prompt.
      Thanks once again!

      Liked by 1 person

  3. Delete corrupt CVS_Cache.tmp from %appdata%\Avaya\CMS Supervisor R16\Cache with CMS closed

    I’ve found error 429 occurs when the user shutsdown the system or reboots and CMS hasn’t had enough time to complete writing to the cache file. I work in an enterprise environment and this has been the fastest way I’ve found to resolve the issue.

    Liked by 1 person

  4. Allen, I think I have your answer…. for running Avaya CMS 16 in a Windows 7 x64 bit Domain environment. I had to tackle this today.

    i haven’t gotten to the root of this issue yet. As in why avaya cms insists on this behavior, but I have found a workable work around though.
    When you fire up Avaya CMS, the software looks to the registry for the location of the software, which is stored in

    PCCentreVu = %PROGRAMFILES(X86)%\Avaya\CMS Supervisor R16

    PCLocale = %PROGRAMFILES(X86)%\Avaya\CMS Supervisor R16\Locale

    PCUser = %AppData%\Avaya\CMS Supervisor R16

    PCLocale = %PROGRAMFILES(X86)%\Avaya\CMS Supervisor R16\Locale

    The problem is that as administrator, this data propagates correctly to the KHCU hive.
    When you log in as a Domain user, you get the wrong values. You instead get.
    PCCentreVu = %PROGRAMFILES%\Avaya\CMS Supervisor R16

    PCLocale = %PROGRAMFILES%\Avaya\CMS Supervisor R16\Locale

    So the software is pointing to the wrong place.

    I solved this by entering the values from the administrator config at top into GPO.
    User Config > Preferences > Windows Settings > Registry
    Set them as Action: “replace”

    Also in
    User Config > Preferences > Windows Settings > Folder
    %AppData%\Avaya\CMS Supervisor R16

    I suppose in a workgroup environment you could just use the
    ..\Program Files (x86)\Avaya\CMS Supervisor R16\RegistryDefaults.bat
    And apply it from the “all users “ startup menu
    %ProgramData%\Microsoft\Windows\Start Menu\Programs\Startup

    So whomever logged in would just get the scripted update…..
    Hope this helps…


  5. This application just sucks…. I run into this problem all the time. Just a poorly written application.


  6. On a Windows 7 x64, Copied IEShims.dll from C:\Program Files (x86)\Internet Explorer to the CMS Supervisor R16 directory and it resolved my “Error 429” issue.

    Stéphane Lodens
    Systemat Belgium


  7. Hi, I had the text for the menus and server set up not displaying correctly after installing R16.3 on Citrix XenApp 6.5 / 2008 R2. I then realised R15 was still installed. After uninstalling R15, R16.3 gave the 429 error. So it was something to do with R15 not being completely removed. I uninstalled both manually, deleted HKLM reg values and the CMS folders under Program Files (x86). Reinstalled R16.3 (all without reboot) and now it works fine. Hope that may help someone!


  8. Hello

    There are too many people using computer and they are facing problems and errors on daily basis. But I think every person will confused when he run an application but it’s not running but shows runtime error 429. I think this solution will helpful for those people.


  9. I’ve been trying to install CMS Supervisor in our office where we have managers on Windows 7 who need to use CMS who are normal domain users.

    When we launch CMS Supervisor 16 from these accounts we try to connect to the server and it does get any further than the ‘Initializing..’ stage and then it times out.

    When it’s launched under admin accounts it works fine.

    I thought I had found a workaround where I edited the registrydefaults.bat file to detail the machine name and the SID of the user so that when run under an admin account I could ‘remotely’ edit that users hive and perform the necessary registry changes.

    I think I got it to work but am now hitting the 429 error, worst thing is I got it working before on another machine! Does anyone have a solution for this once and for all?


  10. DCOM – Distributed Component Object Model (DCOM) a proprietary technology for communication among software components distributed across networked computers. Have you followed the information above


  11. May I know what “DCOM” means?
    “A DCOM issue exists.”

    I have seen this term lots of times but never understadn.


  12. This is a good fix – I ran the yDefaults.bat file and it resolved the issue first time. Prior to this I had been reinstalling CMS and still getting the same error.

    Keep up the good work!


  13. I have an old laptop with XP had CMS supervisor R15. Received new laptop with WIN 7 64bit. Downloaded CMS R16.3 Our Administrator installed the new CMS R16.3. All seems good except when clicking on the ICON. I logon then get the following error 429. CMS was uninstalled and re installed. Roaming and local profiles were removed.restarted still getting 429


    1. Yes it is Win7 professional 32bit english language. It turned out to be a problem with this users profile. Had to delet the local and roaming profile to solve the problem.


    2. The best fix is go to the app data folder and delete the CMS folder. It rebuilds the CMS profile. Below is the path in the directory

      C:\Users\{Person profile aka john doe}\AppData\Roaming\Avaya\CMS Supervisor R16


      1. This is the only fix that actually worked foer me. Note: the AppData folder is usually a Hidden folder. You need to go to Control Panel>Appearance and Personalization>Folder Options in order to view it.


  14. Hi,

    I have the problem on a new installation of Avaya CMS R16 and I have tried to follow the steps above, but I still get the same problem. Any more suggestions to solve this?
    I have tried to reistall the application. Still the same problem.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: