2 Replies Latest reply on Jul 20, 2017 8:08 AM by Roger1

    Database Upgrade Failed 8.6/8.7 to 10.1 FR1

    Roger1 Apprentice

      **Note I've already restored everything from backup and I'm back on 8.6/8.7**

      Curious if anyone has experienced upgrade issues like this.

      I finished my test upgrade of the DesktopNow suite without incident.  The problems began when I tried to connect to the Server Configuration Portal.

      The creds save button returned WinRM errors.  I couldn't find anything on the website regarding the specific error.

      Wasn't too concerned - decided to just do a manual upgrade via PowerShell.

      •      The Management Server DB upgraded fine.
      •      The Personalization Server refused to upgrade.  It continually gave this error - Exception has been thrown by the target of an invocation.

         --- End of inner exception stack trace ---

         at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)

         at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)

         at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

         at ServerConfig.ReflectionHelpers.ReflectivePublicGet(PropertyInfo pi, Object baseObject)

      2017-06-05 22:06:35,076 [Pipeline Execution Thread] INFO  Personalization DEFAULT Exception is TIE - Checking inner exception

      2017-06-05 22:06:35,076 [Pipeline Execution Thread] INFO  Personalization DEFAULT Exception not matched - ignoring

      2017-06-05 22:06:35,092 [Pipeline Execution Thread] INFO  Personalization DEFAULT ResName: REFLECTIVE_PUBLIC_GET_FAIL  ResString: Reflective get of public property 'ConnectionTimeout' failed

      SystemException: Exception has been thrown by the target of an invocation.

      2017-06-05 22:06:35,092 [Pipeline Execution Thread] INFO  Personalization DEFAULT ENTER:ConnectionCredentials:GetConfigPath:

      2017-06-05 22:06:35,092 [Pipeline Execution Thread] INFO  Personalization DEFAULT EXIT:ConnectionCredentials:GetConfigPath:C:\Program Files\AppSense\Environment Manager\Personalization Server\PS\web.config

      2017-06-05 22:06:35,092 [Pipeline Execution Thread] INFO  Personalization DEFAULT ShouldRethrow - Evaluating exception:

      System.Exception: Unable to resolve path

         at SecurityAssist.SecureReference.GetValueFromXML(XPathDocument xpathDocument, String namespaces, String xPath)

         at SecurityAssist.SecureReference.GetConfigValue(String filename, String secureReferenceQuery)

         at ServerConfig.ConnectionCredentials.get_CommandTimeout()

      2017-06-05 22:06:35,092 [Pipeline Execution Thread] INFO  Personalization DEFAULT Exception not matched - ignoring

      2017-06-05 22:06:35,107 [Pipeline Execution Thread] INFO  Personalization DEFAULT ResName: GET_CREDENTIALS_FAIL_COMMAND_TIMEOUT  ResString: Failed to get Command Timeout from credentials storage

      SystemException: Unable to resolve path

      2017-06-05 22:06:35,107 [Pipeline Execution Thread] INFO  Personalization DEFAULT ShouldRethrow - Evaluating exception:

      System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> ServerConfig.ErrorHandling.AppSenseServerConfigAPIException: Failed to get Command Timeout from credentials storage ---> System.Exception: Unable to resolve path

         at SecurityAssist.SecureReference.GetValueFromXML(XPathDocument xpathDocument, String namespaces, String xPath)

         at SecurityAssist.SecureReference.GetConfigValue(String filename, String secureReferenceQuery)

         at ServerConfig.ConnectionCredentials.get_CommandTimeout()

         --- End of inner exception stack trace ---

       

      If y'all have any suggestions before I attempt another upgrade, they are greatly appreciated.  I fear version 8 is going to be my mainstay for some time to come.