KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Article: Q248760
Product(s): Microsoft SourceSafe
Version(s): WINDOWS:6.0
Operating System(s): 
Keyword(s): kbCommandLine kbddconv kbSSafe600 kbSSafe600bug kbSSafe600fix kbAnalyze kbDSupport kbGr
Last Modified: 20-MAY-2002

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Visual SourceSafe for Windows, version 6.0 
-------------------------------------------------------------------------------

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.


RESOLUTION
==========

This feature is available in the latest service pack for Visual Studio 6.0. For
additional information, please see the following article in the Microsoft
Knowledge Base:

  Q194022 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:

  http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

The English version of this fix should have the following file attributes or
later:

+-------------------------------------------------------------------------+
| Name         | Size      | Date       | Time     | Version#  | Platform | 
+-------------------------------------------------------------------------+
| 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.

+------------------------------------------------------------+
| Name        | Size      | Date       | Time     | Platform | 
+------------------------------------------------------------+
| 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.

STATUS
======

Microsoft has confirmed this to be a bug in the Microsoft products 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 article
numbers below to view the articles in the Microsoft Knowledge Base:

  Q194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why

  Q194295 HOWTO: Tell That a Visual Studio Service Pack Is Installed

You can download the latest Visual Studio service pack from the following
Microsoft Web site:

  Visual Studio Product Updates
  (http://msdn.microsoft.com/vstudio/downloads/updates.asp)

Additional query words: sp4 analyze error

======================================================================
Keywords          : kbCommandLine kbddconv kbSSafe600 kbSSafe600bug kbSSafe600fix kbAnalyze kbDSupport kbGrpDSSSafe kbSSafe600qfe kbVS600sp4fix kbVS600sp5fix kbSSafeAnalyze 
Technology        : kbSSafeSearch kbAudDeveloper kbSSafe600
Version           : WINDOWS:6.0
Issue type        : kbbug
Solution Type     : kbfix

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Q248760: FIX: Project Log <physical filename> Share (From Another Proj)