Careers   |   Events   |   Contact   |   402.238.1399   |   contactus@deliveron.com

Deliveron
Connect with us on FacebookConnect with us on LinkedInFollow Us on Twitter

Category List


Tag List

asp.net-mvc-4 (2)
tags (2)
vsdbcmd (2)
c# (13)
feedback (2)
Mike Douglas (4)
serverless (3)
tfs odata (2)
test agent (2)
TestArchitect (5)
association (1)
security (1)
alerts (2)
action-filters (2)
agile (12)
angular 2 (3)
Big Data (2)
nebraska code camp (2)
Functions (2)
Meetings (1)
test controller (2)
asp.net-mvc (6)
Multi-Factor Authentication (1)
load testing (2)
Azure (14)
power tools (2)
scrum (8)
Document (1)
AAD (2)
azure resource manager (1)
tls 1.2 (1)
API Tests (1)
Build (6)
team deploy (2)
fields (2)
selinium (1)
lab environments (1)
test cases (2)
deliveron alm delivery guidance (2)
swagger (1)
whitelist (1)
powershell 2.0 (8)
asp.net-mvc-routing (2)
AzureAD (1)
sp1 (2)
requirements (2)
sharepoint 2007 (2)
cascading-dropdown (2)
continuous inegration (2)
pdf (2)
Cosmos DB (1)
web application firewall (1)
PBI (1)
gherkin (2)
CI (3)
wiki (1)
react (1)
asp.net-mvc-3 (4)
opensource (1)
Decisions (2)
installation (2)
onenote (4)
licensing (2)
dependency-injection (2)
sharepoint 2013 (6)
exchange (2)
Keith Holt (1)
alm (9)
home projects (1)
tfs 2012 (4)
nintex (4)
Visual Studio 2017 (4)
testing (5)
tfs 2010 (2)
performancepoint services (2)
preview (1)
dbpro (2)
user profiles (4)
burndown (2)
OAuth2 (1)
Quality (2)
storyboarding (2)
ssrs (4)
business insight (2)
visual studio 2010 (18)
lync (2)
dns (2)
database projects (4)
razor (4)
visual studio 2012 (10)
visual studio (8)
service-fabric (1)
Web API (1)
Nuget (1)
Business (2)
coded ui tests (6)
reporting (2)
ssas (2)
data warehousing (2)
jquery (4)
TFS 2015 (6)
team web access (2)
fluentvalidation (2)
mstestv2 (1)
database publishing wizard (2)
Automated Testing (10)
load tests (2)
owasp (3)
windows azure (2)
tfs (11)
connect() (1)
tfs 2013 (2)
M Query (1)
spc14 (4)
ARM Template (1)
insiders (1)
rest assured (1)
business intelligence (2)
planning poker (4)
deliveron agile delivery process (2)
Office 365 (1)
DevSecOps (2)
Powershell (1)
ssl (1)
work item (2)
subsites (2)
web (1)
performance (3)
kanban (1)
MVP (2)
Infrastructure (1)
Visual Studio Online (6)
MSBuild (1)
web performance tests (2)
sql server 2008 (2)
team foundation 2012 (2)
faq (2)
Node.js (1)
Azure Functions (1)
vsts (22)
entity-framework (6)
tips (2)
team foundation server 2012 (4)
automatedui (1)
webparts (2)
alm rangers (1)
bundling (2)
visual studio 11 beta (2)
github (1)
microsoft alm rangers (2)
DevOps (14)
Template (1)
tfs 2017 (1)
angular (1)
microsoft test manager (2)
microsoft case study (2)
example (2)
2013 (2)
sql server (2)
AzureAD Admins (1)
selenium (4)
xunit (1)
Power BI (3)
adfs (3)
table-valued-parameters (4)
Collaboration (2)
pipelines (1)
necc (2)
sharepoint 2010 (10)
MFA (1)
Java (1)
gulp (2)
javascript (3)
my work (2)
visual studio team services (1)
continuous integration (2)
bdd (2)
mvvm (2)
silverlight (2)
pipeline (1)
whitesource (1)
release management (7)
netstandard (2)
top 5 (1)
video (2)
single page applicaiton (1)
deployment (2)
certificates (2)
Analytics (2)
event-handling (2)
Data Analytics (1)
IntelliSense (1)
team foundation server 11 beta (2)
workflow (2)
lunch and learn (2)
ninject (2)
site collections (2)
visual studio code (1)
outlook (2)
code-first (4)
application insights (2)
webcast (4)
REST (1)
xaml (2)
artifacts (1)
sharepoint (5)
lab management 2010 (2)
azure mobile services (2)
nunit (1)
webpack (1)
wit (2)
msi (2)
zap (1)
team build (2)
tokenization (1)
HOLs (1)
json (2)
test automation (1)
bi (2)
sql saturday (2)
team foundation server (6)
windows 8 store app (2)
webs (2)
web deploy (1)

Archive

Visual Studio Web Performance Tests Support for TLS 1.2 Workaround

Sep 10, 2018

Websites and API services are requiring a minimum TLS version of 1.2 to access.  The Visual Studio 2017 web performance test runner (and previous versions) does not support TLS 1.2 when executing web performance tests against HTTPS sites requiring TLS 1.2. We have run into a couple issues recently where we weren't able to run our web performance tests because of this.  While we didn't figure out this fix, I wanted to share it so that you might find it faster.  I hope for an out of the box fix so we don't have edit the registry.  If you feel this is important please vote for this item on UserVoice.

When running any web performance test against a HTTPS endpoint requiring TLS 1.2, you will receive the following error:

Request failed: An existing connection was forcibly closed by the remote host

Here is full exception.

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
--- End of inner exception stack trace ---
at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
at System.Net.PooledStream.EndWrite(IAsyncResult asyncResult)
at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.VisualStudio.TestTools.WebStress.WebTestTransaction.ResponseReceived(IAsyncResult result)

To fix the issue, add the following registry keys to your registry (Remember to proceed at your risk.  Invalid registry changes can damage Windows.) 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\]
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\]
"SchUseStrongCrypto"=dword:00000001

To reproduce the issue, create a web app or api app in Azure select TLS 1.2 for the minimum TLS version under the SSL settings.  Create and execute a web performance test against the site using HTTPS.  After adding the registry entries above, the requests should succeed.

tls-setting-azure-app-service.jpg

Thanks Geza Soos for posting the registry fix!  Thanks Federico and Jason for sharing this fix!

 



Category: Visual Studio

Mike Douglas

user_avatar

He is a solution consultant focused on helping organization build high quality application effectively utilizing DevOps practices. He is a Microsoft DevOps / ALM Ranger and you can reach him on Twitter at @mikedouglasdev


We believe in helping our customers create software solutions in a better way.
We do this by having a project delivery process and technology expertise that ensures we are solving the right problem in the right way and driving the most business value.