Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-10813

SourcetreeEnterprise: CompositionException after updating from 2.6.10 to 3.0.8

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Highest Highest
    • None
    • 3.0.8
    • None
    • Severity 1 - Critical

      After updating Sourcetree Enterprise from 2.6.10 to 3.0.8 Sourcetree doesnt start anymore. The splash screen is shown, but then nothing happens.

      The log in C:\Users\user\AppData\Local\Atlassian\SourceTree\sourcetree.log says:

      2018-11-06T11:47:32: CompositionException [Errors occurred during discovery.]

      I tried to deinstall sourcetree before installing by running:

      $sourcetreeGUID = (Get-WmiObject -Class Win32_Product -ComputerName . -Filter "Name='Microsoft .NET Framework 2.0'").IdentifyingNumberStart-Process -Wait -FilePath C:\windows\system32\msiexec.exe -ArgumentList '/x', $sourcetreeGUID, '/qn'

      But that doesn't fix the issue either.

      After completely removing everything related to sourcetree and performing a new install, Sourcetree 3.0.8 does start. I think this is unwanted, because users lose their preferences.

      This is the case for all 3.x versions so far and possible for versions 2.x as well.

            [SRCTREEWIN-10813] SourcetreeEnterprise: CompositionException after updating from 2.6.10 to 3.0.8

            Another ticket already exist for this issue.

            Mukesh Kumar added a comment - Another ticket already exist for this issue.

            minnsey added a comment -

            I believe this might be down to permissions on the installation folder. Unless you are seeing a difference between the contents of the folders before and after a full re-install I believe all of the components are being installed but Sourcetree is being blocked from loading them.

            It might be worth recording the folder permissions when everything is working and then compare to when it stops

            https://social.technet.microsoft.com/wiki/contents/articles/31139.powershell-how-to-get-folder-permissions.aspx

            minnsey added a comment - I believe this might be down to permissions on the installation folder. Unless you are seeing a difference between the contents of the folders before and after a full re-install I believe all of the components are being installed but Sourcetree is being blocked from loading them. It might be worth recording the folder permissions when everything is working and then compare to when it stops https://social.technet.microsoft.com/wiki/contents/articles/31139.powershell-how-to-get-folder-permissions.aspx

              Unassigned Unassigned
              8988432f93ff Rick van Twillert (TMC)
              Affected customers:
              2 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: