Using OneBox as Build-Machine no longer works with 10.0.17 ?

(0) Share

Report

Posted on by JeDe

Hi,

up to version 10.0.15 we've used OnBox-Environments successfully as build-machine with an agent connected to DevOps.

Since 10.0.17 we don't get it working. We always get the following error:

System.Management.Automation.RuntimeException: No AOS website name specified and no existing value found in registry

at: HKLM:\SOFTWARE\Microsoft\Dynamics\AX\7.0\SDK

##[error]Write-Message : 11:26:37 PM: Error preparing build environment: No AOS website name specified and no existing value

found in registry at: HKLM:\SOFTWARE\Microsoft\Dynamics\AX\7.0\SDK

At C:\DynamicsSDK\PrepareForBuild.ps1:724 char:5

+ Write-Message "Error preparing build environment: $($_)" -Error

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException

+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-Message

VERBOSE: Importing function 'Get-AX7SdkDeploymentBinariesPath'.

We now use a build-machine in Azure and that works like a charm but we want to switch back to our "onprem"-build-machine.

Does someone know this error and has some advice for us?

I have the same question (0)

All responses (11)

Answers (1)

WillWU 22,363 on at

Like (0)

Report

Hi JeDe,

Please go to HKLM\Software\Microsoft\Dynamics\AX\7.0\SDK to check the configuration. Could you provide the screenshot of the registry.

Was this reply helpful? Yes No
JeDe 25 on at

Like (0)

Report

This is the config in HKLM\Software\Microsoft\Dynamics\AX\7.0\SDK

Was this reply helpful? Yes No
JeDe 25 on at

Like (0)

Report

On the Azure-machine, the configuration is the following. So where does those keys/values come from? We configured for instance the TeamVoundation-Adress with the agent and the agent also connects and runs, but the agents configuration may be located somewhere else.

Maybe here is now with 10.0.17 some additional step required?

Was this reply helpful? Yes No
Suggested answer

Joris dG 17,775 on at

Like (0)

Report

Can you elaborate a bit? Your last post mentioned "Azure machine" so is your original issue on a downlaoded VHD? If so did it work previously and an update broke it, or you got the new 17 VM and out of the box it's missing these?

Was this reply helpful? Yes No
JeDe 25 on at

Like (0)

Report

Currently I have 3 Machines.

1. VHD VM updated from 10.0.15 (this was working as build machine) to 10.0.17 (this was broken after the update)

2. VHD VM newest version 10.0.17 (this isn't working as build machine)

3. Azure build machine 10.0.17 (this is working perfectly)

I've created the machine 1) and 2) multiple times because I thought that I have broken something in it. But even a clean vhd with only the agent installed failed.

Maybe with 10.0.17 there is an additional step needed within the VHD.

Currently my process is:

a) create a VM from vhd 10.0.17

b) install the build agent from DevOps Pipeline

c) trigger build from Pipeline

After that, the build starts and fails in step "prepare for build":

Was this reply helpful? Yes No
Verified answer

Joris dG 17,775 on at

Like (2)

Report

Do you install the build agent manually, or do you use the powershell script from the DynamicsSDK folder? That may be the difference.

Was this reply helpful? Yes No
Suggested answer

JeDe 25 on at

Like (0)

Report

Yes, this is the difference. Until 10.0.15 it was ok to install the agent by just downloading it from devops and installing it by running the config script.

After 10.0.15 this doesn't work anymore. The correct way is, to use the SDK script.

Thank you very much. You nailed it :)

Was this reply helpful? Yes No
Gokul.S 2 on at

Like (0)

Report

Hi JeDe

Could you pls eloborate what was the issue and what you did to solve?

and where is that SDK Script available then have you deleted the agent you first manually deployed?

Was this reply helpful? Yes No
JeDe 25 on at

Like (0)

Report

I had to use C:\DynamicsSDK\SetupBuildAgent.ps1 That's all. I've started with a new OneBox, so I don't know if this would have had messed with the old agent.

Was this reply helpful? Yes No
Gokul.S 2 on at

Like (0)

Report

Thanks for your quick response, I was able to delete the current agent but while reconfiguring new agent with SDK script, it is asking for some parameters could you pls help me with that.

I was new to this devops project I'm not sure where we need to take these values,

Was this reply helpful? Yes No