Redmine

Hello everybody,

I have problem which I can not solve after an upgrade from Redmine 1.3.x to 2.2.2. I know this error has discussed in some previous posts but either it does not fit to my problem or I do not understand the provides solution. Maybe someone can help me ... But first an explanation what I have done:

My situation was:

Redmine 1.3.x installed on Win 2003 Server using the Bitnami Ruby Stack and the Redmine module. This installation used a local VisualSVN and MySQL which was included in the Bitnami Ruby Stack. Work quite good with linked revisions I could click on and repositories I could browser. Used the file protocol to access them (file:///<repo path>

My situation is:

Made a fresh install on a different Win 2003 using the new Ruby stack and Redmine module 2.2.2 from Bitnami. Then I used the instruction here to the upgrade: http://www.redmine.org/projects/redmine/wiki/RedmineUpgrade. I did NOT move the database to the new system. Instead I copied the database.yml and pointed the production environment to the old server. Also I did not move the SVN repositories but changed the setting for each project from file:/// to https://&lt;path to repo>.

Now everything works find except one issue: I get most of the time 404 when I try to access the repositories. I can NOT access the root (trunk branches tags) of any repository. Some linked revisions instead are working! Not all of them but some. Sometimes I can also get a diff but not the whole file. Also getting change sets using rake -v -f Rakefile RAILS_ENV=production redmine:fetch_changesets works - that means I see no errors in the production.log.

Now most of you think: O.K. this is a certificate problem. Might be but I knew about that because I made a mirror of the SNV some time ago using HTTPS. So I thought I could solve that and I found also some links in the Readmine wiki. According to that I changed subversion_adapter.rb like this:

 str << " --trust-server-cert --no-auth-cache --non-interactive --config-dir \"C:\Documents and Settings\All Users\Application Data\Subversion\"" 

and I accepted once the certificate of course using the svn command.

I also checked the svn command settings and set it to correct path. But still I get 404 errors! Why it works sometimes? Remember, I use an existing database where are already changes sets are stored. I guess old links to already stored revisions do work, but access to the root never works because here the repository is accessed.

All I find in the production log is a strange parser error which was posted some time ago:

No close tag for /lists/list

One will find a issue for that recommending to add 2>$1 at the and of the credentials_string. Tried that but did not change anything - and according to a comment in that issue it is also not necessary. So I say that here only to give a complete picture.

O.K. now any ideas what my problem is or what I can to to figure it our myself? Thanks for any hint or advice!

Peter