Error 7054

[Guest Mark B]

I have a new 2003 Term. Server. I get an error code 7054 when I try to remote

control any T.S. session. Basically says "The system has reached its license

logon limit. Please try again later". Can't find much on the internet. Have

15 T.S. CALS, but only have ONE person connected right now. I need to figure

out this problem before migrating 12 other people. Any help would be greatly

appreciated.

[Guest Crockdaddy77]

RE: Error 7054

 

http://technet2.microsoft.com/windowsserver/en/library/46844a6e-386f-4ce3-98e5-d5377b5d6ba91033.mspx?mfr=true

 

Is your server contacting its license server?

 

 

 

"Mark B" wrote:

> I have a new 2003 Term. Server. I get an error code 7054 when I try to remote

> control any T.S. session. Basically says "The system has reached its license

> logon limit. Please try again later". Can't find much on the internet. Have

> 15 T.S. CALS, but only have ONE person connected right now. I need to figure

> out this problem before migrating 12 other people. Any help would be greatly

> appreciated.

[Guest Vera Noest [MVP]]

RE: Error 7054

 

I don't think that TS Licensing is the problem here.

This message usually means that the server OS has reached its

licensed logon limit.

Check the licensing mode of your server, in Control Panel -

Licensing applet.

Also check the EventLog to verify that it's the OS which is

complaining, not the Terminal Services.

 

If the above is indeed the problem, make sure that you have enough

server CALs for all clients that connect, and then either update

the information in the Licensing wizard with the correct number of

server CALs in your organisation, or change the licensing mode of

the server to "Per User or Per Device" (in stead of the "Per

Server" which is presumably the current licensing mode of the OS),

and then stop and disable the Licensing Logging Service

alltogether.

 

By default, it should be turned off (beginning with 2003 SP1). Read

the details here:

 

824196 - Description of the License Logging Service in Windows

Server Operating Systems

http://support.microsoft.com/?kbid=824196

 

_________________________________________________________

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?Q3JvY2tkYWRkeTc3?=

<Crockdaddy77@discussions.microsoft.com> wrote on 20 feb 2008 in

microsoft.public.windows.terminal_services:

> http://technet2.microsoft.com/windowsserver/en/library/46844a6e-3

> 86f-4ce3-98e5-d5377b5d6ba91033.mspx?mfr=true

>

> Is your server contacting its license server?

>

>

>

> "Mark B" wrote:

>

>> I have a new 2003 Term. Server. I get an error code 7054 when I

>> try to remote control any T.S. session. Basically says "The

>> system has reached its license logon limit. Please try again

>> later". Can't find much on the internet. Have 15 T.S. CALS, but

>> only have ONE person connected right now. I need to figure out

>> this problem before migrating 12 other people. Any help would

>> be greatly appreciated.

[Guest Mark B]

RE: Error 7054

 

Vera,

Thanks for your reply. I agree that the problem is more to do with

Windows rather than T.S.. The server licensing mode is in "Per User/Device"

mode. Funny thing is that only ONE person is using the server right now. I

login via RDP and still cant remote control the session (that's when I get

the error). Even with the default five licenses I shouldn't get this error. I

did see a post somewhere that they recommended deleting the following

registry key:

HKLM\SW\MS\MSLICENSIING

I'm a little leary about removing this key, but I'm really at my wit's

end. I assume removing this key and restarting would reset the licenses for

the O.S. Have you ever heard of anyone doing the same thing??

 

Mark

 

"Vera Noest [MVP]" wrote:

> I don't think that TS Licensing is the problem here.

> This message usually means that the server OS has reached its

> licensed logon limit.

> Check the licensing mode of your server, in Control Panel -

> Licensing applet.

> Also check the EventLog to verify that it's the OS which is

> complaining, not the Terminal Services.

>

> If the above is indeed the problem, make sure that you have enough

> server CALs for all clients that connect, and then either update

> the information in the Licensing wizard with the correct number of

> server CALs in your organisation, or change the licensing mode of

> the server to "Per User or Per Device" (in stead of the "Per

> Server" which is presumably the current licensing mode of the OS),

> and then stop and disable the Licensing Logging Service

> alltogether.

>

> By default, it should be turned off (beginning with 2003 SP1). Read

> the details here:

>

> 824196 - Description of the License Logging Service in Windows

> Server Operating Systems

> http://support.microsoft.com/?kbid=824196

>

> _________________________________________________________

> 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?Q3JvY2tkYWRkeTc3?=

> <Crockdaddy77@discussions.microsoft.com> wrote on 20 feb 2008 in

> microsoft.public.windows.terminal_services:

>

> > http://technet2.microsoft.com/windowsserver/en/library/46844a6e-3

> > 86f-4ce3-98e5-d5377b5d6ba91033.mspx?mfr=true

> >

> > Is your server contacting its license server?

> >

> >

> >

> > "Mark B" wrote:

> >

> >> I have a new 2003 Term. Server. I get an error code 7054 when I

> >> try to remote control any T.S. session. Basically says "The

> >> system has reached its license logon limit. Please try again

> >> later". Can't find much on the internet. Have 15 T.S. CALS, but

> >> only have ONE person connected right now. I need to figure out

> >> this problem before migrating 12 other people. Any help would

> >> be greatly appreciated.

>

[Guest Vera Noest [MVP]]

RE: Error 7054

 

There's no need and no help to get from deleting that registry key.

 

Did you read the KB article? It explains that the Licensing Logging

Service is often wrong, that's why the article (and I) advise to

stop and disable it. And do the same on your DC.

_________________________________________________________

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?TWFyayBC?= <MarkB@discussions.microsoft.com> wrote on 21

feb 2008 in microsoft.public.windows.terminal_services:

> Vera,

> Thanks for your reply. I agree that the problem is more to do

> with

> Windows rather than T.S.. The server licensing mode is in "Per

> User/Device" mode. Funny thing is that only ONE person is using

> the server right now. I login via RDP and still cant remote

> control the session (that's when I get the error). Even with the

> default five licenses I shouldn't get this error. I did see a

> post somewhere that they recommended deleting the following

> registry key: HKLM\SW\MS\MSLICENSIING

> I'm a little leary about removing this key, but I'm really at

> my wit's

> end. I assume removing this key and restarting would reset the

> licenses for the O.S. Have you ever heard of anyone doing the

> same thing??

>

> Mark

>

> "Vera Noest [MVP]" wrote:

>

>> I don't think that TS Licensing is the problem here.

>> This message usually means that the server OS has reached its

>> licensed logon limit.

>> Check the licensing mode of your server, in Control Panel -

>> Licensing applet.

>> Also check the EventLog to verify that it's the OS which is

>> complaining, not the Terminal Services.

>>

>> If the above is indeed the problem, make sure that you have

>> enough server CALs for all clients that connect, and then

>> either update the information in the Licensing wizard with the

>> correct number of server CALs in your organisation, or change

>> the licensing mode of the server to "Per User or Per Device"

>> (in stead of the "Per Server" which is presumably the current

>> licensing mode of the OS), and then stop and disable the

>> Licensing Logging Service alltogether.

>>

>> By default, it should be turned off (beginning with 2003 SP1).

>> Read the details here:

>>

>> 824196 - Description of the License Logging Service in Windows

>> Server Operating Systems

>> http://support.microsoft.com/?kbid=824196

>>

>> _________________________________________________________

>> 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?Q3JvY2tkYWRkeTc3?=

>> <Crockdaddy77@discussions.microsoft.com> wrote on 20 feb 2008

>> in microsoft.public.windows.terminal_services:

>>

>> > http://technet2.microsoft.com/windowsserver/en/library/46844a6

>> > e-3 86f-4ce3-98e5-d5377b5d6ba91033.mspx?mfr=true

>> >

>> > Is your server contacting its license server?

>> >

>> >

>> >

>> > "Mark B" wrote:

>> >

>> >> I have a new 2003 Term. Server. I get an error code 7054

>> >> when I try to remote control any T.S. session. Basically

>> >> says "The system has reached its license logon limit. Please

>> >> try again later". Can't find much on the internet. Have 15

>> >> T.S. CALS, but only have ONE person connected right now. I

>> >> need to figure out this problem before migrating 12 other

>> >> people. Any help would be greatly appreciated.

[Guest Mark B]

RE: Error 7054

 

Vera,

I know the service is disabled on the T.S. server itself. I'll check with

the London office to see if it's disabled there and let you know how it goes.

Thanks so much for your input.

 

Mark

 

"Vera Noest [MVP]" wrote:

> There's no need and no help to get from deleting that registry key.

>

> Did you read the KB article? It explains that the Licensing Logging

> Service is often wrong, that's why the article (and I) advise to

> stop and disable it. And do the same on your DC.

> _________________________________________________________

> 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?TWFyayBC?= <MarkB@discussions.microsoft.com> wrote on 21

> feb 2008 in microsoft.public.windows.terminal_services:

>

> > Vera,

> > Thanks for your reply. I agree that the problem is more to do

> > with

> > Windows rather than T.S.. The server licensing mode is in "Per

> > User/Device" mode. Funny thing is that only ONE person is using

> > the server right now. I login via RDP and still cant remote

> > control the session (that's when I get the error). Even with the

> > default five licenses I shouldn't get this error. I did see a

> > post somewhere that they recommended deleting the following

> > registry key: HKLM\SW\MS\MSLICENSIING

> > I'm a little leary about removing this key, but I'm really at

> > my wit's

> > end. I assume removing this key and restarting would reset the

> > licenses for the O.S. Have you ever heard of anyone doing the

> > same thing??

> >

> > Mark

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> I don't think that TS Licensing is the problem here.

> >> This message usually means that the server OS has reached its

> >> licensed logon limit.

> >> Check the licensing mode of your server, in Control Panel -

> >> Licensing applet.

> >> Also check the EventLog to verify that it's the OS which is

> >> complaining, not the Terminal Services.

> >>

> >> If the above is indeed the problem, make sure that you have

> >> enough server CALs for all clients that connect, and then

> >> either update the information in the Licensing wizard with the

> >> correct number of server CALs in your organisation, or change

> >> the licensing mode of the server to "Per User or Per Device"

> >> (in stead of the "Per Server" which is presumably the current

> >> licensing mode of the OS), and then stop and disable the

> >> Licensing Logging Service alltogether.

> >>

> >> By default, it should be turned off (beginning with 2003 SP1).

> >> Read the details here:

> >>

> >> 824196 - Description of the License Logging Service in Windows

> >> Server Operating Systems

> >> http://support.microsoft.com/?kbid=824196

> >>

> >> _________________________________________________________

> >> 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?Q3JvY2tkYWRkeTc3?=

> >> <Crockdaddy77@discussions.microsoft.com> wrote on 20 feb 2008

> >> in microsoft.public.windows.terminal_services:

> >>

> >> > http://technet2.microsoft.com/windowsserver/en/library/46844a6

> >> > e-3 86f-4ce3-98e5-d5377b5d6ba91033.mspx?mfr=true

> >> >

> >> > Is your server contacting its license server?

> >> >

> >> >

> >> >

> >> > "Mark B" wrote:

> >> >

> >> >> I have a new 2003 Term. Server. I get an error code 7054

> >> >> when I try to remote control any T.S. session. Basically

> >> >> says "The system has reached its license logon limit. Please

> >> >> try again later". Can't find much on the internet. Have 15

> >> >> T.S. CALS, but only have ONE person connected right now. I

> >> >> need to figure out this problem before migrating 12 other

> >> >> people. Any help would be greatly appreciated.

>