Sunday 31 May 2015

Deploying a report local URL not working

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:
  1. Is the service running? If you can connect through Reporting Services Configuration Managerthen the answer is probably yes, but it's always the first thing to check!
  2. 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.
  3. 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?
  4. Are there permission issues? By default the only users that can access SSRS are those in theBUILTIN\Administrators group. Is your user in this group?
  5. 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.
  6. 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.
  7. Any other errors in the log? Failing this, check the log for any more errors.

No comments:

Post a Comment