Member Avatar for Mr.Wobbles

I have been having a bit of trouble with my users trying to install my program, I will list the error messages first and then let you know what my settings are for the click-once deployment. I don't see any errors when I install it on the computer I have been working on, it is only when another computer tries it.

ERROR DETAILS
Following errors were detected during this operation.
* [6/25/2007 1:50:18 PM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from file:// path would be here: 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.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
- Manifest XML signature is not valid.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
--- Inner Exception ---
System.Security.Cryptography.CryptographicException
- No signature was present in the subject.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)

Properties:
It is published to a server, with full trust and ClickOnce Security Settings enabled, It is signed, The Application Files looks like this:


It Automatically generates and opens a deployment web page after every publish, If there is anything else you need to know, just ask. Thanks in advance!

appFiles.jpg 62.21 KB
  • 2 Contributors
  • 1 Reply
  • 130 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by AV Manoharan

Dani AI

Generated

reported a ClickOnce install failure that points at a problem with the deployment manifest/signature. As hinted, the publish output is the right place to inspect, but the root causes are usually one of a few repeatable issues: the manifest was unsigned or its signature was broken during transfer, the signing certificate/private key is missing on the build machine, or the client cannot validate the certificate chain.

Practical troubleshooting steps:

  1. Verify the manifest on the machine that published the files. Use MageUI.exe (from the Windows SDK) to open the .application and the deployment manifest and confirm a valid signature and a timestamp entry. If the signature is missing or invalid there, re-import the PFX that contains the private key and re-sign before republishing.
  2. Check how files are uploaded to the server. Binary-only transfers are required; FTP in ASCII mode or an intermediary that rewrites CR/LF or encoding can corrupt XML signatures. Compare a freshly published file with the copy on the server using a binary diff.
  3. Isolate server vs client by copying the published folder to a client machine (file share) and launching the .application locally. If it installs locally, the server transfer or MIME configuration is suspect.
  4. Ensure the signing certificate is valid (not expired/revoked) and that clients can validate its chain or have the certificate trust installed if using a private CA. Timestamping at sign time helps installations after certificate expiry.

Tools and quick commands:

  • Use MageUI.exe to view and re-sign manifests.
  • Use the Windows SDK tooling to verify manifests (for example, the mage command-line verify option).
  • Check the server (IIS/proxy) for MIME settings and any filters that might alter files.

Follow those checks in order: confirm a valid signature on the publisher, confirm unchanged files on the server, then validate client trust. This sequence isolates where the manifest/signature became invalid and shows the corrective action (re-sign, re-upload in binary mode, or install the cert chain).

Member Avatar for AV Manoharan

Wobbles,
Why do you unload all those program bugs in your thread. The answer to your problem is in the thumbnail, that you had added additionally. Go through it.

Best Wishes.

AV Manoharan

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.