[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Application Validation did not succeed. Unable to continue

Posted on 2007-08-10
1
Medium Priority
?
8,103 Views
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:

ERROR SUMMARY
      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.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
      No transaction error was detected.

WARNINGS
      There were no warnings during this operation.

OPERATION PROGRESS STATUS
      * [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.

ERROR DETAILS
      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)
0
Comment
Question by:esps
1 Comment
 
LVL 4

Accepted Solution

by:
ChadFolden earned 1500 total points
ID: 19733109
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.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

One of the major drawbacks of deploying applications by GPO is the complete lack of any centralized reporting. After a normal deployment, there are two ways to find out if it was successful – by looking in the event log, and by looking in the log of…
If you don't know how to downgrade, my instructions below should be helpful.
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. http://www.experts-exchange.com/videos/1478/Excel-Error-Handlin…
Are you ready to place your question in front of subject-matter experts for more timely responses? With the release of Priority Question, Premium Members, Team Accounts and Qualified Experts can now identify the emergent level of their issue, signal…
Suggested Courses

834 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