Skip to main content
Nintex Community Menu Bar

Known Issue: Custom Reporting Services component (SOURCECODE data source) not visible

  • February 16, 2021
  • 0 replies
  • 46 views
  • Translate

MillaZ
Nintex Employee
Forum|alt.badge.img+21
  • Nintex Employee
  • 682 replies
 

Known Issue: Custom Reporting Services component (SOURCECODE data source) not visible

LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

 

Introduction

After installing K2 blackpoint or K2 blackpearl the SOURCECODE data source in Visual Studio required for designing custom reports is missing.

 

 

Error Message

There are no error messages, however the SOURCECODE data source in Visual Studio does not display.

Workaround

The error can be resolved by following the steps below:

Validating the SQL Business Intelligence Development Studio

If you are encountering issues when designing custom reports using the SQL Business Intelligence Development Studio on top of Microsoft Visual Studio, the following configuration must be checked:

  • The assembly SourceCode.Data.SmartObjectsClient.dll must be present in
    • In Visual Studio 2010 - [InstallDrive]Program Files (x86)Microsoft Visual Studio 10.0Common7IDEPrivateAssemblies
    • In Visual Studio 2012 - [InstallDrive]Program Files (x86)Microsoft Visual Studio 11.0Common7IDEPrivateAssemblies
    • In Visual Studio 2013 - [InstallDrive]Program Files (x86)Microsoft Visual Studio 12.0Common7IDEPrivateAssemblies
    • In Visual Studio 2015 - [InstallDrive]Program Files (x86)Microsoft Visual Studio 14.0Common7IDEPrivateAssemblies

If the DLL is not present, ensure that it is copied there manually

  • In the RSReportDesigner.config file, the following section should be added:
    <Configuration>
    <Extensions>
    <Data>
    <Extension Name="SOURCECODE" Type="SourceCode.Data.SmartObjectsClient.SOConnection,SourceCode.Data.SmartObjectsClient, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16A2C5AAAA1B130D"/>
    </Data>
    <Designer>
    <Extension Name="SOURCECODE" Type="Microsoft.ReportingServices.QueryDesigners.GenericQueryDesigner,
    Microsoft.ReportingServices.QueryDesigners"/>
    </Designer>
    </Extensions>
    </Configuration>

Configuration file changes for the K2 for Reporting Services component

If you are encountering issues with the Reporting Services component, validate that the following configuration changes were made to the appropriate files, located in the following folder:

C:Program FilesMicrosoft SQL ServerMSSQL.1Reporting ServicesReportServer

In the location above, the MSSQL.1 directory depends on the specific environment. The location of the two configuration files described below may then vary depending on where Reporting Services was installed.
  • rsreportserver.config file:
    <Configuration>
    <Extensions>
    <Data>
    <Extension Name="SOURCECODE" Type="SourceCode.Data.SmartObjectsClient.SOConnection,SourceCode.Data.SmartObjectsClient, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16A2C5AAAA1B130D"/>
    </Data>
    </Extensions>
    </Configuration>
  • rssrvpolicy.config file:
    <CodeGroup class="UnionCodeGroup" version="" Name="CustomDataExtensionCodeGroup" Description="Code group for the Custom Data Extension" PermissionSetName="FullTrust">
    <IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:Program FilesMicrosoft SQL ServerMSSQL.1ReportingServicesReportServerinSourcecode.Data.SmartObjectsClient.dll"/>
    </CodeGroup>

 

Did this topic help you find an answer to your question?

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings