The information in this article applies to:
SYMPTOMS
When you attempt to use Visual SourceSafe 5.0 and FrontPage Explorer
together, you may receive unexpected results. Specifically, FrontPage
Explorer will not display a Source Control Project box in the Web Settings
dialog box.
The specific file name in this error message will vary.
Case 3: You see the following error in the error log:
Case 4: You see the following errors in the error log:
Although the error messages may vary, they will always begin with
"Source Control System Failure" or "Visual SourceSafe Failure."
Case 5: No error message (FrontPage 97 or Visual SourceSafe 5.0 beta) Case 6: You see the following errors in the error log:
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, 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 machine.
CAUSE/WORKAROUNDCase 1: Microsoft Personal Web ServerCause:If you are using Microsoft Personal Web server for you Web Server, you cannot use FrontPage and Visual SourceSafe together. Currently, this configuration is unsupported. Case 2: "Source Control System failure: File 'srcsafe.ini' not found"Cause:You did not enable SourceSafe Integration when you installed SourceSafe. The FrontPage user account or the Internet Guest account (on IIS only) does not have an account within the SourceSafe Administrator. If your Visual SourceSafe and your SourceSafe data are stored on an NTFS drive, you may have not granted appropriate NTFS file system rights to the FrontPage user account, to the Internet Guest account (for IIS), or to the user account under which the web server operates. The SourceSafe integration DLLs are either unregistered or are different versions. NOTE: The server's error log will not report errors in this case. The SourceSafe database is located on a different computer than the one running IIS, and the Internet Guest account (typically IUSR_<machine name>) does not have access permissions to the SourceSafe database. For additional information, please see the following article in the Microsoft Knowledge Base: Q131022 INFO: Required Network Rights for the SourceSafe DirectoriesWorkaround To resolve this problem, use the following steps:
Case 3: Source Control System failure: User <your_user_account> not foundStart the Visual SourceSafe Administrator and make sure that your user account has read/write permissions and, for an IIS server only, the IUSR_<machine_name> (the Internet Guest) account has read permission within Visual SourceSafe Administrator. Make sure the passwords for these accounts are left blank.Case 4: "Source Control System Failure", "Visual SourceSafe Failure" ErrorsIn order to properly integrate FrontPage and Visual SourceSafe, assign CHANGE permissions to all SourceSafe logon accounts for all files under the Visual Source Safe installation directory (including the SourceSafe data directory if it is in a different location).Although tighter file restrictions may be possible, full SourceSafe functionality may be jeopardized by tighter restriction. The installation and check installation processes of FrontPage will only set permissions on Ssapi.dll and the SourceSafe resource DLL (Ssus.dll on US English). The installation process will not set permissions in other sections of the SourceSafe directory hierarchy. These permissions must be set manually. NOTE: It is assumed that the Administrators and System accounts will be granted full control to the entire VSS directory hierarchy. Grant at least read permissions to all SourceSafe logon accounts for the following additional files:
Grant at least read/write permissions to all SourceSafe logon accounts for
the following additional files or directories:
If restricting permissions to this level restricts SourceSafe
functionality, assign change permissions to all SourceSafe logon accounts
for all files under the Visual Source Safe installation directory.
For more information about required levels of NTFS permissions for Visual SourceSafe, see the Microsoft Visual Source Safe technical support Web site at: http://www.microsoft.com/ssafesupport/ NOTE: Because the Microsoft Web site is constantly updated, the site address may change without notice. If this occurs, link to the Microsoft home page at the following address: http://www.microsoft.com/FrontPage will log errors to the error log if the Internet Guest Account (of IIS) does not have read permission to the following files
and has read/write permissions to
These errors will not affect the functionality of the integration. You can
ignore them or grant the rights to the Internet Guest account to stop the
errors.
Case 5: You Are Using FrontPage 97 or Visual SourceSafe 5.0 BetaResolutionTo resolve this problem, use the following troubleshooting techniques:
Case 6: Source Control System failure: Invalid Handle ErrorCause:The SourceSafe database is located on a different computer than the one running IIS, and the Internet Guest account (typically IUSR_<machine name>) does not have access permissions to the SourceSafe database. For additional information, please see the following article in the Microsoft Knowledge Base: Q131022 Required Network Rights for the SourceSafe Directories Additional query words: vss
Keywords : kbinterop kbdta fpvss |
Last Reviewed: July 22, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |