'Not A Valid Entry Point' after 4.2.1 upgrade

[vri]

I applied the 4.2.0-to-4.2.1-7017 upgrade; when I try to login to Suger, I get a message 'Not A Valid Entry Point'.

I tried to follow the suggestions given in the 'Not A Valid Entry Point' thread initiated by beedsley, but this does not seem to apply, as none of the php files has the wrong code.

My httpd error log does state two errors from the time when I ran the upgrade:
PHP Notice: Undefined index: js_custom_version in sugarpath/XTemplate/xtpl.php on line 100
PHP Notice: Undefined variable: currentModuleFile in sugarpath/index.php on line 414.

My stack:
Linux 2.6.16-1.2069_FC4smp
sugarCRM 4.2.1 (now; was 4.2.0)
Apache/2.0.54 (Fedora)
php 5.0.4
MySQL 4.1.16


?? Thank you for assistance.

Theo.

[cywolf]

It seems like your index.php file may be out of date. I suppose you could try copying over the latest version from the patch file, but other files may have also been missed (unless you avoided upgrading that one on purpose). If you performed a backup then I would try going back to it and running the upgrade again.

[vri]

Thank you, Andrew, for your suggestion.

I checked, but all files have been upgraded, also index.php. So something else must be wrong.
Meanwhile, I learned that I should have checked the log file.
It shows that the post_install was unsuccessful:

Tue Jul 11 12:37:35 2006,346 [32710] FATAL SugarCRM - Entered post_install function.
Tue Jul 11 12:37:35 2006,359 [32710] FATAL SugarCRM - Upgrading the database to version 4.2.1
Tue Jul 11 12:37:35 2006,359 [32710] FATAL SugarCRM - Running SQL file 420_to_421_mysql.sql
Tue Jul 11 12:37:35 2006,360 [32710] FATAL SugarCRM - Sending query: --
Tue Jul 11 12:37:35 2006,346 [32710] FATAL SugarCRM - Entered post_install function.
Tue Jul 11 12:37:35 2006,359 [32710] FATAL SugarCRM - Upgrading the database to version 4.2.1
Tue Jul 11 12:37:35 2006,359 [32710] FATAL SugarCRM - Running SQL file 420_to_421_mysql.sql
Tue Jul 11 12:37:35 2006,360 [32710] FATAL SugarCRM - Sending query: --

After that, the file lists that all table alterations in the db have failed:

-- accounts
ALTER TABLE `accounts` CHANGE COLUMN `description` `description` longtext NULL ;<br>
Tue Jul 11 12:37:36 2006,307 [32710] FATAL SugarCRM - Sending query: -- accounts_audit
ALTER TABLE `accounts_audit` CHANGE COLUMN `before_value_text` `before_value_text` longtext NULL ;<br>
Tue Jul 11 12:37:36 2006,426 [32710] FATAL SugarCRM - Sending query: ALTER TABLE `accounts_audit` CHANGE COLUMN `after_value_text` `after_value_text` longtext NULL ;<br>
Tue Jul 11 12:37:36 2006,438 [32710] FATAL SugarCRM - Sending query: -- acl_roles
etc.

What could be the reason for the problems? What can I do to finalize the upgrade properly?
And does this explain why I get the error message listed above?

Thanx, Theo

[vri]

Found out that my problem actually is due to my use of the Dutch Language pack and hence is the same as http://www.sugarcrm.com/forums/showthread.php?t=12493 .

The solution is given in http://www.sugarcrm.com/forums/showthread.php?t=12621 : modify the entry point check in each of the language pack files. Did this, and now it is working again

[cywolf]

Don't worry about the messages in the log file. The upgrader uses the 'FATAL' log level to make sure the messages are logged, not to indicate that something went wrong.

[vri]

Ok, thank you, Andrew.
I spent some time on understanding the messages and couldn't figure out what they meant, as the db was adapted accordingly. So I'm not so stupid after all..

Now I'll happily continue using your great CRM software!!

Theo.