Page tree
Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this document is to address an attempted network installation that fails.

Overview

 After running the Sybase installer of the SDK, the installer will finish by stating that the installation was successful, but with errors.

Details

  • All versions of Windows
  • Versions 15.0 Sybase SDK and above
  • GUI Installation

 

At the end of an installation of the Software Developers Kit (SDK) you can get an error the the Installation was successful, but had errors

This can be caused by running the installer from a Shared Network Drive.
You can reproduce the error by installing the 15.7 SDK to a "Clean" machine.  This is also applicable to installing the SDK from an EBF.
After installation, the installer will create logs on the target machine in the $SYBASE\log directory.

Looking in the Suite_log will show that there are successful component installations, but you will also see ERROR and FAILED

 

Custom Action:            com.sybase.ia.common.InstallMergeModuleStatus
                          Status: SUCCESSFUL

Install Merge Module:     \\install_machine\software\Sybase\OpenClient157\archives\open_client_mm\open_client.iam.zip
                          Status: ERROR

Install Merge Module:     \\install_machine\software\Sybase\OpenClient157\archives\open_client_mm\open_client.iam.zip
                          Status: SUCCESSFUL
                          Additional Notes: NOTE - Installing: open_client.iam.zip

                          Status: ERROR
                          Additional Notes: ERROR - Open Client: FAILED.  See log file C:\Sybase\log\open_client.log for detail.

 

The successful entries are the installer has installed the software onto the target machine

What is causing the errors in this instance is that the installer modifies the registry and inserts Sybase entries.
However, the installer tries to update the registry entries on the machine that the "setup.exe" is executed from.
Because the installer isn't physically mapped to the target machine, it tries to update the machine it is running on.
The errors can be resolved in one of two ways.

One is to map a physical drive from the target machine to the installer machine.
Such as mapping an alternative drive (F:) to the installer machine.
Two, is to copy the entire installer package to the target machine and run the install from there.

At this point, the installer is installing the software, and modifying the registry on the local machine.

Related Content

Related Documents

Related SAP Notes/KBAs 

https://service.sap.com/sap/support/notes/2170947

https://service.sap.com/sap/support/notes/2151681 

 
  • No labels