I am running SharePoint 2010 and Reporting Services 2008 R2 SharePoint integrated-mode. I am able to browse to the reportserver site : http://DBserver/reportserver which lists my site collections and I am able to get to the document library which holds my reports. However, when I try opening a report I get the following error:
Report Server has encountered a SharePoint error. (rsSharePointError)
The security validation for this page is invalid. Click Back in your Web browser, refresh the page, and try your operation again.
For more information about this error navigate to the report server on the local server machine, or enable remote errors
I am able to resolve that issue by going to Central Admin, Application Management, General Settings and turning Web Page Security Validation Off. But if I do that I get an error when using silverlight features like site, or list creation.
Any ideas?
Related
We have an internal SSRS report that we recently updated to utilize a new API that replaces an existing service used to display images. The original API was hosted internally while the new service is hosted in our new Azure environment. We updated our SSRS report to utilize the new service and can run that report in our local dev environments, but when we deploy to our staging server (running SQL 2014 on a Windows 2012 R2 box) the pictures don't load and we find the following error in the SSRS log files (I've removed the URL for security reasons):
An error occurred retrieving the external resource The underlying connection was closed: An unexpected error occurred on a send.
After doing a Wireshark capture, we found that SSRS is initiating connection to the API using TLSv1, while calls to the same API URL in the browser on the server, which render images fine, are using TLSv1.2. I can see that TLSv1.2 is enabled on the server, but how do I force SSRS to utilize that when running this report and reaching out to the new API?
So, found out how to do this and turns out there are some simple registery updates that need to be made to force SSRS to communicate over TLSv1.2. This tutorial helped me out, mainly section 3 which dealt with the SSRS/SQL server: https://techcommunity.microsoft.com/t5/sql-server-support/enable-tls-1-2-protocol-for-reporting-services-with-custom-net/ba-p/318825
After successfully installing SQL Server Express 2012. I am trying to get set up my Report Builder. Unfortunately I am asked for a password when clicking on the Report manager URL or the Web Services URL. It says something like this (connecting to "my_Pc").
As far as I am aware I do not have any password on my PC nor set up one when configuring my SQL Server. Please note that I have not configure SSRS yet and my Service account is still ReportServer$SQLExpress. How do I sort this out please
?
Issue is with how you have created data source for Report.
Data source is created with option "Prompted Credentials" .
It should be created with "Stored Credentials" or "Windows Integrated Security"
Read more
At one point you might have configured the user "sa", have you tried using sa login to access the report page? If you are using machine id to authenticate with sql server, to configure a new user, after you connect to your database, browse down to security > logins > right-click and choose "new login".
One easy solution for this is to check the browser you are using . |I was using internet explorer edge and realise that explorer edge was simply not trusting that site. So if you are on explorer just go on setting and trust the site.
However I was on IE edge which does not trust any site. I changed it for google chrome. Everything is running perfectly fine. just change the browser (Internet Explorer best as Google could pose problem to visualize data when creating reports) and refresh everything should be running just fine.
I am able to successfully publish my web-app without the database and it works perfect. But, since it is dynamic, I need to attach database to it but i am not able to do so.
It's raising an error when previewing database.
I've created a Lightswitch HTML application in VS 2013. It relies on a SQL Server database which was created locally and then uploaded to Azure. The database was then linked to the Azure web site.
I tested my database connection strings in the publish routine and they succeeded. The publish succeeded, but when I browse my azure URL, I receive the following message:
You do not have permission to view this directory or page.
What must be done to remedy this error?
I had a similar problem that would not resolve until I moved to a "Pay-As-You-Go" subscription rather than a "Free Trial".
I also had the same problem, but did NOT have to move to a "Pay-As-You-Go" subscription to get it working. Here was what I had to do.
The Azure management portal will tell you that the Site URL is something like https://mywebsite.azurewebsites.net/
but to test a Lightswitch HTML5 client application, the URL in Azure will actually be https://mywebsite.azurewebsites.net/HTMLClient/
Hope that helps.
I configured SSRS 2008 on a remote server.
I can access the report manager from my local machine using http://SERVER_NAME/Reports_INSTANCE_NAME
problem is that when I try to deploy a report from BIDS, I get the "reporting services login" dialog box that asks me for user and password. I try my AD user and it doesnt work.
I already added myself to all possible roles, including System Administrator.
I saw online that the problem maybe with the IIS website that must be configured to allow anonymous access. That's fine, but where can I configure that since SSRS2008 doesn't create the websites on IIS anymore (also read that online) and I don't seem to have this possibility using the Reports Service Configuration Manager
Take a look at the link below...it's in reference to 2008 CTP, but there are still some items to check in your setup...
http://blogs.msdn.com/b/lukaszp/archive/2008/03/26/solving-the-reporting-services-login-issue-in-the-february-ctp-of-sql-server-2008.aspx
Similar issue / resolution here as well...
Repeated Reporting Services Login issue when deploying through BIDS to a remote server
In your report configuration file, try removing the RSWIndowsNegotiate from the Authentication tag:
<Authentication>
<AuthenticationTypes>
<RSWindowsNegotiate />
</AuthenticationTypes>
<EnableAuthPersistence>true</EnableAuthPersistence>
</Authentication>