Skip to main content
Solved

Just In Time Debugger Launched without necessary security permissions


Forum|alt.badge.img

Hi,

I’m having an issue with a customisation.  Not sure if this is relevant, but this is the first customisation I have done in build 2022. All previous have been in 2021 builds and I haven’t seen this issue before:

 

I have a processing form. 

 

When I Update all, after approx. 4 seconds the dialog below pops up

 

The processing form keeps running until it gets to 18 seconds, and then freezes.  Any further interaction with screen results in a request to reload the page

 

 

I think that the screen expirying is probably due to the debug message.  

 

I have tried, click “yes, debug wp3.exe” with the following result:

Clicking “New instance of Visual Studio Community 2019” results in the below:

 

 

Also, when debugging in Visual Studio, after approx 4 seconds I’m getting:

Everything appears to be behaving normally up until this point eg. I can set break points, and execution stops on these as per normal.

 

Thanks in advance for any help on this.

JOhn.

Best answer by JWS539

Hi Graeme,

 

Thanks for your eMail.  Also FYI, I had a separate topic, which I originally thought was unrelated to this one, but turned out to be related.  This is the topic:

 

Took around 12 months to resolve and we finally got a resolution after a 90 min screen share with Acumatica support.  The outcome was that we concluded there was a bug with nLog on my local installs.  From what I know, nLog is used by Acumatica for it’s logging.  The nLog bug was causing the JIT Debugger to fire up where as I was assuming it was my code or VS install that was at fault.  After turning nLog off all my problems in this space went away.

 

John.

 

 

 

 

View original
Did this topic help you find an answer to your question?

3 replies

Graeme Laughton-Mutu
Freshman II
Forum|alt.badge.img

I also get this occasionally with certain long running processes.

I’m not experienced with VS but it seems like the VS popups are interrupting the Acumatica process from running/completing.


Forum|alt.badge.img
  • Author
  • Varsity I
  • 63 replies
  • Answer
  • December 3, 2024

Hi Graeme,

 

Thanks for your eMail.  Also FYI, I had a separate topic, which I originally thought was unrelated to this one, but turned out to be related.  This is the topic:

 

Took around 12 months to resolve and we finally got a resolution after a 90 min screen share with Acumatica support.  The outcome was that we concluded there was a bug with nLog on my local installs.  From what I know, nLog is used by Acumatica for it’s logging.  The nLog bug was causing the JIT Debugger to fire up where as I was assuming it was my code or VS install that was at fault.  After turning nLog off all my problems in this space went away.

 

John.

 

 

 

 


Graeme Laughton-Mutu
Freshman II
Forum|alt.badge.img

Hi ​@JWS539 

Thanks for sharing the fix/workaround.

My scenario doesn’t even involve anything custom or coded. I’m just trying to load the Termination window in MYOB Acumatica Payroll, which was enough to trigger the JIT Debugger.

I have renamed the nlog file, restarted the website & app pool and now don’t get the JIT popups :)

Thanks!

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings