• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

*solved* MySQL Connector/ODBC 5.1 on Windows Plesk "system error 5"

F

firefoxchris

Guest
Hello all,

I encountered a problem after installing MySQL Connector/ODBC 5.1 on my Plesk 9.2 installation.

From ASP Scripts (and probably others run by the IIS user), I was receiving the following error when trying to connect to the database using the newer driver..

Specified driver could not be loaded due to system error 5 (MySQL ODBC 5.1 Driver)

After a bit of digging, I found that Error 5 is an "Access Denied" error, not to the database but to the driver DLL files. I installed Process Monitor, filtered to path containing "MySQL" and ran a script again.

I found entried for ACCESS DENIED to C:\Program Files (x86)\MySQL\Connector ODBC 5.1\myodbc5.dll. After including the colum for username, it appeared the script was running as the user iwam_plesk(default), however further investigation showed it was impersonating as the IUSR_PLESKSITEUSERNAME user.

I gave the Plesk group psacln read/execute access to the C:\Program Files (x86)\MySQL\Connector ODBC 5.1 folder and my site worked!

It took me ages to figure it our so thought it was worth posting to save time of anyone having a similar problem.

Hope this helps.
 
Thank you for this solution. If you don't mind, I could transfer it Workarounds topic? Much more people will see it there.
 
By all means, the more people that see it the better :).
 
Hi guys,
Just a comment to strengthen the forum.
This case happened to me now, because of a version update from 18.0.27 to 18.0.53.

The psacln group, was if, reading/executing the folder C:\Program Files\MySQL\Connector ODBC 5.3. after the correction everything returned to normal.

Thanks a lot.
 
Back
Top