Upgrade Problems
Added by Rohan Alexander about 12 years ago
Hi,
I am attempting to upgrade Redmine from v1.0 to version 2.1.0 on a Windows 2003 server.
I have installed Ruby v1.9.3 and done the bundle install with no problems.
I have followed all the upgrade instructions without any issue until I get to the step that requires me to run the following command : rake generate_secret_token
When I do this I get the following error.
rake aborted!
cannot load such file -- D:/config/environment
The trace returns the following :
D:\redmine-2.1.0>rake generate_secret_token --trace
rake aborted!
cannot load such file -- D:/config/environment
D:/redmine-2.1.0/plugins/redmine_reminder/lib/tasks/reminder_all.rake:29:in `require'
D:/redmine-2.1.0/plugins/redmine_reminder/lib/tasks/reminder_all.rake:29:in `<top (required)>'
D:/redmine-2.1.0/lib/tasks/redmine.rake:121:in `load'
D:/redmine-2.1.0/lib/tasks/redmine.rake:121:in `block in <top (required)>'
D:/redmine-2.1.0/lib/tasks/redmine.rake:121:in `each'
D:/redmine-2.1.0/lib/tasks/redmine.rake:121:in `<top (required)>'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/railties-3.2.8/lib/rails/engine.rb:425:in `load'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/railties-3.2.8/lib/rails/engine.rb:425:in `block in load_tasks'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/railties-3.2.8/lib/rails/engine.rb:425:in `each'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/railties-3.2.8/lib/rails/engine.rb:425:in `load_tasks'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/railties-3.2.8/lib/rails/application.rb:145:in `load_tasks'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/railties-3.2.8/lib/rails/railtie/configurable.rb:30:in `method_missing'
D:/redmine-2.1.0/Rakefile:7:in `<top (required)>'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/rake_module.rb:25:in `load'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/rake_module.rb:25:in `load_rakefile'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:501:in `raw_load_rakefile'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:82:in `block in load_rakefile'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:81:in `load_rakefile'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:65:in `block in run'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:63:in `run'
d:/Ruby193/lib/ruby/gems/1.9.1/gems/rake-0.9.2.2/bin/rake:33:in `<top (required)>'
d:/Ruby193/bin/rake:23:in `load'
d:/Ruby193/bin/rake:23:in `<main>'
I have the following gems installed :
D:\>gem list
- LOCAL GEMS ***
actionmailer (3.2.8)
actionpack (3.2.8)
activemodel (3.2.8)
activerecord (3.2.8)
activeresource (3.2.8)
activesupport (3.2.8)
arel (3.0.2)
bigdecimal (1.1.0)
builder (3.1.3, 3.0.3, 3.0.0)
bundler (1.2.1)
coderay (1.0.7)
erubis (2.7.0)
hike (1.2.1)
i18n (0.6.1)
io-console (0.3)
journey (1.0.4)
jquery-rails (2.0.3)
json (1.7.5)
mail (2.4.4)
metaclass (0.0.1)
mime-types (1.19)
minitest (3.5.0, 2.5.1)
mocha (0.12.4)
multi_json (1.3.6)
mysql2 (0.3.11 x86-mingw32)
net-ldap (0.3.1)
pg (0.14.1 x86-mingw32)
polyglot (0.3.3)
rack (1.4.1)
rack-cache (1.2)
rack-openid (1.3.1)
rack-ssl (1.3.2)
rack-test (0.6.1)
rails (3.2.8)
railties (3.2.8)
rake (0.9.2.2)
rdoc (3.12, 3.9.4)
ruby-openid (2.1.8)
sprockets (2.6.0, 2.1.3)
sqlite3 (1.3.6 x86-mingw32)
thor (0.16.0)
tilt (1.3.3)
treetop (1.4.10)
tzinfo (0.3.33)
I am lost and have no idea how to proceed. I assume there may be some path issue as I do not have D:\config\enviroment directory on my server.
Hope you can help.
Thanks
Rohan
Replies (3)
RE: Upgrade Problems - Added by Jean-Philippe Lang about 12 years ago
This problem seems to be due to the redmine_reminder plugin. Please try without plugins first.
RE: Upgrade Problems - Added by Rohan Alexander about 12 years ago
Thanks but how do I do that?
How do I try without the plugins?
Thanks
RE: Upgrade Problems - Added by Etienne Massip about 12 years ago
Move them out from the plugins directory and restart the instance, that should be enough.