| Ticket Hash: | d8491abd0bcb73694388d4d077042c8b0169b871 | ||
| Title: | Installer Error | ||
| Status: | Closed | Type: | Code_Defect |
| Severity: | Important | Priority: | NextRelease |
| Subsystem: | VsDesignerInstaller | Resolution: | Fixed |
| Last Modified: |
2012-01-28 11:37:20 14.30 years ago |
Created: |
2012-01-27 12:09:57 14.31 years ago |
| Version Found In: | 1.0.78.0 | ||
| Description: | ||||
sqlite-netFx40-setup-bundle-x64-2010-1.0.78.0 At install the following error occurs -> could not open registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx .NET 4.0 is fully installed and in the opened commandline window the error seems to be at Installer.exe #38 After the Setup in Server-Explorer no SQLite Database Connection could be created. <hr /><i>anonymous added on 2012-01-27 12:17:14 UTC:</i><br /> Further investigation: It seems that under X64 the Registry path needed is-> HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx <hr /><i>mistachkin added on 2012-01-27 14:10:33 UTC:</i><br /> As a temporary workaround (for VS 2010), you could do the following steps: 1. Install the 32-bit setup without the option checked to run the VS designer components installer. 2. Open a Visual Studio command prompt. 3. Change to the "System.Data.SQLite\2010\bin" install directory. 4. Using the "corflags" tool (part of the .NET SDK), flag the "Installer.exe" tool as 32-bit only (e.g. "corflags /32BIT+ /Force Installer.exe"). 5. Re-sign the "Installer.exe" assembly using a strong name key pair (e.g. sn -Ra Installer.exe System.Data.SQLite.snk). Any SNK file will work here. 6. Run the "Installer.exe" tool using the following command line: Installer.exe -install true -installFlags AllExceptGAC -tracePriority Lowest -verbose true -noCompact true -noNetFx20 true -noVs2008 true -whatIf false -confirm true <hr /><i>mistachkin added on 2012-01-27 14:12:31 UTC:</i><br /> Flagging the Installer.exe tool as 32-bit only may indeed become the official solution to this issue for the next release. <hr /><i>anonymous added on 2012-01-27 15:09:04 UTC:</i><br /> Same here with Fx35. <hr /><i>mistachkin added on 2012-01-27 15:52:01 UTC:</i><br /> Temporary workaround for VS 2008: 1. Install the 32-bit setup without the option checked to run the VS designer components installer. 2. Open a Visual Studio command prompt. 3. Change to the "System.Data.SQLite\2008\bin" install directory. 4. Using the "corflags" tool (part of the .NET SDK), flag the "Installer.exe" tool as 32-bit only (e.g. "corflags /32BIT+ /Force Installer.exe"). 5. Re-sign the "Installer.exe" assembly using a strong name key pair (e.g. sn -Ra Installer.exe System.Data.SQLite.snk). Any SNK file will work here. 6. Run the "Installer.exe" tool using the following command line: Installer.exe -install true -installFlags AllExceptGAC -tracePriority Lowest -verbose true -noCompact true -noNetFx40 true -noVs2010 true -whatIf false -confirm true <hr /><i>mistachkin added on 2012-01-27 15:54:38 UTC:</i><br /> Working on making the installer aware of the WoW64 subsystem, see check-in [13e7a22c1e]. <hr /><i>mistachkin added on 2012-01-27 19:39:38 UTC:</i><br /> Since Visual Studio is currently a 32-bit application, the 64-bit setups will not be able to install the VS designer components because they only physically include the necessary native code for the 64-bit SQLite core, which cannot be loaded into a 32-bit process. That being the case, the workarounds I added above will only work for the 32-bit setups. <hr /><i>mistachkin added on 2012-01-27 22:30:08 UTC:</i><br /> The fixes for this issue will be in the next release, 1.0.79.0, which will be out sometime tomorrow. Thanks for your patience. <hr /><i>mistachkin added on 2012-01-28 11:37:20 UTC:</i><br /> Confirmed fixed, pending release. | ||||