|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
ClickOnce errorWhen I deploy ClickOnce to our corporate web server outside of our network I am getting an error that I have pasted at the bottom of this post. If I install this on my computer at home from the corporate web server I do not get an error. The only other variable I can think of is we have a proxy server, but the error message does not indicate that this is the problem. Please help. PLATFORM VERSION INFO Windows : 5.1.2600.131072 (Win32NT) Common Language Runtime : 2.0.50727.42 System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200) mscorwks.dll : 2.0.50727.42 (RTM.050727-4200) dfdll.dll : 2.0.50727.42 (RTM.050727-4200) dfshim.dll : 2.0.50727.42 (RTM.050727-4200) SOURCES Deployment url : http://www.REMOVEDFORSECURITYREASONS/bankwayupload/BatchUpload.application ERROR SUMMARY Below is a summary of the errors, details of these errors are listed later in the log. * Activation of http://www.REMOVEDFORSECURITYREASONS.com/bankwayupload/BatchUpload.application resulted in exception. Following failure messages were detected: + Downloading http://www.REMOVEDFORSECURITYREASONS.com/bankwayupload/BatchUpload.application did not succeed. + The underlying connection was closed: An unexpected error occurred on a receive. + Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. + An existing connection was forcibly closed by the remote host COMPONENT STORE TRANSACTION FAILURE SUMMARY No transaction error was detected. WARNINGS There were no warnings during this operation. OPERATION PROGRESS STATUS * [3/16/2006 8:51:55 AM] : Activation of http://www.REMOVEDFORSECURITYREASONS/bankwayupload/BatchUpload.application has started. ERROR DETAILS Following errors were detected during this operation. * [3/16/2006 8:52:17 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype) - Downloading http://www.REMOVEDFORSECURITYREASONS/bankwayupload/BatchUpload.application 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.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) --- Inner Exception --- System.Net.WebException - The underlying connection was closed: An unexpected error occurred on a receive. - Source: System - Stack trace: at System.Net.HttpWebRequest.GetResponse() at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next) --- Inner Exception --- System.IO.IOException - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. - Source: System - Stack trace: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead) --- Inner Exception --- System.Net.Sockets.SocketException - An existing connection was forcibly closed by the remote host - Source: System - Stack trace: at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) COMPONENT STORE TRANSACTION DETAILS No transaction information is available. Hi Bruce,
>The only other variable I can think of is we have a proxy server, In this regard, this problem may be caused by a known issue of Whidbey. It >but the error message does not indicate that this is the problem. is because that .Net deployment APIs do not use the default proxy and credentials to access the remote ClickOnce files. I suggest you set useDefaultCredentials to true as the followings in the machine.config to workaround this issue: <defaultProxy enabled="true" useDefaultCredentials="true"> This could get net classes to apply default domain credentials on the proxy automatically. Please refer to our corresponding MSDN bug link is for the detailed information: "Bug Details: click once fails with proxy authentication" http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=0 a5f94d6-592e-4a3b-9c35-879a1ecdba57 Thanks! Best regards, Gary Chang Microsoft Community Support ====================================================== PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00 AM PST, February 14, 2006. Please complete a re-registration process by entering the secure code mmpng06 when prompted. Once you have entered the secure code mmpng06, you will be able to update your profile and access the partner newsgroups. ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ====================================================== Thanks for the reply,
The work around will not work for us. This click once application is intended for our customers who have various network configurations, including the use of proxy servers. We could not ask our customers to modify thousands of client systems machine.config files or remove their proxy servers. This is a huge obstacle for wide acceptable of the click once technology. I hope Microsoft addresses this issue sooner than later. Thanks again for the prompt response. ""Gary Chang[MSFT]"" wrote: Show quote > Hi Bruce, > > >The only other variable I can think of is we have a proxy server, > >but the error message does not indicate that this is the problem. > > In this regard, this problem may be caused by a known issue of Whidbey. It > is because that .Net deployment APIs do not use the default proxy and > credentials to access the remote ClickOnce files. > > I suggest you set useDefaultCredentials to true as the followings in the > machine.config to workaround this issue: > <defaultProxy enabled="true" useDefaultCredentials="true"> > > This could get net classes to apply default domain credentials on the proxy > automatically. > > Please refer to our corresponding MSDN bug link is for the detailed > information: > > "Bug Details: click once fails with proxy authentication" > http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=0 > a5f94d6-592e-4a3b-9c35-879a1ecdba57 > > > Thanks! > > Best regards, > > Gary Chang > Microsoft Community Support > ====================================================== > PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00 > AM PST, February 14, 2006. Please complete a re-registration process by > entering the secure code mmpng06 when prompted. Once you have entered the > secure code mmpng06, you will be able to update your profile and access the > partner newsgroups. > ====================================================== > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from this issue. > ====================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. > ====================================================== > > Hi Bruce,
>This is a huge obstacle for wide acceptable of the click I apologize for any inconvenience this may cause you. This issue has >once technology. I hope Microsoft addresses this issue >sooner than later. already been logged into our database, the corresponding product team has already perform some work on it, the ClickOnce project may be improved in the next .NET Framework version. Thanks for your understanding! Best regards, Gary Chang Microsoft Community Support ====================================================== PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00 AM PST, February 14, 2006. Please complete a re-registration process by entering the secure code mmpng06 when prompted. Once you have entered the secure code mmpng06, you will be able to update your profile and access the partner newsgroups. ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ====================================================== |
|||||||||||||||||||||||