Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. "The selected data extension <Custom Extension Name> is not installed or cannot be loaded" error when you load custom extensions in SQL Server 2012 Data Tools

"The selected data extension <Custom Extension Name> is not installed or cannot be loaded" error when you load custom extensions in SQL Server 2012 Data Tools

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You develop a custom Reporting Services data processing extension.
  • The custom data processing extension assembly references a Microsoft.ReportingServices.Interfaces.dll file. The file is included with Microsoft SQL Server 2005 Reporting Services, SQL Server 2008 Reporting Services, or SQL Server 2008 R2 Reporting Services.
  • You install SQL Server Data Tools (SSDT) in Microsoft SQL Server 2012.
  • You deploy the data processing extension assembly by using SSDT.
  • You create a new report server project that is based on the "Business Intelligence" template, and you try to select the custom data processing extension in order to add a new data source.
In this scenario, you receive an error message that resembles the following:
Unable to connect to data source '<Data Source Name>'. The selected data extension '<Custom Extension Name>' is not installed or cannot be loaded. Verify that the selected data extension is installed on the client for local reports and on the report server for published reports.

Notes
  • "Data Source Name" is a placeholder for the data source name, and "Custom Extension Name" is a placeholder for the custom extension name.
  • If you load the custom extension in any SQL Server Reporting Services (SSRS) report and then run the report through an SSRS web service or a web interface, the custom extension runs successfully.
  • This issue is not limited to data processing extensions. You may encounter similar errors when any custom extension references the Microsoft.ReportingServices.Interfaces.dll file that is included with SQL Server 2005 Reporting Services, SQL Server 2008 Reporting Services, or SQL Server 2008 R2 Reporting Services.

↑ Back to the top

Cause

The issue occurs because of a bug in the SSDT setup process.

When SSDT is installed, the following incorrect entries are added to the devenv.exe.config file and to the PreviewProcessingService.exe.config file:
<dependentAssembly><assemblyIdentity name="Microsoft.ReportingServices.Interfaces" publicKeyToken="89845dcd8080cc91" culture="neutral"/><bindingRedirect oldVersion="9.0.242.0" newVersion="10.0.0.0"/></dependentAssembly>
If a custom extension references the Microsoft.ReportingServices.Interfaces.dll file whose assembly version is 9.0.242.0, SSDT will look for the Microsoft.ReportingServices.Interfaces.dll file whose assembly version is 10.0.0.0. However, this newer assembly may not exist on the computer where SSDT is installed.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Resolution

To resolve this issue, use the correct entries in the devenv.exe.config file and in the PreviewProcessingService.exe.config file.

To correct the entry in the devenv.exe.config file, follow these steps:
  • Open the devenv.exe.config file that is in the following location:
    %Program Files%\Microsoft Visual Studio 10.0\Common7\IDE

    Note     The PreviewProcessingService.exe.config file is located in %Program Files%\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies
  • In the devenv.exe.config file, locate the following entry:
    <dependentAssembly><assemblyIdentity name="Microsoft.ReportingServices.Interfaces" publicKeyToken="89845dcd8080cc91" culture="neutral"/><bindingRedirect oldVersion="9.0.242.0" newVersion="10.0.0.0"/></dependentAssembly>
  • Replace the entry with the following:
    <dependentAssembly><assemblyIdentity name="Microsoft.ReportingServices.Interfaces" publicKeyToken="89845dcd8080cc91" culture="neutral" />
    <assemblyIdentity name="Microsoft.ReportingServices.Interfaces" publicKeyToken="89845dcd8080cc91" culture="neutral" /><bindingRedirect oldVersion="8.0.242.0" newVersion="11.0.0.0" /><bindingRedirect oldVersion="9.0.242.0" newVersion="11.0.0.0" /><bindingRedirect oldVersion="10.0.0.0" newVersion="11.0.0.0" /></dependentAssembly>
  • Save the devenv.exe.config file.
  • Close and then reopen Visual Studio or SSDT.
Note The steps to correct the entry in the PreviewProcessingService.exe.config file are the same.

↑ Back to the top

Keywords: kbsurveynew, kbtshoot, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 2750044
Revision : 1
Created on : 1/7/2017
Published on : 9/24/2012
Exists online : False
Views : 352