l0gic Posted May 26, 2007 Share Posted May 26, 2007 Hi all, I took Matt's advice to fix a previous problem and upgraded my Plesk machine to run Plesk 8.1 for Windows. (From Plesk 7.5.6) Everything was running smooth for a while, and then suddenly ioncube broke. I may have rebooted IIS or I may not have, I don't remember what I did when the error occurred. All I know is now I get this error: Site error: the file c:\Inetpub\vhosts\infinitynetworks.ca\httpdocs\clients\includes\functions.php requires the ionCube PHP Loader ioncube_loader_win_4.4.dll to be installed by the site administrator. This happens for any of the php pages I try to load. (This is just an example because I'm pulling the announcements on my index.php so it talks to functions.php) Like I said, I don't know what I did, but I could've sworn I didn't touch anything that would break ioncube. My php.ini in C:\Windows (which phpinfo() reports as the right .ini file) has the following line at the end: zend_extension_ts="c:\inetpub\vhosts\infinitynetworks.ca\httpdocs\ioncube\ioncube_loader_win_4.4.dll" And I've played with that, too. I've got ioncube in 3 different places for testing and I've pointed it at all 3. It doesn't make a difference. If I run the ioncube-loader-helper script, it tells me what to change because it claims ioncube isn't working... but it's telling me to do what's already been done.... add that line to php.ini Even though php.ini shows that line, phpinfo() does NOT show ioncube in the additional modules list, which it USED to do before I upgraded to Plesk 8.1. Has anyone else seen ioncube break after performing a seemingly clean upgrade? Cheers, Lee ------------------------------------------------------------------------- Edit: Okay, I solved this problem. For those of you running Windows 2003 and IIS, and perhaps Plesk (especially if you upgrade to the latest plesk). IIS is VERY PARTICULAR it seems about the location of dll files for things like php extensions, etc. I had to move the ioncube loader files to c:\windows\system32\inetsrv\ and then point the php.ini file to there. After that it worked like a charm. So there you have it, persistence pays off! Thanks again for those of you who helped me in the past, and thanks Matt for such an awesome piece of software. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.