We have an Installscript MSI project type installer. This installer has a SQL connection (SQL Object) and it executes database scripts during the installation process. This installer supports DB connection to a remote SQL Server database server. We reply on Installshield's the schema numbers to conditionally execute the SQL Scripts. We are running into issues during upgrading installation. When running the upgrading installer, the installer does not skip the SQL scripts with lower schema numbers. It fails to detect the schema number in the target database. Here is the Log message: 1: Attempting to execute SQL scripts... 1: Determining if the SQL script 'CreateDB.sql' will be executed... 1: The SQL script will be executed because no schema version is found on the target database. It incorrectly executes the SQL Scripts which should be skipped and It generates duplicate schema numbers in [InstallShield ] table. Is this an Installshield issue? what is the best way to resolve this issue? ... View more

I have a Installscript MSI project. I have a function (see below) in the Script to query database and return a value. This function worked fine in our last released installer which was developed in Installshield 2016. This year, we upgraded Installshield 2016 to Installshield 2019 and then this function stopped working at the following line: // Use the recordset to see if the database exists pADORecordSetObj.Open(sSQL); What can be the cause of this issue? How to catch the exception and get more details on the exception? //********************************************************** function STRING GetDMLANValue(sServerName, sDBName, sDriver) OBJECT pADOConnObj, pADORecordSetObj; STRING sConnString, sSQL, sLine, sDatabase, sLANValue, sError; begin sConnString = CreateConnectionStringIntegrated(sServerName, sDriver, sDBName); //the sConnString is: "Provider=sqloledb;server=(local)\MyDBInstance;database=MyDB;Trusted_connection=Yes;Integrated Security=SSPI";   //the connection string has not changed //MessageBox (sConnString, INFORMATION); // Create the SQL string to retrieve the database if it exists sSQL = "SELECT Value FROM [dbo].[APOCDMSYSCONFIGVALUE] WHERE NAME='Language'"; try // Create ADO Connection Object to connect to the SQL server set pADOConnObj = CreateObject(ADODB.Connection); // Open the ADO Connection pADOConnObj.Open(sConnString); // Create ADO Recordset object for the return set pADORecordSetObj = CreateObject(ADODB.Recordset); // Set some ADO Recordset properties pADORecordSetObj.CursorType = 3; pADORecordSetObj.ActiveConnection = pADOConnObj; // Use the recordset to see if the database exists pADORecordSetObj.Open(sSQL); if (pADORecordSetObj.RecordCount = 1) then sLANValue = pADORecordSetObj.Fields(0); else sLANValue = ""; endif; catch // nothing MessageBox ("Cannot retrieve database record: " , INFORMATION); endcatch; return sLANValue; end; ... View more

I have a product. The installation is InstallScript MSI type. This produce has two release versions: Ver 1, Product Code is A, Upgrade code is B Ver 2, Product Code is C, Upgrade code is B. In Ver 1, it supported operating system AA, BB. In Ver 2, the requirement is to support OS AA, BB, CC for upgrading from Ver1; For new installation, it should only support operating system CC. So I need to validate the operating system based on the installation mode (upgrading or fresh new install.) If it is fresh installation, the installer will stop user if it is operating system AA or BB. What is the best way to do this? What is the right way to detect if the Ver 1 is installed, which has different Product code than the current Version? ... View more

I inherited an InstallScript MSI Project.  I do not have much knowledge in Installshield. I created two Public Properties in Behavior and Logic/Property Manager:  IS_UPGRADE_INSTALL value is 1 PSWEBSITENUMBER value is 0. I also created two new Directories in Additional Tool/Direct Editor/Directory table: PS_PF64_APOC_WORLD : path to folder A PS_IIS_WEB: path to folder B I would like to use these properties and directories in the OnBegin() event of the Script. I put the following code in OnBegin(). but the syntax seems all wrong. I could not find good reference or example on how to use the Properties and Directories in code. Would someone please help me to correct the syntax in these code: function OnBegin() BOOL bInstalled; begin           MsiSetProperty(ISMSI_HANDLE, "IS_UPGRADE_INSTALL", "2"); // try to set 2 to IS_UPGRADE_INSTALL property           MessageBox("<IS_UPGRADE_INSTALL>", WARNING); //try to display the value of IS_UPGRADE_INSTALL          if ("<IS_UPGRADE_INSTALL>" = "2") then //try to check the value                MsiSetProperty(ISMSI_HANDLE, "PSWEBSITENUMBER", "3"); // try to set 3 to PSWEBSITENUMBER                FeatureSetTarget(MEDIA, "<PS_PF64_APOC_WORLD>", "<PS_IIS_WEB>"); //try to set the PS_IIS_WEB value to PS_PF64_APOC_WORLD so PS_PF64_APOC_WORLD will point to the folder of PS_IIS_WEB          endif;         MessageBox("<PS_PF64_APOC_WORLD>", WARNING);  // try to display the directory end; ... View more