Event IDs 11000 and 11001 occur when an ISA Server logs on to a SQL Server database

Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

Symptoms

After you configure Microsoft Internet Security and Acceleration (ISA) Server to log on to a Microsoft SQL Server database, you may receive the following error messages in the application event log:
Note The source location values may not match those shown in these event messages. The important information in these messages is that the msFPCName property is not found in the Credentials container.


Workaround

Active Directory


Note Use this section only if the event log message contains the word “LDAP://”.

To use Active Directory and the ADSI Edit snap-in to mask the Event IDs, follow these steps.

Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.

  1. At a command prompt, type Regsvr32 schmmgmt.dll. The Schmmgmt.dll file is in the Windows\System32 folder.

  2. Open the Active Directory Schema snap-in.

  3. Right-click the Active Directory Schema operations master, and then select Schema may be modified on this domain controller.

  4. Expand Classes, right-click msfpccredentials, and then click Properties. Click Attributes, click Add, and then add msFPCName. Click Apply, and then click OK.

  5. Open the ADSI Edit snap-in. Click Domain, click System, click FPC, and then click Arrays. Click GUID, click Logs, click WebProxy, and then click Credentials.

  6. Right-click Credentials, and then click Properties. In the Select which properties to view box, select Both. In the Select a property to view box, select msFPCName. Type any string in the Edit attribute box. Click Apply, and then click OK.

  7. Force replication between the domain controllers.

  8. Restart ISA services.

Registry


Note Use this section only if the event log message does not contain the word “LDAP://”


Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To use the registry to mask the Event IDs, follow these steps:

  1. From a command prompt, type regedit.

  2. Locate the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fpc\Arrays\{CurrentArrayGUID}\Logs\WebProxy\Credentials

  3. Right-click in the right pane, and then click New. Click String Value.

  4. Type msFPCName in the New Value #1 box.

  5. Double-click msFPCName.

  6. Type any string for the value data, and then click OK.

  7. Quit Registry Editor, and then restart ISA services.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

These error messages are false reports that are caused by the SecurID credentials export functionality. This problem only affects the Web Proxy service.

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

313139 How to obtain the latest Internet Security and Acceleration Server 2000 service pack

319380 ISA Server 2000 Feature Pack 1 overview

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×