I have created a Winform App to Run Coded UI test scripts recorded in VS2013. Its finely running in the VS2013[update 4] installed machine. But when try to run this in Test Agent 2013 installed machine, the exception has been thrown at Playback.Initialize() method , as "The following package failed to load: "C:\Program Files (x86)\Common Files\Microsoft Shared\VSTT\12.0\Microsoft.VisualStudio.TestTools.UITest.Extension.IE.dll"
I tried adding this dll in the reference but still the problem persists. I have added the following references. And I am sure that these dlls are available in the mentioned path.
Microsoft.VisualStudio.QualityTools.CodedUITestFramework.dll
Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll
Microsoft.VisualStudio.TestTools.UITest.Common.dll
Microsoft.VisualStudio.TestTools.UITest.Extension.dll
Microsoft.VisualStudio.TestTools.UITest.Extension.IE.dll
Microsoft.VisualStudio.TestTools.UITest.Framework.dll
Microsoft.VisualStudio.TestTools.UITest.Playback.dll
Microsoft.VisualStudio.TestTools.UITesting.dll*
In that machine, only Test agent 2013 is installed and Configured for "Interactive Process" . Neither Test Controller is installed nor configured with any other test Controller installed machine.
I tried to Run the scripts with MStest using Command Line. Its running.
I have tried a lot by adding/removing many Coded UI dlls. But still the problem persists. Did I miss something? Thanks in advance.
Related
I created a Default .net Core RC2 MVC app using VS 2015. I added Docker Support so I could run and debug it in docker.
When I run the project it builds the docker container and starts it. Running the command "docker ps" shows the container running with the correct ports mapped. However I get the following error:
The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use NETStandard [version ...] or newer. This might be expected if the target process did not run.
Also trying to access the web page returns the following error:
[Fiddler] The connection to '10.0.75.2' failed.
Error: ConnectionRefused (0x274d).
System.Net.Sockets.SocketException No connection could be made because the target machine actively refused it 10.0.75.2:80
Turns out the problem is related to the docker for windows beta I am running. By default it does not let you map volumes.
To enable open the docker for window settings:
And select Manage shared drives.
Select the C drive or drive you have the .Net code stored on and rebuild and deploy the project:
I have an application which is build and executed on 'A' machine. Application is c++ based made on vs 2013.
Now i want execute application's .exe on 'B' machine. The 'B' machine has also vs 2013 installed and along with .exe i am providing all the associated dll's but when i execute .exe it throws me error as:
"The application was unable to start correctly(0xc000007b).Click OK to close the application "
Both machines have same OS and are 64 bit. So, please help me how to resolve the error and make .exe to open on other machine.
I am getting the following error while running a workflow in microsoft release management 2013 update 4:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AggregateException: One or more errors occurred. ---> Microsoft.TeamFoundation.Release.Common.Helpers.OperationFailedException: System.AggregateException: Failed to install 'VisualStudioRemoteDeployerbd3a8a59-325a-45d0-89f5-86a548554a12' from service executable path VisualStudioRemoteDeployer.exe . Consult the logs below:
c:\Users\vmadmin\AppData\Local\Temp\mfurnl9w.0.cs(95) : ; expected
c:\Users\vmadmin\AppData\Local\Temp\mfurnl9w.0.cs(94) : IntPtr policyHandle = IntPtr.Zero;
c:\Users\vmadmin\AppData\Local\Temp\mfurnl9w.0.cs(95) : >>> var attributes = new LSA_OBJECT_ATTRIBUTES()
c:\Users\vmadmin\AppData\Local\Temp\mfurnl9w.0.cs(96) :
I am using a vNext Release Template. I have added an action "Deploy using PS/DSC" which is supposed to execute a powershell script on the machine.
All I get is the above error.
I have verified that remoting is setup as per here (on-premise section): https://www.visualstudio.com/en-us/get-started/deploy-no-agents-vs.aspx
I have also referenced this: http://roadtoalm.com/2015/02/04/start-with-visual-studio-release-management-vnextvs-rm-for-dummies/
but our error is slightly different as it doesn't complain about the account. Although i am assuming the account is ok... I did use a couple variations and when the account is incorrect i get an obvious failure.
any help would be appreciated.
I found this question because I had the same issue. In RoadToAlm article he is using Windows Server 2012 on his VM. My Azure VM was Windows Server 2008 SP2 and I resolved the issue by installing Windows Management Framework 3.0 (http://go.microsoft.com/?linkid=9811175) which includes a newer Powershell than was installed on my server. After this update the issue was resolved.
I was facing the same issue on a destination Windows Server 2008 R2. I just shift down the UAC level and it let the deployment tools be copied by the task into the c:\Windows\DtlDownloads folder (with VisualStudioRemoteDeployer.exe).
From the moment this file was available, the artifact copy had been successful.
I'm installing sonarqube on Windows Server 2012.
I have followed the following steps:
Downloaded sonarqube4.4 and extracted to C:\Sonarqube
Downloaded Java JDK 1.7.0_60 and jre 1.7.0_67 as well as jre7
Installed Windows SDK 7 and .NET Framework 4
Navigated to C:\sonar\bin\windows x86-64 and ran StartSonar.bat as an administrator, this ran ok with no output and Ihad to hot ctrl- Z to break
I then ran \windows-x86-64\InstallNTService.bat as an administrator and I am seeing the sonarQube services was launched, but failed to start.
Not sure what the problem is.
I believe you first ran \windows-x86-64\InstallNTService.bat successfully and then StartSonar.bat unsuccessfully (the inverse order of what you describe).
You probably have [this problem]: http://qualilogy.com/fr/wp-content/uploads/sites/2/2013/09/Sonar_ServiceLaunchError2.jpg
Windows could not start the Sonar service on Local Computer.
Error 1067: The process terminated unexpectedly.
In that case, the solution is to change the user/rights to launch the Sonar service: https://qualilogy.com/en/migrate-sonarqube-tomcat-to-windows-service/
Go to the Services window, find the Sonar service, and open the Properties windows to change the user it logs on as to one with sufficient permissions.
I was able to solve this problem by creating a new folder named “Temp” in C:\Windows\System32\config\systemprofile\AppData\Local\
The Log-File will show only
--> Wrapper Started as Service
Cleaning or creating >temp directory C:\Program Files (x86)\SonarQube\sonarqube\temp
<-- Wrapper Stopped
The SonarQube service was launched, but failed to start.
After a long search, I came up to this site http://zen-and-art-of-programming.blogspot.de/2013/03/installing-and-running-sonar-source.html.
Solution:
Navigate to C:\Windows\system32\config\systemprofile\AppData\Local\ and create the directory Temp
2: Set the user rights to full access
3: Run the StartNTService.bat
When I create a new WebAPI project (MVC4) I get the following error.
EntityFramework.5.0.0: Failed to initialize the Powershell host. If your powershell execution policy setting is set to AllSigned, open the package manager console to initialize the host first.
jQuery.1.7.1.1: Failed to initialize the Powershell host. If your powershell execution policy setting is set to AllSigned, open the package manager console to initialize the host first.
After Googling I have found a few answers but nothing that works yet.
Error creating new MVC project - EF and JQuery
This answer seems like it should work for me as my last project was a 7z Command Line app and I might have done something daft with 7zip. But I copy pasted the 7-Zip directory from Program Files to Program Files (86) with no luck.
http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/c934fed4-e44e-4a06-9e3b-eccb9c8aa8d6
There is an answer here that might work (I haven't tried it) but even if it does work I wouldnt want to do this every time I create a new project.
Is anyone able to help me with this one?
I got around a similar error by running PowerShell as administrator with the command Set-ExecutionPolicy Unrestricted, restarting Visual Studio, and opening the Package Manager Console before what I wanted to do.
Make sure you understand the security implications of doing this first.
http://technet.microsoft.com/en-us/library/ee176961.aspx
Restricted - No scripts can be run. Windows PowerShell can be used only in interactive mode.
AllSigned - Only scripts signed by a trusted publisher can be run.
RemoteSigned - Downloaded scripts must be signed by a trusted publisher before they can be run.
Unrestricted - No restrictions; all Windows PowerShell scripts can be run.
I encountered this issue recently, after re-install VS and install the latest VS update 2, things go well. This works for me at least.