Application Validation did not succeed. Unable to continue

Posted on 2007-08-10
Last Modified: 2010-10-05
Hi Experts
I have been working on this app for a while now, using the Publish option within VB 2005 to create the setup files and until now this has worked perfectly.
Environment is VB 2005, SQL 2005, Vista and I repeat until this morning, everything was great.
When I now compile (publish) my setup files creates an error:
Application Validation did not succeed. Unable to continue

I am pasting this from the details provided in the error message which is:

      Below is a summary of the errors, details of these errors are listed later in the log.
      * Activation of D:\IDT\IDT.application resulted in exception. Following failure messages were detected:
            + File, IDT.exe.config, has a different computed hash than specified in manifest.

      No transaction error was detected.

      There were no warnings during this operation.

      * [2007/08/10 06:04:35 PM] : Activation of D:\IDT\IDT.application has started.
      * [2007/08/10 06:04:36 PM] : Processing of deployment manifest has successfully completed.
      * [2007/08/10 06:04:36 PM] : Installation of the application has started.
      * [2007/08/10 06:04:36 PM] : Processing of application manifest has successfully completed.
      * [2007/08/10 06:04:52 PM] : Request of trust and detection of platform is complete.

      Following errors were detected during this operation.
      * [2007/08/10 06:04:54 PM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
            - File, IDT.exe.config, has a different computed hash than specified in manifest.
            - Source: System.Deployment
            - Stack trace:
                  at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
                  at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
                  at System.Deployment.Application.ComponentVerifier.FileComponent.Verify()
                  at System.Deployment.Application.ComponentVerifier.VerifyComponents()
                  at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
                  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)
Question by:esps
    1 Comment
    LVL 4

    Accepted Solution

    Something must have changed.  I'm not sure if this will help, but have you tried this:
    IN VS2005 in your soultion explorer window
    1> click "Properties" a new window will open
    2>  click signing on the left tab row
    3> then place a check in the box that says "click once manifest"
    4>  then click the "create test certificate button"
    5>  then rebuild your project
    6> then publish it.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Installations often have prerequisites, such as “Microsoft .Net framework is required for this product”. The usual implementation in MSI installations is system search for a particular registry setting representing the required prerequisite, followe…
    Among others, I monitor the Windows Installer zone and Installer zone. I find that many of the questions could be answered much more quickly if a Windows Installer verbose log were submitted with the question.   However, I do not always have t…
    This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA.…
    Hi everyone! This is Experts Exchange customer support.  This quick video will show you how to change your primary email address.  If you have any questions, then please Write a Comment below!

    761 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    10 Experts available now in Live!

    Get 1:1 Help Now