Solved

A connection could not be made to the report server

Posted on 2011-02-14
10
262 Views
Last Modified: 2012-08-13
In SQL 2005 Reporting Services, I have made some simple changes to a report.  I just added two columns of data.

Next, I went to Build the report.  I got no errors.  Next, I went to Deploy the report and got the following error:

A connection could not be made to the report server:  https://.........com/Reports
Unable to connect to the remote server.

I do not want to give out the name of the URL.  So, that's why I typed "..." in the URL above.

I can run the report with the two new columns just fine in the Business Intelligence Development Studio.  But, I need to deploy it, so that the SharePoint web site that users use to access this report on a daily basis can see my changes.

This is the first time in the two years that I have been administering these reports that an error like this has happened.  But, over the last few months, some others on my team have been accessing the servers on this network and running updates, etc.  Perhaps, something got "upset".

Thanks!
0
Comment
Question by:apitech
  • 6
  • 4
10 Comments
 
LVL 1

Expert Comment

by:billwillyerd
ID: 34889621
Hello,
Is it just this one report or are any others failing that use the same URL?
0
 
LVL 1

Author Comment

by:apitech
ID: 34889695
Well, I don't have to deploy the others because I did not make any changes to them.  They all do use the same URL, however.  So, my guess is that they would all have this problem.  I don't want to test that theory, though, for fear of making this problem worse.
0
 
LVL 1

Author Comment

by:apitech
ID: 34889761
I did try, for the heck of it, re-deploying the .rds in addition to this one .rdl.  I got the same error.
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 1

Expert Comment

by:billwillyerd
ID: 34889819
My question was basically related to network connectivity and the ability of the report portal (https server) to see the report server. So, I would start by validating connectivity between the web server and the Report server. Once that is verified, I think you may have solved your issue. It may be related to firewalls settings either 3rd party or MS. Those are the things I would check first.
0
 
LVL 1

Author Comment

by:apitech
ID: 34889998
So, there's no smoking gun?  The connectivity is there.  I'm not sure what else to do.
0
 
LVL 1

Expert Comment

by:billwillyerd
ID: 34890087
Do you have access to both the web and the SQL servers?
If so, make sure in IIS that it the Site is Reports and not ReportServer.
If that fails there is this link with some information you may find useful.
0
 
LVL 1

Author Comment

by:apitech
ID: 34890264
No luck on any of that.  Anything else?

I don't get why this has happened all of a sudden!  I didn't just create these reports.  They have been working for years, and I have been able to successfully deploy for years.
0
 
LVL 1

Expert Comment

by:billwillyerd
ID: 34890651
Without physical access to the system to review the objects, I don't have anything else to add. From past development issues, it will most likely be a variable name, or value that has altered just a bit, or some step in the deployment that needs special attention. I have sung the same song 'it has worked for years' and then found one of the items listed above or something similarly simple that puts your world right again. I guess I can add this, talk one of your team mates through your process, so you have a fresh set of eyes on the page. Sometimes just walking someone else through your process will uncover the issue.
Good luck
0
 
LVL 1

Accepted Solution

by:
apitech earned 0 total points
ID: 34915463
Here is the answer:
So the short story is that the user account SSRSSERVICEACCT had a proxy setting in IE that was attempting to send the traffic out to the proxy service.  The IP address that it was being sent to is the one that was returned every time I attempted to run the deploy routine.
0
 
LVL 1

Author Closing Comment

by:apitech
ID: 34949656
This was the answer that our internal IT guy came up with and, when he found this and fixed it, I was able to successfully deploy my SQL reports.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In SQL Server, when rows are selected from a table, does it retrieve data in the order in which it is inserted?  Many believe this is the case. Let us try to examine for ourselves with an example. To get started, use the following script, wh…
In this article I will describe the Backup & Restore method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question