FIX: Project Log <physical filename> has a Share (From Another Project) (248760)
The information in this article applies to:
- Microsoft Visual SourceSafe for Windows 6.0
This article was previously published under Q248760 SYMPTOMS
When running Analyze.exe on a Microsoft Visual SourceSafe (VSS) database, the following error is reported but not fixed.
Project log '<physical filename>' has a share (from another project) record for item '<filename>', but that item wasn't found in the current project.
RESOLUTIONThis feature is available in the latest service pack for Visual Studio 6.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
Also, a supported fix for Visual SourceSafe 6.0 that corrects this problem is available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
The English version of this fix should have the following file attributes or later:
|
Analyze.exe | 211,968 | 12/08/1999 | 10:11 PM | 6.0.87.6 | x86 | Ddconv.exe | 310,784 | 10/22/1999 | 12:55 AM | none | x86 | Ddupd.exe | 443,392 | 12/08/1999 | 09:40 PM | none | x86 | Ss.exe | 415,744 | 12/08/1999 | 09:30 PM | none | x86 | Ssapi.dll | 591,360 | 12/08/1999 | 09:34 PM | 6.0.87.6 | x86 | Ssarc.exe | 528,384 | 12/08/1999 | 09:45 PM | 6.0.87.6 | x86 | Ssrestor.exe | 526,336 | 12/08/1999 | 09:47 PM | 6.0.87.6 | x86 | Dsscc.dll | 1,501,696 | 10/22/1999 | 01:38 AM | 6.0.86.60 | x86 |
All files are contained in a self-extracting EXE. |
VSS8706.exe | 2,178,542 | 12/17/1999 | 11:31 AM | x86 | NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in the latest service pack for Visual Studio 6.0. For additional information about Visual Studio service packs, click the following article numbers to view the articles in the Microsoft Knowledge Base: 194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
194295 HOWTO: Tell That a Visual Studio Service Pack Is Installed To download the latest Visual Studio service pack, visit the following Microsoft Web site:
Modification Type: | Major | Last Reviewed: | 4/7/2006 |
---|
Keywords: | kbQFE KBHotfixServer kbBug kbCommandLine kbddconv kbfix kbSSafe600fix kbSSafeAnalyze kbVS600sp4fix kbVS600sp5fix KB248760 |
---|
|