Plugin migration with Microsoft SQL Server throws error
|Resolution:||Cant reproduce||Affected version:|
we're currently on the way to install redmine on an IIS with Microsoft SQL Server.
The normal Installation worked, even the db connection to our SQL Server.
But we Encounter some strange behaviour if we try to migrate plugins.
The normal migration worked, but the plugin migration reclaims the missing database Adapter. But it's the same configuration as with the normal db:migrate command.
The same error occures even if the plugin directory is empty (so no plugins will be migrated).
Can you confirm this behaviour? If this bug is confirmed, it should be fixed bevor redmine 2.3 will be released.
Set RAILS_ENV=production rake redmine:plugins:migrate --trace ** Invoke redmine:plugins:migrate (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! database configuration does not specify Adapter <pre>
#5 Updated by Daniel Felix over 7 years ago
This is our configuration (pw and username changed).
production: # adapter: sqlite3 # database: db/test.sqlite3 # host: localhost # username: root # password: # encoding: utf8 adapter: sqlserver database: redmine host: localhost port: 11433 username: OurUsername password: OurPassword development: adapter: sqlserver database: redmine_development host: localhost port: 11433 username: OurUsername password: OurPassword
The port is changed in our server. So this is no misstyping.
#8 Updated by Daniel Felix about 7 years ago
- Status changed from New to Closed
- Resolution set to Cant reproduce
This issue has been resolved. I can't point it to something special.
I used the latest trunk after implementations of the gemfile parser and the sql server support.
This was the point, where everything broke together regarding plugin migrations.
The next step was the migration to 2.3 and later 2.3.1. Both failed on plugin migrations.
I currently use the trunk version of Redmine and tada... everything works. I can't break it down to a special change which could describe why this work right now.
I'm closing this issue. Thanks for your support.
#9 Updated by Jeff Pierson about 7 years ago
Will these changes from the trunk that Daniel Felix mentioned be included in 2.3.2 or is that already branched prior to the changes? If there is a wiki or something similar that specifies the branching policy used by Redmine with regard to releases that may also answer the question for me and perhaps allow me to assist in pinpointing the revision in which this issue was fixed.
#10 Updated by Daniel Felix about 7 years ago
As I mentioned, these changes must happened between trunk (pre 2.3.0) and trunk (pre 2.3.2) (not sure which revisions where loaded by our administration).
The other thing were many changes to the server and ruby interpreter itself.
Maybe these changes where already included in 2.3.0. I haven't tested 2.3.0 on SQL Server.