Re: Problem with sharing a label. ( URGENT )

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Lorne (anonymous_at_discussions.microsoft.com)
Date: 02/18/04 

Date: Wed, 18 Feb 2004 08:36:07 -0800

Thanks Joe,

I run the analyze command weekly as follows;

ANALYZE -C -D -F -V4 F:\Progra~1\Micros~1\VSS\data

 I get the following messages;

Analyze Visual SourceSafe Version 6.0a (Build 8987)
Database analysis in progress @ 2/17/04; 9:37a.
Building the project list.
Project log 'clfaaaaa' has a delete record for item 'ObjectOrientedModel_seq_Add_KWSug', but that item wasn't found in the project.
The project contents as rebuilt from the log 'clfaaaaa' does not match the project's actual contents.
Writing a new copy of 'f:\progra~1\micros~1\vss\data\c\clfaaaaa'.
Checking cross file relationships.
The file d_program_count_gol_email.srd was branched from CLHAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_adm_carrier.srd was branched from CAHAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_tone_count.srd was branched from CQHAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_dddw_backorder.srd was branched from CBHAAAAA which is now corrupted and the early versions will be unaccessible.
The file pfc_n_cst_dwsrv_multitable.sru was branched from CCIAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_merge_jurisdition.srd was branched from CDHAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_r_referral_ocan.srd was branched from CPHAAAAA which is now corrupted and the early versions will be unaccessible.
The file w_impact_report_gol_url.srw was branched from CJHAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_callback_origin.srd was branched from CIHAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_classification_count.srd was branched from CRIAAAAA which is now corrupted and the early versions will be unaccessible.
The file pfc_n_cst_returnattrib.sru was branched from CAIAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_far_act_report2.srd was branched from CHHAAAAA which is now corrupted and the early versions will be unaccessible.
The file pfc_w_child.srw was branched from CDIAAAAA which is now corrupted and the early versions will be unaccessible.
The file u_tabpg_dwproperty_srvquerymode.s was branched from CQIAAAAA which is now corrupted and the early versions will be unaccessible.
The file pfc_w_debuglog.srw was branched from CHIAAAAA which is now corrupted and the early versions will be unaccessible.
The file n_cst_metaclass.sru was branched from CKIAAAAA which is now corrupted and the early versions will be unaccessible.
The file imp_caps.pbl was branched from CSKAAAAA which is now corrupted and the early versions will be unaccessible.
The file n_cst_filesrvaix.sru was branched from CJIAAAAA which is now corrupted and the early versions will be unaccessible.
The file pfc_n_cst_dwsrv_resize.sru was branched from CBIAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_adm_carrier.srd was branched from CAHAAAAA which is now corrupted and the early versions will be unaccessible.
The file dc_rpt_survey.srd was branched from CTHAAAAA which is now corrupted and the early versions will be unaccessible.
The file m_impact_find.srm was branched from COHAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_hrdcemployeronline_subject_coun was branched from CTGAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_surveyage_count.srd was branched from CNHAAAAA which is now corrupted and the early versions will be unaccessible.
The file m_tvs.srm was branched from COIAAAAA which is now corrupted and the early versions will be unaccessible.
The file w_filterextended.srw was branched from CLIAAAAA which is now corrupted and the early versions will be unaccessible.
The file dc_calltype_report_gol_email.srd was branched from CKHAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_callback_origin.srd was branched from CIHAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_dddw_countries.srd was branched from CEHAAAAA which is now corrupted and the early versions will be unaccessible.
The file n_cst_trregistration.sru was branched from CIIAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_dddw_lang_doc.srd was branched from CCHAAAAA which is now corrupted and the early versions will be unaccessible.
The file u_cbx.sru was branched from CPIAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_progorg_count_1.srd was branched from CFHAAAAA which is now corrupted and the early versions will be unaccessible.
The file n_tr.sru was branched from CNIAAAAA which is now corrupted and the early versions will be unaccessible.
The file pfc_u_plb.sru was branched from CEIAAAAA which is now corrupted and the early versions will be unaccessible.
The file pfc_u_tabpg_dwproperty_srvreqcolu was branched from CGIAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_document_qty_shipped.srd was branched from CSHAAAAA which is now corrupted and the early versions will be unaccessible.
The file d_program_count.srd was branched from CRHAAAAA which is now corrupted and the early versions will be unaccessible.
The file dc_cumulative1.srd was branched from CGHAAAAA which is now corrupted and the early versions will be unaccessible.
Checking parent/child relationships.
Removing unused items from the database.
Started analyzing user management system.
Successfully completed analyzing the user management system.
Validating the Security System.
File "f:\progra~1\micros~1\vss\data\c\cahaaaaa" not found
Analysis complete @ 2/17/04; 9:51a
        Potentially serious errors or inconsistencies were found.

As you stated when I do a "Show History..." the labels appear to be there but when I do a share, it creates the project folder but it's empty. I am getting really worried that we have lost all previous versions, I am in a bit of panick as to how to fix this. We have an emergency release to production and I can't extract the current production code.

How do I get in touch with MS-Support.

THANKS -Lorne

     
     ----- Joe Masters wrote: -----
     
     When you do a history command on the project, you see the label, right? If
     this is something that has worked for you in the past and your database is
     in good shape (running analyze.exe regularly), then you might want to
     contact Microsoft Product Support.
     
     Joe
     
     "Lorne" <anonymous@discussions.microsoft.com> wrote in message
     news:DCCC4226-DFC0-4165-80F7-6CE279CD9187@microsoft.com...
> I am having a problem when I try to share a label. Up until now, I have
     been sharing a label with out any problems, but now it seems that when I try
     to do a share on a label it appears to work, but nothing is returned to the
     project? It appears that my labels are lost? What could be causing this
     problem?
>> Any an all help are appreciated.
     
     
     

Relevant Pages

  • Re: DABsworth in disguise?
    ... time, as suffering from buffering. ... problematic IP address prefixes would account for the vast majority ... The BBC has the Quova Geo-location database at its disposal, ... yesterday about analyzing a few months' worth of log files wouldn't ...
    (alt.radio.digital)
  • Re: creating a label report in access
    ... It prints with the label in the 0 position. ... I hovered over the VBA page after running the report, ... Should I email you the whole access database? ... Please respond only to this newsgroup. ...
    (microsoft.public.access.reports)
  • Re: address labels joining up on database
    ... >John, Thanks for your help but I find it too difficult to do ... >>>address to 4 lines to ensure they fit to the label when I print them. ... >>>automatically transfer to a database, ... >>>23 The Home, Hall Ings ...
    (microsoft.public.access.externaldata)
  • Access 2007 Bug Persists
    ... I'm seeing the following problem in a database running under Access ... 2007 regardless of if it is Access 2003 format or converted to 2007 ... The backcolour of the label ... one of the other rectangles then exhibits the same behaviour. ...
    (comp.databases.ms-access)
  • Re: Mail Merge Not Picking All Up data
    ... last name on the label and that was no problem. ... See the article "Mailmerge Labels with Word XP" on fellow MVP Graham Mayor's ... responses come into an Excel database automatically.) ... On a second Excel database, I copy/pasted it to a Word table, then ...
    (microsoft.public.word.mailmerge.fields)