Start-BitsTransfer - Submitting >60 asynchronous jobs generates error - by Jonathan Medd

Status : 

 


7
0
Sign in
to vote
ID 785266 Comments
Status Active Workarounds
Type Bug Repros 1
Opened 4/22/2013 3:18:17 AM
Access Restriction Public

Description

PowerShell V3 on Windows 8

I'm using Start-BitsTransfer with the asynchronous switch to kick off the download of multiple files. 

This works fine until I hit what seems to be a limit of 60 jobs, after which further submissions receive the below


Start-BitsTransfer : Object reference not set to an instance of an object.
At line:1 char:1
+ Start-BitsTransfer -Source "http://intranet.server01.local/downlo ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Start-BitsTransfer], NullReferenceException
    + FullyQualifiedErrorId : System.NullReferenceException,Microsoft.BackgroundIntelligentTransfer.Management.NewBitsTransferCommand


If I complete or remove any of the existing jobs I can then carry on until hitting the limit of 60 again.
Sign in to post a comment.
Posted by k.takai on 5/19/2015 at 1:46 AM
Hi DMeier_Nera,

As far as I can see, It's specification of BITS.

> BITS limits the number of jobs in the queue to 300 jobs and the number of jobs that a user can create to 60 job.
> These limits do not apply to administrators or services.
> To change these default limits, see Group Policies.
>
> Prior to Windows Vista: There are no limits to the number of jobs in the queue or the number of jobs that a user can create.

Please refer to the following,
https://msdn.microsoft.com/en-us/library/aa362834(v=vs.85).aspx

Regards,
Posted by k.takai on 5/19/2015 at 1:32 AM
## I'm not a Microsoft employee.

I can see this behavior happen if powershell is not running with administrator's privilege.
If I execute powershell with "run as administrator", the error does not occur.
Posted by DMeier_Nera on 2/25/2015 at 7:35 AM
Sorry, I meant nearly 2 years...
Posted by DMeier_Nera on 2/25/2015 at 7:34 AM
Really MS guys, nearly a year and no comment on this problem which is definitely being a bug?
Nice....