I have an InstallScript custom action where I'm trying to execute a stored procedure that has an out parameter. I'm using ADO to accomplish this. This is what I have so far. set oConn = CreateObject("ADODB.Connection"); /* I open the connection string using the Oracle ODBC driver. I've tested it and am able to execute select queries off of it and get results, so I know it works. */ set oCommand = CreateObject("ADODB.Command"); oCommand.ActiveConnection = oConn; oCommand.CommandType = AD_CMD_STORED_PROC; oCommand.CommandText = "myStoredProcedureName"; set oParams = oCommand.Parameters; set oParam1 = oCommand.CreateParameter("myParam", AD_VARIANT, AD_PARAM_OUTPUT, 10); oParams.Append(oParam1); oCommand.Execute; szResult = oParam1.Value; So my stored procedure has a varchar2 out parameter, and I want to get that value back after executing the stored procedure. I get an error after trying the Execute method where it says "Parameter type is not supported". I think this is in reference to the use of adVariant for VARCHAR2. I see a note saying ADO doesn't support adVariant, but that's what maps to Oracle VARCHAR2. I've tried adVarChar instead of adVariant, but then I get a generic error message instead. Can anyone help me with the syntax for making this stored procedure call? There isn't much guidance out there for doing this in InstallShield. Thanks. ... View more

I have a custom action that calls an InstallScript function to copy files from a resource folder relative to my MSI file and place them on the target system. This custom action executes as Deferred in System Context. The system context is needed because the files will fail to be copied if UAC is enabled. However, the customer also wants to be able to install from a mapped network drive. This is a problem, because custom actions running Deferred in System Context will fail to access network shares because they are running under the SYSTEM account, (in SMB terminology a 'NULL User') which is disallowed in Windows. So, it seems if I have my custom action run in system context, it will fail to install from a network location. If I have it as non-system, it fails due to UAC restrictions. Is there a way to satisfy both of these customer demands? (1. Install from a mapped network drive 2. Install with UAC enabled) It seems like I've hit a catch-22 or something. ... View more

I'm trying to connect to Oracle as the SYS user using ADO in an InstallScript function, but I keep getting an error saying I need to connect as sysdba. I've followed the steps in this post but to no avail. My connection string is Provider=OraOLEDB.Oracle;Data Source=MyDatabase;User ID=SYS;Password=password; In the ISSQLDBMetaData table in Direct Editor, I've changed the following columns to these values: AdoDriverName: {Oracle in client11_home1} AdoCxnServer: DBQ= ISAttributes: 6 AdoCxnAdditional: DBA Privilege=SYSDBA When I connect as SYSTEM, without as sysdba, things work fine. But when I try as SYS, it fails to connect. If I add AS SYSDBA to the password field in my connection string, I get an invalid password error. I'm not sure what I'm doing wrong. Help please. ... View more

I have a Basic MSI project and I want the user to be able to uninstall the application from Add/Remove Programs. I know this method only performs the Execute sequence to silently uninstall the app. My dilemma is, I need to uninstall some database stuff and need the user to enter the password to access it. For security reasons, I can't store this password anywhere. Is there any way for me to gather user input when removing software through ARP? ... View more

I have an InstallScript function that checks if a directory exists in a location relative to the MSI file. When I run the installer from a location on a network drive I have mapped to my local machine, it fails to find the directory. I have tried using both ExistsDir(SourceDir^myDirectory) and Is(PATH_EXISTS, SourceDir^myDirectory) and both return false if the directory it's looking for is located on a mapped network drive (located off the target machine). The directory exists, I can copy the path that is passed into the function and access it myself. The MSI I'm launching is also located on the same mapped drive when this occurs. Is there a way to check if a directory exists or not in InstallScript even if it's located outside the target machine? ... View more

I have a Basic MSI project and during the middle of the Execute phase of the installation, I lost power. I had already set some registry keys, and placed files in folders on the target system. However, the product wasn't registered with Windows (there is no key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall), so Windows doesn't think the product is installed. So when I try to uninstall through the MSI by running maintenance mode, it gets an error because Windows doesn't see it as installed. If I try to run the MSI again, it installs as if the product hadn't been installed. Is there a best practice concerning what to do in these situations? ... View more