Moved previous install to new server, EPC has mysql issues?

[willow]

Moved a fully working install from one server to a new server. Old server used php 5.2, new one uses 5.3, so i went from Zend to ioncube.

EPC 6.4.2 ioncube version will load up the setup manager, but if it's told to use the mysql server, it just fails to load properly. Only the banner displays (see attachment).

If you try using the event manager or display an event, it gives a 500.

Blew it all away, tried setting up EPC from scratch. As soon as it tries using the new mysql database.. it dies again, as before.

Every other piece of software I have is working fine after having been moved. Users have the right permissions.

What's changed?

[Brian]

What version of the calendar was on the old server before the move?

Are both versions of mySQL the same on both servers?

Can you use a flat-file database on the new server (as a test)?

If the script stops when connecting to mySQL, usually it's a server or configuration error. The calendar just uses basic PHP and mySQL connection code.

[willow]

6.4.2 prior

mySQL: 5.1.62 on the new box, 5.1.51 on the old.

Flatfile works fine.

The simplicity of this situation is what boggles my mind, and I've double checked the account settings and stuff because that was my first though. No logged mysql errors or anything.

Other software that uses the database/account works just fine. The only thing which broke when I moved the drive from one box to the next, was EPC.

I attached a copy of the html output when I'm in the database portion of the setup, to show you where it dies once I tell it to read the database.

[Brian]

Did you update the paths (see Paths FAQ below).?

[willow]

Yeah, and I just verified the paths in calendar.php in both the new from scratch build and the old one. In fact, the new one said 'updating paths' or whatnot during install.

[willow]

I just did it all again a 3rd time to make sure I wasn't missing something. Followed the manual instructions to the tee.

Unpacked the file, set the permissions, it set the server paths, it found the new license, it puts me into the setup manager. Everything checks out good.

I go to database, provide the database connect info, tell it to use it, and click save. It dies. At no point does it even suggest running setupSQL.php

I tried manually running setupSQL.php, it gives an Invalid Access - 6 code, which is new.

The database connect info is correct. User has the following permissions:

Select | Insert | Update | Delete | Create | Drop | Index | Alter | Create temp

Am I missing anything? What's with the invalid access code?

[Brian]

Can you change and save anything else in the settings?

You can see the database variables in the config file. Here is the code the calendar uses to connect (you may want to test this in a separate file).

$db = mysql_connect($sqlHost, $sqlUserLogin, $sqlPassword);
mysql_select_db($sqlName, $db);

[willow]

Yeah, everything else works.

Consider this issue solved, however.

Found out that one of the mysql-use flags wasn't enabled for EPC, but it was enabled for everything else.

So for anyone else with this exact issue, check your use flags on php 5.3x.

Thanks for the quick support Brian.