SAP Knowledge Base Article - Preview

2725234 - BI Client Tools installation fails with Error code from call to Windows Installer API: 1612

Symptom

  • After following KBA 1691555 - Manually remove SAP BI 4.0/4.1/4.2 from Windows Server [How-To] [Video] or blog https://blogs.sap.com/2016/04/15/version-2-clean-up-utility-for-manually-remove-sap-business-intelligence-bi-404142-for-windows-how-to-remove-sap-business-intelligence-bi-404142-manually-from-windows-server/ it is not possible to install the client tools successfully.
  • Install ends 'successfully', but the BusinessObjects folder is not complete, and many files are missing
  • In the InstallLogs, it can be seen that dunits are failing to install with following error message:

    Error: Error code from call to Windows Installer API: 1612
    Error: unmarshalSizet: curPos past end of string
    Error: Serialization error. Expecting at least 1 arg(s). Got 0.
    Error: Poco Exception: Software caused connection abort

  • Many InstallDU and UninstallDU log files can be seen in <BOBJINSTALLDIR>\InstallData\logs\<InstallTimestamp>, with below example errors inside:

    SOURCEMGMT: Attempting to use LastUsedSource from source list.
    SOURCEMGMT: Trying source <PREVIOUSLYUSEDINSTALLPATH>\InstallData\InstallCache\bi.2.00.bi.base-4.0-core-nu\14.2.6.2839\.
    Note: 1: 2203 2: <PREVIOUSLYUSEDINSTALLPATH>\InstallData\InstallCache\bi.2.00.bi.base-4.0-core-nu\14.2.6.2839\content.msi 3: -2147287037
    SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    <TRUNCATED>
    SOURCEMGMT: Failed to resolve source
    MainEngineThread is returning 1612


Read more...

Environment

  • SAP BusinessObjects Business Intelligence Platform 4.x (BI 4.0 / 4.1 / 4.2)
  • Windows
  • Linux / Unix 

Product

SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.1 ; SAP BusinessObjects Business Intelligence platform 4.2

Keywords

KBA , BI-BIP-INS , Installation, Updates, Upgrade, Patching , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.