tag:blogger.com,1999:blog-5238131531249720750.post4840405873020416115..comments2024-01-22T04:58:27.847+01:00Comments on Everything SQL Server Compact: How to detect if the x64 SQL Compact 3.5 SP2 desktop runtime is installedErikEJhttp://www.blogger.com/profile/12641272161018114573noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-5238131531249720750.post-60440031401182146372016-05-04T03:03:21.359+02:002016-05-04T03:03:21.359+02:00Thanks Erik. We'll consider private deployment...Thanks Erik. We'll consider private deployment again.<br /><br />HarryHarryhttps://www.blogger.com/profile/00081347210690182994noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-3439540131384871292016-05-03T12:59:57.253+02:002016-05-03T12:59:57.253+02:00Harry: Have you considered private deployment?Harry: Have you considered private deployment?ErikEJhttps://www.blogger.com/profile/12641272161018114573noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-85655372145204062016-05-03T03:13:40.735+02:002016-05-03T03:13:40.735+02:00Hi Erik
One of the users kindly sent us the scree...Hi Erik<br /><br />One of the users kindly sent us the screenshot of "Programs and Features". It shows only "Microsoft SQL Server Compact 3.5 SP2 ENU" and "Microsoft SQL Server Compact 3.5 SP2 x64 ENU" are installed. There is no other SQL Server installed.<br /><br />On this user's computer, our installer finds the x86 version is the new one 3.5.8080, but the x64 version is the old one 3.5.5692 (based on the registry data above). So our installer tries to install the SP2 x64, but fails.<br /><br />Most of the users have x86 version is the old one 3.5.5692, and the x64 version is the new one 3.5.8080. So our installer tries to install the SP2 x86, but fails.<br /><br />We suggest them to uninstall all the Microsoft SQL Server Compact 3.5 and install again. This solves the problem. But since a lot of users have this problem and come to us for a solution, we need to find a way to solve this problem.<br /><br />Regards<br />Harry<br />Harryhttps://www.blogger.com/profile/00081347210690182994noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-43875754921803752802016-05-02T20:08:00.898+02:002016-05-02T20:08:00.898+02:00Harry: maybe they have a mixed install? Meaning x8...Harry: maybe they have a mixed install? Meaning x86 components are old, and the x64 bits are new?ErikEJhttps://www.blogger.com/profile/12641272161018114573noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-33885313633790912812016-05-02T07:31:46.418+02:002016-05-02T07:31:46.418+02:00Hi Erik,
We use the Advanced Installer default se...Hi Erik,<br /><br />We use the Advanced Installer default setting to detect the version number. It checks the registry data <br />"[HKLM]\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server Compact Edition\v3.5\Version" for the version number of SQL Server Compact 3.5 x86<br />"[HKLM]\SOFTWARE\Microsoft\Microsoft SQL Server Compact Edition\v3.5\Version" for the version number of SQL Server Compact 3.5 x64<br /><br />However, many of our users have a problem. They have installed SQL Server Compact 3.5 SP2. It is listed in the Control Panel -> Programs and Features. But on some machines, the x86 registry value somehow keeps the SP1 version number 3.5.5692. On some machines, the x64 registry value keeps the SP1 version number.<br /><br />This causes the installer try to install the SP2 again, but fails because the SP2 has been installed acutally.<br /><br />Do you know why? Would this happen to the suggested registry value "DesktopRuntimeVersion" too?<br /><br />Harryhttps://www.blogger.com/profile/00081347210690182994noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-25738265336783073742010-06-26T10:38:08.323+02:002010-06-26T10:38:08.323+02:00Hmm. Yes, the existing installer sees SP1 is no l...Hmm. Yes, the existing installer sees SP1 is no longer installed, and then downloads it, only to find that it's already installed when run.<br /><br />I guess I need a new strategy. :(A Wieserhttps://www.blogger.com/profile/10113336609848585467noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-47995973546184397882010-06-26T10:32:47.229+02:002010-06-26T10:32:47.229+02:00Yes, that's true.
My code checks for those sp...Yes, that's true.<br /><br />My code checks for those specific product ID's then downloads the SP2 installers from my website though if they're not there, so I guess the only issue is what happens when SP3 comes along and my code tries to install SP2.<br /><br />I probably have a similar problem with SP1 at the moment.A Wieserhttps://www.blogger.com/profile/10113336609848585467noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-74357761197364318952010-06-26T10:12:25.953+02:002010-06-26T10:12:25.953+02:00Sounds doable, but the product IDs could change.Sounds doable, but the product IDs could change.ErikEJhttps://www.blogger.com/profile/12641272161018114573noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-24084559433315003672010-06-26T09:47:08.949+02:002010-06-26T09:47:08.949+02:00Hi Erik,
I check to see if it's installed by ...Hi Erik,<br /><br />I check to see if it's installed by checking for the installed product codes of:<br />{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3} for the 64 bit version and {3A9FC03D-C685-4831-94CF-4EDFD3749497} for the 32 bit version using MsiQueryProductState (extracted from Orca).<br /><br />Does that sound like a reasonable strategy or do I have to change to looking at registry keys?A Wieserhttps://www.blogger.com/profile/10113336609848585467noreply@blogger.com