I am following this Microsoft tutorial http://technet.microsoft.com/en-us/library/c962b0ff-ce8a-4742-8262-dc730901afcf for SSRS and I am having trouble starting the report manager,
The tutorial says to type in the computer name followed by reports in Internet Explorer, i.e. 'http:compname/reports' but I don't know why it won't let me access it,
Any help would be appreciated,
Nick
First off, have you properly configured the report server? If not, follow this tutorial (make sure SSRS service is running beforehand):
http://beyondrelational.com/modules/12/tutorials/26/tutorials/4600/getting-started-with-ssrs-part-4-configuring-sql-server-reporting-services-in-windows-server-2008.aspx
After that, you will probably run into 'access denied' problem - the solution is available here:
http://blog.davyknuysen.be/2009/09/11/administrator-has-no-access-to-the-report-manager-sql2008-r2-and-windows7vista/
After installing SSRS on to a Window 2012 R2 server, I was able to open the report browser from the server but, I was not able to open the report browser from a remote machine ... It said "This page can't be displayed" ... After hours of research, I realized that may be my firewall was blocking port 80 (I know right?) ... Suffice to say, it was blocking port 80!!!
Answer: Create a rule in "Windows Firewall with Advnace Security" to allow port 80 resquests.
Hope this helps
Related
Our team has setup a Windows Server to specifically run SSRS in it. We have the reports running well but we wanted to manage several tasks under the Browser role to get rid of a couple of things. I believe this can be accessed through SSMS by logging in to the Report Server. I did this just fine but when I'm trying to open the properties of the Browser role, it is grayed out and can't be selected. Am I doing something wrong here?
A couple of notes to clear things out:
I'm already using an admin account on the server
The Reporting Server is installed separately to a source DB from which we get to access data
I'm able to do this just fine when both Reporting Server and source DB are on the server
I'm using SQL Server 2016 with the same version of SSRS
We have figured it out. We just need to open SSMS as administrator. Might just be a user error of some sort as we do not need to do this on other servers. Thanks.
I have searched google and stack overflow before making this post, but i might have missed the answer to my issue.
I have an SSRS report server installed on a server hosting MS SQL server as well. The 2 services is working together just fine and I can do what i expect to do.
The issue is that when my colleagues are trying to connect to the report server URL through Report Builder, they cannot get access. They receive 401 unauthorized error. If they use my login on their machine, they still get no access.
If i use their login on my machine, it works fine.
My conclusion is that its not their logins that is causing this error, and it is not the server configuration either as i can login just fine (i am admin and in the admin AD group, but so is 1 of my colleagues who cant get access).
It must be something on their machine, but i just dont know what or where to look.
Thank you in regards.
You would need to navigate to your SSRS website and assign Report Builder to your colleague's domain\user account.
See here https://learn.microsoft.com/en-us/sql/reporting-services/report-server/configure-report-builder-access?view=sql-server-ver15#:~:text=Click%20the%20gear%20icon%20on,Otherwise%2C%20click%20New%20Role%20Assignment.
I know several similar questions to this have been posted, but I've walked through each of the provided solutions and nothing seems to resolve this issue...
I have SQL Express 2012 installed, and have created a simple report and want to deploy it to my local Report Manager website. Every time I try to deploy it from VS, I'm getting an error message that says "The specified Report Server URL "http:///Reports_SQLEXPRESS" could not be found. Verify the syntax of the URL and that the report server exists.
I'm able to browse this URL in my browser no problem; I've also confirmed through Reporting Services Configuration Manager that the URL and Virtual Directory are correct. As far as I can see this should be working...
Does anyone have any advice for next steps so i can deploy this report? I looked into it at the MSDN site and confirmed that the SQL Express w/ advanced tools should have this functionality... any help is appreciated!
"http://machine name/reportserver_sqlexpress"
is what my research has lead me to.
HTH
I'm trying to use MS Reporting Services. So far I have been able to create a simple report, using the AdventureWorks database.
Next step I wanted to take was to deploy my report. This is what I did:
In the Business Intelligence editor I right-clicked on the project name and clicked properties
I added a Start Item and I set the TargetServerURL to the URL that was displayed in the Reporting Services Configuration Manager. The URL is: http://ADMIN-PC:80/ReportServer
After that I clicked "OK" to go out of the Properties window. Then I hit Build Report Project1 in the Build menu.
After it tries to build it gives me the following error:
The specified report server URL: "http://admin-pc/ReportServer" could
not be found. Verify the syntax of the URL and that the report server
exists.
I'm sure the URL is correct. Or at least, that is what the Reporting Services Configuration Manager says.
So I have no clue what to check next in order to fix this problem. Anyone any idea what to do?
It's always tough to try and troubleshoot these general "it's not working" errors, but here's a rough idea of what I'd try looking at:
Is the service running? If you can connect through Reporting Services Configuration Manager then the answer is probably yes, but it's always the first thing to check!
Are the URLs correct? You may need to check you're using the correct URLs - these can be confirmed through Reporting Services Configuration Manager; by default Named Instances will have URLs like http://admin-pc/ReportServer_InstanceName and http://admin-pc/Reports_InstanceName.
Can I connect out of BIDS? What happens when you connect to http://admin-pc/ReportServer through Internet Explorer? What about http://admin-pc/Reports?
Are there permission issues? By default the only users that can access SSRS are those in the BUILTIN\Administrators group. Is your user in this group?
Is UAC mucking me up? As above, only Administrators will have default access, but if UAC is enabled you still won't connect as an admin even if you're in this group. Try running BIDS or Internet Explorer with Run As Administrator and see if it makes any difference.
Is the URL being registered successfully? The URLs won't work if the port is already in use, but Reporting Services Configuration Manager will quite happily allow you to set this without an error even if the port's in use; it's especially when using port 80.
Check the log file at Program Files\Microsoft SQL Server\<SSRSInstance>\Reporting Services\LogFiles; this will have an error logged if it can't register the URL on the port specified. If you see an error here try a different port.
Any other errors in the log? Failing this, check the log for any more errors.
Not much to go on, I admit, but maybe there's something you haven't looked at here. I'd saying stepping through these checks has solved 99% of the errors that I've seen in the past.
I'm developing on SQL Server 2012 Enterprise, and I have a problem. When I access "Reporting Services Configuration Manager" the Report Service Status shows Started, but if I go to the Report Manager URL http://<my computer name>/Reports sometimes when I restart the computer I get a log in dialog and then the SSRS is working fine but sometimes I get this:
I tried different browsers, restarting the SSRS service but nothing seems to help any ideas?
I found the solution, it appears that Skype was using the 80 port that the SSRS was trying to use and that prevented me from entering the report service.
You need to edit Skype settings go to Tools->Options->Advanced->Connection and uncheck the “Use port 80 and 443 as alternatives for incoming connections"
and that fixes everything :)