Microsoft Knowledge Base Email Alertz

(318769) - If SharePoint Team Services or the FrontPage Server Extensions are configured to use Visual SourceSafe (VSS) integration with a project, and that project uses shadow folders, when you check in a file, the changes are not saved, and no warning or error...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 318769 - Last Review: February 21, 2007 - Revision: 2.1

STS: No Error Returned When VSS Shadow Folder Is Inaccessible

This article was previously published under Q318769

SYMPTOMS

If SharePoint Team Services or the FrontPage Server Extensions are configured to use Visual SourceSafe (VSS) integration with a project, and that project uses shadow folders, when you check in a file, the changes are not saved, and no warning or error message is displayed.

CAUSE

This program occurs when you do not have NT File System (NTFS) or share access to the shadow folder.

Visual SourceSafe detects that you do not have read/write access to the shadow folder, and returns an error; however, neither SharePoint Team Services nor FrontPage Server Extensions detects the error. Therefore, when you check in files, any changes that you made are lost, because the files are not replicated to the shadow folder.

RESOLUTION

To resolve this issue, an administrator must grant all users access to the shadow folder if they have read/write access in Microsoft Visual SourceSafe Administrator.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

For additional information about how to troubleshoot FrontPage and VSS integration, click the article numbers below to view the articles in the Microsoft Knowledge Base:
238252  (http://kbalertz.com/Feedback.aspx?kbNumber=238252/EN-US/ ) Enable Event Error Logging for FrontPage 2000 and SourceSafe
243623  (http://kbalertz.com/Feedback.aspx?kbNumber=243623/EN-US/ ) Errors with Source Control Integration When Checking Out Files

APPLIES TO
  • Microsoft SharePoint Team Services
  • Microsoft FrontPage 2002 Server Extensions
Keywords: 
kbbug kbpending KB318769
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate