Announcement

Collapse
No announcement yet.

Error when upgrading 7.3.4 - 7.4.6

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error when upgrading 7.3.4 - 7.4.6

    We've been running 7.2.7 for a while, as upgrading further required php 8

    We've installed php 8 now and the required extensions, and the first upgrade to 7.3.4 went fine.

    Upgrading again to 7.4.6 throws an error though:

    Click image for larger version

Name:	image.png
Views:	231
Size:	31.5 KB
ID:	97669

    The logs show:

    Click image for larger version

Name:	image.png
Views:	168
Size:	398.6 KB
ID:	97670​​

  • #2
    i think this was mentioned before, see the fix here https://github.com/espocrm/espocrm/i...ent-1543704395

    here is the full thread https://forum.espocrm.com/forum/inst...ade-past-7-4-4

    Hope this helps

    Comment


    • #3
      BattleMetalChris

      You can try the following steps:

      1. Make a full backup of your current EspoCRM instance and keep it in a safe place: https://docs.espocrm.com/administrat...p-and-restore/.
      2. Install clean EspoCRM v7.4.6 instance. During installation, select your old database (you need to specify the base of your problem instance).
      3. Delete /custom and /data folders from new instance and copy these folders from backup to the new instance.
      4. Run Rebuild from CLI: https://docs.espocrm.com/administrat...mands/#rebuild. If it does not help, then run Hard Rebuild: https://docs.espocrm.com/administrat.../#hard-rebuild, which will be available in installed v7.4.6.
      5. If the previous steps are successful, then don't forget to update Permissions: https://docs.espocrm.com/administrat...permissions​.

      Comment


      • #4
        Originally posted by victor View Post
        BattleMetalChris

        You can try the following steps:

        1. Make a full backup of your current EspoCRM instance and keep it in a safe place: https://docs.espocrm.com/administrat...p-and-restore/.
        2. Install clean EspoCRM v7.4.6 instance. During installation, select your old database (you need to specify the base of your problem instance).
        3. Delete /custom and /data folders from new instance and copy these folders from backup to the new instance.
        4. Run Rebuild from CLI: https://docs.espocrm.com/administrat...mands/#rebuild. If it does not help, then run Hard Rebuild: https://docs.espocrm.com/administrat.../#hard-rebuild, which will be available in installed v7.4.6.
        5. If the previous steps are successful, then don't forget to update Permissions: https://docs.espocrm.com/administration/server-configuration/#permissions​.
        I've tried that now.

        The latest install runs ok, and I can connect it to my existing DB (and see the contacts when I log in) but after I replaced the data and custom folders I don't get the login screen any more.

        I set permissions, and did both a soft and hard rebuild from the CLI

        I just get a mostly blank screen with:
        Click image for larger version  Name:	image.png Views:	0 Size:	2.3 KB ID:	98768

        No errors (and nothing in the logs), but no login screen.​

        Comment


        • victor
          victor commented
          Editing a comment
          1. Do you currently have 7.4.6 installed?
          2. Do you have an almost blank screen in the main browser where you work with EspoCRM and in the anonymous tab of this browser?
          3. Blank screen on the main page only? Please send a screenshot from the main page and, for example, from #Admin or #Contact. Also send the EspoCRM error log (after you see the blank screen).
          4. Does your CLI rebuild and hard rebuild occur without errors? Has the old error gone (which was current at the time this topic was created)?

      • #5
        An update with this, for completion:

        Firstly we've decided to port everything over to a Linux instance, as the package manager makes setting up the php installation far easier.
        I've been able to install a vanilla 7.3.4, add our customisations to it, and then upgrade that to the latest version.

        So all good!


        Comment

        Working...
        X