Troubleshoot Web Console Issues

Troubleshoot Web Console Issues

If you are having issues with your Web Console, this page will give you a rundown of the various troubleshooting steps that can help solve your individual issue.

Sections

  1. Login Issues
  2. Unable to create/delete/rename or change from PC to User mode
  3. I cannot choose any of the features from the menu on my web console
  4. My web console screen is blank when I try to open it
  5. The web console opens with a 500.19 error page
  6. The web console opens with an “Error connecting to server’ with backend 500.31 error

1 – Login issues

If you are having login issues the troubleshooting steps for can be found here.


2 – Unable to create/delete/rename/move users or change from PC to User mode on Web Console

If a Rest API module called WebDAV is installed on the local IIS(Internet Information Services), it may not allow the Rest API to perform any creation/deletion/renaming/movement of users or changing of select settings on the Web Console.

To solve this Uninstall WebDAV from the IIS

  1. Open IIS by searching IIS or going to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
  2. Expand RestAPI
  3. Double click modules to view the installed modules.
  4. Search for WebDAV module.
  5. Right click and remove.


3 – I cannot choose any of the features from the menu on my web console

If you are attempting to use any of the menu bar options within the web console and the buttons are a light shade of red like below, you need to unselect checkmarked PC’s from the console selection.

As you see the left console has no PC selected from the group folders below and allows access to all features. The right console is actively managing Client PCs and will not allow you to select features before finishing.

Tags: Greyed out, Grayed out, Can’t select


4 – My web console screen is blank when I try to open it

NOTE: The following steps require you to go to your browsers “Console” inspect tool. The KB with steps to see those consoles is here

If you go to the “Console” tab you should get an error which you can attempt to match up with any of the following steps:

Failed to load resource: the server responded with a status of 404()

To solve this you need to go into your CurrentWare server and make sure your “MIME type” settings are correct for both the WebConsole and RestAPI pages.

1. Go to the IIS Management console. Search IIS through windows or go to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools and run Internet Information Services (IIS) Manager.
2. Go to the individual RestAPI page.
3. Check the “MIME Types” .

4. Check for the .json  & .jsonld entries- Add them if not shown.

5. If they are not shown in your list, use the “Add” button on the top right to add them manually.

File name extension:      .json
MIME Type:      application/json

File name extension:      .jsonld
MIME Type:      application/ld+json

6. Right click your IIS and restart it to ensure your changes updated.
7. Try to open the web console and you should get the login screen.

If that did not solve the issue, you may need to select the option on the Webconsole IIS site to allow unlisted file name extensions.

  1. Go to your IIS Webconsole site
  2. Go to the “Request Filtering” option
  3. Select the “File Name Extensions” tab
  4. On the right-hand Actions menu choose “Edit Feature Settings…”
  5. Ensure “Allow unlisted file name extensions” is checked.



5 – The web console opens with a 500.19 error page

This issue is generally caused by Exchange or WSUS servers being on the same PC/Server as CurrentWare.
Find the troubleshooting steps to solve this issue here


6 – The web console opens with an “Error connecting to server’ with backend 500.31 error

This issue is generally caused by the .NET dependencies not installing as expected due to a conflict or windows error.
Find the troubleshooting steps to solve this issue here


7 – The web console opens with Service Unavailable – 503 error page

This issue is generally caused by installing the CurrentWare server and IIS based web console on a machine that currently or previously hosted an Exchange server.
Find the troubleshooting steps to solve this issue here


    • Related Articles

    • BrowseControl is not blocking Internet

      If you are having issues with websites not being blocked accordingly by BrowseControl you can conduct the following troubleshooting steps below: Using Domain Name in the Blocked List URL Category Lookup Tool Change the Web Filtering Technology Using ...
    • Release Notes - Old

      Return to the list of latest changes Version 5.0.7 June 1, 2016 Fixed a bug with BrowseReporter’s PCs/users selection Fixed a bug with Email Report’s corrupted profiles from previous version Enhanced Web Filtering for Download Filter for Windows 10 ...
    • Client Connection Issues – My computer is not showing up on CurrentWare

      You are encountering a client connection issue when your computers are not showing up as “connected” on the CurrentWare Console. There are a few possible causes that will prevent your CurrentWare client from connecting to the CurrentWare Console. ...
    • Web Console Login Issues

      When the CurrentWare Web Console is not configured properly, you will encounter the error message "Error connecting to the server." 1. Clear your Browser Cache Why does my Web Console login screen open on one web browser but won’t open on a different ...
    • Reporting Web Console errors with the inspect elements details

      Sometimes during your install, upgrade or configuration of the CurrentWare Web Console there can be obvious issues that are not visible at first glance. You can help us diagnose the issue(s) by using your browsers inspect tool by following these ...