Home Dashboard Directory Help
Search

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


Status: 

Active


5
0
Sign in
to vote
Type: Bug
ID: 785266
Opened: 4/22/2013 3:18:17 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

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.
Details
Sign in to post a comment.
Sign in to post a workaround.