Re: Licensing errors after following MS Articles

I disabled the LLS on all servers. If that doesn't stop all licensing
errors I'll figure out what servers fear the most and try threats.

Bryan





"Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
wrote in message news:OB0Qm1NfFHA.3944@xxxxxxxxxxxxxxxxxxxxxxx
> It seems the consensus is that the license logging service should be
> stopped, and set to disabled. That may be the entire fix to eliminating
> the errors in the event log.
>
> --
> Les Connor [SBS Community Member - SBS MVP]
> -----------------------------------------------------------
> SBS Rocks !
>
>
> "Bryan L" <blinton.nospam@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:ODfcJSMfFHA.1048@xxxxxxxxxxxxxxxxxxxxxxx
>> Many thanks to Brandy Nee and Les Connor for much help already given with
>> this problem.
>>
>> First, my setup:
>>
>> One SBS 2003 server
>> Four member servers
>> One file server running 2000 Server
>> One SQL Server running 2000 Server
>> Two file servers running Server 2003 Std
>>
>> While attempting to clean up and properly configure licensing in my SBS
>> 2003 network, I followed the instructions in article 153140
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;153140), "How to
>> reset License Manager Information". This article instructed me to delete
>> or rename several files, one of them being C:\Winnt\System32\cpl.cfg,
>> which contains all the license purchase history information. I chose to
>> rename rather than delete this file.
>>
>> After completing the instructions in that article, I moved on to article
>> 327644 (http://support.microsoft.com/default.aspx?scid=kb;en-us;327644),
>> "How to configure licensing on an additional Windows server in an SBS
>> network. Following the instructions in that article under the heading
>> "Configure client access licenses on an additional server" results in the
>> following error message when I attempt to complete step 5:
>>
>> LICENSE SYSTEM
>> You do not have the appropriate access privileges to complete this
>> operation.
>>
>> I finally (after two days) found LicenseService event 205 in my
>> application log. TechNet has this to say about it:
>>
>> "205 The purchased license data could not be
>> saved to CPL.CFG.The data is the error code.
>>
>> "Indicates that changes to license purchase information
>> could not be saved. The License Logging service may
>> be able to successfully save the data later. If not, the data
>> will be lost. Data replicated from other servers will be
>> received again during the next replication. Data entered
>> on this server will have to be re-entered."
>>
>> Over the 5 days I've been messing with this, a new CPL.CFG file has never
>> been created to replace the renamed original. So this morning, on a
>> hunch, I renamed the original file back to CPL.CFG and then tried again
>> to configure licensing according to article 327644. It worked perfectly
>> and no error message was displayed. The Licensing snap-in shows my
>> entire original purchase history, plus the new entry just created by
>> following the instructions in 327644.
>>
>> What I'd like to accomplish is to start with a clean purchase history and
>> configure licensing on my servers from scratch. Apparently, deleting the
>> CPL.CFG file per the instructions in article 153140 isn't always the way
>> to go, since SBS 2003 (or at least, MY SBS 2003) won't or can't recreate
>> the file for some reason. I triple-checked group membership and
>> permissions on my member servers; the Domain Admins group is a member of
>> the local Administrators group on all member servers.
>>
>> Any thoughts?
>>
>> Thanks in advance,
>>
>> Bryan
>>
>
>


.

Relevant Pages

  • Re: Terminal Server License activation
    ... >From the Microsofts Terminal Services FAQ at ... The recommended method to configure TSL servers for high ... CALs for license issuance. ...
    (microsoft.public.windows.terminal_services)
  • Re: Anybody using a "real" Linux domain?
    ... >>servers and a coupla of windows 200x servers. ... >>also have to throw the license away. ... purchase andother license for the replacement machine. ... >>We have been gradually installing Linux in areas where a single ...
    (comp.os.linux.misc)
  • Re: Anybody using a "real" Linux domain?
    ... >>servers and a coupla of windows 200x servers. ... >>also have to throw the license away. ... purchase andother license for the replacement machine. ... >>We have been gradually installing Linux in areas where a single ...
    (comp.os.linux.networking)
  • Re: TS License Server question
    ... The recommended method to configure TSL servers for high availability is ... as enterprise license servers with regard to the following Lightweight ... new clients or clients with expired licenses will be denied access. ...
    (microsoft.public.windows.terminal_services)
  • Re: SBS Licensing Problems
    ... "Indicates that changes to license purchase information ... configure licensing on my servers from scratch. ... CPL.CFG file per the instructions in article 153140 isn't always the way to ...
    (microsoft.public.windows.server.sbs)