Azure-Automation-Exception: Cannot bind parameter 'ScriptBlock'

Question

I'm writing a runbook/workflow like below according to this blog:

workflow Do-RemoteInlineScript
{
    $uri = ...
    $credential = ...

    $result = InlineScript
    {
        <commands>   
    } -PSConnectionUri $uri -PSCredential $credential
}

When I run it, I will get the exception Cannot bind parameter 'ScriptBlock'.

Where do I err?

Note: My problem seems to be related to this msdn-post.

participant · Accepted Answer · 2015-01-15 08:19:37Z

1

Azure Automation currently has a bug where InlineScript cannot target a remote system, as you are trying to do above. The workaround is to put an Invoke-Command in the InlineScript and have this cmdlet target the remote system:

$PSCommandResult = InlineScript {         
    Invoke-Command -ConnectionUri $Using:Uri -Credential $Using:Credential -ScriptBlock { 
        <commands>
    }
}

See the Invoke-Command sample-runbook for more details.

edited Jan 15, 2015 at 8:19

participant

3,0132 gold badges26 silver badges40 bronze badges

answered Jan 14, 2015 at 18:03

Joe

2,5401 gold badge15 silver badges12 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

participant Over a year ago

I am aware of this workaround. Do you have a reference for the bug?

Joe Over a year ago

Just the link you already mentioned: social.msdn.microsoft.com/Forums/sqlserver/en-US/…. I am a member of the Azure Automation team though, so I can tell you it is a bug, and not intended behavior.

Collectives™ on Stack Overflow

Azure-Automation-Exception: Cannot bind parameter 'ScriptBlock'

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related