| |
Propalms |
Kris,
Thank You!
The registry fix did the trick.
It wasn't a TS problem since the server was set for per device instead
On Jun 2, 10:55 am, "Kris Clarke" <kcla...@birdstairs.ca> wrote:
> 2) you might be out of TS CALS on your server. This gets very technical, but
> Kris
> -----Original Message-----
> Of UnderTheHill
> Hello,
> Hope someone can give some insight and maybe help. We are using
> Starting yesterday, when she tries to launch an application in
> An error occured while launching the application. The launch failed
> She was able to launch applications via ProPalms without any problems
> I read on here about corruption of mstscax.dll and mstsc.exe files in
> Any advice would be greatly appreciated.
> Thanks.- Hide quoted text -
> - Show quoted text -
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.
> 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>
> basically you need to buy more users for your server.
> From: Propalms@googlegroups.com [mailto:Propalms@googlegroups.com] On Behalf
> Sent: Tuesday, June 02, 2009 11:45 AM
> To: Propalms
> Subject: Terminal Services Client Access License Error
> ProPalms TSE Version: 6.0.0, Build: 1252. One of my users has been
> having an issue.
> ProPalms, she receives the following message:
> due to some licensing error. Please contact the Administrator and
> check your Terminal Services Client Access License.
> 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.
> 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.