4 Replies Latest reply on Aug 2, 2016 1:21 PM by dmshimself

    Upgrade duration ?

    manicmog Rookie

      I am currently upgrading ServiceDesk from v7.8.1 to 2016.2.

      I am running the upgrade in my Dev environment first (which is spec'd similar to our live environment). The database is approximately 20gb in size and has been restored from the live environment.

      I started in the upgrade at 13:41 and it appears to still be running at 17:10. Image / screenshot attached.

      How long does this upgrade normally take ?

      Has it failed or locked up ?

       

      Thanks in advanced.

       

      Kind regards

      Bryan

        • 1. Re: Upgrade duration ?
          ITSMMVPGroup

          If the clock isn't ticking up (126 goes to 128 goes to ...) then it has failed and a check of the metadata log file should reveal some clues.

          • 2. Re: Upgrade duration ?
            Apprentice

            Just got off the phone with support. First attempt was made on the web server. I never even got to the point of a progress bar. Called support they recommended I try the upgrade on the application server. Same result. Starting Upgrade.

             

            If you are like me and are following the Online guide in the upgrade portion step 2 it says "Using the LANDESK Configuration Center, stop all of the Windows services for all of the instances you have set up."

             

            Once its finished it says to automatically start the configuration center.

            "

            1. Alongside the servicedesk.Framework configured application, click Upgrade.
              The Upgrade dialog appears.

            Click Upgrade.

            The upgrade starts."

             

            Nothing about starting the Services backup...

             

            So yeah make sure the services are started and the upgrade will continue.

            1 of 1 people found this helpful
            • 3. Re: Upgrade duration ?
              manicmog Rookie

              Came in this morning, it is showing the same (no progress). I have checked the log, and this is at the end.... it shows some errors. Not sure what this means.... any ideas ?

               

              - <MetadataLogEntry
              xmlns:xsd
              ="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

               

              <Sql>INSERT INTO ui_shortcut_group_role (ui_guid, ui_shortcut_group_guid,
              ui_role_guid, ui_last_update) VALUES ('3E85BE71-889D-42CB-986A-EC8570092202',
              '8336D639-8FEB-4255-860C-2D427D3AB341', '638C03DB-89E0-4F2A-893F-C5C4F16E327D',
              current_timestamp)
              </Sql>

               

              <Result>Failure</Result>

               

              <ErrorMessage>The INSERT statement conflicted with the
              FOREIGN KEY constraint "fkey$ui_sc_group_role$scgpr". The conflict occurred in
              database "LDSD", table "dbo.ui_shortcut_group", column 'ui_guid'. The statement
              has been terminated.
              </ErrorMessage>

               

              </MetadataLogEntry>

              - <FatalError>

               

              <Description>The INSERT statement conflicted with the
              FOREIGN KEY constraint "fkey$ui_sc_group_role$scgpr". The conflict occurred in
              database "LDSD", table "dbo.ui_shortcut_group", column 'ui_guid'. The statement
              has been terminated.
              </Description>

               

              <CallStack>at
              Touchpaper.Framework.Data.Metadata.MetadataLog.ExecuteNonQuery(IDbCommand cmd,
              Boolean ignoreErrors) at
              Touchpaper.Framework.Data.Metadata.Tools.ScriptRunner.ExecuteScript(DataSourceProvider
              provider, String connectString, SqlScript script, Boolean ignoreErrors) at
              Touchpaper.Framework.Data.Metadata.Tools.ScriptRunner.ExecuteUpgradeScripts(Nullable`1
              scriptVersion, Boolean afterResources) at
              Touchpaper.Framework.Data.Metadata.Manager.MetadataManager.DoConversion(MetadataCatalog
              metadata, Boolean isMdmOperation) at
              Touchpaper.Framework.Data.Metadata.Manager.MetadataManager.SetupDatabase(MetadataCatalog
              metadata)
              </CallStack>

               

              </FatalError>

              </MetadataLog>

              • 4. Re: Upgrade duration ?
                ITSMMVPGroup

                I'd restore your DB to the version prior to running the upgrade and then upgrade again.  I suspect it will do the same thing, so then log a support call.  They will probably want a cleared down copy of your pre-upgrade database.