PowerShell script exchange
Post Reply
Posts: 8
Liked: 1 time
Joined: Mar 04, 2010 12:24 pm
Full Name: Per Alling-Dam
Location: Denmark

Powershell commands not working after upgrade

Post by pallingd »

Hi All

After upgrading from ver. 4 to ver. 5 my scripts are not working at all. Even the get-vbrcommand throws an error at me:

'get-vbrcommand' is not recognized

Other commands like start-vbrjob seem to work, but apparently the syntax has changed, because a simple job like this one fails (e2k7 is the job name in the GUI)

PS C:\> start-vbrjob e2k7
Start-VBRJob : Cannot bind parameter 'Job'. Cannot convert the "e2k7" value of type "System.String" to type "Veeam.Back
At line:1 char:13
+ start-vbrjob <<<< e2k7
+ CategoryInfo : InvalidArgument: (:) [Start-VBRJob], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Veeam.Backup.PowerShell.Command.StartVBRJob

This happens even for a new job created in ver. 5.

What did I miss?

Vitaliy S.
Product Manager
Posts: 25811
Liked: 2398 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Powershell commands not working after upgrade

Post by Vitaliy S. »

Hello Per,

The PowerShell syntax has changed in v5. Please take a look at this topic for more info: Powershell script in v5

Hope it helps!

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests