Announcement

Collapse
No announcement yet.

Timing out (Tortoise SVN)

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Timing out (Tortoise SVN)

    I am trying to carry out an update to some files on a network share, but it keeps freezing while sending content.

    Sorry if this is the wrong section.
    Attached Files
    Last edited by GilderJack; 12-06-2016, 10:19 AM.

  • #2
    What type of URL/connectivity are you using? HTTP/S ? SSH?

    Please verify that a "checkout/update" works properly?

    Is there a firewall between you and the server?

    Comment


    • #3
      [QUOTE=DougR;n79620]What type of URL/connectivity are you using? HTTP/S ? SSH?

      Please verify that a "checkout/update" works properly?

      Is there a firewall between you and the server?[/QUOTE]



      Sorry i'm not 100% sure what you mean, the folders are on a network share.

      The update feature doesn't work and is blocked by our firewall.

      Nope the servers are all locally in house.

      Comment


      • #4
        What is the repository URL that you are using? Does it look anything like "https://hostname/svn/repoName" ? Or does it begin "file:" or?

        Comment


        • #5
          [QUOTE=DougR;n79622]What is the repository URL that you are using? Does it look anything like "https://hostname/svn/repoName" ? Or does it begin "file:" or?[/QUOTE]

          [URL]https://SERVERNAME/svn/Models/trunk/01[/URL] Internal Model/C
          Last edited by DougR; 12-06-2016, 04:19 PM.

          Comment


          • #6
            Ok, so that's communicating via HTTP/S (not via a local file system - e.g. file:UNC).

            And that gets me back to my questions before. Even if all servers are locally in house sometimes they end up running firewalls (not always configured properly either). However, if you can still update the working copy then it's unlikely a firewall.

            Best idea at the moment would be for you to contact whoever is in charge of the server at "SERVERNAME" and ask them to look in their log files for errors, misconfigurations, etc.

            Comment


            • #7
              [QUOTE=DougR;n79625]Ok, so that's communicating via HTTP/S (not via a local file system - e.g. file:UNC).

              And that gets me back to my questions before. Even if all servers are locally in house sometimes they end up running firewalls (not always configured properly either). However, if you can still update the working copy then it's unlikely a firewall.

              Best idea at the moment would be for you to contact whoever is in charge of the server at "SERVERNAME" and ask them to look in their log files for errors, misconfigurations, etc.[/QUOTE]


              Turns out the server was stuck in a "limbo" state, bounced the server and it's working!

              Comment


              • #8
                Excellent!

                Comment


                • #9
                  Great !!!

                  Comment

                  Working...
                  X