MSTerminalServices.org Forums

Forums Home | FAQ | Search | Profile | Private Messages | Log in/Register/Password

Event ID 1004 No Terminal Server License

Page 1 of 1
Next:  General Discussions: Internet Explorer Permissions  
Author Message
th4711

External


Since: Aug 15, 2006
Posts: 6



(Msg. 1) Posted: Tue Aug 15, 2006 9:56 am
Post subject: Event ID 1004 No Terminal Server License
Archived from groups: microsoft>public>windows>terminal_services (more info?)

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
Back to top
Send e-mail Login to vote
th4711

External


Since: Aug 15, 2006
Posts: 6



(Msg. 2) Posted: Wed Aug 16, 2006 8:27 am
Post subject: Re: Event ID 1004 No Terminal Server License [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

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/notconnecttoremotepc.htm
>
>
> 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 DeleteThis @discussions.microsoft.com> wrote in message news:7DA33991-7635-490A-858C-219E46076080@microsoft.com...
> 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
>
Back to top
Send e-mail Login to vote
Vera Noest [MVP]

External


Since: Sep 07, 2003
Posts: 9443



(Msg. 3) Posted: Wed Aug 16, 2006 5:51 pm
Post subject: Re: Event ID 1004 No Terminal Server License [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

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.RemoveThis@discussions.microsoft.com> 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/notconnecttoremotepc.htm
>>
>>
>>
>> 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.RemoveThis@discussions.microsoft.com> wrote in message
>> news:7DA33991-7635-490A-858C-219E46076080@microsoft.com...
>> 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
Back to top
Send e-mail Login to vote
th4711

External


Since: Aug 15, 2006
Posts: 6



(Msg. 4) Posted: Thu Aug 17, 2006 1:51 am
Post subject: Re: Event ID 1004 No Terminal Server License [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

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.TakeThisOut@discussions.microsoft.com> 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/notconnecttoremotepc.htm
> >>
> >>
> >>
> >> 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.TakeThisOut@discussions.microsoft.com> wrote in message
> >> news:7DA33991-7635-490A-858C-219E46076080@microsoft.com...
> >> 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
>
Back to top
Send e-mail Login to vote
Vera Noest [MVP]

External


Since: Sep 19, 2003
Posts: 1954



(Msg. 5) Posted: Thu Aug 17, 2006 9:17 am
Post subject: Re: Event ID 1004 No Terminal Server License [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

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.RemoveThis@discussions.microsoft.com> 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.RemoveThis@discussions.microsoft.com> 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/notconnecttoremotepc.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.RemoveThis@discussions.microsoft.com> wrote in
>> >> message
>> >> news:7DA33991-7635-490A-858C-219E46076080@microsoft.com...
>> >> 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
Back to top
Send e-mail Login to vote
th4711

External


Since: Aug 15, 2006
Posts: 6



(Msg. 6) Posted: Fri Aug 18, 2006 5:55 am
Post subject: Re: Event ID 1004 No Terminal Server License [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

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.TakeThisOut@discussions.microsoft.com> 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.TakeThisOut@discussions.microsoft.com> 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/notconnecttoremotepc.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.TakeThisOut@discussions.microsoft.com> wrote in
> >> >> message
> >> >> news:7DA33991-7635-490A-858C-219E46076080@microsoft.com...
> >> >> 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
>
Back to top
Send e-mail Login to vote
Vera Noest [MVP]

External


Since: Sep 07, 2003
Posts: 9443



(Msg. 7) Posted: Fri Aug 18, 2006 5:06 pm
Post subject: Re: Event ID 1004 No Terminal Server License [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

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 RemoveThis @discussions.microsoft.com> 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 RemoveThis @discussions.microsoft.com> 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 RemoveThis @discussions.microsoft.com>
>> >> 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 RemoveThis @discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:7DA33991-7635-490A-858C-219E46076080@microsoft.com.
>> >> >> .. 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
Back to top
Send e-mail Login to vote
th4711

External


Since: Aug 15, 2006
Posts: 6



(Msg. 8) Posted: Tue Aug 22, 2006 1:20 am
Post subject: Re: Event ID 1004 No Terminal Server License [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

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.DeleteThis@discussions.microsoft.com> 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.DeleteThis@discussions.microsoft.com> 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.DeleteThis@discussions.microsoft.com>
> >> >> 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.DeleteThis@discussions.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:7DA33991-7635-490A-858C-219E46076080@microsoft.com.
> >> >> >> .. 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
>
Back to top
Send e-mail Login to vote
Vera Noest [MVP]

External


Since: Sep 07, 2003
Posts: 9443



(Msg. 9) Posted: Tue Aug 22, 2006 3:35 pm
Post subject: Re: Event ID 1004 No Terminal Server License [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Are you running SP1 on all servers?
Is your TS Licensing Server configures as a Domain or an Enterprise
Licensing Server?

Check if this helps:

895151 - Windows Server 2003-based or Windows 2000-based terminal
servers do not automatically discover a license server that is
designated as an enterprise license server
http://support.microsoft.com/?kbid=895151

If not, I would call Microsoft Support.
_________________________________________________________
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.DeleteThis@discussions.microsoft.com> wrote on
22 aug 2006 in microsoft.public.windows.terminal_services:

> 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.DeleteThis@discussions.microsoft.com> 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.DeleteThis@discussions.microsoft.com>
>> >> 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.DeleteThis@discussions.microsoft.com>
>> >> >> 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/notconnecttoremo
>> >> >> >> tep 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.DeleteThis@discussions.microsoft.com> wrote in
>> >> >> >> message
>> >> >> >> news:7DA33991-7635-490A-858C-219E46076080@microsoft.c
>> >> >> >> om. .. 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
Back to top
Send e-mail Login to vote
th4711

External


Since: Aug 15, 2006
Posts: 6



(Msg. 10) Posted: Wed Aug 23, 2006 2:47 am
Post subject: Re: Event ID 1004 No Terminal Server License ------ Problem solved [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Many Thanks!

The problem is solved. After editing the AD (like described in the KB
892151==> Adding the CN=TS-Enterprise-LicenseServer entry the site location)

All Servers can find automatically the TS License server.

Thanks again for your help.

kind regards

Torsten


"Vera Noest [MVP]" wrote:

> Are you running SP1 on all servers?
> Is your TS Licensing Server configures as a Domain or an Enterprise
> Licensing Server?
>
> Check if this helps:
>
> 895151 - Windows Server 2003-based or Windows 2000-based terminal
> servers do not automatically discover a license server that is
> designated as an enterprise license server
> http://support.microsoft.com/?kbid=895151
>
> If not, I would call Microsoft Support.
> _________________________________________________________
> 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 DeleteThis @discussions.microsoft.com> wrote on
> 22 aug 2006 in microsoft.public.windows.terminal_services:
>
> > 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 DeleteThis @discussions.microsoft.com> 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 DeleteThis @discussions.microsoft.com>
> >> >> 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 DeleteThis @discussions.microsoft.com>
> >> >> >> 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/notconnecttoremo
> >> >> >> >> tep 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 DeleteThis @discussions.microsoft.com> wrote in
> >> >> >> >> message
> >> >> >> >> news:7DA33991-7635-490A-858C-219E46076080@microsoft.c
> >> >> >> >> om. .. 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
>
Back to top
Send e-mail Login to vote
Vera Noest [MVP]

External


Since: Sep 07, 2003
Posts: 9443



(Msg. 11) Posted: Wed Aug 23, 2006 11:27 am
Post subject: Re: Event ID 1004 No Terminal Server License ------ Problem solved [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Great! I'm glad that it's finally solved!
Still don't understand how this has been working for 2 years,
though. But all is well that ends well Smile
_________________________________________________________
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.RemoveThis@discussions.microsoft.com> wrote on
23 aug 2006 in microsoft.public.windows.terminal_services:

> Many Thanks!
>
> The problem is solved. After editing the AD (like described in
> the KB 892151==> Adding the CN=TS-Enterprise-LicenseServer entry
> the site location)
>
> All Servers can find automatically the TS License server.
>
> Thanks again for your help.
>
> kind regards
>
> Torsten
>
>
> "Vera Noest [MVP]" wrote:
>
>> Are you running SP1 on all servers?
>> Is your TS Licensing Server configures as a Domain or an
>> Enterprise Licensing Server?
>>
>> Check if this helps:
>>
>> 895151 - Windows Server 2003-based or Windows 2000-based
>> terminal servers do not automatically discover a license server
>> that is designated as an enterprise license server
>> http://support.microsoft.com/?kbid=895151
>>
>> If not, I would call Microsoft Support.
>> _________________________________________________________
>> 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.RemoveThis@discussions.microsoft.com> wrote
>> on 22 aug 2006 in microsoft.public.windows.terminal_services:
>>
>> > 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.RemoveThis@discussions.microsoft.com>
>> >> 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.RemoveThis@discussions.microsoft.com>
>> >> >> 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.RemoveThis@discussions.microsoft.com> 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/notconnecttor
>> >> >> >> >> emo tep 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.RemoveThis@discussions.microsoft.com> wrote
>> >> >> >> >> in message
>> >> >> >> >> news:7DA33991-7635-490A-858C-219E46076080@microsof
>> >> >> >> >> t.c om. .. 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
Back to top
Send e-mail Login to vote
Shivkumar

External


Since: Oct 26, 2006
Posts: 2



(Msg. 12) Posted: Fri Oct 27, 2006 1:00 am
Post subject: Re: Event ID 1004 No Terminal Server License ------ Problem solve [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Dear Team ,
I need help on simmilar case .One of my user unable to connect with two
terminal server running windows 2000 server .Even we have enough license key .

Many Thanks
Shivkumar


"Vera Noest [MVP]" wrote:

> Great! I'm glad that it's finally solved!
> Still don't understand how this has been working for 2 years,
> though. But all is well that ends well Smile
> _________________________________________________________
> 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.DeleteThis@discussions.microsoft.com> wrote on
> 23 aug 2006 in microsoft.public.windows.terminal_services:
>
> > Many Thanks!
> >
> > The problem is solved. After editing the AD (like described in
> > the KB 892151==> Adding the CN=TS-Enterprise-LicenseServer entry
> > the site location)
> >
> > All Servers can find automatically the TS License server.
> >
> > Thanks again for your help.
> >
> > kind regards
> >
> > Torsten
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Are you running SP1 on all servers?
> >> Is your TS Licensing Server configures as a Domain or an
> >> Enterprise Licensing Server?
> >>
> >> Check if this helps:
> >>
> >> 895151 - Windows Server 2003-based or Windows 2000-based
> >> terminal servers do not automatically discover a license server
> >> that is designated as an enterprise license server
> >> http://support.microsoft.com/?kbid=895151
> >>
> >> If not, I would call Microsoft Support.
> >> _________________________________________________________
> >> 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.DeleteThis@discussions.microsoft.com> wrote
> >> on 22 aug 2006 in microsoft.public.windows.terminal_services:
> >>
> >> > 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.DeleteThis@discussions.microsoft.com>
> >> >> 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.DeleteThis@discussions.microsoft.com>
> >> >> >> 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.DeleteThis@discussions.microsoft.com> 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/notconnecttor
> >> >> >> >> >> emo tep 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.DeleteThis@discussions.microsoft.com> wrote
> >> >> >> >> >> in message
> >> >> >> >> >> news:7DA33991-7635-490A-858C-219E46076080@microsof
> >> >> >> >> >> t.c om. .. 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
>
Back to top
Send e-mail Login to vote
Vera Noest [MVP]

External


Since: Sep 19, 2003
Posts: 1954



(Msg. 13) Posted: Fri Oct 27, 2006 6:56 am
Post subject: Re: Event ID 1004 No Terminal Server License ------ Problem solve [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Since the thread you reply to was about a 2003 TS, I doubt that you
have exactly the same problem.
But I assume that you also see an Event 1004 on the Terminal
Server?

Can you give some more information:
* which OS is the client running?
* are the Terminal Servers member servers in a W2K domain, a 2003
domain, a NT4 domain, or standalone servers in a workgroup?
* on which server is the TS Licensing Server running?
* what OS is the TS Licensing Server running?
* what is listed in the TS Licensing Server under "Available" and
"Issued" for the different types of licenses?
* can the TS locate the LS?
* has the client been able to connect before?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?U2hpdmt1bWFy?= <Shivkumar RemoveThis @discussions.microsoft.com>
wrote on 27 okt 2006:

> Dear Team ,
> I need help on simmilar case .One of my user unable to connect
> with two terminal server running windows 2000 server .Even we
> have enough license key .
>
> Many Thanks
> Shivkumar
Back to top
Send e-mail Login to vote
Display posts from previous:   
    All times are: Eastern Time (US & Canada) (change) Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Looking for more Terminal Services info?

Sign up to the MSTerminalServices.org Monthly Newsletter, written by Terminal Server MVP & Citrix CTP Stefan Vermeulen, containing news, tips, interviews, links of the month and much more. Subscribe today and don't miss a thing!

Become an MSTerminalServices.org member!

Discuss your Terminal Services & Citrix issues with thousands of other SBC experts. Click here to join!

Community Area

Log in | Register