• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 713
  • Last Modified:

SSRS report domain problem

I have the following situation:

I am developing a website in ASP.NET which uses SQL Server Reporting Services (SQL Server 2005) to display reports to the user. We already have done this numerous times and never ran into any problems.

However last week we ran into a new problem:
The website we are currently developing is getting "permission denied" errors on javascript calls from the ReportViewer component in IE (When using Firefox we don't get the problem). This only happens whenever we try to access the page through the fully qualified domain name (Eg: http://expertsexchange.location.mycompany.com/Report.aspx), however when I access it through only the computer name (Eg: http://expertsexchange/Report.aspx) the page does work and no error is shown.

Weirdly enough, we have running another website on the same machine which also uses SSRS to show reports and this website is not giving these problems. I already have checked IIS and folder settings and those are the same. So we have run out of ideas. Does anybody have suggestions?
0
existenz2
Asked:
existenz2
  • 3
  • 2
1 Solution
 
PFrogCommented:
Could it be to do with IE zone security? check which zone both URLs fall under. I'm guessing  http://expertsexchange falls under the intranet zone, whereas http://expertsexchange.location.mycompany.com is internet and not trusted.
0
 
existenz2Author Commented:
No, because that would mean it is a reoccuring problem on other websites also on the same server. Besides that the websites run in a fully trusted intranet.
0
 
PFrogCommented:
It has to be a client problem, otherwise it would also fail with firefox.
If the only difference between the two calls is the server name, then it can only be a setting within IE on the client to do with the server.

As a test, have you tried it with the IP address to see what that does?
0
 
existenz2Author Commented:
Hmm no, I haven't tried ip address yet indeed. If the ip is static and we can't find a solution for the problem, that also is a very good alternative to use also (Especially since the website runs inside a portal environment and the url isn't shown anyway).

I'll give it a shot asap and see what happens then.
0
 
existenz2Author Commented:
It indeed had to do with ip names and domain names. What the exact problem was is, is however still unknown.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

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.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now