I have recorded a simple web test in VS 2013 Ultimate and im attempting to run it on a remote agent.
I get the following error:
Request failed: No connection could be made because the target machine actively refused it 127.0.0.1:23109
If i change my run settings to only run the test locally it succeeds.
When i view the "Manage Test Controller" dialog the agents are registered and in the ready state.
I have checked the Controller and agent LAN settings and none of them is configured (or required) to use a proxy.
Does anyone have any idea whats going on?
So the problem was the Internet Explorer security settings on the agents and also Internet explorer was configured to use a proxy on the agents.
I logged onto the server and checked this initially but as my own user account. I then checked by logging on as the user the agents run as and removed the configured proxy from IE, lowered the security settings and all was well.
Related
I create a new Teams application in Visual Studio 2022 (17.4.4). When I try the "Prepare Teams App Dependencies", I get a failure from AppStudioPlugin with the message "API call to Developer Portal failed: Error, connect EACCES 52.113.194.132:443, API name: create-app, ..."
I am behind a proxy, and I see a drop in the firewall logs to 52.113.194.132:443, so it's not going to the proxy.
When I open a browser on that machine, I can go to the developer portal (https://dev.teams.microsoft.com/) without a problem, so the proxy does allow this.
When I open port 443 in the firewall, everything works.
My question is: How do I get it to work via the proxy ?
I did already try to add the proxy to the visual studio config, but also that did not make a difference.
17.4 VS Teams Toolkit uses a language server to handle data between VS and Teams Dev portal. You can try to add this language server to your proxy and test it.
Language server location: ~\appdata\local\microsoft\visualstudio\{VS_version}\extensions\Microsoft\teams toolkit\{Teams_toolkit_version}\server.exe
I honestly don't know where to start apart from mentioning I've tried absolutely everything and I feel like banging my head against the wall!
I've configured my IIS according to the Microsoft docs and also added Web Deploy 3.6.
In my services I have the following running:
In my windows firewall I have opened port 8172:
In my IIS I have enabled remote connections:
Within IIS I have a Site which points to an empty folder, when I right click -> Deploy -> Configure Web Deploy publishing I get this:
Using this, I've set up a publish profile in VS like so:
But get this error why I try and 'Validate' the connection:
Severity Code Description Project File Line Suppression State
Error Web deployment task failed. (Could not connect to the remote computer ("server2021"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started. Learn more at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.)
This error indicates that you cannot connect to the server. Make sure the service URL is correct, firewall and network settings on this computer and on the server computer are configured properly, and the appropriate services have been started on the server.
Error details:
Could not connect to the remote computer ("server2021"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started. Learn more at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.
Unable to connect to the remote server
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
I can't even remote to this server, I'm accessing it using TeamViewer.
I've viewed EventViewer logs on my local machine and it just says the same error which VS is spitting out.
I honestly don't know what I'm doing and I'd really really appreciate any help
Issue: When running a load test from my client, with a remote controller on a second machine and a remote agent on a third machine, I receive the following error
Error 8/28/2017 6:59:18 AM Failed to queue test run '': No
such host is known.
I have Visual Studio 2017 on my client. The 2017 Test Controller is installed and configured on a second machine running Windows Server 2016. The 2017 Test Agent is installed and configured on a third machine running Windows Server 2016. The Test DB is on SQL Express on the second machine, same box as the Test Controller.
The configuration of all items worked fine (Test Controller, Test Agent, etc) without any issues or errors.
I installed VS 2017 on the Test Controller machine and was able to run tests without issue.
I can debug from my client without issue, but when I try RUNNING the test, it states the error above.
I can "manage test controllers" and see my controller, as well as the test agent listed, all in "ready status." Additionally, setting the LoadTest DB has a "test connection successful" message when setting it up.
My current .testsettings file is set up with the role to have all agents associated with my test controller be for running tests. It is set as the active test setting.
I've put the FQDN in all the setup, and added all the associated machines to the host files on each box.
The firewall has been disabled on every box to try that to no avail. Network Sharing is on, Printer sharing is on, ports are open. Verified this with port scanners, checking settings on the servers, and I can ping and NSLookUp each box from each other.
I've tried recording brand new tests and running existing tests (ones that worked if I ran VS2017 on the Test Controller) to no avail.
At this point, I'm really not sure what else to do or try, nor what other information to provide. I'm dumbfounded as I've read all the troubleshooting docs on network permissions, local permissions, etc. The only thing I haven't done is made an AD group for the machines involved and adding those to local admin groups.
If anyone could help, PLEASE, feel free to ask questions and I'll do my best to provide the info.
You can confirm these:
Create a load test in VS17.
On one computer, you configure a test controller in a domain.
On another computer, you configure a test agent in a different domain.
Note: The two domains trust one another.
You run the load test on the test controller computer and the test agent computer.
Edit:
Connect your controller computer and get its hostname.
Go to host file "C:\Windows\System32\drivers\etc".
And add hostname as IP address.
At last VS17 will successfully connected to your controller.
I had the same issue. The problem is that there was no route BACK to the client. I needed to add a fully qualified entry for the cient to the hosts file on the controller. This was compunded by using a VPN to Azure.
To clarify you need the FQDN of your client added to the hosts file of your controller.
I am receiving the error when trying to register a test agent to the load test controller
Configuration started on 2015/10/16, 16:05:47.
OS Version : Microsoft Windows NT 6.3.9600.0
Executable version : 12.0.21005.1
I, 2015/10/16, 16:06:07.812, Restarted service successfully.
I, 2015/10/16, 16:06:07.968, Verifying that the test agent is able to connect to the test controller.
E, 2015/10/16, 16:08:10.005, Test agent could not connect to the test controller.
I, 2015/10/16, 16:08:10.005, Disabling auto logon on the machine...
I, 2015/10/16, 16:08:10.005, Adding agent setting AutoLogonEnabledByAgentConfiguration=0 on agent machine
In the windows event log, this is seen:
Unable to connect to the controller on 'machinename:6901'. The server has rejected the client credentials.
The logon attempt failed
I've tried all I can find for people that have reported similar issues (Firewall is disabled, no antivirus, UAC is disabled, user is in admin group as well as TeamTestAgentService/ControllerAdmins/ControllerUsers). I've tried running the setup under different users/same user/"as admin" while still using the same username/pass for the log on. Trying to point different machines Test Agents to this controller and the same error occurs. Per another site, I also tried adding this to QTAgentService.exe.config
<appSettings>
<add key="BindTo" value="x.x.x.x"/>
</appSettings>
I have also tried using a different account for the Controller vs Test Agent. IE Both CtrlUser and TestUser are in the same groups listed above. As I understand it thought, this should work since they should be the same name/pass for Workgroup authentication.
I've referenced these pages among others and unless I've missed something, those solutions do not apply.
"Test Agent could not connect to the test controller" VS2012 Agents
VS2013 Test agent and controller not communicating
VS2013 Remote load test agent can't connect to controller
https://social.msdn.microsoft.com/Forums/en-US/59bc2270-37d9-4297-ac3f-e0da21d10a95/test-agent-could-not-connect-to-the-test-controller-vs2012-agents
Any thoughts/suggestions?
I was using a version downloaded by a prior employee that we have been using for CodedUI testing (12.0.21005.1). I downloaded the latest version (2013 Update 5) and after installing that, it worked with the same settings I was using before.
I've installed Web Deploy 2.1 on a Server 2008 R2 running under VMWare.
In the IIS Manager (Management Service applet) I can see that "Enable Remote Connections" is checked and the port is set to 8172. Under "IIS Manager Permissions" I've added my Windows account (CORP\ekkis) and under the "Authentication" applet (for IIS) I have enabled "Windows Authentication".
I've also turned off the firewall.
So from the command line I test the system to work like this:
C:\Program Files\IIS\Microsoft Web Deploy V2>msdeploy -verb:dump -source:contentPath=\temp,wmsvc=192.168.0.70,username=CORP\ekkis,password=MyPass,authType=Basic -allowUntrusted=True
and get this:
Info: Using ID '9b954a0f-ff07-4e77-ba2c-d27472f5fda0' for connections to the rem
ote server.
Error Code: ERROR_USER_UNAUTHORIZED
More Information: Connected to the destination computer ("192.168.0.70") using t
he Web Management Service, but could not authorize. Make sure that you are using
the correct user name and password, that the site you are connecting to exists,
and that the credentials represent a user who has permissions to access the sit
e.
Error: Object of type 'contentPath' and path '\temp' cannot be created.
Error: The remote server returned an error: (401) Unauthorized.
Error count: 1.
I've also tried deploying with Visual Studio 2010 from the host OS with the following service urls (I haven't found proper documentation on how to form this url):
https://192.168.0.70/
https://192.168.0.70:8172/
https://192.168.0.70:8172/MsDeployAgentService/
https://192.168.0.70/MsDeployAgentService/
I've tried the non-secure versions as well but just cannot get it to work. What is the correct format for the url? and what permissions am I missing?
the errors from VS have varied depending on how I attempt it but below is a sample:
Could not complete the request to remote agent URL 'http://192.168.0.70:8172//MSDEPLOYAGENTSERVICE'.
The underlying connection was closed: An unexpected error occurred on a receive.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host
Publish failed to deploy.
there really should be a guide out there to do this (yes, I've googled myself blue in the face)!
thanks - ekkis
ok, I've figured out that the correct url is:
https://192.168.0.70:8172/MsDeploy.axd
and that having the "Windows Authentication" enabled doesn't seem to make a difference. Also, having my account in the "Managers" list doesn't seem to make a difference either.
so the back end was all working fine (I've turned off the Web Deployment Agent Service). it was just the url I had wrong.