Dear Reader, I have sql 2008 32 bit with default instance name "Anaylsis, Integration, and Reporting services are installed", while I was setuping a software I got the following error then the software was rolled back "NOtE: the component which failed is Reporting component" "Software is FEP 2010 on SCCM 2007 SP2 R2 - all per-requisities are met and I have deployed serveral times before and I was not getting this error" [5/17/2011 8:59:19 AM][Normal]> Error: MSI installer detected an unexpected problem. Error message: Error 26204.Error -2147217900: failed to execute SQL string, error detail: Cannot fetch a row from OLE DB provider "SQLNCLI10" for linked server "SelfLinkedServer"., SQL key: SQL.Script.SetFEPServer SQL string: EXEC spFEP_Infra_SetServersNames 'SiteName-SCCM\','SiteName-SCCM\' So Mostly my issue with SelflinkedServer > SQLNCLI10 so: What The Self linked Server perpose? What do SQLNCLI10 Do "since its installed with SQL"? What is the default settings for it? How can we fix the issue? Thanks

Hi Jean M, When installing SCCM 2007 or FEP 2010, MSI installer service would be started automatically, and help install files, create necessary database structure, and so on. The error message is telling us that the MSI installer cannot connect to a Linked server whose name is "SelfLinkedServer" with OLE DB provider SQLNCLI10. For now, this is actually a SCCM or FEP installation problem, and I'd suggest you ask questions to SCCM or FEP forum instead as we only discuss SQL Server Reporting service here (I noticed that you have SQL Server Reporting service installed, and the failed reporting component belongs to FEP). To answer your question, 1. Usually, self linked server is useful for testing remote queries. The server provides a login name and password to connect to itself while performing queries. 2. SQLNCLI10 refers to SQLNCLI10.dll which is SQL Server Native Client 10.0 OLE DB Provider provided by Microsoft. It is a low-level COM API that is used for accessing data. You can find more information here, http://msdn.microsoft.com/en-us/library/ms131687.aspx For point 3, I am not sure if it is created by setup files or created by someone else. By default, SQL server won't create such linked server after we install a fresh SQL server instance. For point 4, I am also not sure how to fix it as it is a setup problem. But, if the linked server is created incorrectly by someone, you may decide to remove it from SQL server and re-install the applications. Thanks for the understanding, Eileen