|
|
Follow up....
I have now resolved the problem and thought I would share my experiences.
I discovered that we were not using the latest BITSAdmin tool supplied as
part of SP2 toolkit and also I didn't appreciate that you needed to use the
/allusers switch under the /list command to see jobs for other users, such
as the local system account. So I did command 'bitsadmin /list /allusers
/verbose' and this listed all the jobs that were currently running.
Secondly I also discovered that our site puts all http traffic through the
proxy server even if an internal web server. With the old bitsadmin tool
there was no way to set the proxy settings for the local service account.
With the new one I did the command 'bitsadmin /util /setieproxy autoscript
'http.....' localservice'.
Both problems fixed.
"Statto" <wardpd@xxxxxxxxxxxx> wrote in message
news:ebIEP20JFHA.3156@xxxxxxxxxxxxxxxxxxxxxxx
> We want to use BITS to download files within an ASP.NET application with
> the transfer being triggered from the VB.NET code behind. We have
> produced a .NET wrapper using the bits idl version 1.5.
>
> Because BITS can only download jobs for the signed on user, we have a
> problem initiating the job creation through the ASP.NET application. We
> get an error stating that jobs can only be created for the signed on user.
> We have tracked this down to the fact that ASP.NET uses the ASPNET user
> account to run the application which is obviously different to the user
> that signed on to the workstation.
>
> To get around this, we have written a VB.NET windows service to do the
> BITS download. This will run under the local system account and be called
> by the VB.NET code behind. The problem is that the service runs and
> creates a 0Kb temp file in the download directory, but no jobs are listed
> in bitsadmin. Nothing seems to happen.
>
> When I change the windows service signon to my specific XP user account,
> which has full network access and is also the account I originally signed
> on to the workstation with, and run the service, the job creation,
> addition of files and resume works successfully. I suspect that the local
> system account does not have the network credentials necessary. Running
> as a network service (NT AUTHORITY\NetworkService) does not seem to make
> any difference.
>
> Does anybody have any ideas?
>
|
|