ParseException on manifest when installing ClickOnce App

I get a ParseException on the manifest when installing ClickOnce App. I can access the manifest just fine with a browser. I have searched the forums and not found asolution to this.

Any help is much appreciated.

Thanks,

Rich

PLATFORM VERSION INFO
Windows    : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.42
System.Deployment.dll   : 2.0.50727.42 (RTM.050727-4200)
mscorwks.dll    : 2.0.50727.42 (RTM.050727-4200)
dfdll.dll    : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll    : 2.0.50727.42 (RTM.050727-4200)

SOURCES
Deployment url   : http://graphite/OpEx/App/Transzap.Shell.application
      Server  : Microsoft-IIS/6.0
      X-Powered-By : ASP.NET
Deployment Provider url  : http://graphite/OpEx/App/Transzap.Shell.application

IDENTITIES
Deployment Identity : Transzap.Shell.application, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f7f9d43db17f1e5a, processorArchitecture=msil

APPLICATION SUMMARY
* Installable application.
* Trust url parameter is set.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://graphite/OpEx/App/Transzap.Shell.application resulted in exception. Following failure messages were detected:
  + Exception reading manifest from http://graphite/OpEx/App/Transzap.Shell_1_0_0_0/Transzap.Shell.exe.manifest: the manifest may not be valid or the file could not be opened.
  + Parsing and DOM creation of the manifest resulted in error. Following parsing errors were noticed:
   -HRESULT: 0x80070c81
    Start line: 0
    Start column: 0
    Host file:
  + Exception from HRESULT: 0x80070C81

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [1/3/2006 10:55:46 AM] : Activation of http://graphite/OpEx/App/Transzap.Shell.application has started.
* [1/3/2006 10:55:46 AM] : Processing of deployment manifest has successfully completed.
* [1/3/2006 10:55:46 AM] : Installation of the application has started.

ERROR DETAILS
Following errors were detected during this operation.
* [1/3/2006 10:55:46 AM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
  - Exception reading manifest from http://graphite/OpEx/App/Transzap.Shell_1_0_0_0/Transzap.Shell.exe.manifest: the manifest may not be valid or the file could not be opened.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
   at System.Deployment.Application.DownloadManager.DownloadApplicationManifest(AssemblyManifest deploymentManifest, String targetDir, Uri deploymentUri, IDownloadNotification notification, DownloadOptions options, Uri& appSourceUri, String& appManifestPath)
   at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
   at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState subState, ActivationDescription actDesc)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
  --- Inner Exception ---
  System.Deployment.Application.InvalidDeploymentException (ManifestParse)
  - Parsing and DOM creation of the manifest resulted in error. Following parsing errors were noticed:
   -HRESULT: 0x80070c81
    Start line: 0
    Start column: 0
    Host file:
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.Manifest.AssemblyManifest.LoadCMSFromStream(Stream stream)
   at System.Deployment.Application.Manifest.AssemblyManifest..ctor(FileStream fileStream)
   at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
  --- Inner Exception ---
  System.Runtime.InteropServices.COMException
  - Exception from HRESULT: 0x80070C81
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Internal.Isolation.IsolationInterop.CreateCMSFromXml(Byte[] buffer, UInt32 bufferSize, IManifestParseErrorCallback Callback, Guid& riid)
   at System.Deployment.Application.Manifest.AssemblyManifest.LoadCMSFromStream(Stream stream)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Answer this question

ParseException on manifest when installing ClickOnce App

AkChauhan
This call stack mostly indicates that the manifest file can not be reached

"the manifest may not be valid or the file could not be opened"

try to see if you can access the manifest via http. Manifest in this context is the application manifest (.exe.manifest). try opening this over http in IE.. see if you can access and open it

sreekanth
Rowjie
This problem was caused because I was including com interop dlls in a project. When I removed them everything worked fine.
MuraliN

Hi,

I am getting the same warning MSB3112 Two or more assemblies have the same identity "go", ."go" is the the project's name.

How can I find out with is the other reference and how can I remove it

thanks

zaynun
Andru

Hi,

Yeah, I can open it over http with no problem.

Rich
Tollerod
Just look on the project refferences list, pickup and remove it.
michael scott
Okay my problem had nothing to do with COM Interop (we aren't using any yet, but I know we will.... so I want to know more about this possible issue).

My issue was that I had 2 log4net assemblies in a nested heirarchy (the assembly shouldn't have been located only in one of these locations...)

Here is what MAGE said when it tried to create and sign the manifest:

deploy:
...
     [exec] Creating new application manifest...
     [exec] Warning MSB3112: Two or more assemblies have the same identity 'log4net, Version=1.2.9.0, Culture=neutral, PublicKeyToken=B32731D11CE58905'.
     [exec]
     [exec] HenrySchein.Startup.exe.manifest successfully created. However, some errors were encountered.
     [exec] HenrySchein.Startup.exe.manifest successfully signed
....

I'll have to play with MAGE to see if it gives me error codes when I do this and it can be passed back to my NANT script to fail the situation where MAGE can't create a valid manifest.

So it boils down to an invalid ClickOnce manifest....
l1101100
I am having the same problem. Is it REALLY because of COM Interop assemblies This seems like a HUGE limitation!

Microsoft team, please advise!
Punky
The 'Generate serialization assembly' option was on, and I refferenced the project.XmlSerializers.exe as well.

When publishing I was getting two warnings:
Warning MSB3112: Two or more assemblies have the same identity "project.exe", for both assemblies, the project.exe and the project.XmlSerializers.exe

Removing the refference and setting the 'Generate serialization assembly' off, fixed the problem.
ParseException on manifest when installing ClickOnce App

Answer this question