none
Starting .NET Application (Clickonce) over task planer -> JiTDebugger Error RRS feed

  • Question

  • Hi.
     
    On a server we created a task, which starts a little application, which calls URL with a click once application behind. Usually the application is allready installed so there will be no download and the application will start immediately.
    But when the Task starts the first (little) application runs. the sencond one creates an error in the event log like this:

    VsJITDebugger 4096

    An unhandled exception ('System.InvalidOperationException') occurred in IBS.Cockpit.exe [3808]. 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.

    This error only accures when noone is logged on. If there is somebody locked on with remote desktop the application runs good.
    Does anyone know about this?

    thank for all help

    Monday, December 8, 2008 9:29 AM

All replies

  • ClickOnce technology uses some settings of logged-on user, so there will be error in ClickOnce Engine in case of no logged-on user available. This error will be handled by JITDebugger in order to show it to user and ask what to do next, but it cannot display any message because again there is no logged-on user! :-) In this case JITDebugger logs an error to EventLog. You can easily found information about it on msdn.

    So the answer is: it is impossible to run ClickOnce Application without logged-on user.

    Workaround is: run application by execution of your .exe file already installled by ClickOnce. But it is bad practice. You have to update application manually. And you don't actually know where it is installed.
    Thursday, May 14, 2009 12:59 PM
  • HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\DbgJITDebugLaunchSetting.
    • If value = 0, prompt the user by means of a message box. The choices are:
      • Continue. This results in a stack dump and process termination.
      • Attach a debugger. In this case, the runtime spawns the debugger listed in the DbgManagedDebugger registry key. If none, control is returned, and the process is terminated.
    • If value = 1, simply return control. This results in a stack dump, after which the process is terminated.  (No more dialog)
    • If value = 2, spawn the debugger listed in the DbgManagedDebugger registry key.

      Try set value = 1. In this case your error "
      Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on" disappear.
    Wednesday, May 20, 2009 6:41 AM