I have 3 server, web server, app server and db server. Where should I place the report url and report datasource in ? currently I placing in the web which is not working right now. Please help. Thanks.
The web server cannot directly go through app server. It block by the firewall and only allow by calling using the wcf request. The SSRS install in db server but the physical report is place in the app server that point to db server virtual directory. The report deployment is using the SSDT at the app server.
Related
I have installed Microsoft SQL Server Developer Edition in my local machine for my own development use with a Windows Authentication. I have been able to connect to DB Engine, SSAS (Multidimensional Model) Engine, SSIS Engine, SSAS (Tabular Model Engine using another instance).
I was able to connect to SSRS engine (Native Mode) a few weeks earlier. Recently I installed CheckPoint SSL VPN to access our client Remote Desktop. After this installation, whenever I connect to SSRS either using SSMS or Report Server or Report Manager, even though the SSRS Services is running (I have been able to verify from SQL Server Configuration Manager as well as Reporting Services Configuration Manager). I even tried to add the SSRS Report Server link in the SSMS for the SSRS Engine, but still not successful.
I get the following:
TITLE: Connect to Server
Cannot connect to LAPTOPNAME\SQL2012DEV.
ADDITIONAL INFORMATION:
Unable to connect to the server at LAPTOPNAME\SQL2012DEV. The specified URL might not be valid or there might be a problem with the report server version or configuration. Specify a different URL, or contact your
server administrator to verify that the report server runs SQL Server 2008 or later. Additionally, if you are trying to connect to a SharePoint-integrated report server, verify that SharePoint is installed on the server
and that the report server uses SharePoint integrated mode. (Microsoft.SqlServer.Management.UI.RSClient)
BUTTONS:
OK
Could this be due to some permission issues ? I have restarted the SSRS services many times, though it is running, I am not able to connect. Should some Admin privileges be given to my Windows account ? If so, can you guide me how ?
Information from SQL Server Configuration Manager (for SSRS service):
Log on As: NT Service\ReportServer$SQL2012DEV
Information from Reporting Serivces Configuration Manager:
Service Account is built-in: ReportServer$SQL2012DEV
Should I change built-in account to Local Service, Network Service, Local System ?
Open "Reporting Services Configuration Manager" in "Web Service URL" OR "Web Portal URL" tab check your IP and Port access & use the link in URLs to be sure. I think your new application changed this settings.
After connecting to the VPN, in Visual Studio on my local machine, I set the target server to
http://[RemoteServer]/ReportServer
but I get the error
"The specified report server URL could not be found"
I can RDP to the remote server, but my login is DOMAIN-B\MyUser. On my local machine, my login is DOMAIN-A\MyUser.
On RDP, I am able to verify that Reporting Services are running and the target URL is correct.
How can I deploy an SSRS project from Visual Studio on my local machine to a remote server, on a different domain, over a VPN connection?
More broadly, how does Reporting Services authenticate report deployments? I would imagine Visual Studio would require some credentials when trying to deploy to the Target Server, just like when you connect to a database in SQL Server, but I am never prompted on my local machine, and I don't know how to set that up on the remote server.
Try:
http://[RemoteServer].[Domain].local/ReportServer
We are planning to deploy reporting service using Microsoft Reporting Server 2012. As I understand it, there will be three components;
Database (SQL Server)
SSRS (Reporting Server)
IIS (Web front end) - SharePoint (alternate Front end)
In setting up the Proof-of-Concept, the dev installed SSRS and SQL Server on same box (let's call it the DB server) and is redirecting client browser to a URL on DB Server from web front end.
Is it possible to architect the solution so that the web front end is the only destination for client browsers, SSRS lives on its own dedicated server separate from both the Web server and the DB Server?
How will authentication work in this scenario? We are using integrated authentication using Enterprise AD.
Configurations I have used in the past are these:
SQL Server on one server; SSRS native on another server. Users accessed reports via the SSRS Report Manager web UI that comes with SSRS.
SQL Server on one server; SSRS install in SharePoint Hosting mode on another server. Users accessed reports via SharePoint.
I am not 100% sure what you mean by “web front end is the only destination for client browsers”. If you mean that the end user only hits a web server, and not the database server to get reports, then either one of the above will work. If you have an existing intranet site that you want to host reports in, you can do so via web parts, if you are using MS technologies. You will still need SSRS setup somewhere so you can deploy reports, and the web part would read from it. Or, you can continue the redirect to either Report Manager or SharePoint if you go that route.
As far as authentication: the authentication between SSRS and SQL Server is usually done via an AD (Active Directory) user/service account that SSRS runs under, and also has access to the databases is uses on the SQL Server.
The authentication that allows users to browse and execute reports is usually done via AD as well. You can add all users to a central AD group and give that group Browser permissions on the SSRS server. This authentication would still apply if you use web parts to host reports outside of SSRS Report Manager.
The authentication that SSRS uses to pull the data that ends up showing in reports is usually SQL Server authentication, or whatever authentication that your data source supports where you can send a user name and password (which is stored within a shares data source on SSRS).
More Info
I am looking for a solution to the following problem:
I have a web application that exposes a Data Warehouse using Views written in my MS-SQL DB
I let the clients of my application use Report Builder to create RDL files against these Views
My application then uploads the RDL files to the SSRS server and makes the required modifications to allow users displaying these reports in different places in my Application.
The problem:
As long as the client's machine has access to the MS SQL server using port 1433 i have no problems with the described scenario.
One of the clients has strict security polices and will not open port 1433 to the SQL server and because of that all the solution I have with reporting will not work.
Can you suggest a workaround or a different approach that will no have to use port 1433 ?
Event if it will require to install some additional software or expose the Views in a different way I'm looking for something that can help me create the same solution without the requirement of port 1433.
Only thing I can think of is an RDP to another server or like a citrix published app or virtualized application where the host server it is running off of would have access
I get the following error:
In remote mode, the Report Viewer control requires session state be
enabled or Report Server connection information specified in the
config file.
Windows 2008 server, IIS 7, Dot Net 3.5
sessionState=InProc
After rebooting, I still get the error.
Do you have the Report Server connection information setup in the Config file of your webservice?
Take a look at http://msdn.microsoft.com/en-us/library/ms251661.aspx
Working in remote mode, you need to specify the reporting service connection string for report viewer to function.