MSDN > Home page del forum > Visual Studio Source Control and SourceSafe > Network Not Found error when Checking In
Formula una domandaFormula una domanda
 

Con rispostaNetwork Not Found error when Checking In

  • mercoledì 27 giugno 2007 18.06PReardon Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    I believe I'm running VSS 2005 (I didn't install it, help/about says Version 8.0.50727.42).

     

    When I go to check something in, after about a 10 second delay, I get a message box that states "Network Not Found".  When I click "ok", the item checks in, and the changes are saved in VSS. I'm the only one having this problem, and it just started last week. Someone in my office ran some utilities and fixed a few issues (don't know the details), but my problem still persists. I am able to ping the server no problem, and I can view the files and folders for VSS on the server in windows explorer.

     

    Thanks,

     

    Paul

Risposte

  • martedì 17 luglio 2007 12.06PReardon Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     Con risposta

    Here's what we found:

     

    The ss.ini file looked like this:

     

    Shadow =

     

    [TimeZone]
    Name = (GMT-05:00) Eastern Time (US & Canada)
    TZ_Bias = 300
    TZ_DaylightBias = -60
    TZ_DaylightDate = 0000/03/02 02:00:00.000
    TZ_StandardBias = 0
    TZ_StandardDate = 0000/11/01 02:00:00.000
    TZ_UseDaylightSavingTime = Yes

     

    [$/]
    Shadow = \\Pxxxxx-dc02\VSS_Shadow

     

     

    We removed the first reference of Shadow =, and it solved our problem.

Tutte le risposte

  • giovedì 28 giugno 2007 20.04Richard BergModeratoreMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     
    My guess is you hit a network glitch of some sort.  Does this happen every time?  Can you reproduce it on other machines?
  • giovedì 28 giugno 2007 20.23PReardon Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    It happens every time I check in while using VSS, and I'm the only one in our company that it happens to. It takes about 10-20 seconds, and then the message comes up for each item that I'm checking in (quickly after the first one). The changes do get saved into VSS, so it's not a show stopper, but definitely an issue.

     

    If I check in from VB 6, it takes about the same amount of time, then completes, but I don't get the message. It's definitely slower than it was before I was having this problem. It is possible I'm getting the error here too, but it's not prompting me for a resonse, and maybe disappears too fast for me to see it.

     

  • martedì 17 luglio 2007 3.30Matt Fitzmaurice Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    This is happening to all 10 developers on my network.

    Any ideas how to resolve it?

     

    We don't have the 10-20 second delay. It's pretty quick.

     

    Thanks

  • martedì 17 luglio 2007 12.06PReardon Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     Con risposta

    Here's what we found:

     

    The ss.ini file looked like this:

     

    Shadow =

     

    [TimeZone]
    Name = (GMT-05:00) Eastern Time (US & Canada)
    TZ_Bias = 300
    TZ_DaylightBias = -60
    TZ_DaylightDate = 0000/03/02 02:00:00.000
    TZ_StandardBias = 0
    TZ_StandardDate = 0000/11/01 02:00:00.000
    TZ_UseDaylightSavingTime = Yes

     

    [$/]
    Shadow = \\Pxxxxx-dc02\VSS_Shadow

     

     

    We removed the first reference of Shadow =, and it solved our problem.

  • martedì 17 luglio 2007 17.23Richard BergModeratoreMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     
    Thanks for following up PReardon!
  • martedì 24 febbraio 2009 19.15GeneInDesert Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     
    I didn't see a 'reply' that directly related to my situation, so here's mine 2 years after the original post ...

    In my case, the srcsafe.ini file that I was pointing to had a reference to a server that was no longer available.  This reference was of the form

    Journal_File = <server>\<path>\VSS\VSSlogs\userlogs

    Since it was just a journal file, VSS was able to go ahead with desired activities even though it showed "Network not found" every time.

  • domenica 28 giugno 2009 15.29Satya C Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     
    I got the same issue after moving VSS to a different system and correcting the Journal_File as mentioned above has resolved the issue.    Thank you for posting the solution.  - Satya
  • lunedì 29 giugno 2009 8.50Catherine Sea Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    Thanks for sharing the solution.

    Catherine Sea
    http://www.scmsoftwareconfigurationmanagement.com