Product Update Notice: The SSRS Native Barcode Generator is now available and offers an easier method of generating barcodes without fonts or other components. IDAutomation now recommends using this product instead of the CRI.

A Reporting Services CRI (Custom Report Item) may fail to display properly on deployed reports. This error was reported by customers using IDAutomation’s Reporting Services Barcode CRI to create barcodes on reports.

The error may occur as follows:

1. When the Barcode CRI is implemented on a report, the Barcode CRI is visible in design and preview mode.
   
2. After the report is deployed, the Barcode CRI disappears completely from the deployed report.
   

This error is generated in the rssrvpolicy.config file, when the <CodeGroup referencing the IDAutomation_ReportingServices_BarcodeCRI.dll is outside the first CodeGroup element.

Solution(s):

Product Update Notice: The SSRS Native Barcode Generator is now available and offers an easier method of generating barcodes without fonts or other components. IDAutomation now recommends using this product instead of the CRI.

Place the <CodeGroup reference of the IDAutomation_ReportingServices_BarcodeCRI.dll after the first <CodeGroup element.

For example:

<CodeGroup class="FirstMatchCodeGroup" version="1" PermissionSetName="Nothing">
<IMembershipCondition class="AllMembershipCondition" version="1" />
<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Description="This code group grants
IDAutomation_ReportingServices_BarcodeCRI.dll FUllTrust permission. ">
<IMembershipCondition class="UrlMembershipCondition"version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\
ReportServer\bin\IDAutomation_ReportingServices_BarcodeCRI.dll" />
</CodeGroup>ect.......................

</CodeGroup>
</CodeGroup>

The Barcode CRI should now be visible on deployed reports.

In the event this does not resolve the issue, IDAutomation recommends using Windows Forms Controls instead of the CRI on reports.