LicenseService Event 202

[Tony King]

Event Type: Error
Event Source: LicenseService
Event Category: None
Event ID: 202
Date: 06/11/2003
Time: 09:43:14
User: N/A
Computer: FISKFS1
Description:
The product Windows Server is out of licenses. Use
License Manager from the Administrative Tools folder for
more information on which users are out of compliance and
how many licenses should be purchased.

I'm getting the above message periodically, about 3-4
times a day. We have a Windows 2000 Small Business Server
and a Windows 2000 Server (Member Server) configured as a
Terminal Server.
We have more than enough CALs, 40 for the SBS machine and
22 Terminal Server CALs for the member server. At most
we're using 35 of the SBS CALs and 16 of the Terminal
Server CALs.

I've read KB article 245823, but that doesn't apply as the
error only occurs on the SBS system.
What is more the Terminal Server holds no data, only user
profiles for the Terminal Server users and printers are
only used by terminal server users too.

When the Terminal Server was installed, initially the SBS
system had not been made Licensing Server and I wonder if
this maybe part of the problem, even though it has been
corrected.

Can someone give me an indication as to why I might be
getting this error?

 

[Ray Lava [MSFT]]

Tony,

I have come across this problem with one other person and this is how it was resolved:

Change the Windows 2000 member server from per seat to per server licensing mode

Once the Win2k member server is in per server mode:

1. Remove any installed licenses using license manager on the Win2k member server.

2. Add the appropriate number of per server licenses

3. Revoke all client (per seat) licenses that have been previously issued

4. Follow Q153140 to reset license manager database on both Win2k server & SBS server



I hope this helps

Ray Lava
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights

 

[Lanwench [MVP - Exchange]]

Stop and disable the license logging service. It's buggy (as is Outlook's
use of it) and not mandatory. Just keep track of your licenses manually.

 

[Tony King]

Ray,

Thanks for your reply. I think that in our case, most but
not all of the right steps had been taken. I've now
revoked all of the previously issued per seat licenses,
which showed as unlicensed in the License Manager on the
member server and the error seems to have stopped occuring.

The terminal server (member srvr) had existed along side a
NT4 SBS system which was upgraded to Win2K SBS. After the
90 day grace period allowed for Terminal server clients
expired, those client were locked out. At that point the
Win2K SBS system was made the licensing server and the
licenses were re-added, but the previously issued licenses
remained.

The problem has essentially been that although the license
error occurs on the SBS system, it has been the member
server, per seat, license that needed to be removed and
that wasn't clear from the event log entry.

Tony