Exception setting "RunspacePool" in 1.6.0.0 build

[replicaJunction]

In the latest build, Start-RsJob gives me the following error each time it runs except for the first time:

Exception setting "RunspacePool": "Object reference not set to an instance of an object."
At E:\MyProject\Modules\PoshRsJob\Public\Start-RSJob.ps1:463 char:17
+                 $PowerShell.RunspacePool = $RunspacePool
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], SetValueInvocationException
    + FullyQualifiedErrorId : ExceptionWhenSetting

I can't share the production code causing this, but here is a sample case that causes the same error:

[CmdletBinding()]
param()

# Not relevant to this sample, just illustrating that I'm using these params
$Throttle = 5
$modules = 'PSSqlite'

foreach ($i in 1..100) {
    Start-RsJob -Batch 'MyProject' -ModulesToImport $modules -Throttle $Throttle -Verbose:$VerbosePreference -Debug:$DebugPreference -ScriptBlock {
        [PSCustomObject] @{
            One = 1
            Two = 2
            Value = $using:i
        }
    }
}

Wait-RsJob -ShowProgress | Receive-RsJob | Write-Output
Get-RsJob | Remove-RsJob

Each run after the first causes the same exception.

I'm on Server 2008R2, PowerShell 4.0. This project works fine on the previous release of the module (1.5.7.7). Let me know if I can do any additional troubleshooting to assist!

[proxb]

Thanks for the heads up! I'm going to dig in and see where this is failing at. Just curious, is this running in a script or function or is this failing when you run this 'as is' such as in the ISE?

[proxb]

I'm in the process of building a VM to mirror the OS and PowerShell version so I can test it properly

[proxb]

Ok, it looks like the runspacepool work that I did is causing the issue. I'm going to dig into this and figure out a good fix.

[proxb]

I found the issue and am working on publishing an update to the module.

[proxb]

@replicaJunction Try the latest version and let me know how it works.

[replicaJunction]

Apologies for the delayed response - I didn't see your question until just now. It was failing when run as a standalone .ps1 file, but I guess that's not relevant since you found the issue.

The latest build runs with no problems. Thanks very much!