We have a hard time getting the AX 2009 debugger to work when breakpoints are set in code executing in Batch Jobs. Microsoft has described this in several documents without any special requirements, but we are unable to get the debugger to work as expected. All settings are correct in the server configuration and in the client when the breakpoint is defined. We have also tried to use the keywork breakpoint in the code without any difference. It seems like the debugger has a hard time attaching to the process. We have tried this in several environments and solutions, and in different combinations, and basically we are stucked.
The fundamental changes in the Batch Framework requires more debugging than ever due to the increased complexity inherited from the changes around impersonation (RunAs) and the prmiary tool in this situation is in fact the debugger.
We have also checked with several other sources and they have done the same experience.
All experience around this issue is highly welcome.
Update 2009/04/03:
Microsoft has confirmed that they have received a problem report (4652) for this issue, but no solution or fix is available yet. The problem was reported in January 2009.
Subscribe to:
Post Comments (Atom)
Posts
3 comments:
Basically, as far I understand, the debugging experience is almost as straightforward as for the regular code.
You debug until the call where RunAs is used, comment that line and replace it with a normal call of the same method.
The debugger will be able to go inside now, with the same logic being performed.
In theory this is the approach, but our experience have shown that the debugger don't get an entry when the execution hits a breakpoint and hence the debugger never kicks in. MS has also confirmed that they have a bug report on this with with the similar diagnose (according to a reply from MS in Partner Private Newsgoup). I'll keep this post updated when new information is avaialble.
Bug report from MS:
The debugging of (Server) Batch Jobs does not work in AX 2009 SP1 running on Windows 2008 Server - neither as regulare user nor local admin.
The Batch job is executing to the end without stopping execution on the breakpoint.
Also observed when running on W2K03 Server
Post a Comment