TfsRedirect.aspx not always redirecting to correct Web Access url.

Question

After i upgraded to TFS 2012 i have noticed some very strange behaviour of the TfsRedirect.aspx on our sharepoint portals. They used to direct to an url which still lingered from back when Web Access was a separate installation and website in IIS.

In our case this URL was https://tfswa.*****.com/tfs/web. Now after the upgrade this URL does not work anymore. This should not be a problem, because the actual url https://tfs.*****.com:8081/tfs works like a charm.

However TfsRedirect still redirects to the old URL sometimes:

- On my work machine (an almost clean Win 7) it redirects to the correct url.

- On my home machine (a brand spanking new Win 8 install) it redirects to the old incorrect url.

- On a co-workers work machine (long running Win 7 install) it redirect to the old incorrect url.

I have already tried running the ClearCache parameter to the TfsRedirect.aspx page to no avail.

I have also recreated the Sharepoint integration target in TFS Admin console, also no luck.

Also changed the notification url in the application tier settings in the TFS Admin console, and then back again to the original and correct value. No luck either.

I'm starting to lose my marbles here. Can anyone help?

Thanks,

Jeroen

Answer 1

Hi Jeroen,

Thanks for your post.

If this issue also happened on TFS 2010 Server machine?(open team project portal on server machine, and link to Web Access)

On that clients which occurred this issue, navigate to the following address in web browser:

http://SharePointServer/sites/TeamProjectCollectionName/TeamProjectName/_layouts/TfsRedirect.aspx?tf:type=webaccess&tf:test=1&tf:clearcache=1.

This will force a refresh of the SharePoint information about the TFS Team Project specified. This page should not return any errors and the value for TeamFoundation.Temp.LastRefreshDate should include the current date. Then check the Redirect URL value under Redirector Test section in that page, ensure it’s the new Web Access url.  

And  if this issue only occurred on client, try to clean the Cache folder on client.    

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us

Answer 2

Hi John,

I have already tried the ClearCache parameter of the TfsRedirect.aspx (as i stated in the original post), and this didn't work (obviously).

Which Cache folder on the client are you talking about? I was unaware that the TfsRedirect.aspx looks at some TFS Cache folder on my local client machine.

Thanks,

Jeroen

Answer 3

Hi Jeroen,

Thanks for your reply.

On client machine, under folder: C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation(os: Windows Server 2008 R2), the TFS 2012 Server Cache folder is under 4.0\Cache, TFS 2010 Cache folder is under 3.0\Cache, please try to both clean the Cache folders which under 4.0 and 3.0 folder.  

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us

Answer 4

Hi John,

We have tried this, and clearing out the cache folders doesn't fix the problem. Do you have any other suggestions?

Answer 5

Hi Jeroen, 

Thanks for your reply.

It seems that you have already tried all the suggestions which we can try. 

At last, I suggest you install the TFS Power Tools, then perform the Best Practices Analyzer to scan your TFS Server.   

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us

Answer 6

Hi John,

I ran the Best Practices scan for the Beta, but i got such strange results that i have a feeling they need to do some tweaking before it will work on the RTM. Most issues i got seemed to be related to the warehouse, so i have a feeling they are not causing this problem.

The only strange thing i saw was:

Cannot access SharePoint Server "tfs.****.com". The results of rules that require access to SharePoint are not included in the report.

Which is probably keeping the tool from finding out other stuff about sharepoint.

I ran the tool as an administrator on the TFS Server. But still this warning pops up.

Answer 7

From a support perspective this is really beyond what we can do here in the forums. This will require  some in-depth troubleshooting. If you cannot determine your answer here or on your own, consider opening a support case with us. Visit this link to see the various support options that are available to better meet your needs:  http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone.

---

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

Answer 8

Hi Trevor,

I will try a workaround with my firewall admin to see if we can reroute the original address correctly to the new one. If that is the case i have a little more time phasing out the old address. I'll contact microsoft support when i have a bit more time on my hands.

I'll be sure to update this post if I ever find a solution, either on my own or with the help of MS Support.