msiexec returns 1067 (%ERRORLEVEL%), but installation is rendered as successful in meanwhile
Hi, Whether all the programs get the error message when using msiexec to install? Whether any error message received when trying to install a program? Whether this installed program could run normally? If the program could run with no error, we can consider it has been installed correctly and no need to worry. Regarding the error 1607, it occurs when the InstallShield application is corrupted or is damaged. Follow the methods listed below to test the issue: Method 1: Rename the InstallShield folder 1. In Windows Explorer or in My Computer, open the following folder: DRIVE \Program Files\Common Files\ 2. Right-click the Installshield folder, and then click Rename. 3. Type InstallShield1, and then press ENTER. 4. Try to install the program. 5. If the problem continues to occur, go to Method 2. Method 2: re-register the msiexec and idriver files to test the issue. Hope this helps. Vincent Wang TechNet Community Support
June 15th, 2012 4:46am

I'm working on automation software deployment. When I try to install one product using .bat file. Using command line (like "msiexec /i some.msi /l log.txt /qb-), and then checking the result returned by msiexec (if ERRORLEVEL 0), I got 1067 error. But something very intresting happens - even I got an error, software is installed successfully in meanwhile. Not at once I got the error, but in 20-30 minutes software is installed. During this 20-30 minutes it seems that nothing really happens: No new entries into log file (log.txt, written by msiexec.exe)Process msiexec.exe still exists even it already returned an error into %ERRORLEVEL%No new event appears in eventvwr.msc After this amount of time, following things happens: New entries appear into system log, about successful installation compeletionLog file is written to the end, with corresponding message about successmsiexec.exe disappears from process list What is going on? How can I check from command line that product is successfully installed? I can only mention two factors: Such installations are primary made on Windows 2008 R2 Server (but sometimes such behavior is observed on Win Pro 7 x64)Installation is made in terminal sessionInstallation often longs about 1-2 hours (heavy product with a lot of custom actions), even successful Can I just ignore 1067 error and wait about 1 hour and be sure the product is installed? Can it be caused by terminal session? P.S. Sorry for inappropriate forum, I didn't find any more matching place for this. Feel free to transfer it to corresponding forum.
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2012 11:15am

Though this http://support.microsoft.com/kb/888019 (and/or http://www.fixyourerrorcodes.com/error-1607 ) is for W XP, there are steps, that can be tested in W 7. Regards Milos
June 17th, 2012 3:15pm

Hi, Whether all the programs get the error message when using msiexec to install? Whether any error message received when trying to install a program? Whether this installed program could run normally? If the program could run with no error, we can consider it has been installed correctly and no need to worry. Regarding the error 1607, it occurs when the InstallShield application is corrupted or is damaged. Follow the methods listed below to test the issue: Method 1: Rename the InstallShield folder 1. In Windows Explorer or in My Computer, open the following folder: DRIVE \Program Files\Common Files\ 2. Right-click the Installshield folder, and then click Rename. 3. Type InstallShield1, and then press ENTER. 4. Try to install the program. 5. If the problem continues to occur, go to Method 2. Method 2: re-register the msiexec and idriver files to test the issue. Hope this helps. Vincent Wang TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2012 4:21am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics