Error Code 1605 Sql Server 2008
Contents |
was installing newly released Visual Studio 2010 RTM on my Windows 7 running PC and Setup encountered the error while installing SQL Server 2008 Express Service Pack 1. Actually msigetproductinfo failed to retrieve productversion for package with product code 1608 I was using pre-release version of Visual Studio 2010 (RC) and uninstalled before sql server setup has encountered the following error msigetproductinfo failed to retrieve prior to install retail release (RTM) of Visual Studio 2010 as instructed. Everything went fine except Visual Studio 2010 RTM sql server setup has encountered the following error invoke or begininvoke Setup that logged the error in log file. [04/13/10,10:00:09] Microsoft SQL Server 2008 Express Service Pack 1 (x64): [2] Error code 2064843076 for this component is not recognized. [04/13/10,10:00:09] Microsoft SQL Server
Sql Server Setup Has Encountered The Following Error The Given Key Was Not Present In The Dictionary
2008 Express Service Pack 1 (x64): [2] Component Microsoft SQL Server 2008 Express Service Pack 1 (x64) returned an unexpected value. Then I tried to install SQL Server 2008 Express manually (out of Visual Studio setup) to know the exact error message and it was- MsiGetProductInfo failed to retireve ProductVersion for package with Product Code = ‘{AA4A4B2C-0465-3CF8-BA76-27A024D8ACAB}’. Error code: 1605 The GUID {AA4A4B2C-0465-3CF8-BA76-27A024D8ACAB} may different on sql server setup has encountered the following error 0x84b10001 different machines After observing few aspects, I got the solution and would like to share it with you. To fix the error, you need to follow these simple steps. How To: 1. Run Registry Editor (type regedit in Start Search or Run dialog box and press enter) and navigate to- HKEY_CLASSES_ROOT\Installer\UpgradeCodes 2. Take the first part of GUID and reverse it, in my case it is AA4A4B2C and its reverse string is C2B4A4AA. Now search for C2B4A4AA and you’ll get a match than delete the its parent subkey (it will be a kind of GUID without braces). 3. Now run the Setup again, it will go smoothly without any hassle. Applies To: SQL Server 2008 SQL Server 2008 Express Share this:TweetEmailPrintFiled Under: Visual Studio Tagged With: Help & How-to, SQL Server 2008, x64, x86 Microsoft discounts $150 on Surface 3 Pro and Surface 3 plus Type Cover Best Black Friday Deals 2015 – $299 Xbox One Black Friday Deals & Sales Black Friday and Cyber Monday deals on Target.com: 15% off sitewide Amazon, Walmart, Microsoft Black Friday Deals go live ahead of Thanksgiving Day Amazon, Walmart Black Friday Deals on HP Laptops and Desk
3, 20101 0 0 0 Sometime remnants of a previous installation/ a failed install can prevent us from reinstalling SQL server I have documented the consequence of one such instance which rendered us to be unable to sql server setup has encountered an error when running a windows installer file install SQL 2008 from the server · When we launched
Sql Server Setup Has Encountered The Following Error C Windows Installer
the setup we got the following error : SQL Server Setup failure. 1 SQL Server Setup has encountered the
Sql Server Setup Has Encountered The Following Error Hexadecimal Value 0x00
following error: MsiGetProductlnfo failed to retrieve Productversion for package with Product Code = ‘{DF167CE3-60E7-44EA-99EC-2507C 5 1F37AE}’. Error code: 1605.. We got the obfuscated product code : ------------------ Obfuscated product code http://www.windowsvalley.com/fix-sql-server-setup-has-encountered-the-error-code-1605/ Result ------------------ 3EC7S1FD7E06AE4499CE52705CF173EA ------------------ OK ------------------ · Went into the registry (start->run->regedit) and took a full registry backup · We then went to the following key HKEY_CLASSES_ROOT\Installer\UpgradeCodes · We then used the obfuscated product code : 3EC761FD-7E06-AE44-99CE-52705CF173EA · We searched for it within the registry key HKCR\Installer\UpgradeCodes for matches. · We got one match and deleted its parent. · We https://blogs.msdn.microsoft.com/amruthavarshinij/2010/11/03/unable-to-install-sql-2008-due-to-the-remnants-of-a-previous-installation/ ran the installation which failed yet again with this error : TITLE: SQL Server Setup failure. -------------------- SQL Server Setup has encountered the following error: MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = ‘{DF167CE3-60E7-44EA-99EC-2507C51F37AE}'. Error code: 1605.. -------------------- BUTTONS: OK -------------------- · We navigated to this key :HKEY_CLASSES_ROOT\Installer\Features\3EC761FD7E06AE4499CE52705CF173EA and saw that we were having issues (access denied ) issues with it · We obfuscated the GUID again : DF167CE360E744EA99EC2507C51F37AE , we searched for it and found a key · We added everyone to the root and added the full control to administrators, System and even replace permission entries to all sub-keys. Same error. · Since we not have any special changes/permissions set, decided to reset the registry permissions(needs to be used with caution , contingent on the fact that we do not have customized permissions set on the registry) · We used the KB : http://support.microsoft.com/kb/313222 to reset the permissions so that the setup program will have access to it · We got this error again from the setup: MSI error description: Could not open key: UNKNOWN\Components\00C004FEE241478418DBB8505B78CBC5\D56941F2B76595E4DABEA0C21C3E
SQL Server 2008 R2 - Error code:1605 October 11, 2011 8 Comments Yet another post on SQL Server 2008 https://slecluyse.wordpress.com/2011/10/11/sql-server-2008-r2-error-code-1605/ R2 deployment woes. An unattended installation of SQL Server 2008 R2 - developer/management tools on Windows XP SP3 clients in this particular case - might fail with the following http://gaurangpatel.net/solving-msigetproductinfo-failed-to-retrieve-productversion-for-package-with-product-code-8bdd006d-d5f0-4aaa-ba13-65995063ec44-error-code-1608 error: MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{0A869A65-8C94-4F7C-A5C7-972D3C8CED9E}'. Error code: 1605. The error appears in Summary_%computername%_%date%_%time%_ComponentUpdate.txt and other log files as described here: sql server View and Read SQL Server Setup Log Files. Error 1605 This record of Windows Installer error codes on MSDN lists 1605 incorrectly as an indicator for not enough free space available on the target drive; DesktopEngineer.com however, states that 1605 designates a missing product, required to complete a custom action successfully: 1605 ERROR_UNKNOWN_PRODUCT This action is sql server setup only valid for products that are currently installed. Windows Installer GUIDs In order to figure out what missing product might be the culprit, we'll check a working installation for the GUID specified in the error message. Windows Installer GUIDs have a different formatting than how they appear in the MSI tables. In this specific case, the product code {0A869A65-8C94-4F7C-A5C7-972D3C8CED9E} needs to be transformed into its equivalent which is stored in the registry. Some swapping and reversing needs to be done: Reverse the first 8 digits Reverse the next 4 digits Reverse the next 4 digits Reverse the next 2 digits (8 times) Drop all hyphens Applying the above transformation to {0A869A65-8C94-4F7C-A5C7-972D3C8CED9E} results in 56A968A049C8C7F45A7C79D2C3C8DEE9. Search for the value in the registry and soon MSXML appears to be the wrongdoer. MSXML6 Now back to the client where the installation fails. Repeat the same search and you'll probably notice that XML 6.0 Parser actually is present on the erroneous machine too, confirmed by the XML Parser entry found in appwiz.c
failed to retrieve ProductVersion for package with Product Code = ‘{8BDD006D-D5F0-4AAA-BA13-65995063EC44}'. Error code: 1608 Today I got call from one of my friend for help in installing SQL Server 2008 R2. Apparently, he somehow cancelled the installation at very beginning of process for some reason and then every single attempt to install it again failed with really weird error. To resolve this problem, we removed registry entries leftover, removed any and every temp files and folders created by SQL Server installation but nothing helped. All the time we get this strange error, MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = ‘{8BDD006D-D5F0-4AAA-BA13-65995063EC44}'. Error code: 1608 With little hope I fired up firefox and search google with this string. With little surprise, we were not the only ones who are getting this error. And there were numerous blogs and solutions about it. Though none seem to have explanation why we are getting this error but all seem to suggest one common solution. All we needed to do is to reverse the GUID and simply search of it in registry. In our case it was D600DDB8 (just the first part), and we searched registry with that parameter and deleted all the entries we encountered (Ofcourse we took backup of registry before deleting anything as removing wrong entry could be fatal in Windows). I think we deleted about 2-3 entries and then restarted the installation. This time it just worked and went all the way to end !!! So I think moral of story is, Don’t touch Microsoft product while it is being installed or else you will have to find hack to get it working again !! It’s Just A Thought … Random Posts: SQL Agent Error : Unable to start JobManager thread for job XXXX Issue with Backup sets of Backup in SSMS 2012 Introduction to Indexing …. and SQL Server RAISERROR with TRY … CATCH block Monitoring SQL Server using Alerts Similar Posts: SQL Server Installation Rules and “System Reboot Required” Error SQL Agent Error : Unable to start JobManager thread for job XXXX Deploying AdventureWorks Analysis Database .. Remote Debugging in SQL Server Management Studio … Database …. Introduction to SQL Server Bug, SQL Server This entry was posted by Gaurang on March 9, 2011 at 9:35 pm, and is filed under Bugs, SQL Server. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own s