id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,branch,changelog,apichanges,internalchanges 10636,Able to add changeset -- Unable to browse repository,aaron.laws@…,,"I recently moved my Trac installation to a new server and I'm seeing some very strange behaviour. My setup: * Windows Server 2008 R2 Datacenter SP 1 * Trac 0.12.3 * Svn server running 1.7.4 * Python 2.7 * Python bindings from Alagazam.net I have tested the python bindings using instructions I found on TracSubversion : `>>> from svn import core` `>>> (core.SVN_VER_MAJOR, core.SVN_VER_MINOR, core.SVN_VER_MICRO, core.SVN_VER_PATCH)` `>>> (1, 7, 4, 4)` As expected. I'm able to add the repository and `trac-admin . repository resync` it with no errors. I can also `changeset add` and `changeset modified` with success. Some excerpts from the log file are http://pastie.org/3641941. I'm unable to browse the repository (the ""Browse Source"" link doesn't appear). I'm using the CommitTicketReferenceMacro plugin, and when I visit a ticket that has a referenced revision (using CommitTicketUpdater), the page says Unsupported version control system ""svn"": DLL load failed: The specified module could not be found. At this point, I cannot see the ticket contents. I get an updating e-mail showing me that the comment from the svn commit was recorded, and the ticket got an appropriate comment from CommitTicketUpdater. I've had problems with the bindings before on a different server, so I feel quite familiar with the requirements and the Trac documentation on the subject, and I can't think of anything more to do to diagnose or alleviate these issues. The issues are also confusing in that Trac seems to be doing alright with subversion up to a point.",defect,closed,normal,,version control,0.12.3,normal,cantfix,python svn repository source,,,,,