Error 1004: cannot issue a client license. Running metaframe XP 1.0 SP3 on 2000 server

J

Jason

I've got a client running 2000 server in an NT domain with Citrix
Metaframe XP 1.0 SP3. They have several users that, when they try to
connect, the ICA client just disappears. When I check the event logs
while they are trying to connect I'm seeing the error: 1004 - Terminal
server cannot issue a client license.

The client has 20 licenses for Citrix. Do they also need TS cals to be
able to connect? This only happens with a few users, which is weird. I
can take a new system, install the ICA client and connect from there
no problem. It's just a few random systems having the issues.

Term services is setup in application mode and the licensing server is
installed on the term/citrix server.

I have also deleted the licenseXXX registry keys with no success. Can
anyone shed some light on this one for me? Thanks.

Jason
 
G

Guest

If the clients are NOT 2000 or XP Pro then they also need Terminal Server CALs. If you try to logon with the Remote Desktop Client from the same machine having a problem, and Event ID 1004 is not logged, then the problem is with Citrix MetaFrame, not Terminal Server

Check the Terminal Services Licensing Service to make sure you have TSCALs and that one is assigned to this workstation

This issue is in the Citrix Knowledgebase

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Jason wrote: ----

I've got a client running 2000 server in an NT domain with Citri
Metaframe XP 1.0 SP3. They have several users that, when they try t
connect, the ICA client just disappears. When I check the event log
while they are trying to connect I'm seeing the error: 1004 - Termina
server cannot issue a client license

The client has 20 licenses for Citrix. Do they also need TS cals to b
able to connect? This only happens with a few users, which is weird.
can take a new system, install the ICA client and connect from ther
no problem. It's just a few random systems having the issues

Term services is setup in application mode and the licensing server i
installed on the term/citrix server

I have also deleted the licenseXXX registry keys with no success. Ca
anyone shed some light on this one for me? Thanks

Jaso
 
S

Seahawk60B

The clients will need a TS cal to connect, in addition to the
Metaframe CAL.
W2K Pro clients have a built-in TS cal, but will still need to access
the license server. Older Windows clients will need a TS cal, but
they can use a temporary 90 day CAL initially. Have you tried setting
the default license server in the registry? - ref. MS KB Q239107

Michael Norton MCSE CCA
Consultrix Technologies
www.consultrix.net
 
J

Jason

Thanks for the reply. One of the clients in question is NT4. but the
other is win2k pro. Any suggestions there?

Another oddity, the TS licensing is running on an expired 90 license.
In fact, it seems it has been expired for QUITE some time.. But again,
they have a wide variety of clients (NT, 2k, XP) and all but the two I
mentioned are working fine and not generating any licensing event
errors. Any ideas on how this could be possible?

This problem gets stranger by the day! Thanks again!
 
G

Guest

Did you try connecting with an RDP Client to determine if the problem was with MSFT or Citrix

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Jason wrote: ----

Thanks for the reply. One of the clients in question is NT4. but th
other is win2k pro. Any suggestions there

Another oddity, the TS licensing is running on an expired 90 license
In fact, it seems it has been expired for QUITE some time.. But again
they have a wide variety of clients (NT, 2k, XP) and all but the two
mentioned are working fine and not generating any licensing even
errors. Any ideas on how this could be possible

This problem gets stranger by the day! Thanks again!
 
M

Martijn

Jason said:
Thanks for the reply. One of the clients in question is NT4. but the
other is win2k pro. Any suggestions there?

Another oddity, the TS licensing is running on an expired 90 license.
In fact, it seems it has been expired for QUITE some time.. But again,
they have a wide variety of clients (NT, 2k, XP) and all but the two I
mentioned are working fine and not generating any licensing event
errors. Any ideas on how this could be possible?

This problem gets stranger by the day! Thanks again!

It's not a strange problem.
You need licenses for workstations not running 2000 professional.
The reason your NT machine cannot connect is because it hasn't a cal
and it's 90 days temporarly license has been expired.

So it's not a problem, you just need to buy terminal server cal's.

--
 
R

Roland Lyngvig

You're right - and a TSCAL costs nearly the same as a full Windows XP, so
perhaps it's better to upgrade the OS and then get the CAL "for free"! :)

Best regards,
Roland Lyngvig
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top