December 11, 2017 at 1:42 pm
Hello!
On the SQL 2016 Server I am a "DBA" of now, I was looking to setting up SSRS. At first glance it looks like it is installed, but when I try to browse to http://localhost/reports no page comes up. The localhost default IIS page does work, so IIS is operational.
I have done the following troubleshooting steps:
1. The SSRS Service package is installed (I ran SQL 2016 media and went to add features and it is already added).
2. The Service - "SQL Server Reporting Services (MSSQLSERVER)" is installed, and it is started.
3. If I run "Reporting Services Configuration Connection" and enter the local server name and click "Find" - no instances are found.
4. If I use SSMS to connect to the Report Server Instance also no instance is found.
5. When I look at the Database list in SSMS, my DB's are there but the two ReportServer and ReportServerTmp that I'm expecting to see do not even exist. (Did my predecessor delete them for some reason?)
6. The local paths seem to exist for the SSRS instance - C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services
What are my options to get this working again?
-Mark
MSSQL 2019 Standard, Azure Hosted. Techie/Sysadmin by trade; Three years as a "DBA" now.
December 11, 2017 at 4:17 pm
usererror - Monday, December 11, 2017 1:42 PMHello!On the SQL 2016 Server I am a "DBA" of now, I was looking to setting up SSRS. At first glance it looks like it is installed, but when I try to browse to http://localhost/reports no page comes up. The localhost default IIS page does work, so IIS is operational.
I have done the following troubleshooting steps:
1. The SSRS Service package is installed (I ran SQL 2016 media and went to add features and it is already added).
2. The Service - "SQL Server Reporting Services (MSSQLSERVER)" is installed, and it is started.
3. If I run "Reporting Services Configuration Connection" and enter the local server name and click "Find" - no instances are found.
4. If I use SSMS to connect to the Report Server Instance also no instance is found.
5. When I look at the Database list in SSMS, my DB's are there but the two ReportServer and ReportServerTmp that I'm expecting to see do not even exist. (Did my predecessor delete them for some reason?)
6. The local paths seem to exist for the SSRS instance - C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting ServicesWhat are my options to get this working again?
When setting up SSRS, you can install Reporting Services on one server and the databases on another so missing those databases may not mean too much. They could just be on another server. You can check the other instances and see if you find the databases. From there, SSRS polls things frequently so you can see if you can get information on the Report Server connection - something basic along the lines of: SELECT
s.session_id,
c.connect_time,
c.last_read,
c.client_net_address,
s.[host_name]
FROM sys.dm_exec_connections c
INNER JOIN sys.dm_exec_sessions s
ON c.session_id = s.session_id
WHERE s.[program_name] like 'Report%'
IIS doesn't really matter to SSRS anymore as it goes through http.sys starting with SQL Server 2008. So you can ignore that.
If you go to the C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles directory, that is where the ReportingServices log files are normally located. If you find some there, the naming convention is ReportServerService_<data and time stamp>.log
If the log files are there, open one up and at the beginning the initialization steps and configuration information is logged. In that file, search for the attribute <SystemName>. Those should have the server name. Not necessarily instance name but just the server.
And then if you search that file for registered url. There should be two - one for ReportServer/ and another for Reports/ and the reservation for Reports is what you are looking for.
When you try to connect, log onto the server where it's supposed to be located and right click on Internet Explorer and select run as administrator and see if that let's you connect. You normally don't get a blank page - you get things like a prompt for credentials, the main page for Report Manager or an error page.
Sue
December 12, 2017 at 6:02 am
Sue,
Thanks for posting back! I left out a crucial detail, we only have one SQL Server the previous person in my chair built (and that I am seriously considering scrapping and building new). So the "ReportServer" and "ReportServerTmp" databases are definitely gone.
I opened the SSRS Log files and here are some details that are interesting:
The <SystemName> variable is as I expected, the hostname of our single SQL Server.
Below are error / warning lines for today's freshly created log file ReportServerService__12_12_2017_03_25_14.log. It looks like there is not a URL configured at all.
WARN: Endpoint 2 is enabled but no url is registered for vdir=, pdir=C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\ReportServer
ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
ERROR: Error initializing configuration from the database: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error.
ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
ERROR: ServiceStartThread: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error.
ERROR: ServiceStartThread: Attempting to start service again...
If I look at the rsreportserver.config file in the <URLReservations> section, those also appear to be blank configurations, as well as the <DSN></DSN> section is blank:
<Dsn>
</Dsn>
<ConnectionType>Default</ConnectionType>
<LogonUser>
</LogonUser>
<LogonDomain>
</LogonDomain>
<LogonCred>
</LogonCred>
<InstanceId>MSRS13.MSSQLSERVER</InstanceId>
...
<URLReservations>
<Application>
<Name>ReportServerWebService</Name>
<VirtualDirectory>
</VirtualDirectory>
<URLs>
<URL>
</URL>
</URLs>
</Application>
<Application>
<Name>ReportServerWebApp</Name>
<VirtualDirectory>
</VirtualDirectory>
<URLs>
<URL>
</URL>
</URLs>
</Application>
</URLReservations>
-Mark
MSSQL 2019 Standard, Azure Hosted. Techie/Sysadmin by trade; Three years as a "DBA" now.
December 12, 2017 at 6:26 am
Sue
December 12, 2017 at 12:16 pm
Sue_H - Tuesday, December 12, 2017 6:26 AMIt looks like it was never configured - maybe had some installation issues if Reporting Services Configuration Manager can't find it.
If there are no databases there are no reports and there is nothing else configured. You could just uninstall and reinstall. The uninstall could have issues if Configuration Manager can't find things but I'd still try that for now.Sue
I'm up and running! Part was that SSRS was truly not even configured and part of it was user error. 🙂 I've installed SQL Server for the last 5 years for facilities, but never once not used the option to let the installer package configure SSRS and create the SSRS databases.
I was able to uninstall SSRS and then reinstall it without any errors on that portion. However, when I ran the Report Server Configuration Manager I still received the error about not finding the report server instance. Here is where the user error occurred - I noticed on the Server 2012 start menu search screen that there are two "Report Server Configuration Manager" icons. One I realized after this is for SQL Server 2017 and then for SQL Server 2016. Each time I tried launching this manager I seemed to have been launching the executable for the 2017 instance. I wasn't sure how that got there, until I checked the install date for SSMS 17.3 which had the same date stamp as the SQL 2017 that is listed in Programs & Features.
Once I had the correct Report Server Manager running, it found my instance, and I walked through this guide to setting up the Database creation, URLs for /reports /reportserver and we're in business. Now I can start testing/practice with some simple SSRS reports in Visual Studio.
Thank you again for the nudges!
-Mark
MSSQL 2019 Standard, Azure Hosted. Techie/Sysadmin by trade; Three years as a "DBA" now.
December 12, 2017 at 12:24 pm
usererror - Tuesday, December 12, 2017 12:16 PMSue_H - Tuesday, December 12, 2017 6:26 AMIt looks like it was never configured - maybe had some installation issues if Reporting Services Configuration Manager can't find it.
If there are no databases there are no reports and there is nothing else configured. You could just uninstall and reinstall. The uninstall could have issues if Configuration Manager can't find things but I'd still try that for now.Sue
I'm up and running! Part was that SSRS was truly not even configured and part of it was user error. 🙂 I've installed SQL Server for the last 5 years for facilities, but never once not used the option to let the installer package configure SSRS and create the SSRS databases.
I was able to uninstall SSRS and then reinstall it without any errors on that portion. However, when I ran the Report Server Configuration Manager I still received the error about not finding the report server instance. Here is where the user error occurred - I noticed on the Server 2012 start menu search screen that there are two "Report Server Configuration Manager" icons. One I realized after this is for SQL Server 2017 and then for SQL Server 2016. Each time I tried launching this manager I seemed to have been launching the executable for the 2017 instance. I wasn't sure how that got there, until I checked the install date for SSMS 17.3 which had the same date stamp as the SQL 2017 that is listed in Programs & Features.
Once I had the correct Report Server Manager running, it found my instance, and I walked through this guide to setting up the Database creation, URLs for /reports /reportserver and we're in business. Now I can start testing/practice with some simple SSRS reports in Visual Studio.
Thank you again for the nudges!
Glad to hear you got it going again - and thanks for posting back.
And now I remember your user name, the user name I said I liked 🙂
Your still doing it well with posting information needed. And then followed up - Thanks!
Sue
February 6, 2018 at 6:32 am
Just as a follow up I have my first SSRS report working. It's silly, but a decent first learning project. I used BGInfo from Microsoft to log workstation information into a Database. Now I have an SSRS report that pulls that data so I can sort out by OS Version, Office Version, Memory, CPU, etc so I can aid our IT vendor on getting our office workstations upgraded. It's quite nice.
-Mark
MSSQL 2019 Standard, Azure Hosted. Techie/Sysadmin by trade; Three years as a "DBA" now.
February 8, 2018 at 4:51 pm
usererror - Tuesday, February 6, 2018 6:32 AMJust as a follow up I have my first SSRS report working. It's silly, but a decent first learning project. I used BGInfo from Microsoft to log workstation information into a Database. Now I have an SSRS report that pulls that data so I can sort out by OS Version, Office Version, Memory, CPU, etc so I can aid our IT vendor on getting our office workstations upgraded. It's quite nice.
Very nice...something useful - and not some generic report listing customers or orders from a demo database. 🙂
Sue
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply