I am receiving the above error when running the task sequence and it is failing on the step that is in the picture I provided. Does anyone have any ideas on why? I know the error is very generic, and I have tried several things to address it - I checked the box to disable 64-bit, I made sure that the package containing the batch file was referenced in that step, etc. Any suggestions would be greatly appreciated, I am very much a noob when it comes to SCCM. Thank you.
Could you post the SMSTS.log saved in C:\Windows\CCM ?
It should contain the reason why this is failing
While looking at your TS, It could be that using a working folder with UNC paths fail the TS because CMD does not support running UNC paths out of the box.
Try adding cmd /c at the start of the Command Line field. It's quirky, but has often fixed my issues.
Related
I am trying to build an app from the CMD line using MSVC 2019.
The instructions that came with the project (libssl) say to run "VCVARS32.BAT" and then "nmake".
When I run VCVARS32.BAT, the following error message is emitted:
\Common was unexpected at this time
A similar issue was discussed in SO (#8756828) but that one applied to modifying VCVARS32 which I am not doing. An answer to that also mentioned quote marks within the PATH, but I checked and that is not so.
I am running from a base CMD.EXE prompt on a Dell Win10-64 machine.
Any idea why this is happening?
I found a fix. The problem was quotes ("") in the PATH as suggested in answer to SO #8756828. Strangely, there were NO quotes in ControlPanel->System->Advanced->EnvironmentVariables->SystemVariables->PATH or in the Registry, however "echo %PATH%" did show quotes. By trial and error, I discovered that the offending component in my PATH was
C:\Program Files (x86)\Common Files\Oracle\Java\javapath
When I removed that, all was good. At first, I suspected that the embedded spaces were the culprit, but then I noticed other PATH components with embedded spaces that caused no problems. So, I still don't understand what was going on but at least I have a working fix.
When I am running application on simulator or device and try to use PO command during debug. Xcode is throwing error instead of printing value. It is happening after I have updated Xcode 12.
error: virtual filesystem overlay file
/all-product-headers.yaml' not found
error: couldn't IRGen expression. Please check the above error messages for possible root causes.
What is the solution for this ?
Any help would be appreciated.
Go to /Users/<YOUR_USER>/Library/Developer/Xcode/ and delete "DerivedData" folder.
If in the path of the missing file is the name of a framework e.g. Usabilla.build/Release-iphonesimulator/Usabilla.build/all-product-headers.yaml
Try using an older version, using version 6.4.7 of Usabilla fixed the issue for me.
If the above fixes don't work, here are some info that might help:
https://steipete.com/posts/couldnt-irgen-expression/
I am trying to compile and run cafee with the directions found here:
https://initialneil.wordpress.com/2015/07/15/caffe-vs2013-opencv-in-windows-tutorial-i/
But when I run it, for example on the MNIST example:
"bin\caffe.exe" train --solver=examples\mnist\lenet_solver.prototxt
I get the output:
Usage: leveldbutil command...
dump files... -- dump contents of specified files
What do I do to fix this?
Pulling from https://github.com/BVLC/caffe/tree/windows solved the problem.
Check the users group in case you need help:
https://groups.google.com/forum/#!forum/caffe-users
Check the issue tracker in case you need help:
https://github.com/BVLC/caffe/issues
I want to add a manifest to .exe file so it stops asking users to run as administrator in Windows 7.
I followed this tutorial which seems to do exactly what I want to accomplish except I get this error when I do the same and I cannot find a solution for it:
mt.exe : general error c101008d: Failed to write the updated manifest to the resource of file "C:\install.exe". The parameter is incorrect.
this is the command I used:
mt.exe –manifest C:\install.exe.manifest -outputresource:C:\install.exe;1
Any help would be really appreciated, thank you.
This is how I solved this problem, it was actually a syntax issue:
mt.exe –manifest "C:\install.exe.manifest" -outputresource:"C:\install.exe;#1"
There is an even better solution is to edit the .exe directly using visual studio.
I'm using ant.bat (in Ant 1.7.1) to build the all target in a build.xml file, on Windows 2003 Server. (I've substituted "xxx" in the error message for the project name in that file.)
It builds successfully, but then ends with:
2009-06-10 17:26:03 | all:
2009-06-10 17:26:03 |
2009-06-10 17:26:03 | BUILD FAILED
2009-06-10 17:26:03 | Target "1" does not exist in the project "xxx".
...and returns with a non-zero error code.
I've searched build.xml unsuccessfully for anything that might lead to this error. (There is no target "1", of course, nor any dependencies that might resolve "1".)
I'm hoping someone out there might recall seeing this. I don't expect anyone to debug the XML for me, but a Google search turned up http://simile.mit.edu/mail/ReadMsg?listId=9&msgId=2735, which contains "I found an email thread on this problem and will
retry.". I wish I could find that thread.
Update - here's the command-line:
D:/build/toolchain/noarch/ant-1.7.1/bin/ant.bat all -DBRANCH_NAME="main" -DBUILD_NUMBER="66675" -DCHANGE_NUMBER="1061789" -DGOBUILD_AUTO_COMPONENTS= -DGOBUILD_OFFICIAL_BUILD=1 -DGOBUILD_VICLIB_ROOT=d:/build/ob/bora-66675/compcache//viclib/ob-65655/windows -DGOBUILD_VIMBASE_ROOT=d:/build/ob/bora-66675/compcache//vimbase/ob-64494/windows -DOBJDIR="beta" -DPRODUCT_BUILD_NUMBER="82" -DPUBLISH_DIR="d:/build/ob/bora-66675/publish" -DRELTYPE="beta" -DREMOTE_COPY_SCRIPT="D:/build/toolchain/win32/python-2.5/python.exe D:/build/gobuild/script/gobuildc.py bora-66675"'
Hopefully it's of some help.
Do you have any targets that depend on "1"? Perhaps due to a typo?
<target name="SomeTarget" depends="1">
....
</target>
Update: You explained (paraphrased) that the error message was a result of the (partial) command-line
-DGOBUILD_AUTO_COMPONENTS= -DGOBUILD_OFFICIAL_BUILD=1
Although there's a space between those two define statements, it's being treated like this:
-DGOBUILD_AUTO_COMPONENTS=-DGOBUILD_OFFICIAL_BUILD=1
because something is expected to follow '='. And it appears that the second '=' is being treated as a whitespace, perhaps because ANT is confused. I would not expect that. The correct way to do what you want to do is:
-DGOBUILD_AUTO_COMPONENTS="" -DGOBUILD_OFFICIAL_BUILD=1
That way, something follows the equals sign and ANT won't get confused.
could you add the commandline you are using. it could be that ant agrees with you that there is no target '1' but that it believes you are passing one in.
This posting helped me resolve this error and wanted to share my version of the problem.
Target "listener" does not exist in the project "null".
ANT will use an environment variable ANT_ARGS if it is set. I was using the -listener option and set this option in my Windows envvar, ANT_ARGS. When I pasted the options into the Env Var:
-listener org.apache.tools.ant.listener.Log4jListener -lib D:\apache-ant-1.7.1\lib
I was missing the 'minus' sign in front of the 'listener' option.
This is similar to the problem above, but was hidden by the fact that I used the envvar ANT_ARGS.
Ya goose :-) You changed the project to "xxx" in the heading but left it as "vireporting" in the error output.
So the cat's out of the bag. You may as well make our life easier and post the XML since our ability to help you (psychic debugging) is greatly limited. If you want, sanitize the XML you post (better than you sanitized the original, hopefully).
And your comment ('There is no target "1"') makes sense since that's what ant is telling you. What you may have done is inadvertently created a dependency on that non-existent target.
It turns out this error message is the result of "-DGOBUILD_AUTO_COMPONENTS= -DGOBUILD_OFFICIAL_BUILD=1" in the command-line. I guess having nothing after the '=' in that -D option confuses Ant. (As an experiment, I changed "-DGOBUILD_OFFICIAL_BUILD=1" to "-DGOBUILD_OFFICIAL_BUILD=2" in this programmatically-generated command-line and the error message changed to "Target "2" does not exist in the project "xxx".")
Removing "-DGOBUILD_AUTO_COMPONENTS=" eliminated the build failure.
If someone can clearly explain why Ant emits such a strange error message in this case (or perhaps why it's not strange if one looks at it correctly), I'll accept your answer.