J
jlainc
I have a smart client app that has been working without a hitch for
weeks. This application requires interaction with some specific
hardware devices, which requires specific driver versions, so I decided
to try and embed the driver install files inside my application for easy
field installation. That is when my problems started...
First I tried to include the raw driver .exe files in the application,
which worked fine when I tested locally, but when I published to the web
server (Win 2003 SE SP-2) the application deploy failed on the .exe
files. I tried to find the problem, but just chalked it up to some
unknown security issues and decided to go the old file extension
renaming route, which worked fine (in the beginning...).
I named the driver files with a .txt extension and they deployed fine,
then I renamed the extensions in my application and installed the
drivers on the client without a hitch!
Then I ran into a problem with the driver utility for the Logitech
QuickCam, where the deploy would hang up on one of the required .dll
files. So I went through the same routine with renaming these files as
well, and eventually ran into a problem with the file path lengths on
some of them. So, I decided to try creating a ZIP file that would be
deployed as part of the project and then unzipped on the client. The
deploy then started hanging on the ZIP file!
At this point I already knew the renaming process was working, so I
decided to rename the ZIP file as well. All works fine on my local
machine, but when attempting to deploy from the web server, I have had
nothing but problems. This seems to be sporatic in nature as sometimes
when I completely clean off both the server and the client machine from
all previous versions of the app it works, but lately most deploys just
fail.
Now the deploy has started hanging on the .txt files that I
programmatically rename... See full error below:
*************************************************************
PLATFORM VERSION INFO
Windows : 6.0.6001.65536 (Win32NT)
Common Language Runtime : 2.0.50727.3074
System.Deployment.dll : 2.0.50727.3053 (netfxsp.050727-3000)
mscorwks.dll : 2.0.50727.3074 (QFE.050727-3000)
dfdll.dll : 2.0.50727.3053 (netfxsp.050727-3000)
dfshim.dll : 2.0.50727.3053 (netfxsp.050727-3000)
SOURCES
Deployment url : http://quickaccess2.alacop.gov/
Server : Microsoft-IIS/6.0
X-Powered-By : ASP.NET
Application url :
http://quickaccess2.alacop.gov/Application...ss.exe.manifest
Server : Microsoft-IIS/6.0
X-Powered-By : ASP.NET
IDENTITIES
Deployment Identity : WinQuickAccess.application, Version=1.0.0.103,
Culture=neutral, PublicKeyToken=99d1cd394fcabffe,
processorArchitecture=msil
Application Identity : WinQuickAccess.exe, Version=1.0.0.103,
Culture=neutral, PublicKeyToken=99d1cd394fcabffe,
processorArchitecture=msil, type=win32
APPLICATION SUMMARY
* Online only application.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed
later in the log.
* Activation of http://quickaccess2.alacop.gov/ resulted in exception.
Following failure messages were detected:
+ *Downloading *'*http://quickaccess2.alacop.gov/Application*'
(http://quickaccess2.alacop.gov/Application)*
Files/WinQuickAccess_1_0_0_103/Drivers/ESEEKMod250/EXE/CDM
2.04.16.txt.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/6/2009 4:43:41 PM] : Activation of
http://quickaccess2.alacop.gov/ has started.
* [7/6/2009 4:43:42 PM] : Processing of deployment manifest has
successfully completed.
* [7/6/2009 4:43:42 PM] : Installation of the application has started.
* [7/6/2009 4:43:42 PM] : Processing of application manifest has
successfully completed.
* [7/6/2009 4:43:44 PM] : Request of trust and detection of platform
is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [7/6/2009 4:48:48 PM]
System.Deployment.Application.DeploymentDownloadException (Unknown
subtype)
- Downloading http://quickaccess2.alacop.gov/Application
Files/WinQuickAccess_1_0_0_103/Drivers/ESEEKMod250/EXE/CDM
2.04.16.txt.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, String textualSubId, String
deploymentProviderUrlFromExtension, BrowserSettings browserSettings,
String& errorPageUrl)
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.
****************************************************
I have read several posts on the internet relating to this issue, but
so far none of the "fixes" have worked for my situation. I have checked
the following:
1 - Bandwidth: We are on a 10gb network, and the target web server is
here - Not a download speed issue...
2 - Firewall: I have turned off the firewall and virus protection on
the client PC
3 - TCP tuning: I have disabled this on the local PC
The suspect files are usually 2mb-in size or larger, but I am able to
directly download the files outside of the deploy package via my browser
in less than 5 seconds each! This has been tested on XP and Vista
clients, and my success rate is deminishing rapidly, as is my
patience...
Please Help,
Larry
--
jlainc
weeks. This application requires interaction with some specific
hardware devices, which requires specific driver versions, so I decided
to try and embed the driver install files inside my application for easy
field installation. That is when my problems started...
First I tried to include the raw driver .exe files in the application,
which worked fine when I tested locally, but when I published to the web
server (Win 2003 SE SP-2) the application deploy failed on the .exe
files. I tried to find the problem, but just chalked it up to some
unknown security issues and decided to go the old file extension
renaming route, which worked fine (in the beginning...).
I named the driver files with a .txt extension and they deployed fine,
then I renamed the extensions in my application and installed the
drivers on the client without a hitch!
Then I ran into a problem with the driver utility for the Logitech
QuickCam, where the deploy would hang up on one of the required .dll
files. So I went through the same routine with renaming these files as
well, and eventually ran into a problem with the file path lengths on
some of them. So, I decided to try creating a ZIP file that would be
deployed as part of the project and then unzipped on the client. The
deploy then started hanging on the ZIP file!
At this point I already knew the renaming process was working, so I
decided to rename the ZIP file as well. All works fine on my local
machine, but when attempting to deploy from the web server, I have had
nothing but problems. This seems to be sporatic in nature as sometimes
when I completely clean off both the server and the client machine from
all previous versions of the app it works, but lately most deploys just
fail.
Now the deploy has started hanging on the .txt files that I
programmatically rename... See full error below:
*************************************************************
PLATFORM VERSION INFO
Windows : 6.0.6001.65536 (Win32NT)
Common Language Runtime : 2.0.50727.3074
System.Deployment.dll : 2.0.50727.3053 (netfxsp.050727-3000)
mscorwks.dll : 2.0.50727.3074 (QFE.050727-3000)
dfdll.dll : 2.0.50727.3053 (netfxsp.050727-3000)
dfshim.dll : 2.0.50727.3053 (netfxsp.050727-3000)
SOURCES
Deployment url : http://quickaccess2.alacop.gov/
Server : Microsoft-IIS/6.0
X-Powered-By : ASP.NET
Application url :
http://quickaccess2.alacop.gov/Application...ss.exe.manifest
Server : Microsoft-IIS/6.0
X-Powered-By : ASP.NET
IDENTITIES
Deployment Identity : WinQuickAccess.application, Version=1.0.0.103,
Culture=neutral, PublicKeyToken=99d1cd394fcabffe,
processorArchitecture=msil
Application Identity : WinQuickAccess.exe, Version=1.0.0.103,
Culture=neutral, PublicKeyToken=99d1cd394fcabffe,
processorArchitecture=msil, type=win32
APPLICATION SUMMARY
* Online only application.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed
later in the log.
* Activation of http://quickaccess2.alacop.gov/ resulted in exception.
Following failure messages were detected:
+ *Downloading *'*http://quickaccess2.alacop.gov/Application*'
(http://quickaccess2.alacop.gov/Application)*
Files/WinQuickAccess_1_0_0_103/Drivers/ESEEKMod250/EXE/CDM
2.04.16.txt.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/6/2009 4:43:41 PM] : Activation of
http://quickaccess2.alacop.gov/ has started.
* [7/6/2009 4:43:42 PM] : Processing of deployment manifest has
successfully completed.
* [7/6/2009 4:43:42 PM] : Installation of the application has started.
* [7/6/2009 4:43:42 PM] : Processing of application manifest has
successfully completed.
* [7/6/2009 4:43:44 PM] : Request of trust and detection of platform
is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [7/6/2009 4:48:48 PM]
System.Deployment.Application.DeploymentDownloadException (Unknown
subtype)
- Downloading http://quickaccess2.alacop.gov/Application
Files/WinQuickAccess_1_0_0_103/Drivers/ESEEKMod250/EXE/CDM
2.04.16.txt.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, String textualSubId, String
deploymentProviderUrlFromExtension, BrowserSettings browserSettings,
String& errorPageUrl)
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.
****************************************************
I have read several posts on the internet relating to this issue, but
so far none of the "fixes" have worked for my situation. I have checked
the following:
1 - Bandwidth: We are on a 10gb network, and the target web server is
here - Not a download speed issue...
2 - Firewall: I have turned off the firewall and virus protection on
the client PC
3 - TCP tuning: I have disabled this on the local PC
The suspect files are usually 2mb-in size or larger, but I am able to
directly download the files outside of the deploy package via my browser
in less than 5 seconds each! This has been tested on XP and Vista
clients, and my success rate is deminishing rapidly, as is my
patience...
Please Help,
Larry
--
jlainc