Thread Details
  • State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 370 subscribers
  • Views 2342 views
  • Users 0 members are here
Forum Actions

A custom composer configuration has been detected which is incompatible with the upgrade process.

Clinton Canarias

Good Day!

I would like to ask for your assistance regarding my SugarCRM Pro 7.7.2.0 upgrade issue. I am trying to upgrade our existing SugarCRM Pro v7.7.2.0 to v7.7.2.2, but I cannot proceed due to an error I encountered. Already reported this issue to Sugar Support with Case #473082, just trying my luck if anyone encounter this error too.

Check my UpgradeWizzard log below:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Tue, 24 Jan 2023 03:24:32 +0000 [Upgrader] - **** Backup complete
Tue, 24 Jan 2023 03:24:32 +0000 [Upgrader] - Finished script BackupFiles
Tue, 24 Jan 2023 03:24:32 +0000 [Upgrader] - Starting script CheckAllowOverride
Tue, 24 Jan 2023 03:24:34 +0000 [Upgrader] - Finished script CheckAllowOverride
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Starting script CheckFTSConfig
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Finished script CheckFTSConfig
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Starting script CheckComposerConfig
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Using /var/www/html/PMS/composer.json as composer.json source
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Using /var/www/html/PMS/composer.lock as composer.lock source
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Using cache/upgrades/temp/SugarPro-Upgrade-7.7.x-to-7.7.2.2/composer.json as composer.json target
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - No hash available in lock file
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Custom composer configuration detected
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Found valid package psr/log with version constraint 1.0.0
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Found valid package ruflin/elastica with version constraint v1.4.3.0
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Found valid package onelogin/php-saml with version constraint 2.10.5
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Found valid package aws/aws-sdk-php with version constraint 2.7.7
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Found valid package phpmailer/phpmailer with version constraint v5.2.22
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Found valid package ircmaxell/password-compat with version constraint v1.0.4
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Found valid package symfony/security-core with version constraint v2.7.1
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Found valid package symfony/security-csrf with version constraint v2.7.1
Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Found valid package symfony/validator with version constraint v2.7.1
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

 

  • 0 Sugar Employee Badge

    Hi  ,

    I recently encountered a similar issue while upgrading a more recent version, and I wanted to share my feedback with you.
    This error occurs when the upgrader detects changes in the composer.json file.

    To resolve this, you can try replacing the composer.json file with the one generated during the upgrade process, as indicated in the logs:

    Tue, 24 Jan 2023 03:24:35 +0000 [Upgrader] - Generating proposal file cache/upgrades/temp/SugarPro-Upgrade-7.7.x-to-7.7.2.2/composer.json.proposal

    If that doesn't resolve the issue, another approach is to obtain a stock composer.json file from the version you are upgrading from and replace it in your instance.

    I hope this information proves helpful to other Sugar admins who might encounter the same error.

    Cheers, 

    André

  • 0 in reply to Andre Serrazina

    Tried both ways still not working. Been searching a lot about this never found a solution.

  • 0 in reply to Wan Amirudin

    Hello,

    Is there any particular reason you are trying to upgrade to 7.7.2.2?

    I am asking this because it does not follow the recommended upgrade path from Sugar:  Upgrade Paths for On-Site Installations 

    It is possible (even probable) there is an issue with this upgrade step; and I would recommend skiping it all together and going from 7.7.2.0 to 7.8.0.0

    Hope this helps,

    Kind regards,

    Vlad

  • 0 in reply to Andre Serrazina

    I experienced the same issue upgrading from 12.0.3-to-12.0.5, see logs below

    What worked for me was downloading the stock installation file for v12.0.3 (SugarEnt-12.0.3.zip) and extracted it to get the stock composer.json file from the version i was upgrading from (12.0.3) and replace it in my current instance in the main sugar files folder. Afterwards, the upgrade process went smooth, all the way to upgrading to v14.0.

    Mon, 22 Apr 2024 15:40:32 +0000 [Upgrader] - Saving file cache/upgrades/temp/SugarEnt-Upgrade-12.0.x-to-12.0.5/composer.json.proposal to disk
    Mon, 22 Apr 2024 15:40:32 +0000 [Upgrader] - ERROR: A custom composer configuration has been detected which is incompatible with the upgrade process. Consult the SugarCRM Administration Guide for more details on how to resolve this issue. Detailed logs are available in /<sugar_folder>/SugarEnt-Upgrade-12.0.x-to-12.0.5/SugarEnt-Upgrade-12.0.x-to-12.0.5.log.
    Mon, 22 Apr 2024 15:40:32 +0000 [Upgrader] - Finished script CheckComposerConfig
    Mon, 22 Apr 2024 15:40:32 +0000 [Upgrader] - ERROR: Pre-upgrade stage failed!