error: c101008d

Question

Hi all,

I have the following minor but annoying error whenever I build my application for the first time after modifying its code .

"Error 2 general error c101008d: Failed to write the updated manifest to the resource of file ".\Debug\eConsole.exe". The process cannot access the file because it is being used by another process. mt.exe "

The building is fine for the second time.  In other words, whenever I modify the code, I have to build it twice because the first time always generates the above error.  This is true for both debuga and release versions.  This is not a big deal, but just a bit annoying.

Could anyone offer some tip to fix this?

Thanks,

hz

Answer 1

Use Handle from SysInternals to see what other process has a handle to the exe.

I suspect what you'll find is that it is a devenv bug, though, especially if you're using VS 2005 which is the worst IDE put out yet by Microsoft in terms of stability.

Handle can be found here:

http://www.sysinternals.com/Utilities/Handle.html

Answer 2

Thanks, Rabbi!

I searched for mt.exe before and after the building and could not find anything.  I am quite sure that I did the search in a correct way because if I have a word file open and search for the file name it will return winword.exe as the process holding the file.

What is puzzling is if I build it again WITHTOUT doing anything, it will build it correctly. In other words, I need to click the build button twice.

hz 

Answer 3

Its probably not related, but atleast two websites report mt.exe as 'most likely a virus/trojan' called Backdoor.W32.EmTee.

See http://www.processlibrary.com/directory/files/mt/ for more information.

Answer 4

Thanks, Nikhil!

According to MSDN, mt.exe seems to be a useful or even necessary file.

http://windowssdk.msdn.microsoft.com/en-us/library/ms716972.aspx

Do you know MS's official opinion regarding this.  I just want to avoid any risk of jeopardizing VS by erasing somthing needed by it.

hz

Answer 5

Yes, but documentation seems to suggest that you need to manually invoke it to sign files and catalogs. I dont think the IDE invokes it automatically. So unless you are calling it manually or through a precompile step on your project....

Answer 6

Nikhil,

I have just gone through all the properties of the VS project and could not find anything referring to mt.exe.  I am lost.

hz 

Answer 7

Find mt.exe and look at its properties... Use processexplorer from sysinternals to see whats spawning mt.exe before/during/after rebuilds. See if you can in any ways indentify what and where this process comes from. All failing, run a antivirus check/investigate possibility that this is a malicious application.

Answer 8

Hi Nikhil,

I used processexplorer to search for mt.exe yesterday and today, before, during and after the building, but I found nothing.

I have just done a virus scan and found nothing. My computer is on our corporate network and guarded tightly.

hz

 

Answer 9

I get this all the time. VS2005, C++ project, release build (debug works fine). I just built the app 27 times in a row before it finally succeeded. It drives me absolutely bonkers. A coworker of mine says he has seen it only a couple times while building the same app.

Answer 10

Thanks,  BradEdwards, for the information.  Now, at least, I know that I am not alone so my computer and its configuration are unlikely the problem.  Most probably it is another VS bug that I can live with for now.

Answer 11

I had this error, too. It seemed to be caused by Norton Antivirus Autoprotect, which tried to scan doings of mt.exe (since it is odd application launched by application). I got rid of the error when I defined Autoprotect to ignore mt.exe. Now everything is smooth.

Answer 12

You may turn off embedding manufist file.. I'm not sure if adding a resource file to your project would help.. but most propubly option one will work.

Answer 13

There is a 'maximum number of paralel project builds' option under 'Tools', 'Options', 'Projects and Solutions', 'Build and Run' branch... Setting it to 1 solved my problems...

Krassi

Answer 14

Great diagnosis Anonymousojjojo!  I had this problem as well.  VERY annoying.  The problem was Symantec Antivirus Autoprotect.  I turned AutoProtect off and immediately everything worked.  Now I just have to figure out how to turn Autoprotect back on without it scanning mt.exe but that should not be very difficult.

 

Answer 15

necrophilissim wrote:

I had this error, too. It seemed to be caused by Norton Antivirus Autoprotect, which tried to scan doings of mt.exe (since it is odd application launched by application). I got rid of the error when I defined Autoprotect to ignore mt.exe. Now everything is smooth.

 

same here. you may want to set norton to ASK ME WHAT TO DO under REAL TIME PROTECTION / AUTO PROTECT which is under ADDITIONAL OPTIONS which is under SETTINGS.