Error 1605 Sql Installation
Contents |
retrieve ProductVersion while installalling SQL 2008R2 RECOMMENDED: Click here to fix Windows errors and improve system performance This week we will discuss one of the most common error messages we get while we error code 1605 sql server 2008 install SQL 2008 /R2 version of Windows. This is the third article of
Windows Installer Error 1605
SQL Troubleshooting series we started two weeks ago. Last week we discussed issues caused by Performance counters issues. MsiGetProductInfo failed windows installer error 1605 outlook 2010 to retrieve ProductVersion This week we are going to discuss the error: MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = ‘{A2122A9C-A699-4365-ADF8-68FEAC125D61}’ Error code 1605 or 1608. The GUID will vary msigetproductinfo failed to retrieve productversion for package with product code 1608 case to case so for this article I’m going to use this particular GUID. The main reason why we get this error message is because of the left overs ofpervious version of SQL. So if it’s a fresh install say on a new computer or a PC that never had SQL before you mostly probably won’t be getting this error message. So there are actually two
Sql Server Setup Has Encountered The Following Error Invoke Or Begininvoke
ways to resolve this problem. One the traditional method and the other is something we came up with. So always I would recommend to follow the traditional method. Method 1: This method is where we will find the GUID responsible for in the registry and delete it. Unfortunatelyit’s not as easy as it sounds. How it works is we need the reverse search the GUID to find it in the registry. That’s that’s weird I know well that’sonly way to get it to work. First setup is exit the install and shutdown all the applications Then go toregistry and create a backup of the registry. Follow this article Backup and Restore Registry in Windows. Now go to paste the GUID in a note pad then reverse the value i.e. {A2122A9C-A699-4365-ADF8-68FEAC125D61} change to {C9A2212A-996A- …. } Now go to Edit and click on File and type in {C9A2212A-996A- …. } Advertisement ^ Once you find the key delete it. Some cases the installer will give you multiple key. So you need to search each keys that you get the error message and delete it. Once you are down go ahead and reboot your system and try to in
use the previous link instead. Select a product Sort by Default Summary New or Updated Description Date Updated Direction Ascending Descending Helpful search tips Find the answer to your question Error Code 1605 sql server setup has encountered the following error msigetproductinfo failed to retrieve or 1608 When Attempting to Install SQL Server® 2008 R2 Answer ID 27112 | Updated sql server setup has encountered the following error error code 0x84b10001 09/10/2016 12:13 PM You are attempting to install the ACT7 SQL Server 2008 R2 instance when you receive the following error
Sql Server Setup Has Encountered An Error When Running A Windows Installer File
message:"MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{GUID}'. Error code: 1605." Or "MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{GUID}'. Error code: 1608." To resolve this issue, use http://www.thewindowsclub.com/msigetproductinfo-failed-to-retrieve-productversion the following steps: Note: The following information is provided as a convenience. Sage does not provide support for Microsoft® Products. For more information on this topic go to Microsoft.com. Click the Windows® Start button and select Run. The Run dialog box appears. In the Select field, type regedit. The Windows Registry appears. Note: For Windows Vista® and Windows® 7 operating systems, enter regedit in the Search field. Caution: We strongly recommend http://kb.act.com/app/answers/detail/a_id/27112/~/error-code-1605-or-1608-when-attempting-to-install-sql-server%C2%AE-2008-r2 that you back up the system registry before making any changes. Incorrect changes to the registry could result in permanent data loss or corrupted files. Please make sure you modify only the keys specified. For detailed information on backing up the Windows Registry, click the link below: Title: How to Backup the Windows Registry Answer ID: 13807 Navigate to the following location and left click on the UpgradeCodes folder to select it: HKEY_Classes_Root\Installer\UpgradeCodes. Using the File \ Export option: export the UpgradeCodes folder using the Selected Branch export range. Rename the UpgradeCodes folder to UpgradeCodesOld. Install Microsoft SQL Server 2008 R2 manually. For instructions on installing Microsoft SQL Server 2008 R2 manually, see the following Knowledgebase article: Title: How to Manually Create the Microsoft® SQL Server® 2008 R2 (Express Edition) ACT7 Instance Answer ID: 26994 Using the File \ Import option: import the exported UpgradeCodes folder created in step 4. Launch the Sage ACT! installation process. WARNING! This KB article (including any software and related documentation) is provided "AS IS." Swiftpage disclaims all express or implied warranties of any kind with respect to the article, including but not limited to, any implied warranties of merchantability or fitness for a particular purpose. ©2016 Swiftpage ACT! LLC. All rights reserved. Swiftpage, ACT!, and the Swiftpage
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 https://blogs.msdn.microsoft.com/amruthavarshinij/2010/11/03/unable-to-install-sql-2008-due-to-the-remnants-of-a-previous-installation/ be unable to install SQL 2008 from the server http://serverfault.com/questions/403525/sql-server-setup-failure · When we launched the setup we got the following error : SQL Server Setup failure. 1 SQL Server Setup has encountered the 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 sql server code : ------------------ Obfuscated product code 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. · sql server setup We got one match and deleted its parent. · We 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 acc
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top SQL Server Setup failure up vote 0 down vote favorite i uninstall sql server 2008 r2 and then install it but now i receive an error: TITLE: SQL Server Setup failure. SQL Server Setup has encountered the following error: MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{A2122A9C-A699-4365-ADF8-68FEAC125D61}'. Error code: 1605.. BUTTONS: OK sql-server sql-server-2008 share|improve this question asked Jun 28 '12 at 23:30 Mohsen Sarmast migrated from stackoverflow.com Jun 29 '12 at 18:05 This question came from our site for professional and enthusiast programmers. add a comment| 3 Answers 3 active oldest votes up vote 3 down vote go to start menu Run -> regedit Edit HKEY_CLASSES_ROOT\Installer\UpgradeCodes rename UpgradeCodes to UpgradeCodesOld Reinstall SQL SERVER again share|improve this answer edited Feb 12 '13 at 9:52 Tom O'Connor 23.6k854132 answered Feb 12 '13 at 9:15 moez 312 Hi @moez. Thanks for your first post on ServerFault, but I'd like to remind you that it's primarily an english language site. I've translated your answer from French with the help of Google Translate, but I'd like it more if you'd do this yourself in future! Thanks! –Tom O'Connor Feb 12 '13 at 9:53 add a comment| up vote 0 down vote Reference SOLUTION (Worked at my end) ***************** Get the Product Code = '{0826F9E4-787E-481D-83E0-BC6A57B056D5}' from the error message that you are getting. Byte reverse the first part from 0826F9E4 to 4E9F6280. Search in the registry under HKEY_CLASSES_ROOT\Installer\UpgradeCodes and try to find a match. Take a backup of the registry and delete the parent key. Re-run the Upgrade and if it fails again for a different GUID, then repeat the steps stated above. In my case, I had to repeat these steps thrice as there were 3 other locations where I needed to change the product code. Then the setup was successful. share|improve this answer answered Jun 28 '12 at 23:44 B