web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Batch server Vs Debugg...
Microsoft Dynamics AX (Archived)

Batch server Vs Debugging X++ code running on Server

(0) ShareShare
ReportReport
Posted on by Lakshmi Karambakkam 1,307

Hi,

We have an AOS server and Batch server separately. This is a development and testing environment. Our batch server is working only when Enable breakpoints to debug x++ running on server is  turned OFF. Enabling this parameter will make AOS restart.

VSDTESTAOS1_5F00_ServerConfig.png

to debug x++ code running on server, I have to turn this ON. for that, I had to stop my colleagues working, save their stuff and enable the parameter which in turn restarts AOS and then i have to do my debugging.

I believe there should be a easier way of handling this?

Lakshmi

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    Martin Dráb 237,880 Most Valuable Professional on at

    If it's a development environment, why don't you keep debugging enabled. Also note that having two AOS servers in a development environment is very unusual, because it complicates deployment and it's not needed from performance perspective.

    And having a single environment for both development and testing usually doesn't make a good sense. Development in progress could prevent testers from testing, you already complain about not being able to debug, you wouldn't test deployment and so on.

  • Suggested answer
    Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at

    Enabling the flag does require restart indeed.

    If the restart is not initiated by you, then it might be a crash. We have noticed that sometimes leftover breakpoints could cause AOS process crash in certain places, thus our way of avoiding this is the following:

    - Enable the flag, do not restart AOS instance.

    - Stop AX AOS service manually

    - Truncate the SysBreakpoints and SysBreakpointList table in SQL Server

    - Start the AX AOS service

    Alternatively when you want to switch back to non-debugging mode, you could clear the breakpoints list at that time.

    Other than the above it implies that you do not have version control in place, so I strongly agree with Martin that you need to have separate developer instances (with proper version control enabled), and also a build/release process of placing code on your Test environment. That way debugging the functionality currently being tested should not interfere with other developers' work.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans