TOPIC: Just-In-Time debug error

Just-In-Time debug error 30 Dec 2014 13:49 #1767

  • beachys
  • beachys's Avatar
  • Offline
I have Logicity Pro Version 1.8.6 installed on Windows Server 2008 R2. I have created a rrd solution. This solution file will run successfully when I run it manually. It will also run successfully using its schedule while someone is logged in to the server, but when I log out and the schedule is run automatically I get this error in the event logs and the solution file does not successfully run:

An unhandled exception ('System.InvalidOperationException') occurred in Logicity Desktop.exe [7984]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on.

Check the documentation index for 'Just-in-time debugging, errors' for more information.
The administrator has disabled public write access.

Just-In-Time debug error 30 Dec 2014 14:27 #1768

  • bellis
  • bellis's Avatar
  • Offline
Can you verify if the scheduled task has the --quiet argument included?

Thanks!
Brian
The administrator has disabled public write access.

Just-In-Time debug error 15 Dec 2016 11:14 #2478

  • tiagofreitas
  • tiagofreitas's Avatar
  • Offline
Hello,
I have the same problem and using the --quiet argument in a bat file.
Using latest logicity pro.
The administrator has disabled public write access.