Re: Filename truncation and renaming question

Thanks again for your prompt reply and your assistance! I will reiterate to
our network folks the need to verify their part of the system. We are running
nightly backups and a weekly (somtimes more often) Analyze/Fix...

Um, what could be causing the spaces in the filenames to be replaced with
underscores? Is that a result of the Analyze/Fix on a corrupted Names.dat as
well?



"Alin Constantin [MSFT]" wrote:

No, I don't think that's the cause of corruption. Basically all IDEs (VB6,
VB.NET, VS, etc) will use the same dll (ssscc.dll, which is the MSSCCI dll
for SourceSafe) to access the VSS database.
Corruption in names.dat can be caused by a bug in VSS (I am not aware of any
bug in this area though), or by power or network failures, in which case VSS
doesn't get to finish updating all the database files during a
checkin/rename.
A good practice is to backup the database regularly and to run analyze on
the database often to keep it clean of corruptions (detecting and fixing
earlier is easier than a couple of months after the corruption appeared). If
VSS users get sometimes messages like "Network not found", "Invalid handle",
or similar errors that indicate network connection loss, it's also good to
check the connections and network cards and run analyze on the database to
fix potential corruptions.
--
Alin Constantin
This posting is provided "AS IS" with no warranties, and confers no rights.


"Miles" <Miles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B4435B10-9A50-4C8D-BCA1-CDCDCCD5BE75@xxxxxxxxxxxxxxxx
Thank you for your response Alin. We have indeed had recurring issues with
corruption in the Names.dat file. What would be causing that andwhat steps
can I take to help prevent that from occurring? We are running three
versions of Visual Studio (VB6, VB.Net for 2003 and 2005) against VSS
concurrently; could that be the problem?

"Alin Constantin [MSFT]" wrote:

Hi Miles,

While it's possible to be a bug in VSS, it is more plausible you had
database corruption in names.dat (or that you were missing names.dat)
Names.dat keeps the long filenames of the files in the VSS database. If
something bad happens with it, analyze has no way of recovering the long
names, and will truncate the filename to 31 characters.
--
Alin Constantin
This posting is provided "AS IS" with no warranties, and confers no
rights.


"Miles" <Miles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7FFE0F5B-2C88-4544-BD13-36B0A66FD884@xxxxxxxxxxxxxxxx
What can I do to cause VSS to not truncate long filenames when running
the
analyze/fix step?

Also, what can I do to cause VSS to not rename files (replacing spaces
with
underscores) when running the analyze/fix step?

I run the analyze/fix weekly, in two steps. Step 1 checks to see if
Step 2
is required.
Step 1 runs with the -X -B flags.
Step 2 does all the work; it uses a list of
parameters: -FL -FP -I- -S -C -D
-DC -DF -B

Thank you in advance for your help!
Miles







.

Relevant Pages

  • Re: Filename truncation and renaming question
    ... Is that a result of the Analyze/Fix on a corrupted Names.dat ... for SourceSafe) to access the VSS database. ... earlier is easier than a couple of months after the corruption appeared). ...
    (microsoft.public.vstudio.sourcesafe)
  • Re: Filename truncation and renaming question
    ... I don't think that's the cause of corruption. ... for SourceSafe) to access the VSS database. ... Corruption in names.dat can be caused by a bug in VSS (I am not aware of any ... A good practice is to backup the database regularly and to run analyze on ...
    (microsoft.public.vstudio.sourcesafe)
  • Re: Corruption of Access 2003 forms
    ... I use VSS with Access and don't usually have problems. ... Corruption seems to ... copy, compare it to a good form, and see if you can fix the file yourself. ... > procedure works fine if the database is in Access 2000 format. ...
    (microsoft.public.vstudio.sourcesafe)
  • Re: Attempt to fetch logical page
    ... You have a corruption in your database. ... Second, if you are on SQL Server 2000, check the specific recommendations for your error. ... This error occurs when Microsoft® SQL ServerT detects database corruption. ... execute DBCC CHECKDB to determine the extent of the damage. ...
    (microsoft.public.sqlserver.server)
  • Re: Do Transactions guard against corruption?
    ... when the database is opened and closed. ... meant by 'corruption'. ... Transactions have NEVER been designed as safeguard for those previous ... not used by Access to protect the structure of the database. ...
    (microsoft.public.access.modulesdaovba)