Tweet
Hei guys,
Hope that one of you could point me in the right direction.
Just upgraded EspoCRM from 4.1.6 to 4.2.0 and got "Bad Server Response". On the page, only the copyrighted footer is visible.
It worked with 4.1.6 without issues, could add and update information when logged in. Have been using it for months and love it.
SERVER OS:
CentOS 7 (64-bit).
WHAT I HAVE DONE:
1. I removed the application folder in //data/cache,
thought there was a cache issue. Getting still the same error.
2. Checked permission on //index.php and //api/v1/index.php, for 644, like pointed out here:
3. Checked log file under //data/logs
THAT WHAT LOG FILE SAID:
I am quite new to EspoCRM, just managed to install it couple of months ago.
Am I right to assume that some files didn't manage to update on the upgrade?
Thinking of manually updating files from the 4.1.6 to 4.2.0, like overriding the files, but before I do that, wanted to ask your advice.
Have made a database backup before I upgrade.
If it is not possible to save, can remove and reinstall a new EspoCRM.
Before I do it, my hope was that maybe some of you guys experienced something similar and managed to fix it. When upgrading from 4.1.6 to 4.2.0
Thank you,
Ollu
Hope that one of you could point me in the right direction.
Just upgraded EspoCRM from 4.1.6 to 4.2.0 and got "Bad Server Response". On the page, only the copyrighted footer is visible.
It worked with 4.1.6 without issues, could add and update information when logged in. Have been using it for months and love it.
SERVER OS:
CentOS 7 (64-bit).
WHAT I HAVE DONE:
1. I removed the application folder in //data/cache,
thought there was a cache issue. Getting still the same error.
2. Checked permission on //index.php and //api/v1/index.php, for 644, like pointed out here:
3. Checked log file under //data/logs
THAT WHAT LOG FILE SAID:
Code:
[2016-08-07 19:06:02] Espo.ERROR: E_RECOVERABLE_ERROR:
Argument 3 passed to Espo\Core\ORM\Repository::__construct() must be an instance of Espo\Core\ORM\EntityFactory,
instance of Espo\ORM\EntityFactory given, called in /home/user/webapps/CRM/application/Espo/ORM/RepositoryFactory.php on line 54 and defined
{"code":4096,"message":"Argument 3 passed to Espo\\Core\\ORM\\Repository::__construct() must be an instance of Espo\\Core\\ORM\\EntityFactory,
instance of Espo\\ORM\\EntityFactory given, called in /home/user/webapps/CRM/application/Espo/ORM/RepositoryFactory.php on line 54
and defined","file":"/home/user/webapps/CRM/application/Espo/Core/ORM/Repository.php","line":71,"context":{"entityType":"Preferences","entityManager":"[object]
(Espo\\Core\\ORM\\EntityManager: {})"}} []
Am I right to assume that some files didn't manage to update on the upgrade?
Thinking of manually updating files from the 4.1.6 to 4.2.0, like overriding the files, but before I do that, wanted to ask your advice.
Have made a database backup before I upgrade.
If it is not possible to save, can remove and reinstall a new EspoCRM.
Before I do it, my hope was that maybe some of you guys experienced something similar and managed to fix it. When upgrading from 4.1.6 to 4.2.0
Thank you,
Ollu
Comment