SQL KURULURKEN ALINAN HATA :sql server setup has encountered the following error failed to retrieve data for this request HATASI

2. Mart 2014 00:31
AŞAĞIDA ÇÖZÜM ÖNERİLERİ VAR. BEN NASIL ÇÖZDÜM? 
CEVAP: REGEDIT AÇTIM VE YEDEĞİNİ ALDIM SONRA İSE  ProductCode GEÇEN KELİMELERİN OLDUĞU SQL SERVER ALANLARINI SİLDİM. SONRA SQL KURABİLDİM. YARIM GÜNÜMÜ ALDI
I hope the advice I sent you last week helped. I've closed this bug since I have not heard a response in more than a week. If you are still having issues please reactivate this bug and provide details. 

Thanks,

Amy Lewis
Posted by Microsoft on 04.05.2008 at 20:49
Todd -

Let me know if this helps:

Case 2 - Installation failed with the error message “Failed to retrieve data for this request”

·         Symptom

When you launch installation, you encounter the error dialog as follows.


The detail setup log contains the following message.


Message: 

        Object reference not set to an instance of an object.

Stack: 

        at Microsoft.SqlServer.Discovery.Feature.GetFeatureInstalledState(FeatureInformation featureInfo)

        at Microsoft.SqlServer.Discovery.Feature.GetColumnData(String column, FeatureInformation featureInfo)

        at Microsoft.SqlServer.Discovery.Feature.AddRow(DataTable dt, FeatureInformation featureInfo)

        at Microsoft.SqlServer.Discovery.Feature.PopulateDataSet(EnumResult result, DataTable contextUrns)

        at Microsoft.SqlServer.Discovery.Feature.GetData(EnumResult erParent)

        at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()

        at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)

        at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)

        at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)



·         Cause

Users wanted to install a new Katmai on a machine where an old Katmai build was installed. Users launched uninstall to remove the old one first. However, uninstall failed for some reasons. Users tried various methods to remove old bits, e.g., delete the entire directory of “C:\Program Files\Microsoft SQL Server”, run some removal tool. Unfortunately those attempts didn’t remove Katmai bits thoroughly. The machine was turned into a corrupted state. 


Users thought the old one had removed, and launched the new installation. During installation setup found ProductCode from Katmai registry key as shown in the example below.



[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\Setup]

"ProductCode"="{B5153233-9AEE-4CD4-9D2C-4FAAC870DBE2}"


It took the value of ProductCode and continued to query Windows Installer engine for its corresponding MSI package. However, MSI package was removed and not present on the machine, which is one of factors as a corrupt state – there was a ProductCode to indicate an MSI, but the MSI was not present at all when setup was trying to read MSI properties. The inconsistency caused setup threw exception and aborted.

·         Solution

The problem has been fixed in CTP6 Refresh. The workaround is to open registry key hive, find the orphan ProductCode as shown above, delete it and launch setup again.

To identify if the registry key value “ProductCode” is orphan or not, go to the following registry key hive, and search the value of ProductCode. 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{B5153233-9AEE-4CD4-9D2C-4FAAC870DBE2}]

If it is not present, it is an orphan ProductCode. If it is present, it means its MSI is still in the machine. 

Thanks,

Amy Lewis

Çıkmış Sorular

WEBŞUBEM

www.hakbil.com


Kategoriler