Glad to see it's working; but just as an FYI, the installer does not have any code that can delete the database. That's only in the uninstaller program, and that needs to be manually run with double-confirmation (in the UI).

I've deleted FTP extension and restarted both BM services. After restart it works properly. Thank you.

There must be some confusion here (and that is understandable since it's a legacy feature that I am in the process of reworking to support the "provider-less" model). An SCM Trigger cannot create a release, only a release package. If there are no releases (or the specific selected release doesn't exist) nothing will happen. Can you share the example pipeline, and the plan associated with its first stage's target?

Are you sure you're using the right server context when calling the BuildMaster Powershell Asset? If you print out the server name in your asset using $env:computername do you get back the expected server? If I create a simple plan ##AH:UseTextMode for server $MyServer { PSCall GLOBAL::Test_Powershell_Asset; } Where my powershell asset is defined as this one-liner Invoke-Expression C:\Path\To\PowerShell\script.ps1 Then I am able to run this script, no problem.

Your template can look like this: template MakePair<$First, $Second, out @Pair> { set @Pair = @($First, $Second); } And the plan that uses the template can look like this: set @Fruits = @(); call MakePair { First: Apple, Second: Orange, Pair => @Fruits }