Microsoft KB Archive/191289

= How To Enable Event Error Logging for FrontPage 2000, FrontPage 98 and SourceSafe =

Article ID: 191289

Article Last Modified on 6/30/2004

-

APPLIES TO


 * Microsoft Visual SourceSafe 5.0 Standard Edition
 * Microsoft Visual SourceSafe 6.0 Standard Edition
 * Microsoft FrontPage 2000 Standard Edition
 * Microsoft FrontPage 98 Standard Edition

-



This article was previously published under Q191289



SUMMARY
With FrontPage 97, errors relating to the SourceSafe integration automatically display in the Web Server NT Event Log, usually on the Application tab. However, this behavior must be enabled in FrontPage 2000 or FrontPage 98.



Front Page 98 Server Extensions
Adding the following entry to the Frontpg.ini file on the Web server, allows you to see the error messages that are causing the SourceSafe integration in FrontPage to fail: LogInitialSourceControlErrors=1 The preceding line should be placed in the "[FrontPage 3.0]" section of the Frontpg.ini file.

Front Page 2000 Server Extensions (version 4.0.2.2717 or later)
Add the following registry entry as a String Value: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\All Ports \LogInitialSourceControlErrors with the value "1"

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 Microsoft Windows 95 or Microsoft Windows 98, the errors are logged in the Frontpg log file located in the root of the drive to which Windows is installed. The errors are not logged to the client computer.

In both cases you may want to set the value to zero once all errors have been resolved to avoid unnecessary activity in the Event log.

Keywords: kbhowto KB191289

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.