mersenneforum.org  

Go Back   mersenneforum.org > Great Internet Mersenne Prime Search > Software

Reply
 
Thread Tools
Old 2014-12-09, 01:27   #1
wombatman
I moo ablest echo power!
 
wombatman's Avatar
 
May 2013

173110 Posts
Default Setting up PRPNET for personal use

I'd like to use PRPNET to distribute numbers for primality checking automatically. MyDogBuster was kind enough to provide instructions, but I'm running into issues that we haven't been able to work out.

I got all of the PRPNet programs (server, client, etc). I downloaded MySQL version 5.6.21 (the latest official version). Had to use Custom to install the programs, but I installed 64-bit where I could and 32-bit where that was the only option. I made sure to get the ODBC connector (version 5.3.4). I was able to set up MySQL with no issue and confirm that the service was running using the MySQL Workbench. I was able to create the database and use the SQL script from the PRPNET sourceforge to create the appropriate tables and again confirm it was created using Workbench. I edited database.ini with the appropriate values. The problem comes when I try to run prpserver.exe with the following command:
Code:
prpserver.exe -d -lsr1025.abcd
I get the following error:
Code:
[2014-12-07 23:55:30 CST] 2: ODBC Connection via a driver: <Driver={MySQL ODBC 5.3 Driver};Server=localhost;Port=3306;Database=testdb;User=root;UID=root;Password=[removed];PWD=[removed];Option=3;>
[2014-12-07 23:55:30 CST] Connect to database failed: Specified driver could not be loaded due to system error  126: The specified module could not be found. (MySQL ODBC 5.3 Driver, C:\Windows\system32\myodbc5a.dall)., native code=160
Just in case there was some issue with the 64-bit version of MySQL, I uninstalled and reinstalled everything as 32-bit. The error persists.

Accordingly, I'd like to see if anybody can suggest a solution (or things to check to try and find a solution). Thanks!
wombatman is offline   Reply With Quote
Old 2014-12-09, 13:42   #2
rogue
 
rogue's Avatar
 
"Mark"
Apr 2003
Between here and the

5,953 Posts
Default

Quote:
Originally Posted by wombatman View Post
I'd like to use PRPNET to distribute numbers for primality checking automatically. MyDogBuster was kind enough to provide instructions, but I'm running into issues that we haven't been able to work out.

I got all of the PRPNet programs (server, client, etc). I downloaded MySQL version 5.6.21 (the latest official version). Had to use Custom to install the programs, but I installed 64-bit where I could and 32-bit where that was the only option. I made sure to get the ODBC connector (version 5.3.4). I was able to set up MySQL with no issue and confirm that the service was running using the MySQL Workbench. I was able to create the database and use the SQL script from the PRPNET sourceforge to create the appropriate tables and again confirm it was created using Workbench. I edited database.ini with the appropriate values. The problem comes when I try to run prpserver.exe with the following command:
Code:
prpserver.exe -d -lsr1025.abcd
I get the following error:
Code:
[2014-12-07 23:55:30 CST] 2: ODBC Connection via a driver: <Driver={MySQL ODBC 5.3 Driver};Server=localhost;Port=3306;Database=testdb;User=root;UID=root;Password=[removed];PWD=[removed];Option=3;>
[2014-12-07 23:55:30 CST] Connect to database failed: Specified driver could not be loaded due to system error  126: The specified module could not be found. (MySQL ODBC 5.3 Driver, C:\Windows\system32\myodbc5a.dall)., native code=160
Just in case there was some issue with the 64-bit version of MySQL, I uninstalled and reinstalled everything as 32-bit. The error persists.

Accordingly, I'd like to see if anybody can suggest a solution (or things to check to try and find a solution). Thanks!
prpserver.exe and the ODBC drivers must both be 64-bit or both be 32-bit. I suggest that you verify that. Also, use ODBC Administrator to verify that your connection information is correct. If you can connect via ODBC, then it is likely a 64-bit vs 32-bit issue. Note that the MySQL database 32-bit vs 64-bit doesn't matter. It is the ODBC driver that matters.
rogue is offline   Reply With Quote
Old 2014-12-09, 14:10   #3
wombatman
I moo ablest echo power!
 
wombatman's Avatar
 
May 2013

3×577 Posts
Default

Good to know. I've uninstalled everything again in preparation for another headlong charge at the wall after work tonight. I'll be back with any new information. Thanks!
wombatman is offline   Reply With Quote
Old 2014-12-11, 02:36   #4
wombatman
I moo ablest echo power!
 
wombatman's Avatar
 
May 2013

3×577 Posts
Default

Ok. Reinstalled everything (MySQL server, workbench, and ODBC connector--I think) as 64-bit, since that's what the prpserver.exe file is.

ODBC Data Source Administrator shows 3 ODBC drivers: "MySQL ODBC 5.3 ANSI driver" (Version 5.03.04.00), "MySQL ODBC 5.3 Driver" (No version--listed as "not marked"), and "MySQL ODBC 5.3 Unicode driver" (Version 5.03.04.00).

The database I made, testdb, also shows up as testdb with the file column showing "MySQL ODBC 5.3 driver"

When I try to run prpserver.exe, I get
Code:
[2014-12-10 20:34:26 CST] 2: ODBC Connection via a driver: <Driver={MySQL ODBC 5.3 Driver};Server=localhost;Port=3306;Database=testdb;User=root;UID=root;Password=[removed];PWD=[removed];Option=3;>
[2014-12-10 20:34:26 CST] Connect to database failed: Specified driver could not be loaded due to system error  126: The specified module could not be found. (MySQL ODBC 5.3 Driver, C:\Windows\system32\myodbc5a.dall)., native code=160
All of the port, server, database, and password information is correct in the database.ini file.

Thoughts? And if there's more information I need to provide, please don't hesitate to ask.
wombatman is offline   Reply With Quote
Old 2014-12-11, 04:30   #5
wombatman
I moo ablest echo power!
 
wombatman's Avatar
 
May 2013

3·577 Posts
Default

Oh, and this is being run in MinGW-w64, but I get the exact same error from the Windows-based command prompt as well.

If I change the driver line in database.ini to
Code:
driver=MySQL ODBC 5.3 UNICODE Driver
or
driver=MySQL ODBC 5.3 ANSI Driver
I get
Code:
[2014-12-10 22:32:48 CST] Connect to database failed: Specified driver could not be loaded 
due to system error  193:  (MySQL ODBC 5.3 ANSI Driver, C:\Program Files\MySQL\Connector ODBC 5.3\myodbc5a.dll)., native code=160
The system error changes from 126 to 193.

Last fiddled with by wombatman on 2014-12-11 at 04:36 Reason: More information
wombatman is offline   Reply With Quote
Old 2014-12-11, 12:44   #6
WraithX
 
WraithX's Avatar
 
Mar 2006

7308 Posts
Default

Quote:
Originally Posted by wombatman View Post
Oh, and this is being run in MinGW-w64, but I get the exact same error from the Windows-based command prompt as well.

If I change the driver line in database.ini to
Code:
driver=MySQL ODBC 5.3 UNICODE Driver
or
driver=MySQL ODBC 5.3 ANSI Driver
I get
Code:
[2014-12-10 22:32:48 CST] Connect to database failed: Specified driver could not be loaded 
due to system error  193:  (MySQL ODBC 5.3 ANSI Driver, C:\Program Files\MySQL\Connector ODBC 5.3\myodbc5a.dll)., native code=160
The system error changes from 126 to 193.
When I search online for "system error 193", it seems to relate to a 32-bit/64-bit issue. Do you have either of the following files?

c:\windows\syswow64\odbcad32.exe
c:\windows\system32\odbcad32.exe

If you do, try both to setup your environment to see if that helps.
WraithX is offline   Reply With Quote
Old 2014-12-11, 13:35   #7
wombatman
I moo ablest echo power!
 
wombatman's Avatar
 
May 2013

3·577 Posts
Default

I have both, and they show completely different drivers. The version in System32 shows the drivers I listed previously. The one in SysWOW64 shows none of the ODBC drivers I installed. Both versions of odbcad32.exe are 32-bit, however.
wombatman is offline   Reply With Quote
Old 2014-12-13, 05:03   #8
wombatman
I moo ablest echo power!
 
wombatman's Avatar
 
May 2013

3·577 Posts
Default

I also went ahead and checked that both of the ODBC connector dll files were 64 bit (they are). Those files are myodbc5w.dll and myodbc5s.dll.
wombatman is offline   Reply With Quote
Old 2014-12-14, 22:26   #9
wombatman
I moo ablest echo power!
 
wombatman's Avatar
 
May 2013

110110000112 Posts
Default

Using the ODBC Data Source Administrator, I can set up a data source (under System DSN and User DSN) and connect to the database (at least according to the "Connection Test") with the same information in the database.ini file.

Still get the following error when trying to use prpserver.exe:
Code:
Connect to database failed: Specified driver could not be loaded due to system error  193:  
(MySQL ODBC 5.3 UNICODE Driver, C:\Program Files\MySQL\Connector ODBC 5.3\myodbc5w.dll)., native code=160
I've also made sure that all the relevant files are 64-bit (prpserver.exe, all the ODBC dll files, the ODBC administrator, and the MySQL server software).

Has anybody set this up themselves recently?
wombatman is offline   Reply With Quote
Old 2014-12-14, 22:59   #10
rogue
 
rogue's Avatar
 
"Mark"
Apr 2003
Between here and the

5,953 Posts
Default

From what I read online it appears that you need the 32-bit ODBC driver.
rogue is offline   Reply With Quote
Old 2014-12-16, 04:49   #11
wombatman
I moo ablest echo power!
 
wombatman's Avatar
 
May 2013

33038 Posts
Default

I've learned the hard way that you have to be careful with what people suggest to solve these problems

One of the suggestions I had found (related to the redistributables, I believe) was to copy one of the mscvr100 dll files and replace it with a different one (msvcr100_clr0400, I think). Turns out that doesn't work. Figured that one out when msieve wouldn't start.

Once corrected, I get this:
Code:
[2014-12-15 22:46:21 CST] 2: successfully connected to a MySQL database
Needless to say, quite happy to be able to start playing around with everything!

Thank you again for your help.

Edit: To be clear, this with all 64-bit versions of prpserver.exe and ODBC Connector (and all the MySQL software).

Last fiddled with by wombatman on 2014-12-16 at 05:36
wombatman is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
PRPNet server for personal use johnadam74 Software 2 2016-01-01 15:58
My personal MEGA drive :) pepi37 Riesel Prime Search 5 2014-02-05 21:39
Personal info on the forum LaurV Forum Feedback 3 2013-09-04 06:50
Setting up PRPnet Mattyp101 Conjectures 'R Us 2 2011-02-07 13:53
Personal Supercomputer? georgekh Hardware 39 2004-11-07 00:55

All times are UTC. The time now is 18:14.

Wed Oct 28 18:14:41 UTC 2020 up 48 days, 15:25, 2 users, load averages: 3.27, 2.84, 2.52

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.