Fatal error: main() Failed opening required '' in tpl_index_default.php

You'd put in the database name, and your database user name and database password that you've set up for the database when you created it.

Well, after a series of guesses I managed to work out the correct combination of usernames/passwords.

Only to discover my new host has mysql5 which is not supported with 1.25 of Zen :(

It is 1am now and all these things have me beaten. I have not even begun to look at the upgrade procedure from 1.25 to the current latest version yet, but im sure it is daunting.

Is anyone here willing to take care of the upgrade procedure in exchange for payment?

I have been through the exact same process.. Moved my site, only to find they have MySQL 5 too. I went through the upgrade procedure and eventually got it to 1.3.5. It was a little daunting, but it can be done (I was upgrading from 1.2.5), check out http://www.t3tuning.co.uk/shopnew/..

We are currently experiencing this exact same issue across 12 servers of over 100 servers. Only zencart and related sites affected, no changes to servers applied to cause such an issue. We are running php 4.4.4, mysql 4.1.x and latest zend optimizer.

We are currently unable to identify the source of this issue or correct it on a permanent basis - moving sites to a new server does temporarily correct the issue. We are currently auditing inbound requests to zendcart installations for possible attacks of somekind but are not coming up with anything suspect.

Fatal error: main() [function.require]: Failed opening required '' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/omni/public_html/store/includes/templates/template_default/templates/tpl_index_default.php on line 39

Same error across sites with issue, no php safe mode enabled, lifted open_basedir restrictions with no difference and permissions are all intact as intended, php NOT running in CGI mode but rather as compiled apache moduls - fresh php compiles make no difference either.

Paths exist and files as intended, but seemingly the error persists no matter how we attempt to resolve the matter.

Any assistance would be greatly appreciated.