Mission Possible? Bind fails after upgrade to TFS 2013

This forum is for all Flare issues related to using Source Control.
Post Reply
Eve Taylor
Jr. Propeller Head
Posts: 1
Joined: Tue Jun 02, 2015 2:45 am

Mission Possible? Bind fails after upgrade to TFS 2013

Post by Eve Taylor »

Hi,

I'm desperately looking for help in binding a new project which completely fails after our TFS 2013 upgrade ("Server path does not exist"). I have no problems in checking out/editing/checking in files that are already bound to source control. I have found some hints here in the forum, tried each and every advice but still no progress.
We're using an older version of Flare (8.1.2), but I cannot think of any reason why binding a new project should pose problems when everything else works fine.

Any ideas here?

Thanks,
Eve
rheinlander
Jr. Propeller Head
Posts: 3
Joined: Thu Feb 08, 2007 8:48 am
Location: Munich, Germany

Re: Mission Possible? Bind fails after upgrade to TFS 2013

Post by rheinlander »

Eve, this may not be the wisest reply. However, Flare 8 may just not be compatible with TFS 2013. So some features of the TFS connection may work, others may not.
For the legacy projects, you can check whether or not the old TFS ist still up and running. If this ist the case, these projects may address the old TFS, thus they show no problem.

Regards
Michael
Flare 11.1
Capture 6.0
Windows 7 Enterprise 64 bit. Service Pack 1
MS Team Foundation Server 2015
MS Sharepoint
Post Reply