> For the complete documentation index, see [llms.txt](https://knowledgebase.qommentary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.qommentary.com/getting-started/troubleshooting/common-issues.md).

# Common Issues

### <mark style="color:blue;">HTTP Error 500.19</mark>

![HTTP Error 500.19](/files/-M5BbM47uT63S7z7Oqi2)

**Problem**\
An Internal Server error is displayed when trying to access the Qommentary Manager

**Possible causes**

* **Rewrite module missing**

  Install the URL Rewrite module included in the [Software Dependencies](/getting-started/prerequisites/software-dependencies.md) section
* **Corrupted .NET Core Hosting Bundle**

  Try repairing the bundle. Otherwise, uninstalling and re-installing.
* **Qommentary Manager/Engine bindings to invalid or expired SSL certificates**

  Bind a valid SSL certificate to the Qommentary Manager/Engine sites.

### <mark style="color:blue;">Service Unavailable</mark>

![Service Unavailable error](/files/-M5C10lKk9LGkt6g-gH5)

**Problem**\
A Service Unavailable error is displayed when trying to access the Qommentary Manager.&#x20;

**Possible Causes**

* **Qommentary Engine application pool stopped**

  Try re-starting the Engine service and accessing the Qommentary Manager again from a browser. If the service is stopped again, try the troubleshooting steps below.
* **.NET Core Framework or one of it's components might be corrupted**

  1\. Open a cmd line terminal

  2\. CD into the Qommentary Engine folder under the installation path

  3\. Run <mark style="color:blue;">`"C:\Program Files\dotnet\dotnet.exe" "C:\Program Files\Qommentary\Qommentary Engine\Qommentary.Api.dll"`</mark>

  If you see the following screen, there is an issue with the .NET Core Framework installation:

  &#x20;<img src="/files/duEoGBJKMUba0clykrIn" alt="" data-size="original">

  Try repairing Microsoft Visual C++ Redistributable (x64). If you encounter any issues repairing the component, it might be related to missing Windows updates. Try updating Windows and repairing the component again
* **QlikClient certificate is not installed**

  Export certificates from Qlik Sense and install client.pfx
* **URL Rewrite version not compatible with Windows version**

  1\. Open Event Viewer\
  2\. Select Application Logs\
  3\. Check if there's any errors related to rewrite.dll failing to load

  ![](/files/vhoNgkq17W5fW3t6ObYC)

  Install the supported URL Rewrite module included in the Software Dependencies section.

### <mark style="color:blue;">415 Method Not Allowed</mark>

![Spinning wheel when updating or deleting commentary](/files/-M5CFkJgzwCw2RpHVjer)

**Problem**\
Extension hangs on spinning wheel when trying to update or delete a commentary.

**Possible cause**\
Wev Dav might be enabled in IIS and is interfering with PUT and DELETE methods.&#x20;

To disable the module, follow these steps:

1. Open Server Manager
2. Click on Add Roles and Features
3. Jump to Server Roles
4. Look for *Web Server  (IIS) > Web Server > Common HTTP features*&#x20;
5. Untick WebDAV Publishing
6. Click on Next and Install

For more information on disabling Web Dav in IIS, please refer to this [guide](https://inedo.com/support/kb/1140/disabling-webdav-in-iis).

### <mark style="color:blue;">ERR CERT COMMON NAME INVALID</mark>

<figure><img src="/files/FUKrKPwhvOz7XgmRd21R" alt=""><figcaption></figcaption></figure>

**Problem**\
Qommentary Admin Console does not load properly and all Qommentary Engine API calls display a *ERR\_CERT\_COMMON\_NAME\_INVALID* issue

**Possible causes**

* **SSL Certificate mismatch**\
  The SSL certificate bound to the Qommentary IIS sites do not match the domain name you're trying to access the Qommentary Admin Console\
  \
  To rectify the issue, follow these steps:
  1. Launch IIS
  2. Select **Qommentary Engine** site and click on **Bindings...**<br>

     <figure><img src="/files/GDgqEuxK11rMsu20ho6x" alt=""><figcaption></figcaption></figure>
  3. Edit the HTTPS binding and select the certificate which matches the QAC domain<br>

     <figure><img src="/files/XE0UbDchaZjMkSF3zlcf" alt=""><figcaption></figcaption></figure>
  4. Recycle the **Qommentary Engine** application pool
  5. Now the QAC should load correctly<br>

     <figure><img src="/files/LwYyx51mVb9vsgA0ycco" alt=""><figcaption></figcaption></figure>
  6. Repeat steps 2-4 for the Qommentary Manager (if necessary)