Hi,
This behaviour is strange cause I have tested your both license files (as shared by you via a private message) on your required environment (Windows Server 2003, SQL Server 2005, SQL Server Business Intelligence Development Studio 2005) and I didn't get the evaluation watermark on Deployed reports or by getting the preview in Visual Studio.
It is recommended to use the Config Tool that installs with any version of Aspose.BarCode for SSRS to configure/setup the Aspose.BarCode for SSRS on any machine. To set the license, you only have to place the .lic file to ReportServer/Bin folder for Deployment and IDE\PrivateAssemblies folder for Development. Please check the
Technical Article on this subject.
During my testing, I have placed the .lic file in only ReportServer/Bin folder and configured the Report Project to deploy on local ReportServer. I am not experiencing Evaluation watermark in either Visual Studio or deployed reports. Please give a try by deploying your reports on local.
There is another aspect that you have to consider, if the barcode labels on the report are generated by the control of previous version, then they may also conflict with the licensing module. To resolve this, please remove and add again the Aspose.BarCode for SSRS control from the Visual Studio Toolbox when upgrading.
Regarding the issue that we have logged earlier under Ticket Id 33023. The random characters at the end of your shared barcodes are actually the Checksum. If you enable the Checksum property of any checksum supported symbology (Code39 in your case) then an extra bit is added to the barcode label. You can turn it off by un-selecting the check box "Enable Checksum". Please check the attached snapshot for your reference.
Babar Raza
Support Developer,
Aspose Sialkot Team
http://www.aspose.com/
Aspose - Your File Format Experts