# Error: procedure entry point not found **URL:** \ **Category:** Rails\ **Created:** [March 27, 2007, 5:35pm UTC](https://www.ruby-forum.com/t/error-procedure-entry-point-not-found/90308 "2007-03-27T17:35:51Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![wmerydith](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/ccd318/32.png) [@wmerydith](https://www.ruby-forum.com/u/wmerydith)\ **Post date:** [March 27, 2007, 5:35pm UTC](https://www.ruby-forum.com/t/error-procedure-entry-point-not-found/90308/1 "2007-03-27T17:35:51Z")
Running Instant Rails - latest version. When I run rake db:migrate, I get the error (in a pop up window): The procedure entry point mysql\_stmt\_row\_tell could not be located in the dynamic link library LIBMYSQL.dll. After clicking ok several times the migration runs. My site also runs locally. What’s this error all about? Thanks. ---
**Author:** ![wmerydith](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/ccd318/32.png) [@wmerydith](https://www.ruby-forum.com/u/wmerydith)\ **Post date:** [March 27, 2007, 9:10pm UTC](https://www.ruby-forum.com/t/error-procedure-entry-point-not-found/90308/2 "2007-03-27T21:10:20Z")
I realized the problem started happening after I install the mysql gem, based on advice from ‘Agile Web D. With Rails’ page 292. So I uninstalled that gem and the error went away. The reason I installed it is because DHH recommended it to increase performance. ---
**Author:** ![wmerydith](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/ccd318/32.png) [@wmerydith](https://www.ruby-forum.com/u/wmerydith)\ **Post date:** [March 28, 2007, 11:30pm UTC](https://www.ruby-forum.com/t/error-procedure-entry-point-not-found/90308/3 "2007-03-28T23:30:40Z")
On 3/27/07, Will M. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > I realized the problem started happening after I install the mysql gem, > based on advice from ‘Agile Web D. With Rails’ page 292. So I > uninstalled that gem and the error went away. > > The reason I installed it is because DHH recommended it to increase > performance. Actually, you don’t need to install it as it is already included in Instant Rails. Curt ---
**Author:** ![wmerydith](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/ccd318/32.png) [@wmerydith](https://www.ruby-forum.com/u/wmerydith)\ **Post date:** [March 28, 2008, 11:21pm UTC](https://www.ruby-forum.com/t/error-procedure-entry-point-not-found/90308/4 "2008-03-28T23:21:41Z")
I received the same error message. After copying libmysql.dll (from my MySQL installation) to my ruby/bin folder, the error went away. I’m not sure if there are any potentially negative consequences of copying the file, but everything seems to be working for now. Will M. wrote: > Running Instant Rails - latest version. > > When I run rake db:migrate, I get the error (in a pop up window): > > The procedure entry point mysql\_stmt\_row\_tell could not be located in > the dynamic link library LIBMYSQL.dll. > > After clicking ok several times the migration runs. My site also runs > locally. > > What’s this error all about? > > Thanks. ---
**Author:** ![wmerydith](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/ccd318/32.png) [@wmerydith](https://www.ruby-forum.com/u/wmerydith)\ **Post date:** [November 29, 2010, 7:08am UTC](https://www.ruby-forum.com/t/error-procedure-entry-point-not-found/90308/5 "2010-11-29T07:08:35Z")
this works as mentioned above: copy libmysql.dll (from my MySQL installation) to my ruby/bin folder ---
**Author:** ![wmerydith](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/ccd318/32.png) [@wmerydith](https://www.ruby-forum.com/u/wmerydith)\ **Post date:** [September 6, 2008, 7:45am UTC](https://www.ruby-forum.com/t/error-procedure-entry-point-not-found/90308/6 "2008-09-06T07:45:23Z")
Samuel Johnson wrote: > I received the same error message. After copying libmysql.dll (from my > MySQL installation) to my ruby/bin folder, the error went away. I’m not > sure if there are any potentially negative consequences of copying the > file, but everything seems to be working for now. It really does resolve the problem. Thanks.