Microsoft KB Archive/254820

From BetaArchive Wiki
Knowledge Base


Site Server 3.0 Membership Broker May Cause Access Violation or Event ID 4105

Article ID: 254820

Article Last Modified on 10/6/2005



APPLIES TO

  • Microsoft Site Server 3.0 Standard Edition
  • Microsoft Site Server 3.0 Commerce Edition



This article was previously published under Q254820

SYMPTOMS

Site Server 3.0 Membership Authentication (Broksvc) may cause intermittent Access Violation errors in the Tokencreator.dll file or cause an event ID 4105 to occur in the event log when the Broker cannot create a Local Windows NT Group corresponding to a new Membership Group.


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. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Site Server service pack that contains this hotfix.

To resolve this problem immediately, 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 typical 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    Version     Size    File name         Platform
   -----------------------------------------------------------------
   02/16/2000 10:51a  7.0.1296.0  27,024  Tokencreator.dll  x86
   02/16/2000 10:50a  7.0.1296.0  47,888  Tokencreator.dll  alpha
                



STATUS

Microsoft has confirmed that this is a problem in Site Server 3.0.

Keywords: kbbug kbfix kbqfe kbhotfixserver KB254820