I have a SQL 2008 developer edition with SSRS and the report manager is only available from the local machine. If I try to access it from any other machine I get challenged for my domain u/name and pwd 3 times and then the screen stays blank.
I have made changes to some config files (originals copied out) in order to get a 3rd party application to run but that is now uninstalled and the config files are all back to vanilla (originals copied back in)
I feel its something to do with authentication but am stuck ...
any suggestions welcomed
Jonathan
I have just stumbled on the answer.
I changed the Report Server Service Account to use the built-in Local System account and its all accessible from remote browsers.
Anyone any ideas why?
You may need to change the SSRS Configuration (through the GUI) (Start - Microsoft SQL Server 2008 - Configuration Tools - Reporting Services Configuration Manager) and set it to allow connections from outside the box it is on.
Also don't forget that it's using domain credentials / local machine credentials, so if you're not on a domain, you'll have to provide credentials to log onto that machine (i.e. MACHINE1 where SSRS is installed, from MACHINE2, log on with MACHINE1\username and password for MACHINE1).
Or you may need to open up your SQL Server instance to permit connections from other boxes.
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.
Let me first describe the actual situation: We want to build a new SQL Server enviroment based on SQL Server 2016. AS you may know, in SQL Server 2016 the mobile reports from Datazen are integrated. So far so good. The Problem: In our current Enviroment, there is one internal Datazen Server and one external server. The external Datazen server exists only to read data from the internal one. So there is no direct Data Access (to Data Sources), the administration part is disabled and only the needed Services (to read from internal server) are installed. We want to build that same archtiecture in SQL Server 2016 Reporting Services. Do you know any way to do that?
I thought the best solution was a second SQL Server with Reporting Services but only read access on the other SQL Server (didn't found any setting like this).
We don't want the internal server to be accessible over the web beacause of security.
interesting question, but not sure i understand correctly ;) what do you mean with "the external datazen Server exists only to read data from the internal one"? How does this configuration look like? Do you have a sale out Deployment where the external Servers hosts "Web Application" and "Share Cache Instance" while internal Server hosts "Data Acquisition" and the same roles as the external Server?
In SSRS you can also Scale out web frontends, but all Servers will act as "data acquisition server" to stay in datazen terminology. Do you have security concerns with this topology? Whats the difference to have the data "read only" in DMZ or connect from DMZ/external Server to internal datasources? One Option would be to do a secure Application Publishing of internal SSRS Server with a Firewall like Microsoft ISA Server
I'm running SQL Server 2012, and I'm trying to configure Reporting Services. I've confirmed that the service is running on my system, but when I start up Reporting Services Configuration Manager, there is no server listed in the start up screen, where it asks to Connect to a Server. When I type in the name of the server, I get a pop up saying,
Cannot Find <Server Name>
That's as far as I get, and I cannot understand why it would not automatically populate the server name or, even less clear, why it wouldn't be able to find the Server once I entered the name in manually.
I wish I could give more information but that's really as far as I get. Are there some basic configurations I can check to see why it's not "aware" of itself as a SQL server?
In my case SSRS was installed but not correctly configured.
I had to use Reporting Services Configuration Manager to create a database (Database panel) and then enable the web services using the 'Web Service URL' panel.
Once both these steps had been completed, I was able to connect via SSMS.
If there's no reporting service instance name displayed in Reporting Services Configuration Manager, it means the Reporting Services instance is not installed properly. You can try to re-add feature(SSRS) to existing SQL instance. Please troubleshooting the installation for SSRS.
https://msdn.microsoft.com/en-us/library/ms144289(v=sql.110).aspx
Also make sure you start SSRS administration tool for right SQL instance.
I'm trying to configure Reporting Services on a dev server so we can use it for development, but it is not working out for me. When I try to access the Reports page, I get the following error:
User 'ServerName/UserName' does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed.
I'm not sure what I need to do to fix this, does Reporting Services need a virtual directory? If so, does anybody have a link on how to configure it? When I created the ReportingServices database, it made me a dbo by default, I'm a sysadmin on sql Server, so the permissions should be good.
I'm running sql server 2008 R2
I figured this out by going to the report manager on the server hosting reporting services by using the link http://localhost/reports. Once I was there then I clicked on home and configured the permissions.
Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed.
If you are running IE on the server on which you installed SSRS, make sure that you right click and run IE as administrator.
Have you tried this from other machines? IF you are getting the same results from multiple machines, then go through the steps in Start -> All Programs -> Microsoft SQL Server 2008 R2 -> Configuration Tools -> Reporting Services Configuration Manager. Here you can reset most of the basic SSRS configuration.
You don't need a virtual directory: SSRS no longer uses IIS: it is built directly on http.sys.
I have just installed SQL Server 2008 including Reporting Services on Windows Server 2003. I'm having a problem though accessing the Report Manager. When the Reporting Service is first started I can access it fine but after maybe an hour when I try and access it I get an error saying: Unable to connect to the remote server.
The reporting service is still running at this point. I can connect to it through Reporting Services Configuration Manager and clicking on the Web Service URL gives a directory listing (I assume that is correct behaviour). If I stop and start the service through Reporting Services Configuration Manager then I can access Report Manager once again (although in maybe an hour I will get the same error once again).
I've installed the latest SP1 service pack. I'm using the same domain account to run all the SQL services. The report server is set to use the default ReportServer virtual directory, is set to IP address All Assigned, TCP Port 80 and no SSL certificate. The report manager is set to use the default Reports virtual directory, IP address All Assigned, TCP Port 80 and no SSL certificates.
In the log file I get an error:
Unable to connect to remote server
HTTP status code 500
An attempt was made to access a socket in a way forbidden by its access permissions.
Does anyone have any idea why this is happening? I've searched the net but haven't been able to find a solution.
It was the anti-virus software on the server that was causing the problem. After adding the pagefile.sys as an exclusion it worked fine.
configure your rs like below link :
http://technet.microsoft.com/en-us/library/bb839480(SQL.90).aspx
maybe it solve your problem.