Issues pushing to sandbox repository - hg push either stalls or displays 404 Error Message

Mcadams, Philip W philip.w.mcadams at
Tue Jun 11 15:51:11 CDT 2013


I'm writing regarding issues my team has encountered cloning repos from sandbox to production.  Two weeks after our server migration I received a JIRA ticket that the user was receiving "abort: HTTP Error 404: Not Found" when attempting to synchronize repos.  Another user received abort: error: An existing connection was forcibly closed by the remote host.

Followed advice I'd found online and I increased the IIS 7.5 connection timeout to 2 hours, and upped the parameters
For the Request Filtering Settings in IIS as well to what shown below:

[cid:image001.png at 01CE66AA.BA9937C0]

The user that initially complained of the "abort: HTTP Error 404: Not Found" error appeared to have his issue resolved.  I was able to reproduce his error as well and I don't get it anymore.  I did screen share session with the developer and he was able to clone prod repo to local pc, create sandbox repo and synchronize local pc repo with sandbox repo fine: it took while as the repo is large.  Prior to pushing out to our team that it's fixed I decided to try it myself.  Although I don't get the "abort: HTTP Error 404: Not Found" but my pushes just stall/hang.  I've tried pushing via cmd and with Tortoisehg and they hang at different spots.  Could this be a network issue?  A coworker informed that I need to clear the Mercurial cache.  Does Mercurial have a cache that can be cleared.

Thank you.

Philip McAdams
Systems Administrator - NVM Solutions Group Systems Engineering Apps & Infrastructure
Desk: (916) 377-6156 Cell: (916) 534-0092 Pole: FM3-1-D7

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8608 bytes
Desc: image001.png
URL: <>

More information about the Mercurial-devel mailing list