TFS web report issue

Question

We have 2 TFS servers.  Using IE, I can view reports on one by going to http://servername/reports.  However, when I try to view reports on the other server, I get as far as selecting the actual report (i.e. Burndown / Burn Rate) and get "IE cannot display the webpage".  I can see the reports on both servers using Firefox and through IE on a different computer using the same logon credentials.  I suspect a client-side issue but cannot understand why reports from one server would work and not from the other.  I have upgraded to IE9, reduced security settings to the bare minimum, cleaned-up the browser etc. to no avail.  Any ideas?

Answer 1

Hi setfsadmin,

Thank you for your post.

According to your description of the issue, hope you can provide following information to help narrow down the issue:
1. In one TFS server machine, use IE to access both report server, can you see the report?
2. Change to another, use IE to access both report server, can you see the report?
3. Use a third machine, use IE to access both report server, can you see the report?
4. Is there any windows log relate to this case?

Regards,

---

Lily Wu [MSFT]
MSDN Community Support | Feedback to us

Answer 2

Thanks for your reply.

From either server, using IE, I can see reports on both servers.  From another workstation, using my same credentials, I can see reports on both servers using IE.

From IE my main computer I can see reports on one server but not the other.  I am sure it's a client-side issue.  My IE log is empty right now - I'll enable logging and see what comes up.

Answer 3

Hi setfsadmin,

How abou the issue now?

Is there any detail log you find out?

Hope you can share your experience here.

Regards,

---

Lily Wu [MSFT]
MSDN Community Support | Feedback to us

Answer 4

I have not been able to resolve this issue.  My IE logs are enabled but empty.

Answer 5

Hi setfsadmin,

Thank you for your post.

I am trying to involve someone to further look at this issue. There might be some time delay. Appreciate your patience.

Thank you for your understanding and support.

Regards,

---

Lily Wu [MSFT]
MSDN Community Support | Feedback to us

Answer 6

Have you tried this when running IE "As Administrator"? Also, do you have anything extra like Google Toolbar or anything else running on the instance of IE that cannot access the reports? Have you tested the page using  IE 9  with no add-ins?  See this link for how to do this:

http://www.thewindowsclub.com/run-internet-explorer-8-in-no-add-ons-mode

 

---

Trevor Hancock (Microsoft)
Please remember to "Mark As Answer" the replies that help.

Answer 7

Thanks very much.

Answer 8

Thanks for the suggestions.  I have tried both running IE9 as an administrator and in no add-ins mode, without success.  I do not have any toolbars installed and have checked for spyware.  Like I said, Firefox works OK for the reports on both servers, so there must be something going on with my IE.  Quite why IE can access reports on one server and not the other, though, is a mystery.

Answer 9

Hi setfsadmin,

You may have already tried this, but can you  clear the cache in IE 9 and try?  Here are the steps:

http://quikstarts.com/Internet/Internet-Explorer-9/How-to-clear-the-browser-cache-in-IE-9/

Do you have any firewall settings on the machine that are blocking any ports or sites?

Can you try running  Fiddler on a machine that works and on the machine that fails?  You can then compare the resulting logs for differences.  Here are the steps for running Fiddler:

The Fiddler tool has a Help file and video, but I wrote some simple instructions that you can follow to capture the trace. I hope they help.

1. Visit the following Web site, and then install the most recent version of the Fiddler tool:
http://www.fiddlertool.com/Fiddler/version.asp
2. To start the Fiddler tool, click Start, point to All Programs, and then click Fiddler.
3. In the Fiddler window, make sure that Capture Traffic is selected on the File menu. Note This menu option toggles between On and Off every time that you click it. Make sure that there is a check mark next to the Capture Traffic option.
4. Now that the Fiddler trace file is running, perform the same operation that previously caused problems.
5. After the issue is reproduced, switch back to the HTTP Fiddler window.
6. On the File menu, click Capture Traffic to stop the data collection.
7. Click anywhere in the Web Sessions window.
8. On the File menu, click Save.
9. In the Save list, click Sessions, and then click as ZIP to save the HTTP Fiddler trace file. If you are prompted to save all sesssions answer "Yes."

You can post the Fiddler log of the failed attempt if you like.

Thanks!

---

Trevor Hancock (Microsoft)
Please remember to "Mark As Answer" the replies that help.