CMS Supervisor User connection initialzing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • scott232
    Member
    • May 2014
    • 3

    CMS Supervisor User connection initialzing

    Hi
    Any help greatly appreciated.
    We are moving to a Windows 7 platform from XP.
    Clients are 64 bit.
    Server is running v14.
    16.3 client connecting back to our DB running v14.
    Software installs, can set a connection to the server and make a connection and login.
    Log a domain user onto client, run the software and message "connection initializing" then a connection could not be established.
    Navigate to the c:\programs files (x86)\ folder and run exe as another user with admin and can login fine.
    Suggests permissions to me so check following and allow users Full Control over
    c:\program files\Avaya
    c:\program files (x86)\Avaya
    %appdata%\user\Avaya
    All without success.
    Make a user a temp admin, still doesn't allow a connection.
    Any help greatly appreciated.
  • shaikht
    Genius
    .
    • Feb 2010
    • 246

    #2
    Hi,

    It looks that domain policy of PC is not allowing connection.

    You need to have access for following on windows 7 for supervisor:

    C:\Program Files (x86)\Avaya\CMS Supervisor R17
    C:\Users\domain_user\AppData\Roaming\Avaya\CMS Supervisor R17

    I hope it helps.

    Comment

    • scott232
      Member
      • May 2014
      • 3

      #3
      I believe those permissions have been set accordingly. I have allowed "users" full control on those relevant paths.

      I am using CMS 16.3, should this be an issue?

      Comment

      • shaikht
        Genius
        .
        • Feb 2010
        • 246

        #4
        Ok..

        No those are independednt to CMS versions. Those locations are for windows 7.

        Comment

        • scott232
          Member
          • May 2014
          • 3

          #5
          Does he user have to be an admin to run?

          Comment

          • shaikht
            Genius
            .
            • Feb 2010
            • 246

            #6
            There is no such specific requirement to run supervisor.

            But if admin users are able to loggin, I guess you need to have admin users to have full permsissions.

            Comment

            • ilalpatidar
              Whiz
              .
              • Jan 2014
              • 37

              #7
              This is something known issue in CMS supervisor, you need to provide full access to folders mentioned and additionally you need to have telephony service running under services.msc window.

              Comment

              Loading