1. Xiaolong Qin
  2. PowerBuilder
  3. Tuesday, 12 September 2023 06:37 AM UTC

Yesterday suddenly we had several PC occured errors when using TFS2012 connecting to Azure DevOps Service..

PowerBuilder version 2017 R3.

TFS Version: VS 2012

SCM: Azure Devops Service.

 

we have run this for some years and it works very well..

not sure what happend in Azure Devops Service recently from MS ,, some PC encountered below error..

btw, no issue to open the Azure devops service in Edge directly,, means there should be no access issue..

 

TF31003: Either you have not entered the necessary credentials or your user account does not have permission to connect to the Team Foundation Server at https://dev.azure.com/XXXXXXXXXXXX. Ask your server administrator to add the appropriate permissions to your account.

 

thanks ahead if anyone can advise on this.

kitty he @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 13 September 2023 06:40 AM UTC
  2. PowerBuilder
  3. # 1

Hi xiaolong,

Please try the following solution and see if it solves the problem.
open HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319 in regedit as an administrator and add two DWORD values:
SchUseStrongCrypto → 1
SystemDefaultTlsVersions → 1

Please refer to: https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client#configure-for-strong-cryptography

Regards,
Kitty
Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 12 September 2023 12:17 PM UTC
  2. PowerBuilder
  3. # 2

Hi Everyone;

  My guess (as I'm not an Azure Guru) is that the TLS requirement has changed. Older Sybase versions of PB supported TLS 1.0. Appeon PB 2017 supported TLS 1.1. Appeon 2019R3 supported TLS 1.2. The new PB 2022R2 supports TLS 1.3. So if your Azure Admin confirms that this error is TLS version related, you may need to upgrade your PB version.

Regards ... Chris 

Comment
  1. D R
  2. Tuesday, 12 September 2023 12:32 PM UTC
Thanks Chris, appreciate the response.

This is kind of where I think this was heading, just going to try some other things or see if anyone else finds a workaround in the mean time.

I should be able to test the new PB version trial end to end connecting to our Azure Devops and see if that is a potential solution.



Regards

DR
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Tuesday, 12 September 2023 14:37 PM UTC
Hi Chris, What is TFS 1.0? Do you mean TLS 1.0?
  1. Helpful
  1. Chris Pollach @Appeon
  2. Tuesday, 12 September 2023 18:38 PM UTC
Thanks Armeen .. Yes, I corrected the spell checker based post from my phone this AM (with no coffee yet) :-(

TLS it is.
  1. Helpful
There are no comments made yet.
D R Accepted Answer Pending Moderation
  1. Tuesday, 12 September 2023 12:00 PM UTC
  2. PowerBuilder
  3. # 3

Hi,

We are getting the same issue.

All working fine last week but now getting the same errors starting this week.

Affecting all our users.

Powerbuilder 11.5 connecting to Azure Devops using the MSSCCI provider (not using GIT)

Open PB, workspace attempts to connect.

Prompts for Azure creds which I supply.

Error in popup when starting PB is:

TF30064: You are not authorized to access the server

Error in PB Output window:


Initialization of Microsoft Team Foundation Server MSSCCI Provider Failed

 

I can successfully connect to the Azure Devops portal with the same credentials in Chrome/Edge.

And I can connect the the same project in VS 2019 via Team Explorer.

I cannot connect from VS 2010 and Team Explorer. Get a similar error message:

TF31003:Either you have not entered the necessary credentials or your user account does not have permission to connect to the Team Foundation Server at dev.azure.com/blah etc

Please let me know if you make any progress on this issue, I will do the same.

Thanks

DR

 

Comment
  1. Xiaolong Qin
  2. Wednesday, 13 September 2023 01:26 AM UTC
Hi D R,



We are migrating from VS2012 to VS2013 which works fine. .. but still dont know what happened to VS2012 or previous versions of VS
  1. Helpful 1
  1. D R
  2. Thursday, 14 September 2023 12:58 PM UTC
In case this helps anyone. It's all mysteriously started working today.

Both in Powerbuilder IDE and VS 2010.

So yesterday I tried the registry changes as Kitty described.

Also tried enabling older protocols in internet explorer and Edge.

Followed with reboots etc.

None of this worked.

Tried today on the off chance and it connected fine.

So either some convoluted set of changed made it work. Or MS reversed a change in Azure Devops yesterday to allow the connections to work again.

I will probably need to wait and see when it's time to re-authenticate with Azure as to if the issue really has gone.

Regards

DR
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.