https://bugs.winehq.org/show_bug.cgi?id=43093
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |0e29f314f5a344f3d5258c88077 | |411837905e3aa Component|-unknown |msi
--- Comment #1 from Zebediah Figura z.figura12@gmail.com --- This appears to be due to commit 0e29f314f5a344f3d5258c88077411837905e3aa. The installer attempts to call the function MsiGetDatabaseState from within a custom action, using the installer handle. This fails on Windows, so it uses GetActiveDatabase to get the real database handle instead. This can be seen from logs—if you create the directory %Application Data%/Caphyon/Advanced Installer/, the program will dump a file AI_ResourceCleaner.log which contains the following lines on Windows (cut for brevity):
| ProductCode: {E80C09B5-A296-47E9-BD4B-BCCF2FDCA13E}. OnAiRemoveFileImmediate start. | MsiTableReader: Getting the active MSI database for this installation session... | Build JOINed tables CustomActionData string... | SELECT Join Query: [SELECT * FROM `RemoveFile`, `AI_RemoveFile` WHERE `RemoveFile`.`FileKey` = `AI_RemoveFile`.`RemoveFile`]. | MsiTableReader::ExecuteQuery [SELECT * FROM `RemoveFile`, `AI_RemoveFile` WHERE `RemoveFile`.`FileKey` = `AI_RemoveFile`.`RemoveFile`]...
but the following lines under WINE:
| ProductCode: {E80C09B5-A296-47E9-BD4B-BCCF2FDCA13E}. OnAiRemoveFileImmediate start. | MsiTableReader: Using the given MSI database handle (opened by the caller)... | Build JOINed tables CustomActionData string... | SELECT Join Query: [SELECT * FROM `RemoveFile`, `AI_RemoveFile` WHERE `RemoveFile`.`FileKey` = `AI_RemoveFile`.`RemoveFile`]. | MsiTableReader::ExecuteQuery [SELECT * FROM `RemoveFile`, `AI_RemoveFile` WHERE `RemoveFile`.`FileKey` = `AI_RemoveFile`.`RemoveFile`]... | Error executing the query ! 6
Reverting 0e29f31, as with the attached patch, seems to allow the program to progress past this hang at least (although others seem to show up later.)
Unfortunately, this may not be a permanent solution. As is given in https://www.winehq.org/pipermail/wine-patches/2007-November/046636.html, applying this patch would seem to break the Microsoft Office 2007 installer. I don't have that installer, however, so I can't test it, or try to find a unified solution.