I have a SSRS report which I've initially created with SQL Server 2014 Report Builder (12.0.6024.0) using Code128 according to this post. It has been working great until we wanted to upgrade our SQL Server to 2016 and then I made the same report using SQL Server 2016 Report Builder (15.0.19611.0).
Now the issue is the new version does not support that custom code which I got from above mentioned post. After installing many Code128 fonts found one of them that works but it did not like all other fonts and barcodes won't show up.
So it would look like following figure
As the counter attack I installed that previously mentioned working one Code128 font which is IDAutomationC128L and turns out it works really until I realize this one glitch. As you can see in the bottom picture I compared the working version(2014) with the new version (2016) the glitch is there is a space in the middle of the barcode, sometimes it's in the Item Number field and sometimes it's under Raw Material Item Number field.
Here's the SQL Server 2014 version(Code128) for the same parameter
Here's the SQL Server 2016 version(IDAutomationC128L) for the same parameter
Does anybody know how to fix that issue? I have tried couple of other things too just to make sure, such as attaching the newest .NET version's(4.8.4390.0) System.Drawing.dll just becuase I thought SQL Server 2016 might not support .NET version 2.0(which I'm using for SQL Server 2014)
Appreciate all your support!
Related
I've recently migrated a report from 2008 to 2016 Reporting Services and for some reason the 'back to parent' button which takes me up and down drilldowns as has stopped showing.
This is what it should look like:
I've read around that people have manually added a 'back to parent' button through using history.back but this will not work for me.
The report is not a 'classic' SSRS report in that there is a .rdl file that I can edit. What happens is that the report is driven off of a series of tables (such as lines, headers and some figures) that populate a design table that we can see.
I was wondering if anyone has experience anything like this before when migrating across, or perhaps a DBA might know of a flag that needs setting up on the server that may have been missed?
After a long time searching around online, I've finally found the answer.
I needed to add the following line to the end of the report link:
&rc:showbackbutton=true
I'm getting the following error when publishing a report from the command line using the report scripting tool:
System.Web.Services.Protocols.SoapException: The definition of this
report is not valid or supported by this version of Reporting
Services. The report definition may have been created with a later
version of Reporting Services, or contain content that is not
well-formed or not valid based on Reporting Services schemas
There are other questions regarding this error and the solution always seems to be to either install SQL Server 2016 or to change my reports project to output for 2014. This does, in fact, work but it shouldn't be necessary. My SQL Server version is 13.0.4446.0, which is 2016. Furthermore, I can publish just fine from within VS with it set to 2016.
Anyone know what's causing this?
A couple things to try:
What version of VS are you using? I came across an issue where I'd open a solutions in VS 2015 (I think) and it upgraded report definitions without telling me. When you pick a deployment target in VS it changes the file on the fly, not the source file in the solution. Hence the different results you see.
You can check this by downloading a report from SSRS & open the RDL in a text editor. Compare with your solution RDL & check the header. The Schema at the top is what you want to compare:
Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner"
Another option: Have you tried deploying with PowerShell? Check out the SSRS GitHub for commands but it will be 2, maybe 3 lines of code. Very easy to use.
I had to upgrade the report server used by some application from SSRS 2014 to SSRS 2016.
I did the migration manually, because the old and new SSRS were installed on different machines, and I could not do an in-place update.
So the approach was (long story short):
backup ReportServer on SSRS 2014
install SSRS 2016 on new server
restore ReportServer database
update its structure to match SSRS 2016; I used Sql Compare to get structure from an in-purpose, empty ReportServer database created by SSRS 2016
added record in ServerUpgradeHistory with version for SSRS 2016 (173)
restored the Encryption keys from SSRS 2014.
Everything works ok, with one small issue.
When I try to open SSRS Web Portal URL (http://...myServer.../Reports), or to refresh main page, I get the following error popup.
This error doesn't appear to affect the functionality of SSRS - all reports work just fine. Also it does's appear when opening Web Service URL (http://...myServer.../ReportServer).
So it's just annoying so far.
I searched for the guid string in Catalog table (I thought it might be some folder name or something), but I found nothing.
Does anyone have any idea where it comes from and how to get rid of it?
Thank you
Edit
Recently I updated from SSRS 2016 to 2017, and I kept carrying this error with me.
However I found the offending item. It is in Catalog table, and it is of Type = 3 (Resource), with mime-type application/octet-stream
I deleted it from catalog (I did a backup of it into a separate table - catalog_bak), but I still get the error when I load main page in (/reports)
Beside that, it never pops-up again, with one exception: it always shows-up when I access Site Settings -> Branding
I guess it has something to do with branding packages.
Does anyone knows where are they stored, and how can I uninstall / clean-up that?
A Branding Package is created by a user. If the original package can't be found or is corrupted it should revert to the default. Have you tried removing the package or creating and uploading a new one? Also, try downloading SQL Server Mobile Report Publisher (https://www.microsoft.com/en-us/download/details.aspx?id=50400) and then connect your server with it. It may contain a theme that was used on your original server.
For me Uninstall and Reinstall did the trick for me.
I have almost spent a day but still can't find the proper solution. I am trying to connect my DropList component in Visual Studio with MySql database. DropList component is as follows:-
Server Explorer is also showing a valid database connection:
While choosing a data source for my Droplist component, Test Connection shows that everything working fine:
Selected all columns available in the respective Table:
Here comes the Issue, in the next screen when I click on Test Query, this error pops up:
I have tried creating the DB again as well as resetting the settings of both, VS and MySQL, still no success. Can anyone please guide me through this process of how to pass this error. Using Latest version of VS and MySQL. Correct Server Name, Username and Password also entered.
I have also cleared the VS Cache and other local app data, still not able to pass through this error
You might want to go back and check your steps:
https://dev.mysql.com/doc/visual-studio/en/visual-studio-making-a-connection.html
Unfortunately, even after trying everything, I was not able to make all this work with MySQL Database. I repeated all the similar steps, as explained in my question, by moving to Microsoft SQL Server 2017, and it worked like a charm just in seconds, without any errors. Attaching the picture below after migrating to Microsoft SQL Server 2017 from MySQL 2017 :
Running into an issue where after upgrading SQL Server from 2008/R2 to 2012, SSRS report when rendered to PDF will display "Page x of 0" at the bottom (x = page number of report). This only occurs in PDF.
I open the reports, and the correct usage of the global parameters is there. If I re-deploy the report to the upgraded SSRS, it works fine.
It appears to be an upgrade issue. Applying the SQL Server 2012 SP1 doesn't help either.
Any ideas?
So we opened a ticket with MS. In a nutshell, when running an in-place upgrade, the RDL's stored in the ReportServer DB are "left alone". Because MS changed only the Globals!TotalPages to Globals!OverAllTotalPages and the RDL's are never touched during the upgrade process, the error occurs.
This also explains why when you take the un-modified original report and re-upload/deploy the report. It works.
This is fine if your just updating you local server. When you have 4500+ installations which can support up to N users, and 180+ reports. We get a trouble ticket in when a customer upgrades. That can be a lot of trouble tickets.
Not sure why MS just didn't "upgrade" the Globals!TotalPages to Globals!OverAllTotalPages. Didn't get an answer for that one.