4 Replies Latest reply on Nov 28, 2017 1:41 AM by swabedoo

    Update DSM 2014.1 auf DSM 2016.2 R2

    bomber1 Apprentice

      Hallo,

       

      ich habe das Update bis zum Primary BLS durchgeführt. Dort bekomme ich nun allerdings die Fehlermeldung, dass der öffentliche Schlüssel von Heat Remote nicht abgerufen bzw. gespeichert werden konnte.

      Vermutlich kein dramatischer Fehler und ich könnte das Update fortführen, mir wäre aber daran gelegen den Fehler vorher zu beheben.

      Kennt jemand das Problem?

       

      DSM-Update-Error-2.png

      DSM-Update-Error-1.png

       

      Mit freundlichen Grüßen

      Klaus Meyer

        • 1. Re: Update DSM 2014.1 auf DSM 2016.2 R2
          bomber1 Apprentice

          Hallo nochmal,

           

          die Fehlermeldung von oben ist natürlich Quatsch.. Beim Durchsuchen des Logfile MPInstallUpdate_Install_Update_4.log steht folgendes im Schritt Deinstallation MPBase:

           

          16:59:15.614 E      Warning (Module:Main, Severity:0x03): Can't resolve variable MPS.MgntPointSettings.VirtualDirPhysicalPath

          16:59:15.615 E      Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

           

          16:59:15.625 E       Error (Module:Main, Severity:0x0b): Fehler beim Anlegen des Verzeichnisses %MPS.MgntPointSettings.VirtualDirPhysicalPath%

          Das System kann die angegebene Datei nicht finden. (0x00000002)

          16:59:15.626 2       Messagebox suppressed  (No output allowed), output is written to the log files

          16:59:15.626 2       MsgBox: [Fehler beim Anlegen des Verzeichnisses %MPS.MgntPointSettings.VirtualDirPhysicalPath%

          Das System kann die angegebene Datei nicht finden. (0x00000002)

          Installation wird beendet.]

           

          Auch andere Variablen können nicht aufgelöst werden:

          16:59:15.608 E      Warning (Module:Main, Severity:0x03): Can't resolve variable MPS.LogFileSettings.LogFilePath

           

          Gruß

          Klaus

          • 2. Re: Update DSM 2014.1 auf DSM 2016.2 R2
            _Mel_ Master

            schau mal weiter oben, die MPS.* variablen werden aus der ncp befüllt - ich hab in letzter zeit zwei/drei mal gesehen, daß der management point nicht wußte welcher MP er ist; evtl ist es das

            • 3. Re: Update DSM 2014.1 auf DSM 2016.2 R2
              bomber1 Apprentice

              Hallo Mel,

               

              sieht irgendwie nicht gut aus:

               

              16:59:15.584 2      ---->Starting uninstallation of "SSI:DSM Portal wird deinstalliert..."

               

               

              16:59:15.585 2      -> Set('BLSDbPasswordEncrypted','k2EC313803DA8CDF597FDE7EF5E847F3388G0A')

               

               

              16:59:15.586 2      -> Set('MPTYPE','BlsMgntPoint')

               

               

              16:59:15.587 2      -> Set('BLSDbConnectionString','Provider=SQLOLEDB.1;Persist Security Info=True;Initial Catalog=DSM;Data Source=sqlsrv;Network Library=DBMSSOCN;Application Name=DSM')

               

               

              16:59:15.588 2      -> Set('BLSDbUser','dsm')

               

               

              16:59:15.590 2      -> Set('MPSERVERNAME','NETINSTALL.dohle.com')

               

               

              16:59:15.591 2      -> Set('BLSDBMS','SqlServer')

               

               

              16:59:15.592 2      -> Set('ManagementPortalVirDir','ManagementPortal')

               

               

              16:59:15.593 2      -> Set('ClientManagementVirDir','blsClientManagement')

               

               

              16:59:15.594 2      -> Set('IISName','NETINSTALL')

               

               

              16:59:15.596 2      -> RegReadValue('HKEY_LOCAL_MACHINE\SOFTWARE\NetSupport\Shared Infrastructure\MgntPoint','MgntPointID','REG_MGNT_POINT_ID')

              16:59:15.596 0       Uninstall of RegReadValue not supported

              16:59:15.596 E      Warning (Module:Main, Severity:0x03): Can't resolve variable REG_MGNT_POINT_ID

              16:59:15.597 E      Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

               

               

              16:59:15.598 2      -> NcpSimpleQuery('*','<ID>=_REG_MGNT_POINT_ID_','MPS.','') ...

              16:59:15.598 2       xniTools: Using current NCP

              16:59:15.598 1       xniTools: <ID> --> comparing container ID 65535 with 0

              16:59:15.598 1       xniTools: <ID> --> comparing container ID 66031 with 0

              16:59:15.598 1       xniTools: <ID> --> comparing container ID 66138 with 0

              16:59:15.598 1       xniTools: <ID> --> comparing container ID 66139 with 0

              16:59:15.598 1       xniTools: <ID> --> comparing container ID 66140 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66144 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66670 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66672 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66671 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66673 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66180 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66189 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66185 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66669 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66032 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66691 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66030 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66027 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66028 with 0

              16:59:15.599 1       xniTools: <ID> --> comparing container ID 66029 with 0

               

               

              16:59:15.599 1      Evaluating condition "_MPS.MgntPointSettings.MPServerName_=''"

              16:59:15.599 E        Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

              16:59:15.600 E        Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

              16:59:15.601 E       Warning (Module:Main, Severity:0x03): Can't resolve variable MPS.MgntPointSettings.MPServerName

              16:59:15.602 E       Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

              16:59:15.603 0       Comparing '' with ''

              16:59:15.603 2      Condition TRUE    -> entering IF part

               

               

              16:59:15.604 2      ->  NcpSimpleQuery('*','MgntPointSettings.MPServerName=NETINSTALL','MPS.','') ...

              16:59:15.604 2       xniTools: Using current NCP

              16:59:15.604 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.604 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is mfshit03.hit003.dohle.com. Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is mfshit998.hit998.dohle.com. Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is NETINSTALL.dohle.com. Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is NETINSTALL.dohle.com. Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.605 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.606 1       xniTools:   Ok. Queried value is . Now compare it with NETINSTALL

              16:59:15.606 E       Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

              16:59:15.607 E       Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

              16:59:15.608 E      Warning (Module:Main, Severity:0x03): Can't resolve variable MPS.LogFileSettings.LogFilePath

              16:59:15.609 E      Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

               

               

              16:59:15.609 2      -> Set('MPS.LogFileSettings.LogFilePath','_MPS.LogFileSettings.LogFilePath_')

               

               

              16:59:15.611 2      -> GetFrameworkPath('2.0.0','FrameworkPath',rfxUseX64HiveOnWOW64+rfxCheckSpecificVersion)

              16:59:15.612 1       xniTools: Checking if a .NET Framework version equal or higher than 2.0.0 installed

              16:59:15.612 0       xniTools: Using framework root path: C:\Windows\Microsoft.NET\Framework64\

              16:59:15.612 0       xniTools: Checking 1031

              16:59:15.612 0       xniTools: Checking v2.0.50727

              16:59:15.612 0       xniTools: matched

              16:59:15.613 E       Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

              16:59:15.613 E       Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

              16:59:15.614 E      Warning (Module:Main, Severity:0x03): Can't resolve variable MPS.MgntPointSettings.VirtualDirPhysicalPath

              16:59:15.615 E      Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

               

               

              16:59:15.616 2      -> Delete('_MPS.MgntPointSettings.VirtualDirPhysicalPath_\ManagementPortal\bin\Infra*.*')/F/TS

              16:59:15.616 0       Uninstall of Delete not supported

              16:59:15.617 E       Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

              16:59:15.617 E       Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

              16:59:15.618 E      Warning (Module:Main, Severity:0x03): Can't resolve variable MPS.MgntPointSettings.VirtualDirPhysicalPath

              16:59:15.619 E      Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

               

               

              16:59:15.620 2      -> Copy('\\magnum\dsm\SSI\{2BB29EF9-D7C8-4E07-A59D-660932E44F0F}\VirDir\*.*','_MPS.MgntPointSettings.VirtualDirPhysicalPath_\ManagementPortal')/S/TW

              16:59:15.620 0       do not use registry for uninstall, the command will be reverted.

              16:59:15.621 0       force schedule command for service execution.

              16:59:15.621 2       SI: Message........: [Dateien löschen...]

              16:59:15.622 2       SI: Text Index: [1], Text: [Dateien löschen...]

              16:59:15.624 1       Including subdirs

              16:59:15.624 2       Creating dir (if needed) %MPS.MgntPointSettings.VirtualDirPhysicalPath%

              16:59:15.625 E       Error (Module:Main, Severity:0x0b): Fehler beim Anlegen des Verzeichnisses %MPS.MgntPointSettings.VirtualDirPhysicalPath%

              Das System kann die angegebene Datei nicht finden. (0x00000002)

              16:59:15.626 2       Messagebox suppressed  (No output allowed), output is written to the log files

              16:59:15.626 2       MsgBox: [Fehler beim Anlegen des Verzeichnisses %MPS.MgntPointSettings.VirtualDirPhysicalPath%

              Das System kann die angegebene Datei nicht finden. (0x00000002)

              Installation wird beendet.]

              16:59:15.627 E       Warning (Module:SWMSRT, Severity:0x03): failed to get SWMSRunTimeMgr

              16:59:15.650 2      New last error from script command is 2147614729 (0x80020009)

              16:59:15.650 2      Resolved new last error from script command is: Ausnahmefehler aufgetreten.

              16:59:15.651 2     Execution terminated on error

              16:59:15.652 2     SI: Message........: [Installationsstatus melden...]

              16:59:15.652 2     SI: Text Index: [1], Text: [Installationsstatus melden...]

              16:59:15.652 2     SI: Message........: [Installationsstatus melden...]

              16:59:15.653 2     SI: Text Index: [1], Text: [Installationsstatus melden...]

              16:59:15.653 2     SI: Text Index: [1], Text: []

               

               

              16:59:15.653 2     ---->Uninstallation of SSI:DSM Portal wird deinstalliert... has not completed on exit.

               

              Ich hab mir hier auch mal das Quellverzeichniss angesehen, da ist bis auf das Script nichts drin:

              16:59:15.620 2      -> Copy('\\magnum\dsm\SSI\{2BB29EF9-D7C8-4E07-A59D-660932E44F0F}\VirDir\*.*','_MPS.MgntPointSettings.VirtualDirPhysicalPath_\ManagementPortal')/S/TW

              • 4. Re: Update DSM 2014.1 auf DSM 2016.2 R2
                swabedoo Apprentice

                Hallo Klaus,

                 

                das ist das ganz alte Management Portal, das wird immer entfernt. Also kein Grund zur Panik. Aber ich denke, du solltest beim Support anrufen, Update-Problemen im Forum auf die Spur zu kommen ist schwer und langwierig.

                 

                Viele Grüße,

                swabedoo