Outstanding, thanks Alex

There's just the two connection strings (web and service)... you shouldn't be getting timeouts, however. It might be network related?

Hello Clint, This SQL will copy any credentials that BuildMaster has but Otter doesn't to Otter. However, it will not work if BuildMaster and Otter use different encryption keys. You can find the encryption keys for BuildMaster and Otter in app_appSettings.config and in web_appSettings.config. The key will look like this in the file: <add key="Persistence.EncryptionKey" value="[encryption key is here]" /> INSERT INTO [Otter].[dbo].[Credentials] ([Environment_Id], [Credential_Name], [CredentialType_Name], [LegacyConfiguration_Bytes], [Configuration_Xml], [AllowFunctionAccess_Indicator]) -- Omit the line above this comment to test this before running it for real SELECT OE.[Environment_Id] ,BC.[Credential_Name] ,BC.[CredentialType_Name] ,[LegacyConfiguration_Bytes] = NULL ,[Configuration_Xml] = CAST(REPLACE( REPLACE( REPLACE( REPLACE( REPLACE( REPLACE( REPLACE( REPLACE( REPLACE( REPLACE( CAST(BC.[Configuration_Xml] AS VARCHAR(MAX)), '<Inedo.BuildMaster.Extensibility.Credentials.BuildMasterCredentials Assembly="BuildMasterCore">', '<Inedo.Otter.Extensions.Credentials.BuildMasterCredentials Assembly="OtterCore">' ), '<Inedo.BuildMaster.Extensibility.Credentials.OtterCredentials Assembly="BuildMasterCore">', '<Inedo.Otter.Extensions.Credentials.OtterCredentials Assembly="OtterCore">' ), '<Inedo.BuildMaster.Extensibility.Credentials.ProGetCredentials Assembly="BuildMasterCore">', '<Inedo.Otter.Extensions.Credentials.ProGetCredentials Assembly="OtterCore">' ), '<Inedo.BuildMaster.Extensibility.Credentials.PrivateKeyCredentials Assembly="BuildMasterCore">', '<Inedo.Otter.Extensions.Credentials.PrivateKeyCredentials Assembly="OtterCore">' ), '<Inedo.BuildMaster.Extensibility.Credentials.UsernamePasswordCredentials Assembly="BuildMasterCore">', '<Inedo.Otter.Extensions.Credentials.UsernamePasswordCredentials Assembly="OtterCore">' ), '</Inedo.BuildMaster.Extensibility.Credentials.BuildMasterCredentials>', '</Inedo.Otter.Extensions.Credentials.BuildMasterCredentials>' ), '</Inedo.BuildMaster.Extensibility.Credentials.OtterCredentials>', '</Inedo.Otter.Extensions.Credentials.OtterCredentials>' ), '</Inedo.BuildMaster.Extensibility.Credentials.ProGetCredentials>', '</Inedo.Otter.Extensions.Credentials.ProGetCredentials>' ), '</Inedo.BuildMaster.Extensibility.Credentials.PrivateKeyCredentials>', '</Inedo.Otter.Extensions.Credentials.PrivateKeyCredentials>' ), '</Inedo.BuildMaster.Extensibility.Credentials.UsernamePasswordCredentials>', '</Inedo.Otter.Extensions.Credentials.UsernamePasswordCredentials>' ) AS XML) ,BC.[AllowFunctionAccess_Indicator] FROM [BuildMaster].[dbo].[Credentials] BC LEFT OUTER JOIN [Otter].[dbo].[Credentials] OC ON BC.[Credential_Name] = OC.[Credential_Name] LEFT OUTER JOIN [BuildMaster].[dbo].[Environments] BE ON BC.[Environment_Id] = BE.[Environment_Id] LEFT OUTER JOIN [Otter].[dbo].[Environments] OE ON BE.[Environment_Name] = OE.[Environment_Name] WHERE OC.[Credential_Id] IS NULL

Basically, the template doesn't represent valid OtterScript, and that's why there is an error. Basically, this is not a valid OtterScript statement: $Increment(${index}, 1); You can, however, do this: set ${index} = $Increment(${index}, 1); Except, the "set" statement is not supported in a text template, which means you cannot do what you're doing. You could probably work something out with $foreach $i in @Range(...), but it could get a little messy.

Thanks Alana, [EDO-2856] has been raised. Thanks, Clint

There doesn't appear to be; but we have a new issue (BM-3034) for this. If it's easy to do, we'll get it in ASAP!

BuildMaster runs the PowerShell scripts in-process, so it's not possible. The method you've identified (running a separat eprocess) is the best way to accomplish it I think.

This was a regression in 5.5.2, but will be fixed in 5.5.3 (shipping later today) As a work-around, you can use text-mode to invoke PSCall

You are not going wrong :) Support for XSL as the template and data as the instance will be added in v5.3.4 as a separate template type so it doesn't break existing deployments. We'll release this within the next day or so.