Re: Error in Licensing Protocol
Just to be absolutely sure:
you have 18 purchased Windows 2003 Per Device TS CALs available?
But the TS recorded an EventID 21, meaning it thought you hade none
available?
I can only think of 2 scenarios in which this could happen:
1) your Terminal Server has been switched to use the Per User
licensing mode. You can check this in Terminal Services
Configuration - Server settings.
2) your TS is configured to use another Licensing Server, which
doesn't have licenses available. You can check that as well in
tscc.msc
You might want to run the lsview and lsreport tool from the
Resource Kit from the TS, to see which Licensing Servers it sees
and which licenses.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
Steve Paris <paris@DELETECAPSplgs.com> wrote on 07 jan 2008 in
microsoft.public.windows.terminal_services:
> In article <Xns9A1C890FBCBE8veranoesthemutforsse@207.46.248.16>,
> vera.noest@remove-this.hem.utfors.se says...
>
>
> Thank you for your response. I did find an event on 12/21/2007
> as follows:
>
> Source: TermServLicensing Event ID: 21
>
> The Terminal Server Licensing Server XXXSERVER has no permanent
> licenses for product "Windows Server 2003 - Terminal Server Per
> Device CAL Token." Use Terminal Server License administrative
> tool to register more licenses.
>
> When viewing the Terminal Server Licensing, it shows that there
> are 18 available.
>
> I have not modified the licensing properties.
>
> Any advice would be greatly appreciated.
>
> Steve Paris
> Pathfinder Logistics Group
>
>
>> Can you post the EventID and source from the EventLog on the
>> Terminal Server?
>>
>> You should also follow the troubleshooting guide here:
>>
>> The remote computer disconnected the session because of an
>> error in the licensing protocol
>> http://technet2.microsoft.com/windowsserver/en/library/22cba6d1-
>> f7a2-432e-9d91-8e27a75434601033.mspx?mfr=true
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> Steve Paris <paris@DELETECAPSplgs.com> wrote on 05 jan 2008 in
>> microsoft.public.windows.terminal_services:
>>
> Vera,
>
> Thank you for your response. I did find an event on 12/21/2007
> as follows:
>
> Source: TermServLicensing Event ID: 21
>
> The Terminal Server Licensing Server XXXSERVER has no permanent
> licenses for product "Windows Server 2003 - Terminal Server Per
> Device CAL Token." Use Terminal Server License administrative
> tool to register more licenses.
>
> When viwing the Terminal Server Licensing, it shows that there
> are 18 available.
>
> Any advice?
>
>
>
>
>> > I have a remote client computer that has been connecting to
>> > our Windows 2003 Terminal server without a problem for a
>> > couple of years.
>> >
>> > Starting the first of this year, it will no longer connect
>> > because of a licensing protocol error. I have plenty of TS
>> > Device CALS available.
>> >
>> > This computer has been issued a license but the dates look
>> > suspect. It was issued on March 23, 2007 and it is set to
>> > expire on March 18, 2008. All of my other issued licenses
>> > are set to expire in 90 days from the issue data.
>> >
>> > No other remote client computers are having a problem
>> > connecting to the terminal server.
>> >
>> > Any advice on how to get this client computer connected
>> > again.
>> >
>> > Thank you.