3 Replies Latest reply on Dec 20, 2018 11:17 AM by MarkWard

    PI AF Client SDK Windows 10 not supported

    MarkWard

      A colleague of mine has tried to install the PI AF Client 2018 SP1 SDK but is receiving an error of

       

      Installation of PI Software Development Kit (PI SDK) 2018 has failed. Setup return code 1603. InstallThread Error 1603.

       

      The accompanying error log shows

      --- >>> Setup Module 8

      [UNSUPPORTED_OPERATING_SYSTEMS]: 8 = X64

      Setup module PIBufss.msi is not supported on WIN81NOSP_X64 operating systems.

      CompareVersions> NewVer4 > InstalledVer4...returning 1

      IsMSIInstalled> The installed version 4.7.0.26 is older than the new version to install 4.7.0.37 - returning FALSE.

      Module (PI Buffer Subsystem v4.7.0.37) is not installed, Reason: operating system is not supported - skip installation.

      --- >>> Setup Module 9

      CompareVersions> NewVer4 > InstalledVer4...returning 1

      IsMSIInstalled> The installed version 4.7.0.26 is older than the new version to install 4.7.0.37 - returning FALSE.

      Module (PI Buffer Subsystem v4.7.0.37) will be upgraded.

      --- >>> Setup Module 10

      [UNSUPPORTED_OPERATING_SYSTEMS]: 10 = X64

      Setup module AFClient_x86.msi is not supported on WIN81NOSP_X64 operating systems.

      IsMSIInstalled> Unable to obtain Related Products for Upgrade Code {redacted}. Returned error: 259

      Module (PI AF Client 2018 SP1 v2.10.1.8731) is not installed, Reason: operating system is not supported - skip installation.

      --- >>> Setup Module 11

      IsMSIInstalled> Unable to obtain Related Products for Upgrade Code {redacted}. Returned error: 259

      Module (PI AF Client 2018 SP1 v2.10.1.8731) will be installed.

       

      Note that it shows the OS as 'Win81NoSP_X64' where the OS is actually 64-bit Windows 10. I note that our machines received a Windows update the day prior to attempting to install, so I am wondering if this has perhaps affected it.

       

      I am using Windows 10 and have previously successfully installed the SDK (though the 2016 version, not 2018)


      Any help appreciated, thanks

        • Re: PI AF Client SDK Windows 10 not supported
          gregor

          Hello Mark,

           

          As far as I recall, PI AF Client 2018 SP1 offers PI SDK only as optional package as PI SDK is not needed anymore by the majority of clients. Please see the PI AF SDK product page which doesn't even mention PI SDK being included. Unless you like to use the legacy AF SDK which still requires PI SDK, you would be good to go without PI SDK.

           

          It will be difficult to troubleshoot this through the forums but in case you need PI SDK let's see what we can do. Windows Update should not prevent PI SDK from successfully installing which doesn't mean I want to exclude Windows Update as a potential reason for the failure. I have a few questions.

           

          • Is PI SDK already installed on the client and if so what version?
          • Can you try downloading the latest PI SDK setup kit and see if installs properly?
          • If the PI SDK package does not install, please let us know the errors.
            • Re: PI AF Client SDK Windows 10 not supported
              MarkWard

              Thanks for that reply Gregor.

              Trying to install the 2018 PI SDK ( PISDK_2018_.exe, 183 MB) on the machine, results in the following errors:

               

              ==============================

              ==>>  Begin Verification  <<==

              ==============================

              --- >>> Setup Module 1

              Loading: 1 (C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\dotNetRedistrib\dotnet462Setup.dll)

              C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\dotNetRedistrib\dotnet462Setup.dll version 1.0.0.8

              dotnet462Setup> The version of the .Net Framework on the destination machine is 4.7.02556

              CompareVersions> NewVer4 not found...padding with 0

              CompareVersions> InstalledVer4 not found...padding with 0

              CompareVersions> NewVer2 < InstalledVer2...returning -1

              Module (Microsoft .NET Framework 4.6.2 Setup v4.6.01586) already installed.

              --- >>> Setup Module 2

              Loading: 2 (C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\SetupDialogs\PreInstallTasks.dll)

              C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\SetupDialogs\PreInstallTasks.dll version 1.4.1.37

              CommonInstallTasks> Setup.exe path determined to be: C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\Setup.exe

              CommonInstallTasks> C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\Setup.exe version 1.0.2.65

              CompareVersions> NewVer4 > InstalledVer4...returning 1

              CommonInstallTasks> SetupUtils.dll path determined to be: C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\SetupUtils.dll

              CommonInstallTasks> C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\SetupUtils.dll version 1.0.2.55

              CompareVersions> NewVer4 > InstalledVer4...returning 1

              SetupWizardPreInstallTasks> Entering IsModulePresent

              CommonInstallTasks> PreInstallTasks_InstallComplete is set to 1 (retval = 1)

              SetupWizardPreInstallTasks> Installation tasks have already been completed

              SetupWizardPreInstallTasks> Exiting IsModulePresent

              Module (Pre-Installation Tasks vHIDDEN) already installed.

              --- >>> Setup Module 3

              Module (OSIsoft MS VB Runtime Redistributables v1.0.1) already installed.

              --- >>> Setup Module 4

              Loading: 4 (C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\VS2008Redistrib\MSVC9SP1x86Redistrib.dll)

              C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\VS2008Redistrib\MSVC9SP1x86Redistrib.dll version 1, 0, 0, 3

              CompareVersions> Versions identical...returning 0

              MSVC9SP1x86Redistrib> The installed version 9.0.30729.6161 is the same as the new version to install 9.0.30729.6161 - returning TRUE.

              MSVC9SP1x86Redistrib> The version of the runtime redistributable to be installed is 9.0.30729.6161

              Module (Microsoft Visual C++ 2008 x86 Redistributable v9.0.30729.6161) already installed.

              --- >>> Setup Module 5

              Loading: 5 (C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\VS2008Redistrib\MSVC9SP1x64Redistrib.dll)

              C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\VS2008Redistrib\MSVC9SP1x64Redistrib.dll version 1, 0, 0, 2

              CompareVersions> Versions identical...returning 0

              MSVC9SP1x64Redistrib> The installed version 9.0.30729.6161 is the same as the new version to install 9.0.30729.6161 - returning TRUE.

              MSVC9SP1x64Redistrib> The version of the runtime redistributable to be installed is 9.0.30729.6161

              Module (Microsoft Visual C++ 2008 x64 Redistributable v9.0.30729.6161) already installed.

              --- >>> Setup Module 6

              Loading: 6 (C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\VS2017Redistrib\MSRuntimesVS2017_x86.dll)

              C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\VS2017Redistrib\MSRuntimesVS2017_x86.dll version 1.0.3.0

              MSRuntimesVS2017_x86> Detecting whether or not the Visual Studio 2017 Runtimes are installed

              CompareVersions> InstalledVer4 not found...padding with 0

              CompareVersions> NewVer2 < InstalledVer2...returning -1

              MSRuntimesVS2017_x86> Found version 14.14.26405 with product code {2BCACFA1-2BE1-373C-9051-76A9661D9FC4}. This version is the same or newer than the version to install 14.11.25325.0. Continue checking for additional versions installed.

              MSRuntimesVS2017_x86> The installed version 14.14.26405 is the same as or newer than the version to install 14.11.25325.0 - returning TRUE.

              Module (Microsoft Visual C++ 2017 Redistributable (x86) v14.11.25325.0) already installed.

              --- >>> Setup Module 7

              Loading: 7 (C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\VS2017Redistrib\MSRuntimesVS2017_x64.dll)

              C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\VS2017Redistrib\MSRuntimesVS2017_x64.dll version 1.0.3.0

              MSRuntimesVS2017_x64> Detecting whether or not the Visual Studio 2017 Runtimes are installed

              CompareVersions> InstalledVer4 not found...padding with 0

              CompareVersions> NewVer2 < InstalledVer2...returning -1

              MSRuntimesVS2017_x64> Found version 14.14.26405 with product code {A2999714-5C2C-3729-A911-4AE198B7B2FD}. This version is the same or newer than the version to install 14.11.25325.0. Continue checking for additional versions installed.

              MSRuntimesVS2017_x64> The installed version 14.14.26405 is the same as or newer than the version to install 14.11.25325.0 - returning TRUE.

              Module (Microsoft Visual C++ 2017 Redistributable (x64) v14.11.25325.0) already installed.

              --- >>> Setup Module 8

              Loading: 8 (C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\PINS\pins.dll)

              C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\PINS\pins.dll version 4.0.0.1

              IsMSIInstalled> Unable to obtain Related Products for Upgrade Code {E997574C-9855-4CD6-A21F-DD7A836EAED6}. Returned error: 259

              Module (PI Network Subsystem Support (PINS) v3.4.420.1153) will be installed or upgraded.

              --- >>> Setup Module 9

              IsMSIInstalled> Unable to obtain Related Products for Upgrade Code {9A1A3A9E-DF93-48EF-A658-C052B3148BF9}. Returned error: 259

              Module (PI Software Development Kit (PI SDK) x86 v1.4.7.516) will be installed.

              --- >>> Setup Module 10

              IsMSIInstalled> Unable to obtain Related Products for Upgrade Code {AD7714C6-7563-4CF3-954A-C29093B388ED}. Returned error: 259

              Module (PI Software Development Kit (PI SDK) x64 v1.4.7.516) will be installed.

              --- >>> Setup Module 11

              [UNSUPPORTED_OPERATING_SYSTEMS]: 11 = X64

              Setup module PIBufss.msi is not supported on WIN81NOSP_X64 operating systems.

              CompareVersions> Versions identical...returning 0

              IsMSIInstalled> The installed version 4.7.0.37 is the same as the new version to install 4.7.0.37 - returning TRUE.

              Module (PI Buffer Subsystem v4.7.0.37) is not installed, Reason: operating system is not supported - skip installation.

              --- >>> Setup Module 12

              Module (PI Buffer Subsystem v4.7.0.37) already installed.

              ----------------------

              Completed Verification checks for all modules.

              ============================

              ==>>  End Verification  <<==

              ============================

              Suppress completion message FALSE

              Found custom completion module C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\SetupDialogs\PostInstallTasks.dll in C:\pisetup.ini

              Completion module directory is C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\SetupDialogs

              ====================================

              ==>>  BEGIN COMPLETION MODULE  <<==

              ====================================

              Loading custom completion module: C:\Users\donald.macleod\AppData\Local\Temp\PISDK_1.4.7.516\SetupDialogs\PostInstallTasks.dll

              SetupWizardPostInstallTasks> Mon Dec 17 18:09:33 2018> Entering post-installation tasks. Setup flags:. Installation status: NOT COMPLETED

              SetupWizardPostInstallTasks> Mon Dec 17 18:09:33 2018> Starting SetupDialogs.exe. CMD LINE: SetupDialogs.exe /caller:PostInstallTasks

              SetupWizardPostInstallTasks> ===================================================================================

              SetupWizardPostInstallTasks> ERROR: "SetupDialogs.exe /caller:PostInstallTasks " returned -5

              SetupWizardPostInstallTasks> PLEASE LOOK IN "C:\ProgramData\OSIsoft\Setup\log\SetupPISDK_Dialogs.log" FOR ERROR MESSAGES.

              SetupWizardPostInstallTasks> NOTE:  THE LOG FILE MAY HAVE BEEN RENAMED TO INCLUDE THE DATE.

              SetupWizardPostInstallTasks> ===================================================================================

              SetupWizardPostInstallTasks> Moving C:\ProgramData\OSIsoft\Setup\log\SetupPISDK_Dialogs.log to C:\ProgramData\OSIsoft\Setup\log\SetupPISDK_Dialogs_Mon Dec 17 18_09_41 2018.log

              SetupWizardPostInstallTasks> Mon Dec 17 18:09:41 2018> Post-installation tasks FAILED

              Successfully Unregistered completion module in C:\pisetup.ini

              ====================================

              ==>>  END COMPLETION MODULE  <<==

              ====================================

              Installation of PI Software Development Kit (PI SDK) 2018 has failed. Setup return code 1603. InstallThread Error 1603.

              Module Pre-Installation Tasks (2) will not be displayed because its version number is set to HIDDEN

              Module PI Buffer Subsystem (11) will not be displayed because it is skipped

                • Re: PI AF Client SDK Windows 10 not supported
                  gregor

                  Hello Mark,

                   

                  Errors show for module 8 (PINS), 9 (32-bit PISDK) and 10 (64-bit PISDK). There is also a Warning for module 11 (PI Buffer Subsystem 32-bit) but the product is found being already installed with version 4.7.0.37.

                   

                  I suggest the following:

                   

                  • Create a new local user account and add it to the local Administrators group
                  • Log on with the newly created account
                  • Run PISDK_2018_.exe setup kit again but this time extract to a folder outside the user directory e.g. C:\Temp\PISDK2018\
                  • If the setup again fails with similar issues, please try running the MSI files in the following order:
                    • PINS_x86.msi
                    • PINS_x64.msi
                    • pisdk.msi
                    • pisdk_X64.msi

                   

                  Please let us know your experience with this exercise. If individual MSI's are failing, please let us know what they report.

                  2 of 2 people found this helpful