6 Replies Latest reply on Sep 24, 2012 5:19 AM by KaiEilert

    difficulties upgrading to

    Apprentice

      folks,

       

      trying to install 7.5.1 but the install/upgrade falls over at the preparing service desk upgrade stage. Specifically when i check the log it falls over when uninstalling 7.5. is anyone else experiencing this? on killing the sp1 upgrade i found that 7.5 had been uninstalled. so i ran it again and this time it installed successfully. now getting errors when trying to log in (and this is after fixing the console64.exe config file.  This may be due to licence though - web access is giving me a licence error as well as that the md_is_localised column is invalid as is the console login (can't even log in as sa!)

      any suggestions would be greatly appreciated.

       

      rgds,

      dave

        • 1. Re: difficulties upgrading to
          karenpeacock SupportEmployee

          Hi Dave

           

          It sounds as if you have a mixture of different versions there which is why webaccess is complaining about being unable to find a new column which should've been added to your database by the database upgrade.  You shouldn't need a new licence between 7.5 and 7.5sp1.  The installer problem that you experienced with 7.5sp1 sounds like this issue:

           

          Unable to uninstall or upgrade from 7.5 - Error while removing web services / preparing additional components

           

          You don't say whether this is a production environment but if the above doesn't fix this then I would recommend you logging with support.

           

          Regards

          Karen

          • 2. Re: difficulties upgrading to
            Specialist

            Hi Dave,

             

            If you are getting the md_is_localised column is invalid message when trying to run console that means the MDM has not run. You need to upgrade the DB by running the MDM.

             

            Krishan

            • 3. Re: difficulties upgrading to
              Apprentice

              thanks Krishan/Karen - This is test environment by the way. i didn't realise that an mdm run was required. i had a quick look at the accompanying docs for the upgrade and sp 1 before the upgrade and presumed that these were for if you were installed Service Desk from scratch or upgrading from a previous version not for 7.5! anyway i ran the mdm successfully and then tried to logon but message from console login was the administrator should logon first. after attempting to logon as sa i got a query object migration failed message in the login screen but was still able to access the application. logging on as any other analyst though relays the same info. must login as administrator first.

              shoud i have done the sa login before the running the mdm against the db?

              will check out the installer problem link.

              rgds,

              dave

              • 4. Re: difficulties upgrading to
                Apprentice

                folks - just to add that i'm logging into webdesk fine the problem is with console alone.

                rgds,

                dave

                • 5. Re: difficulties upgrading to
                  karenpeacock SupportEmployee

                  I think that the query migration is performed as a part of the fix for Problem 4448 which was to do with queries launching the wrong objects.  I am told that data from the md_launch_class_type_guid column in md_query_template is migrated to an attribute path in new column md_launch_path.  This new column gets added as part of the MDM.

                   

                  As long as you now have 7.5sp1 installed ok I would recommend restoring back your database, running the MDM again and then straight away logging in to console as SA.  If this doesn't work then I would recommend logging this with support.

                   

                  Regards

                  Karen

                  • 6. Re: difficulties upgrading to
                    KaiEilert Apprentice

                    Hi Dave,

                     

                    Did you manage to solve this issue?

                    I am experiencing the same problems after an update from 7.2.6 to 7.5 SP1

                     

                    Regards

                    Kai