Hi, I've recently encountered this error when adding a CMS server to a newly installed CMS supervisor R19 on VDI environment (Windows 10).
"Failed to initialize TAPI. The Windows Telephony service may not be running or cannot start"
Tried both on R19.1 and 19.2, same error.
Any advice on how...
Sorry for the very late reply, I forgot about this. It's named VDIA on SMGR licenses, same name when we moved the licenses to the stand alone webLM.
Then it says VDIA R1 or version 1 something like that on SMGR. Should be R2, it will show up with R2 in the name when downloaded on PLDS.
Ok, we saw what was causing the issue. Our AAfD product license was version 1 in SMGR, and the AAfD user's apps were already in version 2 (we upgraded the app version when we first saw the issue and thought it was resolved, until it showed grace period error again after 30days). v1 is also...
Thanks for your replies. Yes, correct format of license server, and able to get to the web page, https. It was working fine last year, then suddenly this year issue started, when nearing 30 days it will show that grace period warning.
Hi, I am new in using AAfD and have been encountering this issue of users receiving the error "License Server Unreachable. Grace period expired. No license available", when we have license available and WebLM server URL is correct on AAfD. Workaround is we reinstall but then when it is nearing...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.