I'm trying to repackage a Setup.exe into an MSI for an upgrade this weekend and keep running into trouble when I try to use the repackaged MSI. When I try to install it I keep getting an MSI error 2343, Specified path is empty message when I run the MSI file.

The instance that I monitored the installation for is working correctly, and there are no major differences between the original system and the one that I'm trying to test the MSI on. After turning on Installation Monitoring I have discovered the following in the logs leading up to the error.

MSI (c) (2C:5C) [14:08:12:593]: Note: 1: 2205 2:  3: MsiAssembly 
MSI (c) (2C:5C) [14:08:12:593]: Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`,  `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE  `MsiAssembly`.`Component_` = `Component`.`Component` AND `MsiAssembly`.`Component_` = ? 
MSI (c) (2C:5C) [14:08:12:593]: Disallowing installation of component: {D93EBF7D-1D53-11D4-A53C-0090278A1BB8} since the same component with higher versioned keyfile exists
MSI (c) (2C:5C) [14:08:12:593]: Allowing installation of component: {B7F3DAA8-A87F-4A3B-AE74-43F9F95C1BC1} even though a modified unversioned keyfile exists and file versioning rules would disable the component
Action ended 14:08:12: CostFinalize. Return value 1.
MSI (c) (2C:5C) [14:08:12:593]: Doing action: ISIS_SQLSERVER_AUTHENTICATION
MSI (c) (2C:5C) [14:08:12:593]: Note: 1: 2343 
Error 2343.Specified path is empty.
MSI (c) (2C:5C) [14:16:00:968]: Product: iMIS 15 -- Error 2343.Specified path is empty.
The original monitored installation is working correctly, and I can't figure out what is missing from the MSI that is preventing it from installing. From this log I would guess something to do with the ISIS_SQLSERVER_AUTHENTICATION, but I can't find anything relevant to my product. It is an application that uses a MSSQL database on the back end and authenticates against SQL user accounts. Thank you for any direction for where to look for a resolution to this issue.