Since the October preview of SSDT supports SSRS in Visual Studio 2015, I installed that and am trying to use it with my existing reports. I'm getting a bunch of errors, warnings, and messages, however. 61 messages exist that say the following:
Could not find schema information for the element /
'http://schemas.microsoft.com/SQLServer/reporting/reportdesigner'.
I also get a warning for this report. Note that line 33 is just <Fields>.
[rsInvalidReportDefinition] 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. Details: Data at the root level is /
invalid. Line 33, position 28519.
The report code sections throwing these errors look like this:
<Field Name="PriorityId">
<DataField>PriorityId</DataField>
<rd:TypeName>System.Int32</rd:TypeName>
</Field>
The MSDN article for that field gives that schema link as the correct link, but navigating to it shows it doesn't exist. I tried several others on the server, but they all return the same error with the relevant URL.
The reporting server is running SQL Server 2008 R2, hopefully being upgraded soon to 2014. How can I resolve these errors and (hopefully) therefore the build error?
Related
I am using Visual Studio 2017 to write SSRS reports. I have one solution with multiple reports in it, so I am using a shared data source.
For some reason, some of my reports are able to connect and I can preview them, but other reports cannot.
For the reports that are unable to connect, I get the error:
Format of the initialization string does not conform to specification starting at index 94
I don't understand why the connection works for some reports (I can preview them), but not others since they are using the same shared data source and therefore should be using the same connection string.
I have no issue deploying the reports, even the ones that cannot connect. They all show up fine online.
How can I troubleshoot this error? Is there a way for me to see the exact connection string for each report if they are somehow using different strings?
Edits:
I meant line 94, corrected above and below
As requested by the comment, this is line 94 from the RDL file:
I've been running a schema compare in a database project in Visual Studio 2017, when I do this I get the following message in the Error List tab:
Unexpected exception caught during population of source model: Object
reference not set to instance object.
I found this blog, which appears to be the same issue, but the suggested solution (of removing the entry using the Select Target Schema window) has not worked despite trying it a few times.
The compare has (and does) work fine with the same project and database in Visual Studio 2013, so I have a work around, but it would be nice to know what is causing the problem (and leave VS2013 behind!)
I found a solution to this; for database projects there is a 'Target platform' setting in the properties (see below). I set this to SQL Server 2017 and the compare now works.
The default platform required appears to depend on the compatibility of the database (see https://learn.microsoft.com/en-us/sql/t-sql/statements/alter-database-transact-sql-compatibility-level); while I required 2017 when I initially encountered this problem, a recurrence (against a database with a compatibility level of 120) needed SQL Server 2014 to be selected.
Oddly I have now seen that just switching the target platform back and forth can solve the problem e.g. I have a database project with SQL commands which were not present in SQL 2014, I ran the compare with a target of 2017 and it failed with the above error, ran with a 2014 target and it errors (as you would expect, since it does not understand the newer SQL functions), switch back to the 2017 target and the compare now works fine!
Edit: different job, different DB version (2019). Has all been working fine for months then this error cropped up. the above didn't work this time, so just in case anyone finds the same, the tried and tested closing and reopening VS sorted it!
My reports were working like a charm until yesterday. But after un-installing and installing again these Nugets packages i.e. Jquery, Bootstrap, Microsoft reporting service control web and others, it not working any more. Although i can build and display new reports but not able to view the old ones. Could you please give me some hint to fix these. I am using visual studio 2017, sql server 2016.
This is the exact error
An unexpected error occurred in Report Processing.Exception has been
thrown by the target of an invocation.The type initializer for
'System.Diagnostics.Activity' threw an exception.Operation could
destabilize the runtime.
Thanks,
Ghaffar
Preface: Installed SQL Server 2016 RC0 and installed and configured Reporting Services all fine, thoughts maybe on potential conflicts with existing SSRS instances?
Issue with SQL Server 2012 Reporting Services, every time I navigate through the configuration manager to either the Web Service URL or the Report Manager URL, I get the following errors:
Report Manager URL returns
HTTP 500 error
Console when opening the Report Manager URL returns
SCRIPT16389: Unspecified error.
http_500.htm (1,1)
HTML1524: Invalid HTML5 DOCTYPE. Consider using the interoperable form
!DOCTYPE html
.http_500.htm (1,1)
Web Service URL returns
The version of the report server database is either in a format that
is not valid, or it cannot be read. The found version is 'C.0.9.45'.
The expected version is '162'. (rsInvalidReportServerDatabase) Get
Online Help
Console when opening the Web Service URL returns,
GET http://localhost:8085/ReportServer_MYREPORTS 500 (Server Error)
To try and resolve this, i've already tried adding RSExecRole to RoleMembers under both ReportServer$MyReports and ReportServer$MyReportsTempDB.
Also tried recreating ReportServer database under the Config Manager, but get the following error.
Generating Database Script - Error:
Microsoft.ReportingServices.WmiProvider.WMIProviderException: An error occurred when attempting to connect to the report server remote procedure call (RPC) end point.
I can confirm that both RPC services, SSRS Services are running with no problems, and also restarted these services multiple times.
I have realised that my ReportServer$MyReports is missing the DBUpgradeHistory table.
Any thoughts?
This will fix the issue right away:
delete from dbo.ServerUpgradeHistory where ServerVersion=[The wrong or upgraded version]
In my case, there was no "ServerUpgradeHistory" table. I needed to install SSRS 2012 on a machine that already had SSRS 2016 to do regression testing for a client that doesn't want to upgrade their system.
What I discovered is that there are SharePoint settings that SSRS installs even if you don't install SharePoint or SharePoint Plugins on your box.
Here's what fixed the problem for me:
Navigate your File Explorer to C:\Windows\assembly\GAC_MSIL\
Note there are many directories in here that have nothing to do with SSRS. We will just focus on seven directories that appear to be related to this problem.
Navigate to Policy.11.0.Microsoft.ReportingServices.Alerting
Enter the assembly directory. This is usually a series of digits followed by a hexadecimal identifier.
E.G. 13.0.0.0__89845dcd8080cc91
This path will vary based on what is installed on the machine
Backup the config file in case you need to roll back changes
E.G. from a Command prompt: COPY *.config *.bak
Open the config file.
Look for the text in the newVersion attribute of the bindingRedirect tag:
<bindingRedirect oldVersion="11.0.0.0" newVersion="13.0.0.0">
Modify this to use "11.0.0.0"
<bindingRedirect oldVersion="11.0.0.0" newVersion="11.0.0.0">
Save your changes
Repeat steps 2 through 8 with the following subpaths:
Policy.11.0.Microsoft.ReportingServices.SharePoint.Common
Policy.11.0.Microsoft.ReportingServices.SharePoint.ObjectModel
Policy.11.0.Microsoft.ReportingServices.SharePoint.Server
Policy.11.0.Microsoft.ReportingServices.SharePoint.SharedService
Policy.11.0.Microsoft.ReportingServices.SharePoint12.Server
Policy.11.0.Microsoft.ReportingServices.SharePoint14.Server
Reboot your computer
I have a report in SSRS (SSRS 2008, running on Windows 2008 Server, running in Sharepoint integrated mode) that is returning an error. However - I have no idea what the error is. If I run the report on the Report Server, I'm returned this error message.
Crystal clear, right?
I have enabled Remote Errors via Reporting Services, so I believe I can get the error by querying the ReportServer database by this:
SELECT * FROM ExecutionLogStorage
ORDER BY TimeStart DESC
I see the report I ran, but "Status" is "rsSuccess".
The AdditionalInfo field returns:
<AdditionalInfo>
<ProcessingEngine>2</ProcessingEngine>
<ScalabilityTime>
<Pagination>0</Pagination>
<Processing>0</Processing>
</ScalabilityTime>
<EstimatedMemoryUsageKB>
<Pagination>4</Pagination>
<Processing>18</Processing>
</EstimatedMemoryUsageKB>
<DataExtension>
<SQL>1</SQL>
</DataExtension>
</AdditionalInfo>
From that, it looks the report ran successfully, but it obviously didn't.
When I look through the SSRS logs, located here:
I see this:
library!ReportServer_0-9!abc!12/02/2013-13:52:47:: Call to GetPermissionsAction(http://ReportServer/reports/Documents/BlackList_Report.rdl).
library!ReportServer_0-9!11a4!12/02/2013-13:52:47:: Call to ListParentsAction(http://ReportServer/reports/Documents/BlackList_Report.rdl).
library!ReportServer_0-9!d54!12/02/2013-13:52:47:: Call to GetPermissionsAction(http://ReportServer/reports).
library!ReportServer_0-9!1c2c!12/02/2013-13:52:47:: Call to GetSystemPropertiesAction().
library!ReportServer_0-9!abc!12/02/2013-13:52:47:: Call to GetPermissionsAction(http://ReportServer/reports/Documents/BlackList_Report.rdl).
library!ReportServer_0-9!11b4!12/02/2013-13:52:48:: i INFO: RenderForNewSession('http://ReportServer/reports/Documents/BlackList_Report.rdl')
runningjobs!ReportServer_0-9!a70!12/02/2013-13:54:18:: i INFO: Adding: 1 running jobs to the database
Again, nothing that explains what the error is. How can I figure out what is causing this error?
Alright - I was able to configure Sharepoint to display the actual error. It has nothing to do with SSRS.
To get the full Sharepoint error, you need to make some changes in the web.config file, which is typically located in the following directory: c:\inetpub\wwwroot\wss\VirtualDirectories.
The changes you need to make are:
Find this entry:
<SafeMode MaxControls="200" CallStack="false" DirectFileDependencies="10" TotalFileDependencies="50" AllowPageLevelTrace="false">
and replace it with:
<SafeMode MaxControls="200" CallStack="true" DirectFileDependencies="10" TotalFileDependencies="50" AllowPageLevelTrace="true">
Lastly, change:<customErrors mode="On" /> to <customErrors mode="Off" />.
Save the file. I did not need to reboot Sharepoint for this to work.
Now Sharepoint should provide a detailed error message.