We’ve updated our product from SQL Server 2005 to 2008. The development and demo-machines run with SQL Server Express 2008 R2 x64, the production server will run with SQL Server 2008 R2 x64. I installed the newest version of the .dll, all the configuration entries look OK to me. I can use the barcode plugin in SQL Server Business Intelligence Development Studio (what a name!), but deployed on my server they don’t render. The rest of the report comes out fine, but the barcodes are simply missing. We want to demo on Friday, so please, if you can, help.
Please note that we provide separate assemblies for SQL Server 2008 and SQL Server 2008 R2. So you need to copy the assembly from SSRS2008R2 folder of Aspose.BarCode for Reporting Services installation directory to the Reporting Services\ReportServer\bin folder.
I have just tested the latest version v4.7.0 on my end with Windows Server 2008 R2 and SQL Server 2008 R2. The results produced are as expected. Unfortunately, the SQL Server is installed on C drive, so I am unable to verify if installing the SQL Server on other drive may effect the results.
If Config Tool is updating the “rsreportserver.config” and “rssrvpolicy.config” files then it is OK to manually copy the Aspose.BarCode.ReportingServices assembly. Could you please confirm if the above said configuration files have the respective entries as discussed in Step 3 & 4 of this article? I have also attached the configuration files from my machine for your reference.
If the configuration files have the respective entries then please restart the Reporting Services and check the deployed reports.
I have compared the config files. My rssrvpolicy.config is identical to yours. My rsreportserver.config has some small differences to yours, but none in the aspose-section.
Restarted the service, tried the deployed report (it contains only a single barcode, no database-connection), I still get an empty pdf.
No, I do not get a barcode. I don’t get anything in the pdf.
In the Business Intelligence Development Studio I see the barcode, If I do a preview rendering, I get a barcode. If I deploy the report to the server and request the report in the /Reports interface, I get an empty pdf file.
Sorry for the misunderstanding and your inconvenience.
If the configuration files have the corresponding entries and Aspose.BarCode.ReportingServices.dll is in place (Reporting Services\ReportServer\bin folder) then the deployed reports should exhibit desired results. I am pretty sure that installing the SQL Server on D drive has nothing to do with this issue, but I still need to confirm this on my end. Please note, it may take some time to simulate the environment and to do so, I will require the exact specifications of your server like,
OS version
OS architecture
SQL Server version
OS service pack
SQL Server service pack
You can try one more thing, please copy the Aspose.BarCode.ReportingServices assembly from your development machine to your problematic server. Check the version of both assemblies are same. Create a new report with just one barcode. Deploy it on server. Check the deployed report in any browser and without exporting it to PDF.
SQL-Server MS SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Standard Edition
I’ve run the test on the server as you suggested, the barcode does render. Everything seems fine. The issue seems to be either the OS (rather improbable) or the SQL Server Express (somewhat more probable).
We don’t have (and probably could not afford) a full SQL Server License for each development/demo machine. Can you help?
First of all, please accept my apologies for the delayed response.
I have simulated the environment as of your demo server by freshly installing the SQL Server 2008 Express R2 (with additional services) on Windows 7 Professional and Ultimate versions. On both virtual machines, I am unable to render barcodes when reports are deployed. With these results, I have started to believe that Aspose.BarCode for Reporting Services component is not fully compatible with above said version of the SQL Server.
I will further troubleshoot the problem on my end, and if required I will also log an appropriate ticket for the development team to have a look into this matter.
I have logged a ticket (BARCODREP-33124) in our bug tracking system to get the expert’s opinion from the development end on your said issue. As soon as I receive any updates, I will be more than happy to share it with you.
bensch: