Getting 404's in front-end + manager can't load resources after upgrade to 2.1.3

Hi

Just upgraded a 2.0.7 standard install to version 2.1.3 without any problem.

After that I tried upgrading a 2.0.7 advanced install to version 2.1.3 advanced, I pre-unzipped the core package and choose the correct name of my config file. I upgraded this installation before without any kind of problem. After the upgrade I logged into the manager and tried loading a resource, this results in a 500 internal server error. Trying to load a page in the front-end redirects to my 404 page, the home page loads completely fine without any problem. I use the default .htaccess file, only added AddHandler x-httpd-php5 .php for php5 support.

This is weird behavior I have never had before. I checked out my error log, it’s spammed with:

[2011-07-26 21:46:06] (ERROR @ /connectors/resource/index.php) Error preparing statement for query: SELECT modAccessContext.id, modAccessContext.target, modAccessContext.principal, modAccessContext.authority, modAccessContext.policy, Policy.data FROM `modx_access_context` AS `modAccessContext` LEFT JOIN `modx_access_policies` `Policy` ON `modAccessContext`.`policy` = `Policy`.`id` WHERE ( `modAccessContext`.`principal_class` = ? AND `modAccessContext`.`target` = ? ) ORDER BY modAccessContext.target,modAccessContext.principal,modAccessContext.authority,modAccessContext.policy ASC - Array
(
[0] => HY000
[1] => 2014
[2] => Cannot execute queries while other unbuffered queries are active. Consider using PDOStatement::fetchAll(). Alternatively, if your code is only ever going to run against mysql, you may enable query buffering by setting the PDO::MYSQL_ATTR_USE_BUFFERED_QUERY attribute.
)

[2011-07-26 21:46:11] (ERROR @ /manager/index.php) Error preparing statement for query: SELECT `modActionDom`.`id`, `modActionDom`.`set`, `modActionDom`.`action`, `modActionDom`.`name`, `modActionDom`.`description`, `modActionDom`.`xtype`, `modActionDom`.`container`, `modActionDom`.`rule`, `modActionDom`.`value`, `modActionDom`.`constraint`, `modActionDom`.`constraint_field`, `modActionDom`.`constraint_class`, `modActionDom`.`active`, `modActionDom`.`for_parent`, `modActionDom`.`rank`, `FCSet`.`template`, `FCSet`.`constraint`, `FCSet`.`constraint_field`, `FCSet`.`constraint_class` FROM `modx_actiondom` AS `modActionDom` JOIN `modx_fc_sets` `FCSet` ON `modActionDom`.`set` = `FCSet`.`id` JOIN `modx_fc_profiles` `Profile` ON FCSet.profile = Profile.id LEFT JOIN `modx_fc_profiles_usergroups` `ProfileUserGroup` ON Profile.id = ProfileUserGroup.profile LEFT JOIN `modx_fc_profiles` `UGProfile` ON UGProfile.id = ProfileUserGroup.profile WHERE ( ( `modActionDom`.`action` = ? AND `modActionDom`.`for_parent` = ? AND `FCSet`.`active` = ? AND `Profile`.`active` = ? ) AND ( ( `ProfileUserGroup`.`usergroup` IN (’1’) OR ( `ProfileUserGroup`.`usergroup` IS ? AND `UGProfile`.`active` = ? ) ) OR `ProfileUserGroup`.`usergroup` IS ? ) ) ORDER BY modActionDom.rank ASC - Array
(
[0] => 42000
[1] => 1064
[2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ’? AND `UGProfile`.`active` = ? ) ) OR `ProfileUserGroup`.`usergroup` IS ? ) )’ at line 1
)

Site URL: http://rainbowracing.nl

Help?

Let me know if you need some more details.

Thanks in advance for your help, really desperate here

Could you please post the System Info stuff about your environment?

Sure: posted screenschots because I couldnt properly copy them, hope thats ok...

And last one...

Found something, when I try to clear cache with the manager I get a bunch of the following errors:

Resource URI already exists for resource id = 4; skipping duplicate resource URI for resource id = 5
Resource URI already exists for resource id = 4; skipping duplicate resource URI for resource id = 6
Resource URI already exists for resource id = 4; skipping duplicate resource URI for resource id = 7
Resource URI already exists for resource id = 4; skipping duplicate resource URI for resource id = 8
Resource URI already exists for resource id = 4; skipping duplicate resource URI for resource id = 9

Managed to get rid of the cache errors bij updating the friendly url settings (Thx OpenGeek @ http://modxcms.com/forums/index.php/topic,62878.msg367328.html#msg367328)

I read in that topic about the uri field in the modx_site_content table. The succesfulll upgrade site shows my page mapped alias in that column, the failled upgrade site shows NULL’s... maybe this is a clue?

Just a quick update. I didn’t found the problem, got sick of it after 24 hours so I did a re-install. Started with a clean 2.1.3 and manually added my resources / templates / chunks / etc to the database. That still didn’t make it all working! The manager is functional again, I can edit my resources again. The front-end side still gave 404’s if I had Friendly URL’s enabled but after enabling the "Freeze URI" @ Page settings tab it suddenly worked! So the site is up and running again Got some more sites to upgrade, here’s hoping it goes smoothly again