Event ID 1004

[Zack]

I have just started to get this error on my terminal
server. Anything which does not already have a TS cal
cannot attach, either by RDP or ICA. All current clients
with TS CALS can wityh no problems. I have changed nothing
on the servers or the network. I have 42 available TS cals
and 15 available Citrix concurrent licenses. It seems like
the TS licensing server has just decided to stop issuing
new CALS! HELP!

 

[Guest]

Server is W2K SP2 with terminal services enhancement patch
applied.

 

[Vera Noest [MVP]]

Can you check if the TS can locate the LS (this would cause an event
1010 = "cannot locate LS" on the TS).

Does the LS log any problems?

If you delete the licensing information from one of the clients that
can't connect, does it connect afterwards (try at least twice: first
login should give you a temporary license, second login should give
you a permanent license).

 

[Guest]

I should be more specific. The 1004 is coming from the LS
(which is also the TS in question). There is no 1010 error
in the log. Also, the clients are Wyse Winterms, which
have been reset to factory defaults and reconfigured to no
avail.

 

[Vera Noest [MVP]]

OK, there are a number of specific problems and hotfixes for your
setup. Check if one of these helps:

813508 - Cannot Connect to a Terminal Server From a Windows-Based
Terminal
http://support.microsoft.com/?kbid=813508

825027 - Terminal Services Licensing Denies Your Connection to
Your Terminal Server from Your WBT Device
http://support.microsoft.com/?kbid=825027

329700 - Event ID 1004 and "Network or Dialup Problems Are
Preventing Communications with Citrix Server" Error Message When
Clients Try to Connect to Terminal Server
http://support.microsoft.com/?kbid=329700

 

[Guest]

I just had a problem somewhat like this. Here was the
issue and the resolution.

I was running TS on a Windows 2000 server with SP4
installed. My licensing server was a Windows 2000 Domain
Controller with SP4 installed as well. I had recently
purchase 10 TS CALs from my vendor and was told that the
2003 TS CALs were backwards compatible. It turns out
that while they are backwards compatible, they only work
if installed on a 2003 licensing server. If installed on
a 2000 licensing server, the install goes fine and
everything appears fine within the Licensing Manager snap-
in. It turns out that installing these not only corrupts
the licensing database but that once the server picks
that as the pool from which to issue licenses from it
won't stop until it has issued all of them. The only fix
was to re-install TS Licensing on the DC and re-activate
the server and licenses by calling the Microsoft
Clearinghouse.

Hope this helps.

DLB