Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/247794

From BetaArchive Wiki
Knowledge Base


Deadlock Condition in License Manager Service Causing Service to Hang

Article ID: 247794

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Server 4.0 Standard Edition



This article was previously published under Q247794

SYMPTOMS

The following error message may appear in the Event log:

Event 213 -Replication of license information failed because the License Logging Service on server (PDC servername) could not be contacted.

Programs that try to contact the License Server service may receive the following error message:

RPC Server Busy

CAUSE

There is a problem in the License Server service that could cause the service to deadlock. This stops the service from processing any requests.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

   Date      Time      Size       File name    Platform
   ----------------------------------------------------
   12/6/99    3:17p    119,056    Llssrv.exe   Intel
   12/6/99    4:12p    189,712    Llssrv.exe   Alpha
                



STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbhotfixserver kbqfe kbbug kbfix KB247794