I have been trying to automate some deployment and regularly used tf.exe through .bat files. I recently started getting "this app can't run on your pc" on my .bat files and upon checking I saw my tf.exe is 0KB.
following is the example of a ```.bat`` files I usually ran.
SET tfs=http://vm03:8080/tfs
SET chg= %1
"%programfiles(x86)%\Microsoft Visual Studio 14.0\Common7\IDE\TF.exe"
changeset /server:%tfs% %chg% /noprompt
I am using 64-bit windows 10. anyway I can have tf.exe reinstalled? and can anyone explain what happened?
edit: I have another instance of visual studio 17, and I am using its tf.exe however what happened to my original tf.exe is still unknown. Anything to help me understand will be great.
Related
I am following this trail and I have completed all the steps correctly. Even I able to download the debug logs.
But Problem occurs when I am trying to run the following command
> SFDX: Launch Apex Replay Debugger with Current File
It shows the below error.
But, the thing is, I have jdk-12.0.1 installed on my PC. After that, I have installed the Java 8 also and thus jdk-1.8.0_181 is also installed.
My Java Home setting in VS code is following
I have also restarted my PC, But no luck. It is throwing the same error.
How to solve this ?
You have to set the path as 'C://Program Files//Java//jdk1.8.0_181' and then restart the vs code
In case any Mac users needed help:
I installed Java 11 and then ran this code:
/usr/libexec/java_home -v 11 to find the exact directory and then pasted it in the user settings you have marked with a red rectangle. Then I restarted VS code and it worked.
Edit: Looked at your screenshots...
You did this: C:\Program Files\Java\jdk1.8.0_181
You wanted this: C:/Program Files/Java/jdk1.8.0_181
From the Trailhead unit you linked:
I've been working on trying to figure out why our auto-generated deploy.cmdscripts will not work when installed to C:\Program Files (x86)\OurProgram. I finally narrowed down the issue to the closing parenthesis in (x86) as the script would terminate with "Files was unexpected at this time". One possible solution was to manually create another batch file to set _DeploySetParametersFile to a Windows path ( C:\Program^ Files^ (x86^)\OurProgram\Program.Parameters.xml). This isn't a valid solution for me, so I dug into the auto generated file and found the issue to be 2 variables:
RootPath
_DeploySetParametersFile
Both of which were referenced using %'s(i.e. %RootPath%), however as soon as they were changed to !'s(i.e. !RootPath!), no 2nd script was needed and I can run the cmd script from Program Files (x86) just fine. The issue of course with this is, the deploy.cmd file is auto-generated on each build, thus I have to change it for each build I do. My question is this: Is there a way to edit the template Visual Studio uses to generate the deploy.cmd file? If so, where? It seems so ridiculous that Microsoft would have this be an issue in their web deployment.
I am trying to uninstall a program using a batch file. I looked at a previously posted question from about 3 years ago using a variation of this:
wmic product where name="VIPRE Business Agent" call uninstall
While it appears to be working, the script runs and returns a successful reply, the program isn't uninstalling. What am I doing wrong or am I using the script wrong?
I know there is another question exactly like this, it's mine, and I am am trying to have it deleted since it started out completely different. I should have closed it first and then opened this one.
Here is the output from when the batch is ran:
E:\>echo off
E:\>wmic product where name="VIPRE Business Agent" call uninstall
Executing (\\DC-30026\ROOT\CIMV2:Win32_Product.IdentifyingNumber=" {56CA3334-8B72-48D1-81E7-3EF5243E45D5}",Name="VIPRE Business Agent",Version="7.5.5841")->Uninstall()
Method execution successful.
Out Parameters:
instance of __PARAMETERS
{
ReturnValue = 1603;
};
Edit Addition:
I finally got the batch to uninstall Vipre. But it still leaves behind the folder C:\Program Files (x86)\Vipre Business Agent w\ a deployment folder and a config folder. How can I get a total uninstall?
If this was a 32 bit app installed with InstallShield use this command:
C:\Program Files (x86)\InstallShield Installation Information[YourUninstallProductCodeGoesHere]\Setup.exe
I have few Ordered tests which I execute locally using the VSTEST.CONSOLE.EXE In a batch file. I want to launch this batch file from remote system on about 15 VMs. I have the desktop active on all the VMs and user under which these test cases need to be executed are also same as the user logged in. When I try to execute the batch file using the PSExec it throws an error and dosent launch the tests the error shown is as below
C:\TestRunningFolder>vstest.console.exe C:\BuildsFolder\BVTTests.orderedtest /Settings:C:\BuildsFolder\QuestCodedUI.testsettings /Logger:trx
Microsoft (R) Test Execution Command Line Tool Version 12.0.30723.0
Copyright (c) Microsoft Corporation. All rights reserved.
starting test execution, please wait...
Warning: Warning: Test Run deployment issue: The assembly or module 'UiaComWrapp
r' directly or indirectly referenced by the test container 'c:\BuildsFolder\questcodedui.dll' was not found.Error: Test host process
exited unexpectedly.
Error: Failed to queue test run 'testuser#RemoteMachine 2015-05-14 15:57:49':
Unable to start the agent process.
Please let me know how can I execute the CodedUI tests on remote machine without using the TestAgent/Controller. Is it possible Via WMI ?. Anyone tried and succeeded please let me know.
Update : I was able to get past this issue by copying the required files in the folder. Now I am trying to launch the CodedUI tests using the PSExec.exe on remote system. I have remote desktop active and when I try to launch the batch file using the command line and it just gives me a message as shown below. PSEXEC.EXE \RemoteMachinename -i "c\users\testuser\desktop\Runtests.bat" when I do that it returns with error code 1 and tests are not started yet. I tried searching for solution I couldn't find anything that is usefull.
For the above mentioned scenario, please copy all the dependency dll (eg : Microsoft.Visualstudio.Qualitytools.CodeduiTest etc.) to the folder where your build dll (projectname.dll) file is copied. Make sure that you are using correct version of vstest that supports the version of the VS you are using. For example, if your code is builded using VS 2015, you have to use vstest.console.exe that comes with Test Agent 2015/Test Agent 2013 Update 5. This trick worked for me. Please let me know whether this works for you. Regards.
This is the first time that this error has come up. I am using Cygwin with Eclipse 3.5 and my Path variable is set to: %CommonProgramFiles%\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Apache Ant\bin;C:\Program Files\SVN\bin;C:\Program Files\Java\jdk1.6.0_18\bin;C:\Users\Mohit\Developer\AndroidSDK\tools;C:\Program Files\QuickTime\QTSystem\;C:\cygwin\bin Notice that C:\cygwin\bin is in my Path. And make.exe is is my Cygwin bin. So I think the problem is not with my system, but maybe my project. But I can't find anything wrong with it. Any suggestions?
Use Process Explorer to take a look at the PATH environment variable inside Eclipse's process. It's possible that it's changing its PATH internally -- if that's the case, you'll need to figure out how to configure Eclipse so that its PATH is set up correctly.
If you're finding that C:\cygwin\bin isn't in Eclipse's PATH, and you recently added that to your PATH, you need to close and restart Eclipse for that change to take affect.
If you still can't figure it out, try using Process Monitor with a filter for Eclipse.exe to get a long, detailed listing of everything it's trying to do. Look for the call to CreateProcess() that's failing and see if you can learn anything more.
I had same problem and I solved that copy make.exe file in path that ecilipse given.
from link below
http://www.mediafire.com/download/e9j9g4zun2t68jn/make.exe
hope helps
I go around this issue by installing MinGW and use its GCC compiler.
Environment - OS: Windows 10, Eclipse: Oxygen