Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, March 14, 2017 8:55 AM
I have finished my application but encountered an unexpected error while installing. I am using Visual Studio 2008. I published my application with a clickonce manifest. When the installation process was almost done, an error pops out. On the details it said that my "Database.accdb" has a different computed hash than specified in manifest. Please help me this is urgent. I already tried using the MageUI and clearing the bin/debug and bin/release. Here are the error details:
PLATFORM VERSION INFO Windows : 6.1.7601.65536 (Win32NT) Common Language Runtime : 4.0.30319.42000 System.Deployment.dll : 4.6.1081.0 built by: NETFXREL3STAGE clr.dll : 4.6.1081.0 built by: NETFXREL3STAGE dfdll.dll : 4.6.1081.0 built by: NETFXREL3STAGE dfshim.dll : 4.0.41209.0 (Main.041209-0000)
SOURCES Deployment url : file:///C:/Backup/Senior%20Project/Pre-Final/ComSAINos.application Application url : file:///C:/Backup/Senior%20Project/Pre-Final/Application%20Files/ComSAINos_1_1_1_9/ComSAINos.exe.manifest
IDENTITIES Deployment Identity : ComSAINos.application, Version=1.1.1.3, Culture=neutral, PublicKeyToken=bde51c6b819cb260, processorArchitecture=msil Application Identity : ComSAINos.exe, Version=1.1.1.3, Culture=neutral, PublicKeyToken=bde51c6b819cb260, processorArchitecture=msil, type=win32
APPLICATION SUMMARY * Installable application.
ERROR SUMMARY Below is a summary of the errors, details of these errors are listed later in the log. * Activation of C:\Backup\Senior Project\Pre-Final\ComSAINos.application resulted in exception. Following failure messages were detected: + File, Database11.accdb, 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 * [3/14/2017 4:16:43 PM] : Activation of C:\Backup\Senior Project\Pre-Final\ComSAINos.application has started. * [3/14/2017 4:16:43 PM] : Processing of deployment manifest has successfully completed. * [3/14/2017 4:16:43 PM] : Installation of the application has started. * [3/14/2017 4:16:43 PM] : Processing of application manifest has successfully completed. * [3/14/2017 4:16:46 PM] : Found compatible runtime version 2.0.50727. * [3/14/2017 4:16:46 PM] : Detecting dependent assembly Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil using Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil. * [3/14/2017 4:16:46 PM] : Detecting dependent assembly System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil. * [3/14/2017 4:16:46 PM] : Detecting dependent assembly WindowsBase, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=msil using WindowsBase, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=msil. * [3/14/2017 4:16:46 PM] : Detecting dependent assembly stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A using stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a. * [3/14/2017 4:16:46 PM] : Detecting dependent assembly System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil. * [3/14/2017 4:16:46 PM] : Request of trust and detection of platform is complete.
ERROR DETAILS Following errors were detected during this operation. * [3/14/2017 4:16:46 PM] System.Deployment.Application.InvalidDeploymentException (HashValidation) - File, Database11.accdb, 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.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, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl) at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS No transaction information is available.
All replies (3)
Wednesday, March 15, 2017 2:52 AM
Hi -TwisTedfaTe-,
This forum discusses and asks questions about the Visual Basic programming language, Since your issue is more related to click once. we'll move it click once for suitable support.
Thanks for your understanding and cooperation.
Best regards,
Cole Wu
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].
Wednesday, March 15, 2017 6:33 AM
ok thank you, but any response/answer regarding to my problem, please? :-(
Thursday, March 16, 2017 11:56 AM
Hi,
>> "Database.accdb" has a different computed hash than specified in manifest.
The reason for this problem is the file "Database.accdb" get the new hash after you re-sign your executable, this cause "Database.accdb" have a different hash than specified in the manifest.
To resolve this problem, you need to update or regenerate the application manifest.
https://msdn.microsoft.com/en-us/library/acz3y3te.aspx****
You can also try below solution. You could sign the executable in the AfterCompile target. Please add the following tag before the final project close tag.
<Target Name="AfterCompile" Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
<Exec Command=""C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\signtool.exe" sign /f "C:\temp\myPFX.pfx" /p "admin" /v "$(ProjectDir)obj\$(ConfigurationName)\$(TargetFileName)"" />
</Target>
Best Regards,
Bob
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].