我们正在创建一个软件项目（VS 2010，.NET 3.5 SP1），它通过Office 2007 PIA使用Excel Interop。我们正在将其部署到互联网上以进行clickonce安装。在大多数情况下，它工作正常。但最近有一位客户在安装它时遇到了问题（参见下面的日志文件）。
据我在互联网上阅读时所知，它可能在某种程度上与另一个应用程序注册的PIA有关。
任何人都可以提供一些有用的提示（也许还有一些关于这个主题的阅读资料）？
非常感谢！
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 4.0.30319.269
System.Deployment.dll : 4.0.30319.1 (RTMRel.030319-0100)
clr.dll : 4.0.30319.269 (RTMGDR.030319-2600)
dfdll.dll : 4.0.30319.1 (RTMRel.030319-0100)
dfshim.dll : 4.0.31106.0 (Main.031106-0000)
SOURCES
Deployment url : http://***/***.application
Server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
Deployment Provider url : http://***/***.application
Server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
Application url : http://***/***.manifest
Server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
IDENTITIES
Deployment Identity : ***, Version=1.1.0.893, Culture=neutral, PublicKeyToken=b5867eb738db6c5c, processorArchitecture=msil
Application Identity : ***, Version=1.1.0.893, Culture=neutral, PublicKeyToken=b5867eb738db6c5c, 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 http://***/***.application resulted in exception. Following failure messages were detected:
+ Exception occurred loading manifest from file Microsoft.Office.Interop.Excel.dll: the manifest may not be valid or the file could not be opened.
+ File Microsoft.Office.Interop.Excel.dll is not a valid Portable Executable (PE) file.
+ File {0} is not a valid Portable Executable (PE) file.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [9/20/2012 2:44:56 PM] : Activation of http://***/***.application has started.
* [9/20/2012 2:44:57 PM] : Processing of deployment manifest has successfully completed.
* [9/20/2012 2:44:57 PM] : Installation of the application has started.
* [9/20/2012 2:44:58 PM] : Processing of application manifest has successfully completed.
* [9/20/2012 2:45:00 PM] : Found compatible runtime version 2.0.50727.
* [9/20/2012 2:45:00 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.
* [9/20/2012 2:45:00 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.
* [9/20/2012 2:45:00 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.
* [9/20/2012 2:45:00 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.
* [9/20/2012 2:45:00 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.
* [9/20/2012 2:45:00 PM] : Request of trust and detection of platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [9/20/2012 2:45:34 PM] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
- Exception occurred loading manifest from file Microsoft.Office.Interop.Excel.dll: the manifest may not be valid or the file could not be opened.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.ManifestLoadExceptionHelper(Exception exception, String filePath)
at System.Deployment.Application.Manifest.AssemblyManifest.LoadFromInternalManifestFile(String filePath)
at System.Deployment.Application.DownloadManager.ProcessDownloadedFile(Object sender, DownloadEventArgs e)
at System.Deployment.Application.FileDownloader.DownloadModifiedEventHandler.Invoke(Object sender, DownloadEventArgs e)
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
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)
--- Inner Exception ---
System.IO.IOException
- File Microsoft.Office.Interop.Excel.dll is not a valid Portable Executable (PE) file.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.PEStream.ConstructFromFile(String filePath, Boolean partialConstruct)
at System.Deployment.Application.Manifest.AssemblyManifest.LoadFromInternalManifestFile(String filePath)
--- Inner Exception ---
System.ComponentModel.Win32Exception
- File {0} is not a valid Portable Executable (PE) file.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.PEStream.DosHeader..ctor(FileStream file)
at System.Deployment.Application.PEStream.ConstructPEImage(FileStream file, Boolean partialConstruct)
at System.Deployment.Application.PEStream.ConstructFromFile(String filePath, Boolean partialConstruct)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
我们有一个几乎相同的日志文件与我们自己的ClickOnce应用程序，虽然它在第一个文件下载失败（ClickOnce似乎按字母顺序下载文件）。我们让用户将部署应用程序的域列入白名单，问题得到解决。
https://answers.atlassian.com/questions/154127/sourcetree-for-windows-install。
在我的商店，ClickOnce通常用于超级锁定的IT环境（只有我们的软件可用的工厂floof机器，用户甚至无法将文件保存到他们的桌面），因此将网站列入白名单可以解决一系列问题。
在这里恢复一个死人，但由于我刚刚与我的一个部署遇到了同样的事情，我也会加上我的五美分。
部署日志的输出与您的基本相同：
* Activation of //***//.application resulted in exception. Following failure messages were detected:
+ Exception occurred loading manifest from file DevExpress.Utils.v17.1.UI.dll: the manifest may not be valid or the file could not be opened.
+ File DevExpress.Utils.v17.1.UI.dll is not a valid Portable Executable (PE) file.
+ PE file does not have enough data.
我删除了对相关dll的引用，重新添加并再次发布。这解决了我的问题。