We have a clickonce application that we deploy to 2 locations - production and alpha (hosted at completely different facilities). We have a user that at random times cannot receive clickonce updates successfully because of timeouts (trace attached). They always fail in the middle of the update, and once it fails theycontinue tofail at the same point (although that pointcan be different on different days).

Here's some more data points:

• After a failure, at some point in the future (usually the next day), the download beginsworking fine.
• He is on a fiber network to the internet which is usually very fast and from what I've seen very reliable.
• He has 2 machines - 1 xp and 1 vista - they either both work or both fail at the same times.
• Only the Production version will fail. When the production version fails, he can still get the alpha version just fine. (Note that the Alpha version is hosted at our development office and has a limited download speed of about 60k)
• When he cannot get the production version, other peopleCAN get the production version (they are not on his network obviously).

I've seen a few posts about timeouts on this forum, but no real answers. Anyone see anything like this or have suggestions for IIS settings that might have some positive affect??

Thanks!

David Bosley

IncWell Software

PLATFORM VERSION INFO
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)

SOURCES
Deployment url: http://www.incwellvdr.com/IncWellInstall/IncWell.Application
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Deployment Provider url: http://www.incwellvdr.com/IncWellInstall/IncWell.application
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Application url: http://www.incwellvdr.com/IncWellInstall/IncWell.exe.manifest
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET

IDENTITIES
Deployment Identity: IncWell.application, Version=1.0.0.1101, Culture=neutral, PublicKeyToken=8ce0b0fe255a85a0, processorArchitecture=msil
Application Identity: IncWell.exe, Version=1.0.0.1101, Culture=neutral, PublicKeyToken=8ce0b0fe255a85a0, 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://www.incwellvdr.com/IncWellInstall/IncWell.Application resulted in exception. Following failure messages were detected:
+ Downloading http://www.incwellvdr.com/IncWellInstall/GBWinClientCommon.dll.deploy did not succeed.
+ The operation has timed out.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [7/22/2008 11:06:45 PM] : Activation of http://www.incwellvdr.com/IncWellInstall/IncWell.Application has started.
* [7/22/2008 11:07:01 PM] : Processing of deployment manifest has successfully completed.
* [7/22/2008 11:07:01 PM] : Installation of the application has started.
* [7/22/2008 11:07:02 PM] : Processing of application manifest has successfully completed.
* [7/22/2008 11:07:06 PM] : Request of trust and detection of platform is complete.

ERROR DETAILS
Following errors were detected during this operation.
* [7/22/2008 11:12:16 PM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://www.incwellvdr.com/IncWellInstall/GBWinClientCommon.dll.deploy did not succeed.
- 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.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)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.Net.WebException
- The operation has timed out.
- Source: System
- Stack trace:
at System.Net.ConnectStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

You need to talk to your network guys and have them run a sniffer and see what the problem is. This is not a ClickOnce problem per se.

One thing you CAN get them to do it make sure the MIME types are set up correctly on the server for the ClickOnce deployment. Maybe it's not inherently serving it as the right kind of data or something.

These are the MIME types you need in order to host a ClickOnce application:

.application --> application/x-ms-application
.manifest --> application/x-ms-application
.deploy --> application/octet stream

If you are deploying .Net 3.5 as a prerequisite, you need these as well:

.msp --> application/microsoftpatch
.msu --> application/microsoftupdate

If you have vsto apps, you need this one:

.vsto --> application/x-ms-vsto

RobinDotNet