Microsoft KB Archive/943628

Knowledge Base

An error message is logged in ProgramLog.txt file after you relocate the database in Forefront Security for SharePoint

Article ID: 943628

Article Last Modified on 11/21/2007

---

APPLIES TO

• Microsoft Forefront Security for SharePoint

---

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows XP and Windows Vista

SYMPTOMS

After you relocate the database in Microsoft Forefront Security for SharePoint, you experience the following symptoms:

• The following error is frequently logged in the ProgramLog.txt file:

  Day Date Time ( 2928- 2128), "ERROR: Unable to create SharePoint Notifications database."

• The following related messages are frequently logged in the HRlog.txt file:

  Day Date Time ( 2928- 2128), "INFORMATION: F 0x80004005, 19364-(sybariservice)"
  Day Date Time ( 2928- 2128), "INFORMATION: S 0x80040e17, 19408-(sybariservice)"
  Day Date Time ( 2928- 2128), "INFORMATION: F 0x80040e17, 19526-(sybariservice)"

• Forefront Security does not load notifications when these errors and messages are logged.

Note Typically, the ProgramLog.txt and HRLog.txt files are located in the following folder:

C:\Program Files\Microsoft Forefront Security\SharePoint

CAUSE

This problem occurs when Notifications.mdb is no longer registered correctly as a System Data Source in the Open Database Connectivity (ODBC) configuration.

RESOLUTION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this issue follow these steps:

1. Click Start, click Run, type regedt32, and then press ENTER.
2. Locate and then click the following registry subkey:

   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Forefront Server Security\Sharepoint Server

3. In the right-pane, double-click the DatabasePath registry entry. Note the value that appears in the Value data box. This is the current location of the Forefront database files.
4. Exit Registry Editor.
5. Start Windows Explorer, and then move to the folder that you noted in step 3.
6. In that folder, rename the Notifications.mdb file. Change the name to Notifications.bak.
7. In the Services snap-in, restart the FSCController service. A new Notifications.mdb file is created.
8. Rename the new Notifications.mdb file. Change the name to Notifications.old.
9. Rename the original Notifications.bak file. Change the name to Notifications.mdb.
10. Restart the FSCController service.

REFERENCES

For more information, visit the following Microsoft Forefront Server Security TechCenter Web site:

http://technet.microsoft.com/en-us/forefront/serversecurity/bb734828.aspx

Keywords: kbtshoot kbregistry kbdatabase kbexpertiseadvanced KB943628

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.