FIX: You cannot download the .application file when you deploy an application by using ClickOnce deployment in a secure environment


Consider the following scenario:
  • You deploy an application by using ClickOnce deployment in a secure environment.
  • You set the client computers to use a proxy server.
  • You set the client computers to bypass the proxy server for local addresses.
  • In the Machine.config file on the client computers, you set the enabled attribute of the defaultproxy feature to false.
In this scenario, you cannot download the .application file. Additionally, the following information is logged in the error log of ClickOnce deployment:
Windows: 5.1.2600.131072 (Win32NT)
Common Language Runtime: 2.0.50727.832
System.Deployment.dll: 2.0.50727.832 (QFE.050727-8300)
mscorwks.dll: 2.0.50727.832 (QFE.050727-8300)
dfdll.dll: 2.0.50727.42 (RTM.050727-4200)
dfshim.dll: 2.0.50727.42 (RTM.050727-4200)

Deployment url: http://DeployServerName:8000/YourClickOnceApplication.application

Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://DeployServerName:8000/YourClickOnceApplication.application resulted in exception. Following failure messages were detected:
+ Object reference not set to an instance of an object.

No transaction error was detected.

There were no warnings during this operation.

* [1/11/2008 1:01:25 PM] : Activation of http://DeployServerName:8000/YourClickOnceApplication.application has started.

Following errors were detected during this operation.
* [1/11/2008 1:01:25 PM] System.NullReferenceException
- Object reference not set to an instance of an object.
- Source: System.Deployment

- Stack trace:

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.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
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)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

No transaction information is available.


Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework 2.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Note You must apply this hotfix on the client computers.


You must have the .NET Framework 2.0 Service Pack 1 installed to apply this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform


To work around this problem, follow these steps.

Important These steps may increase your security risk. These steps may also make the computer or the network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you decide to implement this process, take any appropriate additional steps to help protect the system. We recommend that you use this process only if you really require this process.
  1. Find the following code in the Machine.config file.
    <defaultProxy enabled="false" useDefaultCredentials="false">
    Then, change it to the following code.
    <defaultProxy enabled="true" useDefaultCredentials="false">
    Note This file is usually located in the following path:
  2. Restart the client computers.
Note This workaround reduces the security level on the client computers.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

917952 FIX: Error message when you try to install a ClickOnce application that you created in the .NET Framework 2.0 onto a client computer that is configured to use a proxy server: "Proxy authentication required"

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

รหัสบทความ: 952324 - การตรวจสอบครั้งสุดท้าย: 8 ต.ค. 2011 - ฉบับแก้ไข: 1

Microsoft .NET Framework 2.0