Redmine migrated > Error 500 Accessing Tickets

Added by dave uhlmann about 9 years ago

Hello

I made a migration of my existing Redmine-Environement to my Test-Platform. There is the following issue:

When I try to access the Tickets, I get the 500-Error. I also testet to create a new Project named "Test" and open the ticket (empty), this runs fine. But I can't access any Tickets of the migrated Projects.

Any ideas?

Attached my production.log

Thanks for your help.

production.log (4.58 KB)

Replies (3)

RE: Redmine migrated > Error 500 Accessing Tickets - Added by dave uhlmann about 9 years ago

Sorry, I forget to tell you my current Version:

Redmine 1.0.3.stable (MySQL)

RE: Redmine migrated > Error 500 Accessing Tickets - Added by dave uhlmann about 9 years ago

  • LOCAL GEMS ***

actionmailer (2.3.9)
actionpack (2.3.9)
activerecord (2.3.9)
activeresource (2.3.9)
activesupport (2.3.9)
after_commit (1.0.6)
bluecloth (2.0.7)
builder (2.1.2)
capistrano (2.5.18)
cgi_multipart_eof_fix (2.5.0)
cucumber (0.6.4)
daemons (1.0.10)
delayed_job (2.0.3)
diff-lcs (1.1.2)
echoe (4.3)
eventmachine (0.12.10)
fastthread (1.0.7)
gem_plugin (0.2.3)
gemcutter (0.5.0)
gruff (0.3.6)
highline (1.5.2)
hoe (2.3.3)
hpricot (0.8.2)
json (1.2.4)
json_pure (1.2.4)
memcache-client (1.8.2)
mini_magick (1.2.5)
mongrel (1.1.5)
mongrel_cluster (1.0.5)
mysql (2.8.1)
needle (1.3.0)
net-scp (1.0.2)
net-sftp (2.0.4)
net-ssh (2.0.21)
net-ssh-gateway (1.0.1)
nokogiri (1.4.1)
passenger (2.2.11)
polyglot (0.3.1)
rack (1.1.0, 1.0.1)
rack-test (0.5.4)
rails (2.3.9)
rails_analyzer_tools (1.4.0)
rake (0.8.7)
rcov (0.8.1.2.0)
RedCloth (4.2.3)
riddle (1.0.10)
rmagick (2.12.2)
rspec (1.3.0)
rspec-rails (1.3.0)
rubyforge (2.0.4)
sqlite3-ruby (1.2.5)
SyslogLogger (1.4.0)
term-ansicolor (1.0.4)
thin (1.2.7)
thinking-sphinx (1.3.16)
treetop (1.4.5)
webrat (0.7.0)
ZenTest (4.1.4)

RE: Redmine migrated > Error 500 Accessing Tickets - Added by Felix Schäfer about 9 years ago

My first thought would be that you have a newer redmine version than the database comes from and that you haven't run the proper migrations.

(1-3/3)