Skip to main content

Notifications

Microsoft Dynamics GP (Archived)

Dexterity 2016 error trying to connect to TFS 2015 "The source control provider could not be initialized"

Posted on by Microsoft Employee

We have recently upgraded our TFS server to 2015 and are now experiencing some difficulty connecting. At first we could connect, fetch, update but could not Check out resources. I have read and followed the suggestions in this blog post, https://community.dynamics.com/gp/b/dynamicsgp/archive/2016/09/01/ambiguous-team-foundation-server-tfs-error-39-source-control-provider-could-not-be-initialized-39.

After setting the workspace to be server and not local, This is when I now recieve the error "The source control provider could not be initialized."

I have tried clearing the TFS cache but this has made no difference.

I have no problems with VS connecting and checking out and back in again. Only have issues in Dexterity.

Any help with this would be very much appreciated.

Dexterity 16.00.0033

TFS 2015

Visual Studio Professional 2015 Version 14.0.25431.01 Update 3

Stephen Hudson

*This post is locked for comments

  • Suggested answer
    Nizamudeen Profile Picture
    Nizamudeen 790 on at
    RE: Dexterity 2016 error trying to connect to TFS 2015 "The source control provider could not be initialized"

    Hi Stephen,

    I Hope your doing good.

    I do face the same issue while connecting to TFS from dexterity, I found the solution for this . Previously I have installed in my system VS2015 and Dex18 after my investigation I feel that VS2015 is not compatible for Dexterity versions, then after I have installed as VS2013 in my system and made to connection between TFS and Dexterity and then it work fine.

    Thanks for all your suggestions... :) 

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Dexterity 2016 error trying to connect to TFS 2015 "The source control provider could not be initialized"

    Works. Thanks Mariano.

  • Mariano Gomez Profile Picture
    Mariano Gomez 26,225 on at
    RE: Dexterity 2016 error trying to connect to TFS 2015 "The source control provider could not be initialized"

    Make sure you install Update 5 with VS 2012.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Dexterity 2016 error trying to connect to TFS 2015 "The source control provider could not be initialized"

    Excellent. I'm installing VS2012 right now.

  • Mariano Gomez Profile Picture
    Mariano Gomez 26,225 on at
    RE: Dexterity 2016 error trying to connect to TFS 2015 "The source control provider could not be initialized"

    Stephen,

    I wasn't suggesting changing the version of TFS, but rather downgrading to Visual Studio 2012 in order to be able to use the Dexterity TFS 2012 provider. And yes, you will be able to use it with your installation of TFS 2015. We currently use Visual Studio Team Services, so definitely no control over versions.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Dexterity 2016 error trying to connect to TFS 2015 "The source control provider could not be initialized"

    unfortunately, I don't have any control over the version of TFS. I do however have the ability to install multiple versions of VS. Do you know, or have you confirmed if VS2012 will work with TFS2015?

  • Verified answer
    Mariano Gomez Profile Picture
    Mariano Gomez 26,225 on at
    RE: Dexterity 2016 error trying to connect to TFS 2015 "The source control provider could not be initialized"

    I've pretty much come to the conclusion that that particular Dex TFS provider (Team Foundation Server 2013/2015) does not work with Visual Studio 2015. I also run Visual Studio 2015 Professional with Update 3, and have tried with both the x64 and the x86 versions to no avail. I've tried installing the Dexterity Source Code Control services and that does not work either. The only provider I have been able to get working is the Team Foundation Server 2012 provider, which requires Visual Studio 2012 with Update 4. Since I have to support GP 2013 through 2018, I have decided to use that particular provider since the TFS 2013/2015 provider is not available to Dex 12 - and well, doesn't work! Suffice to say, all versions of Dex play nicely with the TFS 2012 provider and I have not had any issues whatsoever, so there must be some bug with the TFS 2013/2015 provider.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans