Some server error occurred. Try to login later

Troubleshooting the error: "Unable to connect with the MAWi Server" or "Some server error occurred. Try to login later" when trying to login into MAWi Management Console

Introduction

In this article, we will walk you through the steps on how to troubleshoot and fix the issue that is some cases, trying to login into MAWi Management Console would lead to the error: "Unable to connect with the MAWi Server" or "Some server error occurred. Try to login later" 


Step 1: Check if the Gateway of MAWi web application is running

 
 Open your browser and try to open this URL:
http://{SERVER-IP}:60668

* Replace the {SERVER-IP} with the actual IP or hostname of the server.

Confirm that you can see the MAWi Gateway page: 



If not - move to step no.2. 


Step 2: Check if the IIS Express is running


If the server is installed on a standard Windows10 PC, please look for the IIS Express icon, in the taskbar and confirm that is running and showing the correct IP/hostname and directed to port 60668, as shown below:





In case the IIS Express is not running, please open this folder:

C:\Program Files (x86)\Monitors AnyWhere\Common\

And run this script with administrative privileges:

IISExpressDeployServer.bat

.



Confirm that the IIS Express is running now and try to access the gateway as shown in Step 1. 

If the IIS Express is still not running as shown, go to Step 3, otherwise, you should be able to login to the MAWi Management console.  

Step 3: Confirm the MAWi IIS Service is running 


Check if the MAWi IIS service is running in the Task Manager:

1- Open the Task Manager and go to the Services tab and search for the 'MAWi IIS Express Server':



2- Right click the service and select Restart. 


Please note:

When installing MAWi on Windows10/11 machine, the IIS Express settings will be saved in the following folder:

C:\Program Files (x86)\Monitors AnyWhere\Web.Server\applicationHost.config


If still, it's not connecting - move to step no.4. 


Step 4: Check the SQL Server status


Check in the SQL Configuration if the SQL Server is running:



If the SQL Server is not running, try to run it and check if that fixed the issue.
If still it's not connecting - move to step no.5. 


Step 5: Open MAWi Management console using Chrom in Incognito Mode


Try to open Chrome in Incognito mode and open the MAWi URL:



In case MAWi is working using Incognito Mode, then clear the cache using the following steps:



Refresh MAWi dashboard using Shift + F5


    • Related Articles

    • How to install MAWi's DB on a remote SQL Server

      Introduction In this article we will walk you through the process of installing MAWi Server on one machine and the Database will be installed on a remote machine. This scenario is mostly used when your organization is using a central SQL Server ...
    • Troubleshooting Issue "I can't see my screens in the MAWi management console"

      Introduction In this troubleshooting guide we will walk you through the steps to fix the issue where you are unable to see your screens in the MAWi management console. 1 - Are you connected over RDP to the host PC? You can’t use any remote control ...
    • MAWi Spacewall - Quick Installation Guide - Utilizing Android-based MAWi Players

      MAWi Spacewall - Quick Installation Guide Introduction MAWi Spacewall is a tool for managing screen displays. Here's a simple breakdown: 1. Display unique content on individual screens. 2. Link several screens to show identical content. 3. Design ...
    • How to activate MAWi license

      Introduction In this guide we will show you step by step how to activate the MAWi system Login to MAWi’s management console with an administrative user account. Once logged in, click on the Dashboard menu item and select “Admin panel” In case your ...
    • How to Fix the "Network-Related or Instance-Specific Error" When Logging into MAWi

      If you encounter the error message "A network-related or instance-specific error occurred..." when logging into MAWi: Please follow these steps to resolve it: 1. Navigate to: `C:\Program Files\Microsoft SQL Server\150\LocalDB\Binn\Templates` 2. Copy ...