Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Upgrade Issue

    Scheduled Pinned Locked Moved Support
    2 Posts 1 Posters 3 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      We got part way through upgrading from 3.7.0 build 5 to 4.0.6 build 26 when we got this error. How do we fix this up so that we can complete the release?

      Debug: The script "10-RELNO. DROP NumericReleaseNumber" executed successfully.
      Debug: 10-RELNO. UPDATE Sortable Release Numbers v2...
      Error: The script "10-RELNO. UPDATE Sortable Release Numbers v2" execution failed. SQL Error: Release number '9.4.0' is invalid for the selected application.
      Error: The transaction ended in the trigger. The batch has been aborted.
      Error: System.InvalidOperationException: C:\Users\SVC_JE~1\AppData\Local\Temp\2\BuildMasterSetup\bmdbupdate.exe returned exit code -2
      at Inedo.Installer.Subtasks.RunProcessSubtask.Run()
      at Inedo.Installer.Subtasks.InstallationSubtask.RunSubtask(IInstallationTask parentTask)
      at Inedo.BuildMaster.Setup.InstallBuildMasterTask.Upgrade(Version oldVersion)
      at Inedo.Installer.InstallationTask`1.Inedo.Installer.IInstallationTask.RunInternal()

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        We've seen this error pop-up a few times, mostly if the ReleaseNumberScheme was altered on the table directly. This script will get fixed in a future release... but in the mean time...

        One fix is to purge the offending application or releases causing the problem. To purge releases, you need to use the method Releases_PurgeReleaseData.

        Of course, that may not be possible, so you can bypass this update script with this:

        DELETE [__BuildMaster_DbSchemaChanges] WHERE [Script_Id] = 612
        INSERT INTO [__BuildMaster_DbSchemaChanges]
        SELECT '406239826673664', 612, 1, '10-RELNO. UPDATE Sortable Release Numbers v2', GETDATE(), 'N' UNION ALL
        SELECT '406239826673664', 612, 2, '10-RELNO. UPDATE Sortable Release Numbers v2', GETDATE(), 'N' UNION ALL
        SELECT '406239826673664', 612, 3, '10-RELNO. UPDATE Sortable Release Numbers v2', GETDATE(), 'N'

        hope that helps

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation