-----Original Message-----
From: Propalms@googlegroups.com [mailto:Propalms@googlegroups.com] On Behalf
Of UnderTheHill
Sent: Wednesday, June 03, 2009 1:58 PM
To: Propalms
Subject: Re: Terminal Services Client Access License Error
No problem. We ran into this issue several years ago. Then it would no
longer work, and then we had to deal with the CALs. We are device based as
well.
Kris,
Thank You!
The registry fix did the trick.
It wasn't a TS problem since the server was set for per device instead
of per user and this week, we have a half the office traveling for a
major conference, so there definitely were TS CALS available that
wasn't being used.
On Jun 2, 10:55 am, "Kris Clarke" <kcla...@birdstairs.ca> wrote:
> We have had the same error, and there was 2 ways to fix the issue:
> 1) you need to do the following steps: LICENSE ERROR:
> Go to "RUN" and type"REGEDIT" then look for the following:-H+KEY LOCAL
> MACHINE
> Then:-SOFTWARE
> Then:-MICROSOFT
> Then:-MSLICENSING
> Then:-STORE
> then:-LICENSE 000 this you will need to <delete>
> 2) you might be out of TS CALS on your server. This gets very technical,
but
> basically you need to buy more users for your server.
> Kris
> -----Original Message-----
> From: Propalms@googlegroups.com [mailto:Propalms@googlegroups.com] On
Behalf
> Of UnderTheHill
> Sent: Tuesday, June 02, 2009 11:45 AM
> To: Propalms
> Subject: Terminal Services Client Access License Error
> Hello,
> Hope someone can give some insight and maybe help. We are using
> ProPalms TSE Version: 6.0.0, Build: 1252. One of my users has been
> having an issue.
> Starting yesterday, when she tries to launch an application in
> ProPalms, she receives the following message:
> An error occured while launching the application. The launch failed
> due to some licensing error. Please contact the Administrator and
> check your Terminal Services Client Access License.
> She was able to launch applications via ProPalms without any problems
> till yesterday. When we tried to have her access the server via RDP,
> the same error message appears, yet if we tried other computers using
> her credentials, there are no problems, able to access applications
> via ProPalms and RDP.
> I read on here about corruption of mstscax.dll and mstsc.exe files in
> the c:\windows\system32 directory, we have tried replacing them via
> Windows Recovery Console but that didn't do the trick. Have also
> uninstalled and reinstalled the ProPalms client on the computer, still
> no go. The computer is running XP SP2.
> Any advice would be greatly appreciated.
> Thanks.- Hide quoted text -
> - Show quoted text -
|
