Permissions Required for CMS Supervisor R16.2 Functionality

[Johnny5000]

Hi Folks,

We're in the process of deploying Windows 7 x64 machines. During our pilot testing, CMS Supervisor failed to load for one of our users. Upon entering their login credentials, the 'Connect' window appears with the 'Initializing' status. After 30-45 seconds this error appears : "A connection to specified CMS server could not be established". However, when I log into the machine with the local admin account, the application connects to the server fine.

The 'Authenticated Users' group has Full Control permissions to the Avaya folders within Program Files and Program Files (x86). The app was uninstalled and re-installed, but still no success. When using the application on Win 7 32bit, users encounter no problems at all.

Has anyone encounter this problem with CMS Sup on Win 7 x64? If so, how did you resolve it without granting local admin rights to users?

Thank you for your help.

 

[DAVIDPAYNE]

What version of the CMS supervisor software are you using, and what version of CMS do you have?

 

[Johnny5000]

We're currently using 16.2 for both.

 

[DAVIDPAYNE]

Do they have full control of the AppData\Roaming\Avaya\CMS Supervisor R16?

 

[Johnny5000]

Yes, the users do have permission.

 

[Stinney]

User is positive they are using the correct credentials to login?

If they swear they are:

Have the user try to log in, then log onto the CMS Server (the server, not through CMS Superviser).

Execute the command tail -10 /var/log/authlog

Hopefully your authlog is running and you will get an entry that shows the user's login but using the wrong password. If you are using ssh (port 22) for users to access the system, then you may see an entry with the wrong user name, if you are using telenet (port 23) and the user uses the wrong login name, then no entry will appear in the log.

If your authlog is not capturing login information you can activate it by editing the syslog.conf file.
Remove the comment (# sign) from line: #auth.notice ifdef(`LOGHOST', /var/log/authlog, @loghost)
Restart syslog by executing: pkill -HUP syslogd




- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[BIS]

Could also be a reverse dns issue, so check /var/adm/messages as well...

 

[brunnen]

Try to execute the RegistryDefaults.bat file under the Program Files installation folder. If it doesn't work, try to delete the cache file at AppData\Roaming\Avaya\CMS Supervisor R16\Cache.

Bye