While I'd love to upgrade, it's more complicated than that in this environment. If anyone can point to a specific fix that will definitely solve this issue, I can make a case for a speedier process, but otherwise it may well be a month or more before I can get through all the hoops necessary.
On Thu, May 12, 2016 at 8:45 AM Pavel Lyalyakin < pavel.lyalya...@visualsvn.com> wrote: > Hello, > > On Wed, May 11, 2016 at 9:41 PM, Sasquatch N <webqa...@gmail.com> wrote: > >> >> I have a user who has tried twice in recent times to commit changes to a >> large (just under 40MB) file. Both times, the commit appears to have timed >> out. The only error message dispayed in the log is a pair of them: >> >> - Named transaction doesn't exist. [404, #175002] >> - Could not fetch resource information. [404, #0] >> >> After the command line returns to the $ prompt (unix system), the user >> checks the progress using svn status and it comes back as "M" (modified) >> status. >> >> The client is AIX running command line SVN version 1.8.5, and it's >> connected to a VisualSVN Server v3.4.3 on a Windows server. >> >> Any thoughts on what could be causing this and, more importantly, how to >> fix it? >> >> 40MB commit is not that large. Even much larger commits should complete > successfully. > > First of all, I'd check if any proxy server or firewall is causing this > behavior (e.g. check the logs of the firewall or proxy if there is any). > Next step would be to update your SVN client because SVN 1.8.5 is outdated. > Update it to 1.8.16 which is the latest maintenance patch update in 1.8.x > branch and try again. > > -- > With best regards, > Pavel Lyalyakin > VisualSVN Team > > On Wed, May 11, 2016 at 9:41 PM, Sasquatch N <webqa...@gmail.com> wrote: > >> I have a user who has tried twice in recent times to commit changes to a >> large (just under 40MB) file. Both times, the commit appears to have timed >> out. The only error message dispayed in the log is a pair of them: >> >> - >> - Named transaction doesn't exist. [404, #175002] >> - Could not fetch resource information. [404, #0] >> >> After the command line returns to the $ prompt (unix system), the user >> checks the progress using svn status and it comes back as "M" (modified) >> status. >> >> The client is AIX running command line SVN version 1.8.5, and it's >> connected to a VisualSVN Server v3.4.3 on a Windows server. >> >> Any thoughts on what could be causing this and, more importantly, how to >> fix it? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "VisualSVN" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to visualsvn+unsubscr...@googlegroups.com. >> To post to this group, send email to visualsvn@googlegroups.com. >> Visit this group at https://groups.google.com/group/visualsvn. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > With best regards, > Pavel Lyalyakin > VisualSVN Team > -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to visualsvn+unsubscr...@googlegroups.com. To post to this group, send email to visualsvn@googlegroups.com. Visit this group at https://groups.google.com/group/visualsvn. For more options, visit https://groups.google.com/d/optout.
