February 9, 2012 at 8:13 am
Our production database is in SQL Server 2005 SP4. We used to have SQL 2005 installed on a different server, but some years ago we had to migrate it off of that server to its current location. On the old server SSRS worked fine, had a nice web user interface that users could use fine, etc. However, on its current location something went wrong in setting up SSRS. Instead of a web interface, with links to the various reports, entering http://ourserver/reportserver in the web browser's address bar gives us a directory listing. This the users HATE, and thus won't use, so we're reduced to having to run all of the reports for them, since they refuse to run them for themselves.
What did we do wrong? How do we fix it?
Kindest Regards, Rod Connect with me on LinkedIn.
February 9, 2012 at 2:53 pm
The URL for the pretty SSRS interface isn't http://servername/reportserver it is http://servername/reports. That drives me insane as well.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 10, 2012 at 8:10 am
Jack Corbett (2/9/2012)
The URL for the pretty SSRS interface isn't http://servername/reportserver it is http://servername/reports. That drives me insane as well.
Oh, interesting, I didn't realize. Thank you for correcting me.
OK, so I just tried it. I've got an error that reads:
Error
Unable to connect to the remore server
and then there's a hyperlink labeled "Home".
The URL is: http://servername/reports/Pages/Folder.aspx. And the hyperlink points to the same page that I'm already on. Any ideas as to what's wrong?
Kindest Regards, Rod Connect with me on LinkedIn.
February 10, 2012 at 8:20 am
What do you see when you go into Report Server Configuration on the report server? That should tell you what the URL's are setup as and if you have any errors in your configuration. I don't think you have any errors because the reports work, but you aren't getting the "nice" interface.
When all else fails you can always create a web page as a portal to the reports so the users can go to that to get to the reports without seeing the directory structure.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 10, 2012 at 9:27 am
OK, right off I've got to tell you that I'm not familiar with Report Server Configuration Manager.
So, I got into it on the report server. On the left side of the page, it has 6 items which all have those green check marks next to them: Server Status, Report Server Virtual Directory, Report Manager Virtual Directory, Windows Service Identity, Web Service Identity, Database Setup.
The Report Server Virtual Directory is pointing to a website on the server named ReportServer.
The Report Manager Virtual Directory is pointing to a website on the server named Reports.
SharePoint Integration and Encryption Keys both have a blue exclamation mark next to them, but that indicates that they're optional configurations, and at least with respect to SharePoint that's fine, as we don't even use SharePoint.
Initialization (whatever that means) is "not supported in the current mode" (it has a gray check mark next to it).
Both Email Settings and Execution Account have a yellow exclamation mark next to them. I can try to set up the email settings, but I've no idea what the Execution Account means or is. (I just tried configuring the email settings, but that failed. I'm not surprised in a way, because the email address we'd use requires changes to the default SMTP port, and that Report Server Configuration Manager UI doesn't really give me access to change the ports.)
Kindest Regards, Rod Connect with me on LinkedIn.
February 10, 2012 at 9:47 am
Rod at work (2/10/2012)
OK, right off I've got to tell you that I'm not familiar with Report Server Configuration Manager.So, I got into it on the report server. On the left side of the page, it has 6 items which all have those green check marks next to them: Server Status, Report Server Virtual Directory, Report Manager Virtual Directory, Windows Service Identity, Web Service Identity, Database Setup.
The Report Server Virtual Directory is pointing to a website on the server named ReportServer.
The Report Manager Virtual Directory is pointing to a website on the server named Reports.
SharePoint Integration and Encryption Keys both have a blue exclamation mark next to them, but that indicates that they're optional configurations, and at least with respect to SharePoint that's fine, as we don't even use SharePoint.
Initialization (whatever that means) is "not supported in the current mode" (it has a gray check mark next to it).
Both Email Settings and Execution Account have a yellow exclamation mark next to them. I can try to set up the email settings, but I've no idea what the Execution Account means or is. (I just tried configuring the email settings, but that failed. I'm not surprised in a way, because the email address we'd use requires changes to the default SMTP port, and that Report Server Configuration Manager UI doesn't really give me access to change the ports.)
All of that sounds fine. You don't really need the Email and Execution Account for SSRS to work. I'm really at a loss as to why the http://reportservername/reports does not work. It appears to be setup correctly.
Take a look at this blog post, http://skamie.wordpress.com/2011/05/26/ssrs-error-unable-to-connect-to/
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
April 4, 2012 at 11:57 am
I know it's been a while since I last responded to this tread, but it's becoming important again. I think what happened was the former DBA, when he set up our current server for SQL Server, he just copied all of the report files from the old server, and plopped them into the folder directory for the new server (years ago). And I'm guessing that's why they've never worked on the current, production server.
How do I fix it, given that scenario?
Kindest Regards, Rod Connect with me on LinkedIn.
April 5, 2012 at 8:17 am
What's the current state? Has anything changed from above? What happens if you try clicking on the link from inside the report server configuration manager? (both Web Service URL and report Manager URL)
April 5, 2012 at 8:52 am
Steven.Howes (4/5/2012)
What's the current state? Has anything changed from above? What happens if you try clicking on the link from inside the report server configuration manager? (both Web Service URL and report Manager URL)
It hasn't changed at all from when I posted the messages back in February. It's just a case of not being able to give it any time. I don't know how to click on the links from inside of the Report Services Configuration Manager. When I click on "Report Server Virtual Directory" or "Report Manager Virtual Directory" (which both have a green check mark next to them) it shows the proper virtual directory in IIS for both of them, but there's no clickable link to either website from within Reporting Services Configuration Manager.
If I bring up IE and enter the websites in the address bar, I get this:
for localhost/Reports: "Internet Explorer cannot display the webpage"
for localhost/ReportServer: "Internet Explorer cannot display the webpage"
If I use Firefox I get:
for localhost/Reports: "Unable to connect"
for localhost/ReportServer: "Unable to connect"
Kindest Regards, Rod Connect with me on LinkedIn.
April 5, 2012 at 10:01 am
My Mistake. I've been using the 2008 Reporting services Configuration for so long I forgot what the 2005 version looked like. I thought they were the same...
What happens if you try connecting using the IIS Manager? (Servername -> WebSites ->Default Webpage >rightclick & choose Browse)
April 6, 2012 at 6:02 am
Steven.Howes (4/5/2012)
My Mistake. I've been using the 2008 Reporting services Configuration for so long I forgot what the 2005 version looked like. I thought they were the same...What happens if you try connecting using the IIS Manager? (Servername -> WebSites ->Default Webpage >rightclick & choose Browse)
Don't know. Will try when I'm at work.
I've been wondering if we wouldn't be better off just uninstalling SSRS and re-installing it again. If we went that route, would it just be a case of using the SQL 2005 DVD to uninstall & re-install?
Kindest Regards, Rod Connect with me on LinkedIn.
April 6, 2012 at 8:24 am
Steven.Howes (4/5/2012)
My Mistake. I've been using the 2008 Reporting services Configuration for so long I forgot what the 2005 version looked like. I thought they were the same...What happens if you try connecting using the IIS Manager? (Servername -> WebSites ->Default Webpage >rightclick & choose Browse)
OK, I'm at work and can try usein IIS Manager from the server to see how it behaves. If I try to browse http://<ourserver>/Reports I get the following:
"This program cannot display the webpage"
If I try to browse, from within IIS, the website http://<ourserver>/ReportServer, I get the following:
"This program cannot display the webpage"
Kindest Regards, Rod Connect with me on LinkedIn.
May 3, 2012 at 11:27 am
Rod at work (4/4/2012)
I think what happened was the former DBA, when he set up our current server for SQL Server, he just copied all of the report files from the old server, and plopped them into the folder directory for the new server (years ago). And I'm guessing that's why they've never worked on the current, production server.How do I fix it, given that scenario?
If that is how he did it, and he did not do anything with the encryption key, it's not supposed to work. Is the old server still available and operational? Perhaps you can "backup" the encryption key there, and "restore" it to this server.
Of course, before you go and change the key on the new server, make a backup copy of that, just in case things get worse.
There are several reasons why this won't work. The encryption key must be backed up when anything dealing with credentials changes... like the service accounts used. The algorithm used to create the symmetric key, also uses the private and public keys on the server (those of the user performing the work). It then uses the password provided to encrypt the file where you backup the key.
I am intimately involved in a similar situation this week. Perhaps we can help each other here.
Thank-you,
David Russell
Any Cloud, Any Database, Oracle since 1982
Viewing 15 posts - 1 through 15 (of 19 total)
You must be logged in to reply to this topic. Login to reply