Microsoft Dynamics AX (Archived)

TFS Build - Time out error in "AxBuild Compile Log Compile" step

(0) Share

Report

Posted on by Anitha Eswaran

312

Hi,

I am using VS 2013 and created a new Build definition (with the standard template defined in XAML file )

There are no build errors and the build creates a new model file/XPOs are exported/Logs have been created in Binaries folder.

But when it reaches the step "AxBuild Compile Log Compile" , I face an issue due to time out error. Tried setting from 60 mts to 600 minutes. But still the same error.

The build was successful when I queued it without this step.

User account which was registered in build controller has full rights to the machine, (I am not sure if this is issue related to permission)

I am using AX2012 R3 and customizations are done in VAR layer.

Any help is highly appreciated

Regards,

Anitha.E

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (0)

Iulian Cordobin 8,201 on at

Like (0)

Report

I am not sure what template you used in order to create a build definition for AX. Are you sure it's the standard template XAML file you are using?

Was this reply helpful? Yes No
Anitha Eswaran 312 on at

Like (0)

Report

Yes lulian. I am sure that is the standard template.

I am facing error only in this step. When this is commented, build is success.

Was this reply helpful? Yes No
Martin Dráb 237,965 Most Valuable Professional on at

Like (0)

Report

There is no standard XAML build template for AX 2012, AFAIK. Do you mean CodeCrib AX TFS Build.xaml from dynamicsaxadmin.codeplex.com?

Was this reply helpful? Yes No
Martin Dráb 237,965 Most Valuable Professional on at

Like (0)

Report

What if you run the same command interactively, logged in as the build service?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Log in to the server with the build controller user account and open up Dynamics AX. If you get a dialog showing if you want to participate in the Microsoft evaluate program you have to click no.

The build process will open Dynamics AX and if you haven´t clicked no on the evaluation dialog the build process can´t continue, because the process don´t know how to handle the dialog.

After that close Dynamics AX, log out of the server and try the build process again.

Was this reply helpful? Yes No
Martin Dráb 237,965 Most Valuable Professional on at

Like (0)

Report

AxBuild doesn't use AX client, so it shouldn't be the case.

Was this reply helpful? Yes No
Suggested answer

Iulian Cordobin 8,201 on at

Like (0)

Report

It looks though like it's trying to start the AX client from the commands it's passing? (looking closer at the screenshot included). And, just realized that if this is the case, then the normal compile process takes around 150 minutes on an average server so, this can be the answer (also, your change to 600 minutes either was not saved or this is another screenshot, because you still show the 60 minutes timeout).

However, it looks like the build template is using a custom library AvAxBuild ..... this means not a standard XAML template that came with TFS 2013 build services.

Was this reply helpful? Yes No
Martin Dráb 237,965 Most Valuable Professional on at

Like (0)

Report

Aha, you're right. So it's not an AxBuild compilation at all, it just calls an AX startup command.

Was this reply helpful? Yes No
Anitha Eswaran 312 on at

Like (0)

Report

Yes. It is one of the steps in TFS build.

I found the issue. The command prompt doesnt accept spaces in between.

For e.g., ax32.exe F:\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\

When I tried to execute from command prompt, i got an error message invalid parameter "F:\Program ".

Any idea how to handle spaces in command prompt.

Was this reply helpful? Yes No
Iulian Cordobin 8,201 on at

Like (0)

Report

You just need to include the path in double quotes.

Was this reply helpful? Yes No