Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IPO VMPro not start .exe 1

Status
Not open for further replies.

PeterG911

Technical User
Mar 24, 2017
36
JO
Hi ..

my VM Pro log-on user is called 'pbx'. 'pbx' is a domain user of the active directory. the computer on which VM Pro is installed is a windows 2012 server with IIS installed prior to VM Pro installtion (I-A-N sequence, IIS then ASP.Net and then .Net framework installed in that sequence and lastly VM Pro application. VMPro service runs under the 'pbx' user account that is a domain user account. 'Pbx' is also a user under Local Administrator group on the VM Pro server.
loging into my voicemail pro and getting "this user does not have necessary rights permissions to access this application". Running 9.1.10 both Manager and VMPro and Windows 2012R2. Anyone have any idea whats up.
tried to right click and run the client as administrator. disable UAC window. Firwall (off). there is no antivirus installed.
As I say the service is running, because when calling from extention hears that this call recoreded ...
try another user domain, the same occurs.

Hope to find solution to this .


 
Hello, Peter-

By now you have probably solved your issue but, just in case, here goes.

We just finished the 9.1.10 upgrade, including VM Pro. Got the same error msg when trying to launch the VM Pro Client per my usual pre-upgrade account.

Somehow, the permissions on the folder VM Pro folder (C:\Program Files (x86)\Avaya\IP Office\Voicemail Pro) got damaged.
The permissions for the local machine's Users Group and Administrators Group were gone (no longer inheriting.)

Only the SYSTEM account and the account that was used to install the VM Pro upgrade from had explicit permissions (both "Full Control")

My fix was to add explicit permissions for local Administrators (Full Control) and local Users (Read & Execute, List and Read)- now all is well.
This may not be the ideal solution, but this issue is fixed and VM Pro is reliably operational again.

Hope this helps.




 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top