Troubleshooting

Applies to: ✅ Azure Data Explorer

This article describes common difficulties in running and using Kusto.Explorer and offers solutions. It also explains how to reset Kusto.Explorer.

Kusto.Explorer fails to start

Symptom

At startup, Kusto.Explorer shows an InvalidOperationException error during or after startup.

Possible solution

This error might suggest that the operating system is corrupted or missing some essential modules. To check for missing or corrupted system files, follow the steps described here:
https://support.microsoft.com/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

Kusto.Explorer always downloads even when there are no updates

Symptom

Every time you open Kusto.Explorer, you're prompted to install a new version. Kusto.Explorer downloads the entire package without updating the already installed version.

Possible solution

This symptom might result from corruption in your local ClickOnce store. Clear the local ClickOnce store by running the following command in an elevated command prompt.

rd /q /s %userprofile%\appdata\local\apps\2.0

Install Kusto.Explorer again from one of the installation mirrors.

ClickOnce error: cannot start application

Symptoms

The program fails to start and displays one of the following errors:

• External component has thrown an exception
• Value does not fall within the expected range
• The application binding data format is invalid.
• Exception from HRESULT: 0x800736B2
• The referenced assembly is not installed on your system. (Exception from HRESULT: 0x800736B3)

You can explore the error details by clicking Details in the following error dialog:

Following errors were detected during this operation.
    * System.ArgumentException
        - Value does not fall within the expected range.
        - Source: System.Deployment
        - Stack trace:
            at System.Deployment.Application.NativeMethods.CorLaunchApplication(UInt32 hostType, String applicationFullName, Int32 manifestPathsCount, String[] manifestPaths, Int32 activationDataCount, String[] activationData, PROCESS_INFORMATION processInformation)
            at System.Deployment.Application.ComponentStore.ActivateApplication(DefinitionAppId appId, String activationParameter, Boolean useActivationParameter)
            at System.Deployment.Application.SubscriptionStore.ActivateApplication(DefinitionAppId appId, String activationParameter, Boolean useActivationParameter)
            at System.Deployment.Application.ApplicationActivator.Activate(DefinitionAppId appId, AssemblyManifest appManifest, String activationParameter, Boolean useActivationParameter)
            at System.Deployment.Application.ApplicationActivator.ProcessOrFollowShortcut(String shortcutFile, String& errorPageUrl, TempFile& deployFile)
            at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
            at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

Possible solution

1. Uninstall Kusto.Explorer using Programs and Features (appwiz.cpl).

2. Try running CleanOnlineAppCache, and then try installing Kusto.Explorer again. From an elevated command-prompt:

   rundll32 %windir%\system32\dfshim.dll CleanOnlineAppCache
   

   Install Kusto.Explorer from one of the installation mirrors.

3. All ClickOnce apps reinstall automatically the next time you run them if you have access to the original install location stored in the app shortcut. App shortcuts aren't deleted.

   From an elevated command-prompt:

   rd /q /s %userprofile%\appdata\local\apps\2.0
   

   Install Kusto.Explorer again from one of the installation mirrors

4. If the application still doesn't start:

   1. Delete temporary deployment files.

   2. Rename the Kusto.Explorer local AppData folder.

      From an elevated command-prompt:

      rd /s/q %userprofile%\AppData\Local\Temp\Deployment
      ren %LOCALAPPDATA%\Kusto.Explorer Kusto.Explorer.bak
      

   3. Install Kusto.Explorer again from one of the installation mirrors

   4. To restore your connections from Kusto.Explorer.bak, from an elevated command-prompt:

      copy %LOCALAPPDATA%\Kusto.Explorer.bak\User*.xml %LOCALAPPDATA%\Kusto.Explorer
      

Enable ClickOnce verbose logging

If the application still doesn't start:

1. Enable verbose ClickOnce logging by creating a LogVerbosityLevel string value of 1 under:

       HKEY_CURRENT_USER\Software\Classes\Software\Microsoft\Windows\CurrentVersion\Deployment
   

2. Reproduce the issue again.

3. Send the verbose output to KEBugReport@microsoft.com.

ClickOnce error: your administrator has blocked this application

Symptom

The application fails to install with either of the following errors:

• Your administrator has blocked this application because it potentially poses a security risk to your computer.
• Your security settings do not allow this application to be installed on your computer.

Solution

This issue might occur because another application overrides the default ClickOnce trust prompt behavior.

1. Check your default configuration settings.
2. Compare your configuration settings to the ones on your machine.
3. Reset your configuration settings if needed, as explained in this how-to article.

Clean up application data

If the previous troubleshooting steps don't help Kusto.Explorer start, cleaning locally stored data might help.

You can find data stored by the Kusto.Explorer application at: C:\Users\[your username]\AppData\Local\Kusto.Explorer.

Reset Kusto.Explorer

You can completely reset Kusto.Explorer. This procedure describes how to progressively reset Kusto.Explorer until it's removed from your computer and needs to be installed from scratch.

1. In Windows, open Change or remove a program (also called Programs and Features).

2. Select each item that starts with Kusto.Explorer.

3. Select Uninstall.

   If this procedure doesn't uninstall the application (a known issue with ClickOnce applications), see this article for instructions.

4. Delete the folder %LOCALAPPDATA%\Kusto.Explorer, which removes all connections, history, and other data.

5. Delete the folder %APPDATA%\Kusto, which removes the Kusto.Explorer token cache. You need to reauthenticate to all clusters.

You can also revert to a specific version of Kusto.Explorer:

1. Run appwiz.cpl.
2. Select Kusto.Explorer, and then select Uninstall/Change.
3. Select Restore the application to its previous state.

Related content

• Learn about the Kusto.Explorer user interface.
• Learn about running Kusto.Explorer from the command line.
• Learn about Kusto Query Language (KQL).