TF80068 Team Foundation error when opening Project Server 2007 file after installing VS2010SP1 - by Travis Shepherd

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 651290 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 3/14/2011 7:31:54 AM
Access Restriction Public


After installing Visual Studio 2010 SP1 on my machine, every time I open a project on our project 2007 server, I receive an error:

TF80068: Team Foundation encountered an error while communicating with the server.
Check your connection and try again.

Dismissing and attempting to add new tasks/mark tasks complete/etc yield similar errors.

We are not using Team Foundation server at this time.  Previously I had VS2010 installed and did not have any issues.
Sign in to post a comment.
Posted by EeeeEfff on 6/24/2011 at 1:04 PM
For anyone encountering this, the hotfix in solved this problem for me.
Posted by reidca on 6/10/2011 at 1:54 AM
Apologies for the late reply, I can confirm that when both hotfixes are installed the problem is resolved.
This has been tested on two machines (Windows XP SP3).

What is strange is the hotfix ( has a date of February 23rd 2010. Surely, if this was an important fix it should have been pushed out as part of the other hotfix or in a service pack.

Anyway, thank you for looking into this.

Posted by Federico [MSFT] on 5/24/2011 at 9:47 AM
Hi Carl, can you also please make sure you have the following Project Professional 2007 Hotfix installed on your client machine,
Posted by Federico [MSFT] on 5/24/2011 at 9:18 AM
Hi Carl, I'm sorry to hear the fix has not resolved your issue. I would like to ask you to collect some debugging information in your system to see what is the problem you are experiencing.

Can you please create the file winproj.exe.config with the contents below and drop it next to winproj.exe. Then close MS Project and repeat your scenario until you see the error. At that point you should be able to see a log file under %temp% that should contain more details about the error. Can you please share that?

<?xml version="1.0"?>
     <add name="General" value="4" />
    <trace autoflush="false" indentsize="4" />

Also, please feel free to contact me directly at

Thank you.
Posted by reidca on 5/13/2011 at 1:52 AM
Thanks for the update.

The hotfix appears to be already available:

However, we have tested this and disappointingly it does not resolve the problem.
Posted by hzieenana on 5/10/2011 at 2:19 AM
To resolve the problem, you can download hotfix in which will be available around May 25th. Thanks.
Posted by reidca on 5/9/2011 at 2:58 AM
Is there any update on this fix? It has been sometime now....
Posted by Microsoft on 4/15/2011 at 9:37 AM

We hear you loud and clear and apologize for the trouble we've caused. We'll create a fix as soon as possible.

Posted by reidca on 4/15/2011 at 1:23 AM
I appreciate your update on this issue and take note of your suggestions.

Whilst installing the feature pack is an option, I would much prefer a client side-solution since the project server is used across the entire company and there is no requirement for the feature pack at this time.

Any installation to a production server requires time for planning, performing the install and testing and it is not something we would undertake lightly respite your assurances!

For the people who have already installed SP1, the work-around to disable the add-in is useful although less than ideal since it must be performed as an administrator and is not something we can automate as part of the VS2010 build.

I cannot stress how important a fix is to us, for credibility reasons as well as technical. After all, service packs are meant to fix issues, not cause further issues.



Posted by Microsoft on 4/14/2011 at 3:55 PM
Hi Ohad and Reidca,

I'm sorry for the trouble that you're having. We know about the issue and are working on a plan for a fix to create a client-side solution.

In the meantime, there are two possible workarounds --
If your IT department permits it, please go ahead and download the Team Foundation Server and Project Server Integration Feature Pack on your Project Server:
Ohad -- I understand the restrictions that IT departments can have. I'll add that the Feature Pack is installed on a Project Server in the Microsoft IT department today and if it will help, I can request the Project Server team to send a note mentioning how benign simply installing the Feature Pack on Project Server is.

If you aren't using the TFS add-in in MS Project to connect to TFS, you can choose to disable to add-in. Please see the Workarounds tab for more information on how Travis did it.

If both of those methods are not acceptable, please let me know as soon as possible.

Posted by reidca on 4/6/2011 at 3:53 AM
This issue is causing us a real problem and has effectively stopped our roll-out of VS2010. Any chance we can have a response from Microsoft as to when a fix might be due?
Posted by Ohad Israeli on 3/30/2011 at 2:15 AM
Its nice to offer to install tfs and proj server integration pack on our project server but in large organizations the IT wont let you install anything on the project server thus we need a client side solution !

if it wasnt clear... i'm suffering from the same issue.
Posted by Microsoft on 3/17/2011 at 6:19 PM
Hi Travis,

We're sorry that you're having trouble here. This is an issue that we caused with the SP1 and we're working on a fix.

In the meantime, the workaround is to go ahead and install the Team Foundation Server and Project Server Integration Feature Pack on your Project Server.

You can download it here:

If you don't have access, please let us know.

To learn more about the Project Server-TFS integration, please check out these blog posts and the documentation:

Posted by Microsoft on 3/15/2011 at 11:59 PM
Thank you for attaching the setup logs. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by Microsoft on 3/14/2011 at 11:49 PM
Thanks for reporting the issue.
Could you please upload a setup log file to help us investigate the issue?
You can get the log files with the following steps:
1) Download collect.exe from the link below.
2) You may choose to save the tool for later use, or to run directly.
3) The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\

You can get more details about how to get the log files here:

Posted by Microsoft on 3/14/2011 at 8:13 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(