Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSRS 2005 appears to be broken, how do I fix it?


SSRS 2005 appears to be broken, how do I fix it?

Author
Message
Steven.Howes
Steven.Howes
SSChasing Mays
SSChasing Mays (654 reputation)SSChasing Mays (654 reputation)SSChasing Mays (654 reputation)SSChasing Mays (654 reputation)SSChasing Mays (654 reputation)SSChasing Mays (654 reputation)SSChasing Mays (654 reputation)SSChasing Mays (654 reputation)

Group: General Forum Members
Points: 654 Visits: 2328
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)
Rod
Rod
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1126 Visits: 1928
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,RodConnect with me on LinkedIn.
Rod
Rod
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1126 Visits: 1928
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,RodConnect with me on LinkedIn.
debrucer1
debrucer1
SSC Veteran
SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)

Group: General Forum Members
Points: 258 Visits: 136
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.

Thanks,

David Russell
Oracle Since 1982
SQL Server Since 1998
Rod
Rod
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1126 Visits: 1928
No, on the old server SSRS isn't functional at all.

Kindest Regards,RodConnect with me on LinkedIn.
cphite
cphite
SSC-Enthusiastic
SSC-Enthusiastic (138 reputation)SSC-Enthusiastic (138 reputation)SSC-Enthusiastic (138 reputation)SSC-Enthusiastic (138 reputation)SSC-Enthusiastic (138 reputation)SSC-Enthusiastic (138 reputation)SSC-Enthusiastic (138 reputation)SSC-Enthusiastic (138 reputation)

Group: General Forum Members
Points: 138 Visits: 650
Rod,

Based on the above, my understanding is that you can access the reports via the ReportServer URL but not via the Reports URL... is this still the case?

Maybe a shot in the dark, but I had a similar issue not long ago... log into your server and navigate to C:\Windows\Temp and make sure that whatever account the SQL Reporting Services server is running under has full access to that TEMP directory. Basically, whenever you run the nice friendly interface it's building and modifying temporary files in that directory, and if it doesn't have full access it can't do that properly, and it fails.

Aside from that, if you can run the reports via ReportServer and not via Reports, it's almost certainly a web issue (IIS or something) and not an SSRS issue. Someone mentioned the encryption key, but all those really protect is the data sources. If that key was the issue, what you'd be seeing is that you'd be able to navigate the site okay but whenever you tried to actually RUN a report, it'd fail to connect to the data source.

When you try to go to Reports, are you only doing so from your own computer or have you also tried doing so from the server itself? On the server itself, by default, you get more verbose error messages on your screen when something fails.

Take a look in c:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager and look for the following section:

<system.diagnostics>
<switches>
<!-- 1 = error, 2 = warning, 3 = info, 4 = verbose -->
<add name="DefaultTraceSwitch" value="3" />
</switches>
</system.diagnostics>

Set the DefaultTraceSwitch value to 4, save the file then restart SQL Reporting Services (best to do this via the SSRS Config Manager) and then try going to your Reports site. The log files should be at c:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles
Rod
Rod
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1126 Visits: 1928
cphite (5/3/2012)
Rod,

Based on the above, my understanding is that you can access the reports via the ReportServer URL but not via the Reports URL... is this still the case?

Maybe a shot in the dark, but I had a similar issue not long ago... log into your server and navigate to C:\Windows\Temp and make sure that whatever account the SQL Reporting Services server is running under has full access to that TEMP directory. Basically, whenever you run the nice friendly interface it's building and modifying temporary files in that directory, and if it doesn't have full access it can't do that properly, and it fails.

Aside from that, if you can run the reports via ReportServer and not via Reports, it's almost certainly a web issue (IIS or something) and not an SSRS issue. Someone mentioned the encryption key, but all those really protect is the data sources. If that key was the issue, what you'd be seeing is that you'd be able to navigate the site okay but whenever you tried to actually RUN a report, it'd fail to connect to the data source.

When you try to go to Reports, are you only doing so from your own computer or have you also tried doing so from the server itself? On the server itself, by default, you get more verbose error messages on your screen when something fails.

Take a look in c:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager and look for the following section:

<system.diagnostics>
<switches>
<!-- 1 = error, 2 = warning, 3 = info, 4 = verbose -->
<add name="DefaultTraceSwitch" value="3" />
</switches>
</system.diagnostics>

Set the DefaultTraceSwitch value to 4, save the file then restart SQL Reporting Services (best to do this via the SSRS Config Manager) and then try going to your Reports site. The log files should be at c:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles



I've finally had a chance to try what you suggested. I've given full control privileges to the account that the SSRS service is running under, on that server. Then I brought up web browser on the server, and went to http://myserver/Reports. I got the following error message:

Unable to connect to the remote server


Kindest Regards,RodConnect with me on LinkedIn.
Lynn Pettis
Lynn Pettis
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24171 Visits: 37936
Seems to me that Reporting Services just doesn't like you for some reason. Wish I could help but not familiar with it enough to provide much assistance. I am watching to see how things turn out. Never know when I might face a similar situation.

Cool
Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
debrucer1
debrucer1
SSC Veteran
SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)

Group: General Forum Members
Points: 258 Visits: 136
so we're back to where I came in. You can't see the reports either way. You have the pretty GUI and the list... and before, you were seeing through the list; but, people didn't like that. Now you can't see anything. Perhaps something was left in cache and you've cleared it alone the way. Has this machine been restarted since February? Patches applied, etc? It's not always easy to un-install/re-install SQL Server. I haven't done that since 2006 when this site published my notes on cleaning up. We were using Beta software, so anything I wrote about could have been fixed... Still, it could still be difficult. You would be better off trying to install fresh on another host or in a VM. seems like I had other suggestions, let me finish reading and I will comment again below.

Thanks,

David Russell
Oracle Since 1982
SQL Server Since 1998
debrucer1
debrucer1
SSC Veteran
SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)

Group: General Forum Members
Points: 258 Visits: 136
changing the service accounts used will invalidate the encryption key. I suspect you have now lost your authentication information which means you might as well go ahead and delete the existing key and create a new one. Make a backup of the key to disk before you delete it, just in case. When you make the key, remember the security password you use. You will need to use that if you restore it.

Thanks,

David Russell
Oracle Since 1982
SQL Server Since 1998
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search