PDA

View Full Version : Error 1723



DuncanWinner
01-03-2006, 12:30 PM
Hi,

I have just upgraded from InstallShield Express v4 to v11 and upgraded my project.

If I then deploy my package to XP then no problem.

If I deploy to 9x or NT I get the following error...

"Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor."

Has anyone any suggestions?

Thanks in advance,
Duncan

TsungH
01-09-2006, 04:03 AM
You would want to generate and analyze the installation log to identify the custom action causing this error message.

DuncanWinner
01-09-2006, 04:15 AM
Hi,

Thanks for your reply.

I do not have any Custom Actions defined in my project.

If I recreate the exact same project using InstallShield Express version 4.1, I do not have any problems at all.

It seems to be a problem with InstallShield Express version 11.

Regards,
Duncan

TsungH
01-09-2006, 04:55 AM
I will still recommend taking a look at the log.

Another thing that comes to my mind is the version of Windows Installer. InstallShield 11 Express Edition supports Windows Installer 3.1, which does not support some older operating systems. For a list of supported operating systems, you can refer to http://www.microsoft.com/downloads/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en.

You may want to verify Schema property in General Information Properties (http://documentation.installshield.com/robo/projects/isxhelp11/GeneralInfoProperties.htm).

DuncanWinner
01-09-2006, 05:09 AM
I have the Schema (under the Gerneral Information section) set to 200.

I have also got the MSI Engine Version (under the Build Your Release section) set to Version 2.0.

Where can I find the install log? Do I have to enable an option somewhere to generate a log file or does it generate one anyway? Either way where does the log file get generated?

Thanks for your help so far.

Regards,
Duncan

TsungH
01-09-2006, 05:35 AM
Windows Installer does not generate an installation log by default. Depending on your release configurations, you can generate a log as follows.

setup.exe /v"/l*v c:\setup.log"

msiexec.exe /l*v c:\setup.log /i <path_to_your_msi>\your.msi

For a complete list of command line parameters, please refer to Setup.exe Command-Line Parameters (http://helpnet.macrovision.com/Robo/BIN/Robo.dll?tpc=/robo/projects/ISXHelp11/IHelpSetup_EXECmdLine.htm).

DuncanWinner
01-09-2006, 08:09 AM
Hi,

I have run the setup again on a Win 98 SE machine logging the actions as you mentioned. I searched the log and found the error. Here is an extract with a few lines either side of the error 1723...

*** Log ***

MSI (c) (27:37): Doing action: ValidateKeycode.E9DEA130_0DC6_4047_8C57_2A204727CB81

Action start 12:29:44: ValidateKeycode.E9DEA130_0DC6_4047_8C57_2A204727CB81.

MSI (c) (27:37): Creating MSIHANDLE (66) of type 790542 for thread -423881

MSI (c) (27:37): Closing MSIHANDLE (66) of type 790542 for thread -423881

MSI (c) (27:37): Note: 1: 1723 2: ValidateKeycode.E9DEA130_0DC6_4047_8C57_2A204727CB81 3: MsiKC_CheckForSpecificProduct 4: c:\windows\TEMP\MSID2C5.TMP

DEBUG: Error 2835: The control ErrorIcon was not found on dialog SetupError

Internal Error 2835. ErrorIcon, SetupError

Error 1723.There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action ValidateKeycode.E9DEA130_0DC6_4047_8C57_2A204727CB81, entry: MsiKC_CheckForSpecificProduct, library: c:\windows\TEMP\MSID2C5.TMP

MSI (c) (27:37): Product: Traka 32bit Administrator v02.05.0006 -- Error 1723.There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action V
alidateKeycode.E9DEA130_0DC6_4047_8C57_2A204727CB81, entry: MsiKC_CheckForSpecificProduct, library: c:\windows\TEMP\MSID2C5.TMP

Action ended 12:29:47: ValidateKeycode.E9DEA130_0DC6_4047_8C57_2A204727CB81. Return value 3.

Action ended 12:29:47: INSTALL. Return value 3.

MSI (c) (27:37): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1

Action ended 12:29:47: ExecuteAction. Return value 3.

MSI (c) (27:37): Doing action: SetupCompleteError

*** End Log ***

I am not sure what this means but it seems as if Installshield is not able to validate a key code? I am unable to find any relation to the above to my project? Any ideas?

Thanks again for your support.

Regards,
Duncan

TsungH
01-10-2006, 05:53 AM
The names do not ring any bell. I believe that the custom action is in some merge module included in the package.

DuncanWinner
01-10-2006, 06:56 AM
The odd thing is, if I go back to InstallShield v4.1, set up the exact same project using all the same merge modules, I do not have the problem? I only have the problem with version 11?

TsungH
01-10-2006, 07:21 AM
If the names of merge modules selected are identical, the only explanation I could think of would be, the content of those merge modules is different. Perhaps, a newer version of DLLs in some merge modules included in InstallShield 11 Express Edition which are different from those in Express 4.x.