Error Message
-
Hi Guys, I am developing a MFC application using Microsoft Visual Studio 2008, i have a strange error, i dont know how to solve it, if any one know pls tell me the reason.. Error 1 general error c101008a: Failed to save the updated manifest to the file ".\Debug\Account Pro.exe.embed.manifest". The parameter is incorrect. mt.exe
-
Hi Guys, I am developing a MFC application using Microsoft Visual Studio 2008, i have a strange error, i dont know how to solve it, if any one know pls tell me the reason.. Error 1 general error c101008a: Failed to save the updated manifest to the file ".\Debug\Account Pro.exe.embed.manifest". The parameter is incorrect. mt.exe
I regularly see the same error with Visual C++ 2010 Express, but a rebuild always fixes it. I suspect some timing issues in the build process that causes mt.exe to fail. I have not researched the solution since it is always recoverable.
Just say 'NO' to evaluated arguments for diadic functions! Ash
-
I regularly see the same error with Visual C++ 2010 Express, but a rebuild always fixes it. I suspect some timing issues in the build process that causes mt.exe to fail. I have not researched the solution since it is always recoverable.
Just say 'NO' to evaluated arguments for diadic functions! Ash
I experienced too the same issue. Searching the Internet, I found an explaination of it: the build process basically moves through 3 steps:
- compiling
- linking
- embedding manifest
After the linking stage, you have a new exe file on your output folder, and the Manifest Tool (mt.exe) is called on it to embed the application manifest. If you have an AntiVirus that perform real-time scanning, is possible that immediately after the linking stage and before that the Manifest Tool gets access to the executable file, it find the new executable and lock the file to scan it for viruses; in that case, the Manifest Tool gets the file locked for writing and fails.
-
I experienced too the same issue. Searching the Internet, I found an explaination of it: the build process basically moves through 3 steps:
- compiling
- linking
- embedding manifest
After the linking stage, you have a new exe file on your output folder, and the Manifest Tool (mt.exe) is called on it to embed the application manifest. If you have an AntiVirus that perform real-time scanning, is possible that immediately after the linking stage and before that the Manifest Tool gets access to the executable file, it find the new executable and lock the file to scan it for viruses; in that case, the Manifest Tool gets the file locked for writing and fails.
-
An interesting analysis; but I wonder why it only ever affects the manifest builder and never the compiler, linker or any other program I run?
Just say 'NO' to evaluated arguments for diadic functions! Ash
It is not so strange for me: let's assume that the AntiVirus real-time scanner only scan executable files... Then the compiler could not be affected, because it gets source files and produces object files; the linker could not be affected because it gets object files and produce an executable file, but the AntiVirus is not able to scan the created executable until the linker closes the file. Then it seems that the only one tool that could be affected is the Manifest Tool as it gets an executable file that already exists and open it to modify its content. Anyway, this is the only one explaination that I found, but I'm not sure that it's correct nor that it could be the only one reason for the Manifest Tool to fail... I found too something about this issue on the official technical blog of the VC++ team, and I wonder that they simply said: "after our tests, we was not able to reproduce the issue"
-
It is not so strange for me: let's assume that the AntiVirus real-time scanner only scan executable files... Then the compiler could not be affected, because it gets source files and produces object files; the linker could not be affected because it gets object files and produce an executable file, but the AntiVirus is not able to scan the created executable until the linker closes the file. Then it seems that the only one tool that could be affected is the Manifest Tool as it gets an executable file that already exists and open it to modify its content. Anyway, this is the only one explaination that I found, but I'm not sure that it's correct nor that it could be the only one reason for the Manifest Tool to fail... I found too something about this issue on the official technical blog of the VC++ team, and I wonder that they simply said: "after our tests, we was not able to reproduce the issue"