I am trying to run SSRS locally from my computer, using SQL Server 2014. In the Reporting Services Configuration Manager, I can connect to the Database I created on my own computer and my credentials checkout too. The issue is when I click on the Web Service URL and Report Manager URL, I get an access is denied error (401.2). I have went in and checked my user permissions in the SQL Server Management Studio, and I have all permissions set to where I should be able to connect and get in. To my understanding, this is not an IIS related issue, and since I am doing things locally, it shouldn't have to do with Kerberos either. Any help or direction would be greatly appreciated! I have tried running IE as admin, but it still denies me with same error.
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.
We have SQL Server Reporting Services 2005 (SSRS) installed and running just fine. I can connect via SQL Server Management Studio 2005 using "Connect -> Reporting Services" and "Windows Authentication".
When I am connected, I can bring up the server properties and view Permissions and see myself there w/ System Administrator checked, but not System User. Which is fine because I have no problem accessing the entirety of the server.
Using the same "permissions" dialog, I use the "Add Group or User" button to add my colleagues domain account (I have tried this with just "System Administrator" and also with "System User" checked).
My colleague cannot connect. He gets the following error message when trying to connect:
TITLE: Connect to Server
Cannot connect to XXXXXXXXXX.
ADDITIONAL INFORMATION:
A connection to the report server failed. Most likely, you do not have
permission to connect to the computer. You should either try to
connect using a report server URL for the Server name, or if the
Distributed COM Users group exists on the remote computer, verify that
you are a member. (Microsoft.SqlServer.Management.UI.RSClient)
Anyone know what else I need to do to allow him to connect to Reporting Services via SSMS?
Note: I can give him permissions to reports and he can view those reports via the SSRS website.
The Microsoft link below has an article that summarizes the connection syntax, operations, and permissions required to connect to SSRS.
Basically, the user connecting has to be assigned to the System Administrator role. If this doesn't work, you will need to add the account to the 'Distributed COM Users' local group, that should let you connect via SSMS.
see here http://technet.microsoft.com/en-us/library/ms159797.aspx and
http://www.mssqltips.com/sqlservertip/2793/sql-server-reporting-services-2012-permissions/
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'm using Windows Server 2003 to run a server application which utilizes SQL Express 2008. I'm also using Windows Terminal Services to host a bunch of thin clients, so I've had no need for active directory domain server and other stuff like that.
Now I have "small" problem regarding logging in to the SQL Server. Only the Administrator account can do this, even if I give my other (test) user administrator privileges by adding him to the Administrators group.
This is the error received: Cannot attach db file to database [Client 127.0.0.1]
I've already checked that the filepath is accessible by the user in question, and like I said, this works perfectly fine for the administrator user.
What account is the SQL Server itself running under? Often it may be running under a domain service account, and it may not have permission to certain folders. Also, the C: drive has progressively become more locked down in Windows with regard to SQL Server database files.
Seems I found the answer. Using SQL Management Studio i gave the "Users" group sysadmin permission for the database, now everything works as expected.
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.