CLICKONCE安装失败 [英] CLICKONCE INSTALLATION IS FAILING

查看:76
本文介绍了CLICKONCE安装失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好

我收到以下错误我想通过网址在客户端计算机上安装一次点击。请帮助我,因为我已经尝试了所有可用的线程和选项。作为我保存在应用程序的参考文件夹中的所有引用。因为直到现在还没有创造这个问题的
。为什么会这样,以及如何解决?

I am getting below error wen I am tring to install the click once in the client machine by URL. Please help me as I have tried all the threads and option available .As all the references I have kept in the reference folder of the application. As it was not creating the issue till now. Why this is happing and how it can be resolved

 请找到错误的描述:

 Please find the description of the error:

PLATFORM VERSION INFO

  Windows   :6.2.9200.0(Win32NT)

  Common Language Runtime :4.0.30319.36366

 系统。 Deployment.dll  :4.0.30319.36366建立者:FX452RTMLDR

  clr.dll   :4.0.30319.36366建立者:FX452RTMLDR

  dfdll.dll  &NBSP ;: 4.0.30319.36366通过内置:FX452RTMLDR

  dfshim.dll  &NBSP ;: 6.3.9600.16384(winblue_rtm.130821-1623)

PLATFORM VERSION INFO
 Windows    : 6.2.9200.0 (Win32NT)
 Common Language Runtime  : 4.0.30319.36366
 System.Deployment.dll   : 4.0.30319.36366 built by: FX452RTMLDR
 clr.dll    : 4.0.30319.36366 built by: FX452RTMLDR
 dfdll.dll    : 4.0.30319.36366 built by: FX452RTMLDR
 dfshim.dll    : 6.3.9600.16384 (winblue_rtm.130821-1623)

来源

 部署网址   :应用网址

       ;服务器  :Microsoft-IIS / 7.0

       X-Powered-By :ASP.NET

  ;部署提供商网址  :应用程序网址

 应用程序网址   :application.manifest

       Server  :Microsoft-IIS / 7.0

       X -Powered-By :ASP.NET

SOURCES
 Deployment url   : application URL
      Server  : Microsoft-IIS/7.0
      X-Powered-By : ASP.NET
 Deployment Provider url  : application URL
 Application url   : application.manifest
      Server  : Microsoft-IIS/7.0
      X-Powered-By : ASP.NET

IDENTITIES

 部署身份  : 版本=文化=中性公钥= c0471355aba7d66e,ProcessorArchitecture用于= MSIL

 应用程序标识  :application.exe,版本= 1.2.46.24,文化=中性公钥= c0471355aba7d66e,ProcessorArchitecture用于= msil,type = win32

IDENTITIES
 Deployment Identity  :  Version=,Culture=neutral, PublicKeyToken=c0471355aba7d66e, processorArchitecture=msil
 Application Identity  : application.exe, Version=1.2.46.24, Culture=neutral, PublicKeyToken=c0471355aba7d66e, processorArchitecture=msil, type=win32

应用程序摘要

  *可安装的应用程序。

APPLICATION SUMMARY
 * Installable application.

错误摘要

 以下是错误摘要,日志中稍后列出了这些错误的详细信息。

  *激活应用程序URL导致异常。检测到以下失败消息:

   +文件,stdole.dll,具有与清单中指定的不同的计算哈希。

ERROR SUMMARY
 Below is a summary of the errors, details of these errors are listed later in the log.
 * Activation of application URL resulted in exception. Following failure messages were detected:
  + File, stdole.dll, 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.

操作进度状态

  * [01/03/2017 17:31:08]:已开始激活应用程序URL。

  * [01/03/2017 17:31:08]:部署清单的处理已成功完成。

  * [01/03/2017 17:31:08]:安装申请已经开始。

  * [01/03/2017 17:31:09]:申请清单的处理已成功完成。

  * [01 / 03/2017 17:31:12]:找到兼容的运行时版本4.0.30319。

  * [01/03/2017 17:31:12]:请求信任和检测平台已完成。

OPERATION PROGRESS STATUS
 * [01/03/2017 17:31:08] : Activation of application URL has started.
 * [01/03/2017 17:31:08] : Processing of deployment manifest has successfully completed.
 * [01/03/2017 17:31:08] : Installation of the application has started.
 * [01/03/2017 17:31:09] : Processing of application manifest has successfully completed.
 * [01/03/2017 17:31:12] : Found compatible runtime version 4.0.30319.
 * [01/03/2017 17:31:12] : Request of trust and detection of platform is complete.

错误详情

 以下错误是d在此操作中被检测到。

  * [01/03/2017 17:31:37] System.Deployment.Application.InvalidDeploymentException(HashValidation)

   - 文件,stdole.dll,具有与清单中指定的不同的计算哈希。

   - 来源:System.Deployment

   - 堆栈跟踪:$
    at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath,Hash hash)

    at System.Deployment .Application.ComponentVerifier.VerifyFileHash(字符串文件路径,hashCollection hashCollection)

   在System.Deployment.Application.ComponentVerifier.VerifyComponents()

 &NBSP ; 在System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState子状态中,AssemblyManifest deployManifest,AssemblyManifest appManifest,乌里sourceUriBase,字符串targetdirectory中,字符串基,IDownloadNotification
通知,DownloadOptions运蒸发散)

   在System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState子状态中,ActivationDescription actDesc,Int64类型的transactionId,TempDirectory&安培; downloadTemp)

   在System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState&安培;子状态中,ActivationDescription actDesc)

   在系统.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri,Boolean isShortcut,String textualSubId,String deploymentProviderUrlFromExtension,BrowserSettings browserSettings,String& errorPageUrl)

    at System.Deployment.Application.ApplicationActivator .ActivateDeploymentWorker(对象状态)

ERROR DETAILS
 Following errors were detected during this operation.
 * [01/03/2017 17:31:37] System.Deployment.Application.InvalidDeploymentException (HashValidation)
  - File, stdole.dll, 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

 没有可用的交易信息。

COMPONENT STORE TRANSACTION DETAILS
 No transaction information is available.

如果Sytem有stdole.dll文件22kb 和服务器有22kb文件然后它工作正常如果系统有16kb stdole文件和服务器也有16kb stdole.dll。客户端系统具有.net框架4.6.1。

If Sytem has stdole.dll file 22kb  and server has 22kb file then it is working fine And if the system has 16kb stdole file and server also have the 16kb stdole.dll. Client system have the .net framework 4.6.1.

请提供一些解决方案。

谢谢

Rakesh Birda

Rakesh Birda

推荐答案

>> stdole.dll具有与清单中指定的不同的计算哈希值。

>> stdole.dll, has a different computed hash than specified in manifest.

出现此问题的原因 是"stdole.dll"。重新签名可执行文件后获取新哈希,此原因"stdole.dll"具有与清单中指定的不同的
哈希值。

The reason for this problem is the "stdole.dll" get the new hash after you re-sign your executable, this cause "stdole.dll" 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

https://msdn.microsoft.com/en-us/library/acz3y3te.aspx

您也可以尝试以下解决方案。您可以在AfterCompile目标中签署可执行文件。请在最终项目关闭标记之前添加以下标记。

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=" '


(配置)|


(平台)'=='发布| AnyCPU'">
< Exec Command ="& quot; C:\Program Files(x86)\ Mysoftoft SDKs \ Windows \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ sign / f& quot; C:\ temp \ myPFX.pfx& quot; / p& quot; admin& quot; / v& quot;
(Platform)' == 'Release|AnyCPU' "> <Exec Command="&quot;C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\signtool.exe&quot; sign /f &quot;C:\temp\myPFX.pfx&quot; /p &quot;admin&quot; /v &quot;


这篇关于CLICKONCE安装失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆