March 30, 2005 at 11:27 am
I rolled out a new report yesterday that I had been creating / testing on the machine that has both SQL and RS installed. It worked great and I sent out the link.
Today, I came in to messages that they were getting "page cannot be displayed".
I checked by trying to access the report from a remote computer - "page cannot be displayed".
I then tried connecting to the Report Manager, which I am positive was working just fine last week - "page cannot be displayed".
I can deploy reports and access both the Report Manager and all reports from the machine with RS installed.
Since they can't access the RM, it doesn't seem to be a report or single solution problem, seems to be RS or IIS related. I don't think I changed any settings since last week, but I went thru everything just to make sure.
I rebooted the machine. I tried every possible combination of anonymous, basic, windows authentication on the report and reportserver websites in IIS. I checked the security and permissions from the local Report Manager.
I just don't get it. ERGGG! I feel like I'm going insane...
Any suggestions?
March 30, 2005 at 7:35 pm
using ServerA as your production server (one that's not working) and ServerB as your dev server ->
Just to clarify, you can deploy reports to to Server A and ServerB from eithin VS2K3?
Have you tried accessing http://ServerA/reportserver to see if the webservice returns a folder/report list?
Steve.
March 31, 2005 at 9:49 am
Actually, I only have ServerAB - both dev and production, it's a Windows XP SP2 box with VS2k3, SQL, and RS installed. I verified that I can access http://pb000778/reports/ and http://pb000778/reportserver/ and http://pb000778/ from ServerAB, but when I log onto any other machine, I get: "The page cannot be displayed". Seems like an IIS problem, no? IIS is supposedly running without error.
I do have a W2k3 Server with SQL and RS installed that is working. (Although I don't want to deploy the reports in question to this server because it doesn't make sense in our network and corporate structure.)
I compared the default websites in IIS - the only thing that is different is that the XP machine (ServerAB above) has SSL port 443 established (and Remove is grayed out) and the server does not have an SSL port established. Also, on the Directory Security Tab, the Edit button is grayed out under IP Address and domain name restrictions on the XP machine, but not on the server.
Just some oddities I need to look into.
Obviously, I am not an expert, so any help would be wonderful.
Thanks so much,
-Megan
April 6, 2005 at 5:20 pm
Have you checked your IIS logs? This may tell you why the request is being rejected. A gut feel is security but it's hard to tell. Did you install RS until SSL on pb000778? If so, then i'm not sure why hitting "http//..." from your local machine will work, i would have thought it should require "https://...."?
Steve.
July 17, 2007 at 12:43 pm
were you able to find the solution for your problem? I am facing the same problem..Thanks
July 17, 2007 at 4:09 pm
uninstalled reporting services
deleted reports and reportserver databases from sql
installed reporting services
installed sp2
installed after sp2 patch
checked rs and sharepoint on same box 'patches' (search MS for KB article on this if you have sharepoint on the same box)
that seemed to fix the problem, but i tried it several months after this posting, so it could have been a coincidence too.
Good luck!
July 17, 2007 at 4:16 pm
Also -
I don't think you can use Win XP as a host for others to view RS reports, so if that is what you are trying to do, I don't think it will work. I think you need a server.
And make sure you have the right setting set on:
[servername]\reports - site settings - site-wide security
and
[servername]\reports - properties - security
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply