also posted this message here (http://rubyforge.org/forum/forum.php?
thread_id=49785&forum_id=9503), but afterwards I found this group and
think it is more suitable to ask that question in this group!
I am using Windows Server 2008 R2 and try to get RoR to work for the
last three days. Basically I did the following
Installed Ruby 1.9.2 with Ruby installer
Installed gem
Installed rails 3.0.7
installed DB2 with gem install ibm_db
When I enetered irb and executed the command “require ‘ibm_db’” as
suggested here http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.apdv.ruby.doc/doc/t0052765.html
I got an error, that the DB2CLI.dll is missing, so I did some internet
research and found out here that the installation of “IBM Data Server
Driver for ODBC and CLI (Windows/x86-64 64 bit) V9.7 Fix Pack 4” is
necessary. So I installed it but the error message still appeared, so
I manually copied “C:\db2_cli_odbc_driver\clidriver\bin” to “C:
\Ruby192\bin”
When I executed the command “require ‘ibm_db’” again, the following
error message appeared:
irb(main):001:0> require ‘ibm_db’
LoadError: 14001: The application has failed to start because its side-
by-side configuration is incorrect. Please see the application event
log or use the comma
nd-line sxstrace.exe tool for more detail. - C:/Ruby192/lib/ruby/gems/
1.9.1/gems/ibm_db-2.5.6-x86-mingw32/lib/mswin32/rb19x/ibm_db.so
from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:
59:in require' from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb: 59:in rescue in require’
from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:
35:in require' from C:/Ruby192/lib/ruby/gems/1.9.1/gems/ibm_db-2.5.6-x86-mingw32/lib/ mswin32/ibm_db.rb:1:in <top (required)>’
from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:
36:in require' from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb: 36:in require’
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/ibm_db-2.5.6-x86-mingw32/lib/
IBM_DB.rb:1:in <top (required)>' from <internal:lib/rubygems/custom_require>:33:in require’
from internal:lib/rubygems/custom_require:33:in rescue in require' from <internal:lib/rubygems/custom_require>:29:in require’
from (irb):1
from C:/Ruby192/bin/irb:12:in `’
irb(main):002:0>
I also installed VC_redist 2005 and 2010.
I hope that anybody can help me with that problem.
Yeah I have tried that several times, the problem resists. I also
installed the 32 bit version of DB2CLI.DLL in the meanwhile but this
also didn’t do the trick!
does the file C:\Ruby192\bin\DB2CLI.dll exist and registered properly?
btw, why are you using
“require ‘ibm_db’” instead of “require ‘mswin32/ibm_db’” ?
tom
On May 15, 2011, at 11:22 , Wolfgang wrote:
could not be found. Please use sxstrace.exe for detailed diagnosis.
what about running sxstrace.exe from console and paste the output?
does this file exist?
C:/Ruby192/lib/ruby/gems/1.9.1/gems/ibm_db-2.5.6-x86-mingw32/lib/mswin32/rb19x/ibm_db.so
tom
On May 15, 2011, at 10:24 , Wolfgang wrote:
installed DB2 with gem install ibm_db
When I executed the command “require ‘ibm_db’” again, the following
from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:
IBM_DB.rb:1:in `<top (required)>’
–
You received this message because you are subscribed to the Google G.
“Ruby on Rails: Talk” group.> To post to this group, send email [email protected].> To unsubscribe from this group, send email [email protected].
For more options, visit this group
athttp://groups.google.com/group/rubyonrails-talk?hl=en.
Activation context generation failed for “C:\Ruby192\bin\DB2CLI.dll”.
Dependent Assembly
IBM.DB2.CLI,language="*",processorArchitecture=“x86”,type=“win32”,version=“9.1.0.000”
could not be found. Please use sxstrace.exe for detailed diagnosis.
sxstrace.exe requires an .etl file wich seems to be not produced by
ruby!
Its not possible for me to execute the command because after I press
enter the error “The module ‘db2cli.dll’ was loaded but the entry-
point DllRegisterServer was not found. Make sure that ‘db2cli.dll’ is
a valid DLL or OCX file and then try again.”