dotnet distributed apps:
Perhaps you upgraded the BITS downloader. I know there was an updated UAB
posted for BITS 2.0. This link might get you there:
http://www.gotdotnet.com/workspaces/releases/viewuploads.aspx?id=83c68646-befb-4586-ba9f-fdf1301902f5 If not, go to
http://www.gotdotnet.com and check out the workspace on the
UAB there.
Thanks,
Sam
--
_______________________________
Sam Santiago
ssantiago@n0spam-SoftiTechture.com
http://www.SoftiTechture.com _______________________________
[quoted text, click to view] "Postman" <kfkenneth2001@yahoo.com.hk> wrote in message
news:O5SkhHgtEHA.4040@tk2msftngp13.phx.gbl...
> I have used UAB in my application which run smooth in win2000. After a
> little change to my app and moved to a newly installed WinXP Prof SP2 PC,
I
> got the following error in log file while trying to download from a URL.
I
> have successfully done the update using the same URL before.
>
> [DownloaderManager.BeginFileDownloads] :
> Status updated with job id '7bf22c9b-6889-40d4-a31f-ef9615264e0d' for
> the application 'myApp'.
>
> [BITSDownloader] :
> The BITS service returned an error for the job with the ID
> '7bf22c9b-6889-40d4-a31f-ef9615264e0d';
> the job's name and description are 'BITS_Files_Download_Job' and
> 'BITS_Files_Download_Job'.
> The BITS service error message for this job is
> 'An unexpected condition prevented the server from fulfilling the
request.
> '.
> This job has been canceled, and the DownloaderManager will attempt it
> again. If you see this error frequently, you may have a
mis-configuration,
> or another
> administrator process/user is canceling BITS jobs.
> It is also possible that some mis-configuration of the Manifest file is
> causing BITS to have trouble with a source or destination path;
> be sure that all SOURCE paths are valid URLs, and that all DESTINATION
> paths are valid LOCAL UNC paths--__shares are not allowed__.
>
>
> The Manifect is downloaded and the folders are established. Error come
when
> file download start.
> The same config(only the URL change to localhost) and update success if I
> changed to localhost with IIS installed in the WinXP PC. I therefore
doubt
> the whetheir the problem is caused by WinXP SP2 security, however the
> problem still exist even I turn off WinXP firewall.
> Any expert prease help.
> Thanks,
>
> Kennon
>
>