部署提供程序上的部署标识与原始部署标识不同 [英] The deployment identity at the deployment provider is not the same as the original deployment identity

查看:158
本文介绍了部署提供程序上的部署标识与原始部署标识不同的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

发布我的应用程序时出错了,它给我一个错误  部署提供商的部署标识与原始部署标识不同

Whats wrong when I publish my application, it give me an error The deployment identity at the deployment provider is not the same as the original deployment identity

PLATFORM VERSION INFO
	Windows 			: 6.1.7601.65536 (Win32NT)
	Common Language Runtime 	: 4.0.30319.42000
	System.Deployment.dll 		: 4.7.2116.0 built by: NET47REL1LAST
	clr.dll 			: 4.7.2116.0 built by: NET47REL1LAST
	dfdll.dll 			: 4.7.2116.0 built by: NET47REL1LAST
	dfshim.dll 			: 4.0.41209.0 (Main.041209-0000)

SOURCES
	Deployment url			: file:///C:/Users/fsze88/Downloads/KennamApp.application
	Deployment Provider url		: file://server/publish/KennamApp.application

ERROR SUMMARY
	Below is a summary of the errors, details of these errors are listed later in the log.
	* Activation of C:\Users\fsze88\Downloads\KennamApp.application resulted in exception. Following failure messages were detected:
		+ The deployment identity at the deployment provider is not the same as the original deployment identity.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
	No transaction error was detected.

WARNINGS
	There were no warnings during this operation.

OPERATION PROGRESS STATUS
	* [29/10/2017 19:52:22] : Activation of C:\Users\fsze88\Downloads\KennamApp.application has started.

ERROR DETAILS
	Following errors were detected during this operation.
	* [29/10/2017 19:52:22] System.Deployment.Application.InvalidDeploymentException (SubscriptionSemanticValidation)
		- The deployment identity at the deployment provider is not the same as the original deployment identity.
		- Source: System.Deployment
		- Stack trace:
			at System.Deployment.Application.DownloadManager.FollowDeploymentProviderUri(SubscriptionStore subStore, AssemblyManifest& deployment, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options)
			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, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl, Uri& deploymentUri)
			at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
--- End of stack trace from previous location where exception was thrown ---
			at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
			at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(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.


谢谢!!!

Thank You!!!

fsze88

推荐答案

您好fsze88,

Hi fsze88,

> >部署提供商处的部署标识与原始部署标识不同。

>>The deployment identity at the deployment provider is not the same as the original deployment identity.


我们通常会收到此错误:

We usually get this error:

1,当尝试发布具有不同目标体系结构的单击一次应用程序时,那么当前在计算机上安装的内容(x86 vs x64)

1, When tried to publish a click once app with a different target architecture then what is currently installed on a machine (x86 vs x64)

2,或者当申请的签名/证书与原始出版物不同时。

2, Or when the signature/certificate of the application is different than the original publish.


这篇关于部署提供程序上的部署标识与原始部署标识不同的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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