I am trying to create a new environment using microsoft test manager. Unfortuntely I get the following error:
Microsoft Test Manager cannot install test agent on these machines. Possible causes:
- Machines are not running or they are not available on the network
- The File and Printer Sharing exception is not enabled on the machines.
Controller is up and running , the user and password is correct. Firewall is disabled. File and Printer sharing exception too.
I do not know what is going on. How could it be solved? Do not know how to go further with this.
Try running MTM as Administrator. Also check the article on MSDN
https://social.msdn.microsoft.com/Forums/vstudio/en-US/a790f8d3-489d-4fd6-9204-2fb1f7e21b50/microsoft-test-manager-cannot-install-test-agent-on-these-machines?forum=vsmantest&tduid=(bbfad4796548274f6ccbc9c1b7d15461)(256380)(2459594)(XdSn0e3h3.k-lkj0MqSQojhOnvvQ2ym5yA)()
Related
I have been trying to browse a website run under IIS Express VS2019 from another computer on the same network. I see the following error.
Bad Request - Invalid Hostname
I found several discussions where people suggested adding bindings and I did try adding so many different bindings in applicationhost.config with specific hostname, IP, hostname+ip, wildcards. When I add any binding or modify the existing localhost binding VS 2019 start giving me the following error
Unable to connect to web server 'IIS Express'
I am running VS2019 as an admin. What else I am missing?
Here is what I discovered. I do not have admin privileges on my local PC. Our sysadmin had created a shortcut for me which launches VS2019 as an admin. However, the VS was still not run as elevated Admin privileges. Turns out, you need to be an admin, and you must right-click the VS2019 shortcut and choose Run As Administrator with a shield and say Yes to the warning. The shortcut wasn't doing none of that. Now my custom IIS Express bindings are picked up from applicationhost.config without any issue.
I have installed CouchDB on my Windows machine but while starting the CouchDB service, I am getting a message like:
Windows could not start the Apache CouchDB service on Local Computer. The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, please contact your system administrator.
As the service is not running, I am unable to access Fauxton too.
I am using Windows 7. CouchDB is 2.0.0. Port 5984 is not in use.
I don't think your question is a duplicate of https://stackoverflow.com/a/44107335/219187 because you are on Windows 7, and the problem described there is for Windows 10 with the creators update.
But maybe the solution fixes your problem as well? Here is the procedure:
Download the prelease build 2.2.4-101 from https://nssm.cc/download
Stop the CouchDB service through the Windows Services dialog (paused is not enough)
Overwrite nssm.exe in <CouchDbInstallDir>\bin with the one from the downloaded ZIP file (make sure you pick the right version 32 bit / 64 bit)
Start the CouchDB service
Issue it's happening since the last updates released by Microsoft. I'm not completely aware of what's causing it, but I think it's something related to CouchDB service not been able to start using Local Administrator rights.
However I've managed to start the service manually, by doing so:
Open Command Prompt - in the Search from the Start Menu or Task Bar type "cmd"
Run it as an Administrator - right click on the Command Prompt application and choose "Run as administrator" option /this is really IMPORTANT as it will allow the service to have administrator access/
Navigate to the folder where CouchDB is install - default path is "D:/CouchDB", but could be anywhere else; you have to find it
Go to the "bin" folder in there
Type "couchdb" as a command to start the service
You will see a message showing after this - "kernel-poll not supported; "K" parameter ignored"
If it adds some error messages after it or closes the whole terminal, you're making some things bad from this guide, so follow it strictly.
You can now open up the Fauxton application in the browser like normal from here - http://localhost:5984/_utils/
Keep in mind that you have to leave the cmd opened in order the service to be working as expected. As far as I saw no information was lost, so it's all good.
This is a temporary solution though, as we are waiting a relase from either Microsoft or Apache to solve the issue, or at least give us more explanation about it.
i just met the same problem.
the cause is space, you have to install CouchDB in a path without any space, even Program Files folder, because there is a space between Program and Files...
When I try to publish it I get the following error message:
Error 1 Web deployment task failed. (Could not connect to the remote computer ("..*.*"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.)
I dont understand why is it referring me to a remote computer, I've specified the destination URL as my own IP address. And I have web management service checked on windows features.
How do I solve this particular error?
Try to publish to the file system, if this works move the files into you wwwroot, normally c:\inetpub\www.
then go to start and run inetmgr to open iis configuration manager, if you see your folder there right click and convert to application, accept settings then right click / manage / browse and you should see your site or an IIS error that should be easy to debug.
I never use the deploy to IIS feature from VS as it's pants.
Good luck!
I have created a small application that auto elevates as administrator using the command:
requestedExecutionLevel level="highestAvailable" uiAccess="false"
This works fine if I run the application locally on the computer. However, if the computer tries to run my execuatable across the netork, it simply crashes on startup with a message "Do you want to send more information about the problem?" error. If I right click and run as administrator, my application will work and will prompt for admin credentials.
The folder I am running my application from (across the network) has full read/write permissions for 'everyone'.
My question is: Is there something I've missed? Why can I run my application locally and not get prompted but across the network crashes or requires admin?
Can anyone help explain what might be causing this issue?
UPDATE
I have checked my event viewer log and it shows the following:
Application: AutoUpdater.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Net.Sockets.SocketException
Stack:
at System.Net.Sockets.Socket..ctor(System.Net.Sockets.AddressFamily, System.Net.Sockets.SocketType, System.Net.Sockets.ProtocolType)
at System.Net.Sockets.TcpListener..ctor(System.Net.IPAddress, Int32)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel()
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(System.Collections.IDictionary, System.Runtime.Remoting.Channels.IServerChannelSinkProvider, System.Runtime.Remoting.Channels.IAuthorizeRemotingConnection)
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.RegisterChannel(ChannelType, Boolean)
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])
at AutoUpdater.My.MyApplication.Main(System.String[])
I don't understand why it is making reference to System.Net.Sockets?? But that is what seems to be crashing my app.
Make sure that the other computers attempting to run your application have the correct .Net framework versions installed. If users are able to open the executable, there shouldn't be any other issues with permission.
If you have verified the framework versions, see if there is anything in the error report that might point to a reason for the crash. A lot of times there may be something in there that can point you in the right direction.
.NET applications don't like to run from the intranet by default.
Try this:
Go to Control Panel -> Administrative Tools -> Microsoft .NET Framework 2.0 Configuration
Click Configure Code Access Security Policy link
Click Adjust Zone Security
Set the My Computer and Local Intranet to Full Trust
If this works, then it is a local security issue. If you need it scripted out, you can use the caspol exe that is in the framework. Sample
C:
cd %windir%\Microsoft.NET\Framework\v2.0.50727
CasPol.exe -pp off -m -ag 1. -URL Z:\folder\EXEName.exe FullTrust -n FriendlyNameOfEXE
I have two basic issues:
I can't seem to get the "Restart Rig" to work when the Controller is listed as 'localhost'.
I can't seem to get the agent to run as expected in the load test.
Here are the details:
I am using Visual Studio Team System 2008 with a Load Test. On the Windows XP system running Visual Studio, I have installed the Visual Studio Team Test Controller. On another Windows 2003 Standard system, I have installed the Visual Studio Team Test Agent (I will call these the Controller and Agent, respectively).
I believe I have set up the Agent correctly using the command:
AgentConfigUtil.exe /controller:
The log file for this action indicates the agent was successfully added to the controller for both machines using the login account I was logged in with.
On the Controller, within Visual Studiio, I can select Test | Administer Test Controllers from the menu. In the Controller drop-down, I select "localhost". I have my "Load Test Result Store" correctly configured, and I add the Agent as defined. The Agent status is "Ready".
I then click on the "Restart Rig" button and receive the following message:
Microsoft Visual Studio
Rig failed to restart for controller 'localhost'.
The following error was reported
Access is denied.
I am logged into both systems with a domain account that has local admin access to both machines.
Both the Controller and Agent services (running on their respective machines), have the "Log On As" user as my domain user with appropriate password. Both services are running without problems.
On the controller, I have the following groups: TeamTestAgentService, TeamTestControllerAdmins, and TeamTestControllerUsers. My domain account is a member of each group as well.
Note that if I select the name of the machine rather than 'localhost' in the Controller drop-down for the "Administer Test Controller" dialog, then the "Restart Rig" seems to work without any problems. Honestly, I'm not sure which is appropriate or correc for this situation. I would think these settings (localhost vs. machine name) were equivalent.
Finally, using the Test | Edit Test Run Configuration, I have created the following:
Test Run Configuration where the "Select location to run tests"is set to "Local" and the name of the Agent is in the name/value pair box.
Test Run Configuration where the "Select location to run tests" is set to "Remote" and the Agent is in the name/value pair box.
If I select the active configuration as the first one listed above, the test runs but I get no indication that the Agent is being used for the test. Yes, I do get an additional dialog telling me that: "You specified to execute test run remotely on a local machine. Are you sure you want to do that instead of executing locally?"
If I select the active configuration as the second one above, I get a "Test Run Error" of: "Failed to queue test run 'username#machinename time': Test run 'username#machinename time' cannot be executed on controller MACHINENAME. No agent matches the specified agent properties.
I've searched MSDN, I've read the appropriate articles on how to perform these actions (here and here), but these articles are very basic and don't really help me much.
I'd appreciate any insight for getting my test configuration working correctly. Basically, I want to be able to run load tests with the agent working.