Re: Event ID 1004 No Terminal Server License
- From: th4711 <th4711@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 21 Aug 2006 22:20:01 -0700
Hi,
I find the two following eventlog entries repating:
TermService =>Warning => EID 1026
The terminal server could not locate a license server in the kusch.de
domain. Confirm that all license servers on the network are registered in
WINS/DNS, accepting network requests, and the Terminal Server Licensing
Service is running.
TermService=>Information=>EID 1008
The terminal server cannot issue a client license. It was unable to issue
the license due to a changed (mismatched) client license, insufficient
memory, or an internal error. Further details for this problem may have been
reported at the client's computer.
"Vera Noest [MVP]" wrote:
Yes, there's something strange going on, but I'm not sure what..
I would keep a close eye on the EventLog for licensing events.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?dGg0NzEx?= <th4711@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
18 aug 2006 in microsoft.public.windows.terminal_services:
Hello,
not automatically, on none of our terminalservers only if I do
this manual. So I am wondering why the existing TS were running
without error for about 2 years?
Thats strange isn't it.
kind regards
"Vera Noest [MVP]" wrote:
If you start the Terminal services Licensing tool on the
Terminal Server (not the LS), does it automatically find the
LS? If it does (and it should!), then all is well.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
=?Utf-8?B?dGg0NzEx?= <th4711@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 17 aug 2006:
Yes I did verify the registry entry.
After reinstalling the server it seems to work.
Is it possible to see, if the server is running because of
the 120 days test period or an active connection to the
license server?
We are using the "per user" license mode.
kind regards
Torsten
"Vera Noest [MVP]" wrote:
Have you verified the registry entry?
279561 - How to Override the License Server Discovery
Process in Windows Server 2003 Terminal Services
http://support.microsoft.com/?kbid=279561
Or use a Group Policy to set the preferred TS Licensing
Server (assuming you run SP1 on all servers).
Computer Configuration - Administrative templates - Windows
components - Terminal Services
"Use the specified Terminal Server license servers"
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?dGg0NzEx?= <th4711@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 16 aug 2006 in
microsoft.public.windows.terminal_services:
Hello,
I tried to use lsview from my Client, the operational
german Terminalserver and the non working englisch TS all
with the same result there is no license server shown.
If I use the terminal service license console ( from the
Englisch TS) and connect manually to the License server
the licenses are correct shown.
Is it possible to publish the location (because it is not
on the DC) of the License Server over AD or DHCP?
I think I try to make a clean install and see if the
problem is still there.
"Robert L [MS-MVP]" wrote:
You may want to use Terminal Services Viewer to check the
TS licensing server status. These search result may help,
not establish a connection to the remote computer On the
TS, you may receive Event ID 1004 - Source: TermService
-Description: The Terminal Server cannot issue a client
license. Resolution: 1. ...
www.chicagotech.net/remoteissues/notconnecttoremotep
c.h tm
How to How to use the Terminal Services Viewer. Case
Study: one of our clients received this message when they
accessed the TS using RDC: "The client could not ...
www.howtonetworking.com/RemoteAccess/ts14.htm
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net How to Setup Windows, Network,
VPN & Remote Access on http://www.HowToNetworking.com
"th4711" <th4711@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:7DA33991-7635-490A-858C-219E46076080@xxxxxxxxxxxxxx
.. Hello,
I have the following configuration:
1 Terminal License Server W2K3 German
4 Terminal Server W2K3 / Citrix PS 3.0 German
This works correct.
I try to install an additonal Termnalserver W2K3
englisch. I have manually entered the Terminal License
Server in the registry as I did by the german ones.
In the EventLog on the new TS there is an entry 1004:
"The terminal server cannot issue a client license. It
was unable to issue the license due to a changed
(mismatched) client license, insufficient memory, or an
internal error. Further details for this problem may
have been reported at the client's computer."
When I try to connect via RDP it says that there is no
License Server.
what can i do?
greetings
Torsten
- Follow-Ups:
- Re: Event ID 1004 No Terminal Server License
- From: Vera Noest [MVP]
- Re: Event ID 1004 No Terminal Server License
- References:
- Re: Event ID 1004 No Terminal Server License
- From: th4711
- Re: Event ID 1004 No Terminal Server License
- From: Vera Noest [MVP]
- Re: Event ID 1004 No Terminal Server License
- From: th4711
- Re: Event ID 1004 No Terminal Server License
- From: Vera Noest [MVP]
- Re: Event ID 1004 No Terminal Server License
- From: th4711
- Re: Event ID 1004 No Terminal Server License
- From: Vera Noest [MVP]
- Re: Event ID 1004 No Terminal Server License
- Prev by Date: Re: Licensing
- Next by Date: Re: File copy and paste Win2k3
- Previous by thread: Re: Event ID 1004 No Terminal Server License
- Next by thread: Re: Event ID 1004 No Terminal Server License
- Index(es):
Relevant Pages
|
Loading
