Troubleshooting BI Indexing Connector (SharePoint Server 2010)
Applies to: SharePoint Server 2010
Topic Last Modified: 2011-03-28
|The Microsoft Business Intelligence Indexing Connector free download was removed from the download site. Customers who have downloaded the Business Intelligence Indexing Connector as of March 2011 will continue to be supported as per standard support procedures. However, Business Intelligence Indexing Connector will not be tested or supported for SharePoint Server 2010 Service Pack 1.|
This article describes considerations when you install, configure, and crawl data sources for business intelligence assets by using Microsoft Business Intelligence Indexing Connector.
Business Intelligence Indexing Connector crawls files and can optionally crawl external data sources to data-driven files such as an Microsoft Excel file connected to a Microsoft SQL Server source or a Microsoft SQL Server Reporting Services (SSRS) .rdl file connected to a SQL Server database. This is so that you can see the database name of the data source and also elements of the data, including dimensions and measures of a Microsoft SQL Server Analysis Services (SSAS) cube. The following are considerations and issues that you may encounter when Business Intelligence Indexing Connector crawls Excel and SSRS .rdl files.
Crawling Excel files with custom SQL statements is not supported. If a data source for an Excel file has a custom SQL statement for the data source query, you will receive an error message in an enabled event log that the SQL query cannot be read.
To crawl files for Microsoft SQL Server PowerPivot for Microsoft Excel, you must deploy PowerPivot for Excel 2010 on the instance of FAST Search Server 2010 for SharePoint that is installed on the client. The client files that are crawled must be Excel 2010 files with the same version of PowerPivot for Excel that is installed on FAST Search Server 2010 for SharePoint.
Any changes on the configuration made through the configuration wizard will stop and restart the service after configuration has completed successfully. If the service stops or cannot restart after configuration, review the Unified Logging Service (ULS) log. The ULS writes Microsoft SharePoint Server 2010 events to SharePoint Server 2010 Trace Logs which are located at:
%ProgramFile%\Common Files\Microsoft Shared\web server extensions\14\LOGS.
Collectively this location and its files are commonly referred to as the “ULS Logs” though MSDN calls them the Trace Logs. The ulscommoncore.msi file is installed when FAST Search Server 2010 for SharePoint is installed. If it has not been installed, run ulscommoncore.msi from %FastSetupFolder%\installer\files to enable the Business Intelligence Indexing Connector log file.