General error c1010070 failed to load and parse the manifest

• Remove From My Forums

• Question

• hello, I am trying to embed a manifest file to a C++ project using VS 2003 to provide execution level «highest available».

  here is my manifest file LibTree.exe.manifest

  <?xml version=»1.0″ encoding=»UTF-8″ standalone=»yes»?>
  <assembly xmlns=»urn:schemas-microsoft-com:asm.v1″ manifestVersion=»1.0″>
  <assemblyIdentity type=»win32″ name=»Microsoft.Windows.ProcessMgr» version=»1.0.0.0″ processorArchitecture=»x86″ >
  </assemblyIdentity>
  <trustInfo xmlns=»urn:schemas-microsoft-com:asm.v3″>
      <security>
        <requestedPrivileges>
          <requestedExecutionLevel level=»highestAvailable» uiAccess=»false»></requestedExecutionLevel>
        </requestedPrivileges>
      </security>
    </trustInfo>
  <assembly>

  and given below is the command i set commandline in post build event in project configuration.

  «C:Program FilesMicrosoft SDKsWindowsv7.0Abinmt.exe» -manifest LibTree.exe.manifest -outputresource:$(OutDir)$(TargetFileName);#1

  when building the project I am getting some error, i am posting here.

  Linking…
  Performing Post-Build Event…
  Microsoft (R) Manifest Tool version 5.2.3790.2076
  Copyright (c) Microsoft Corporation 2005. 
  All rights reserved.
  LibTree.exe.manifest : general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified.
  Project : error PRJ0019: A tool returned an error code from «Performing Post-Build Event…»

  Build log was saved at «file://d:ProjectWorkLibTreeLibTreeDebugBuildLog.htm»
  LibTree — 2 error(s), 0 warning(s)

  • Moved by

    Monday, August 27, 2012 8:46 AM
    Move to a more appropriate forum. (From:Visual Studio Debugger)

I never saw that one before, but a Google search suggests that one possibility is too long a path for the manifest file. That does not seem to be your problem.

I suppose a simple solution is to disable generation of manifests. In the project properties, select Linker > Manifest File and change «Generate Manifest» to no. I doubt you will miss it.

I»ve done it. But now it shows:

Embedding manifest...
mt.exe : general error c10100b1: Failed to load file ".Debugsdue2AE.exe". {q~0H

I’ve ReBuild or Clean the solution, it doesn’t work either.

I’ve checked the *.obj files. They are not rebuilt at all.

Thank you for your help.

Mike

Are those strange characters which show in the post actually in the filename?

No. The strange characters are outside the filename. The filename is correct.

Now, it shows:

========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========

There is no Buildlog in ./Debug/, no ***.obj. Silent.

Thanks for keeping help me.

Mike

I started a new and very simple project now.

program main
print *,’sss’
end program main

After Build Solution, it shows:

1>—— Build started: Project: Console2, Configuration: Debug Win32 ——
1>
1>Build log written to «file://D:tempConsole2Console2DebugBuildLog.htm»
1>Console2 — 0 error(s), 0 warning(s)
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

But I don’t find the *.obj in ./Debug at all.

and Build Solution again,
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
Still no *.obj.

Then I Run it, it shows:

Visual Studio cannot debug because the debug target ‘D:tempConsole2Console2debugconsole2.exe’ is missing.

Mike

Oh, I find out that IVF will not automatically remind user to save the newly edited file and add to the project.

I remember CVF will do it.

After I save and add it to project, it works now.

But back to my previous post, it still shows

========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========

There is no new Buildlog in ./Debug/, no updated ***.obj. Silent.

Thanks for keeping help me.

Mike

I’ve redone one static-library project by collecting all the files(modules and external files) except main file.

This is done successfully.

I create a main project to add the main file and also linking thestatic library.

I compare the settings in Project->properties and find Fortran is missing in Configuration Properties for the old project.

Also there is also another Common Properties added.

Mike

Mike,

You will not see Fortran in the Configuration Properties. It will be in the Project Properties.

At this point I suggest that you enter an issue at Intel Premier Support and attach a ZIP of your solution folder. There’s not enough information here so far to understand the problem.

Thank you for your information.

I find out I forgot to include *.mod. There are so many settings to be remebered and they appear in many places.

Mike

Mike

We have a C++ application using MFC. We also use the manifest that is auto generated and we actually do use it.

The environment is windows server 2012 it has TFS 2018 installed on it and a build agent configured. Visual studio 2017 pro 15.6.2 is also installed with all the needed packages for our project.

The weird thing is when i compile the project within visual studio everything is build just fine BUT when i build with the build agent on the same machine there is an error: 

Generating code

All 26621 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.

Finished generating code

C:_TFS(0,0): Error c1010070: Failed to load and parse the manifest. The system cannot find the file specified.

C:_TFS : general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified. [C:_TFS
Build AgentsDEUSRV52_work1stestAppHC100HC100.vcxproj]

LINK(0,0): Error LNK1327: failure during running mt.exe

LINK : fatal error LNK1327: failure during running mt.exe [C:_TFS Build AgentsDEUSRV52_work1stestAppHC100HC100.vcxproj]

Done Building Project «C:_TFS Build AgentsDEUSRV52_work1stestAppHC100HC100.vcxproj» (default targets)
— FAILED.

Done Building Project «C:_TFS Build AgentsDEUSRV52_work1stestAppHC100.sln» (default targets) — FAILED.

Build FAILED.

«C:_TFS Build AgentsDEUSRV52_work1stestAppHC100.sln» (default target) (1) ->

«C:_TFS Build AgentsDEUSRV52_work1stestAppHC100HC100.vcxproj» (default target) (4) ->

(Link target) ->

 
C:_TFS : general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified. [C:_TFS Build AgentsDEUSRV52_work1stestAppHC100HC100.vcxproj]

 
LINK : fatal error LNK1327: failure during running mt.exe [C:_TFS Build AgentsDEUSRV52_work1stestAppHC100HC100.vcxproj]

   
0 Warning(s)

   
2 Error(s)

Time Elapsed 00:02:11.68

Process ‘msbuild.exe’ exited with code ‘1’.

Now it says that a certain file cannot be found except that the file is actually there. My guess is that something else might be wrong here.

So I went to the folder where the sources are being placed via the get sources task which is in the agents folder structure and I then opened the solution with visual studio and build it there and again within visual studio the build is successful.

I’ve been looking on the internet and I found a couple of solutions such as:

1. disable manifest creation in the linker options menu… (this is not a solution for us since we need it)
2. mt.exe can’t cope with spaces in the file path (strange since when opening the same files in visual studio it does built or is there something different when opening it from VS or building it with an agent?)
3. Digital Guardian might restrict execution (we don’t have that nor can i see it in procmon)
4. A virus scanner might block execution (nothing is installed only windows defender is running)

I’m pretty sure that it has nothing to do with points 3 and 4 (virus scanners/ security restrictions) since I can build it successfully within visual studio itself.

I just started to use TFS build for the first time so there is a big chance that i’m missing something here. Hopefully someone can help me out.

• Перемещено

  26 марта 2018 г. 1:12
  TFS issue.