Avaya CMS User issues. 1

[NThomas77]

Hi,

We have an issue where using exactly the same CMS supervisor application on the same desktop, different logins will work and some won't. The issue only started last week after years of no issue. The login in question suddenly stopped working whilst another login (which has been compared and is identical in settings does work) The issue is that the supervisor sticks on processing when trying to run any report. You can't access dictionary either or any other menu. You need to kill off supervisor in the Task Manager.
We have been able to replicate this users issue on other machines and can login with one login and run reports whilst then trying with another and it fails.
I am wondering if there is any such issue as Login User info full on CMS server. Would there be an issue against not allowing a few users to run reports. It is happening across a few users and we can replicate with all of them. We are running CMS V17 and updated software to version 18 and still the issue persists.
So we have ruled out desktops, ruled out software version, and ruled out the server as same issue happens on the secondary and we restarted the primary and issue still present.
Anyone experienced anything similar? Any tips to share please?
Thanks

 

[phoneguy55]

Seen something similar. Uninstall cms on the desktop. Then regedit and remove anything CMS related. Reboot and re install CMS.

 

[NThomas77]

Thanks very much for the reply. We have gotten to the bottom of this one now after a lot of testing. It seems that the business users had added a carte blanche access in user permissions to their vdn permissions and the range was by far exceeding that of the Measured VDN limit in Measured Items. Instead of adding specific vans for e.g. they added 10,000-11,000 and 11,000-12,000 etc.This was set at 6500 on the primary but their permissions were exceeding 10,000 VDNS across unmeasured VDNs also. So this was causing CMS to freeze. When we removed the mass access it resolved the issue and the logins then started to run reports again. This issue was one we were never aware of before and is a lesson learnt all around. Its def one worth noting though should anyone else experience the same issue in their CMS.