Article ID: 238252
Article Last Modified on 2/19/2007
APPLIES TO
- Microsoft FrontPage 2000 Server Extensions
- Microsoft Visual SourceSafe 5.0 Standard Edition
- Microsoft Visual SourceSafe 6.0 Standard Edition
This article was previously published under Q238252
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
SUMMARY
In FrontPage 2000, errors relating to Visual SourceSafe integration are not automatically logged in the Event Viewer. For troubleshooting purposes, you may want to enable this capability by editing the registry.
MORE INFORMATION
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.
- Start Registry Editor (Regedt32.exe).
- Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\All Ports
- On the Edit menu, click Add Value, and then add the following registry value:
Value Name: LogInitialSourceControlErrors
Data Type: REG_SZ
Value: 1 - Quit Registry Editor.
NOTE: All errors logged by FrontPage regarding SourceSafe integration are logged at the server-end of the transaction. On a Windows NT system, the errors are logged in the Windows NT Event Viewer Application log. On a computer running Windows 95 or Windows 98, the errors are logged in the Frontpg.log file, which is located in the root of the drive where Windows is installed. The errors are not logged to the client computer.
Additional query words: front page vss
Keywords: kbinfo KB238252
