I am getting this error： nsis output setup.exe cannnot be overwrited.
How do I fix this?
There will be one of two issues here:
There is a handle open on it. Most probable cause for this is that it's running.
You don't have permissions to write to it.
Related
Boiled down issue:
Background:
I am trying to get opencv4nodejs to install and am running into errors like opencv2/core.hpp file not found.
Digging into this, knowing full well that I have installed the appropriate files in C:\tools, and added all the required paths and refreshed my cmd.exe to reflect this, I am still getting hit with errors.
Question:
Could someone please describe why the above commands would lead to cmd.exe being unable to find the file I need?
The first dir %OPENCV_INCLUDE_DIR%opencv2\core.hpp command clearly shows that it exists within the environment of the console. Note: This variable has been appended to PATH as %OPENCV_INCLUDE_DIR%
The where opencv2\core.hpp cannot find it, much like my other program cannot find it. I am a bit of a cmd noob, so I may be missing something obvious here, but how can this be the case?
Thanks!
I am currently using Primer3 2.3.6 in Linux. I am using the command "primer3_core -p3_settings_file=/my/path/to/settingsfile.txt /my/path/to/inputfile.txt".
I also tried it in Windows 7 and it worked without any problem. However, in Linux I got the error message "primer3_core: First line must be "Primer3 File - http://primer3.sourceforge.net"..". But the missing line is in the first line of my settings file.
Do you have any suggestions or ideas what could be wrong?
Thanks in advance!
Okay, I could solve the problem. It was more a mistake of myself, because I edited the default settings file, provided by primer3, using word pad in windows. Thereby, I changed the formatting and primer3 was not able to use it anymore.
Now I just use the text editor or visual studio to change parameters in the settings file.
I have the following test InstallScript InstallShield code, which executes correctly in the normal interactive mode, but crashes setup.exe /s (silent) mode on calls to ChangeDirectory that involve any sort of actual depth of directories.
//Note: "C:" ^ "temp" resolves to "C:\temp", but it never successfully
//executes when run silent mode. It works fine in interactive mode, however.
ChangeDirectory("C:" ^ "temp");
//No subsequent code gets executed at this point in silent mode
I'm running this on a Windows 2008 x64 Server in a command window with Administrator privileges. The c:\temp directory exists, and EVERYONE has been granted full control rights to it.
The exit code is -2147213312, which is 0x80042000 in the error guide corresponding to
The installation exited with the abort keyword because the end user
canceled the installation.
What could possibly be going on here? I've tried using the try/catch syntax to examine the error, but the catch block never executes in this case, seemingly asserting that there's no error but instead an abort called?
The Installscript Engine does a lot of stuff behind the scene. It keeps changing the working directory. Thus, it is not very reliable to use ChangeDirectory(). It is surely better to use FULL PATH to all executables and other files. LaunchAppAndWait() too has this trouble. So full path needs to be used without fail.
Further, the Installshield help for ChangeDirectory() clearly mentions the following:
When you are specifying a file in your script, always specify the full
path (using the appropriate InstallShield system variable, for
example, SRCDIR) rather than depend on the current folder having the
appropriate value. The script internally executes code that can change
the current folder, so its value may not be what you expect.
The thing is, results are not reliable. They may work or may not.
We get this errorcode when our recorded .iss file is missing an entry in the .iss response file.
See Creating the Response File for more Details.
Logging an installscript setup didn't give us much information, so we wrote some functions to write to a custom logfile which helped us a lot.
One of my users sent error report that the installer has crashed with following error:
Runtime error (at 34:1346): Type Mismatch
The installer uses Inno Setup. The investigation showed that the bug caused error has been contained in installer.iss.
Where can error be located if I know "34:1346" ?
That error location is in the compiled bytecode of your script and as such is pretty much impossible to track back to a line of code.
If they can reproduce it, they should launch your installer with /log=filename command line option and you can take a look into such file.
When I try to compile my c++ dll I get this error
mt.exe : command line error c10100a9: Some operation on the input manifests must be specified (even if it is just to pipe the input to the output). Use the /? option for help on usage and samples.
I have disabled Manifest Tool from the properties menu, the only reason I did that was because it was giving me a hard time to compile.
Now I can build my DLL, but only once every three times, because of the above mentioned error.
Any help to get rid of this problem would be appreciated.
I found solution by (project properties ->Configuration properties ->Manifest Tool ->Input and Output) in Output Manifest File type:
$(IntDir)$(TargetName)$(TargetExt).embed.manifest
and press Ok.
I see this q is languishing. Is the problem you have now better or worse than what you had before disabling Manifest Tool? Perhaps it would be worth re-enabling it and trying to work through those problems.
I have never seen this error, though I know MT.EXE has had a few problems. Make sure you have the latest SP for your VS installation as well.