This post is about failing to log in to eSpace mobile. Please see below the procedure on how to tackle this issue.
【Problem description】
The issue is that espace mobile failed to login.
Network topology
Server-1 is 'Install the BMU, APPAgent, eServer'
Server 2 is 'Install the MAA, Meeting MS, UM'
【Problem analysis】
1. Checked if the MAA server is running. It was running and pingable.
2. Collected the eSpace mobile logs, the MAA log and the eServer log.
a) eSpace mobile log
b) MAA log path: \eSpace_UC\eSpace_UC_Server\Logs\MAA
c) eServer log: \eSpace_UC\eSpace_UC_Server\Logs\eServer
3. Checked if the MAA and BMU started.
(running)
4. Checked the connection of BMU and U19.
Found it was connected (normal).
5. Checked the logs
We checked the configurations and the logs and we found the issue was caused by the fact that the Windows OS socket connections have reached a maximum; it needs to restart the MAA server to release it.
6. Checked the disk space of the MAA.
Found there was space.
7. Checked the CPU utilization.
【Root cause】
The Windows OS socket connections have reached a maximum; it needs to restart the MAA server to release it.
【Solution description】
Restart the MAA server, the issue was solved and eSpace mobile can login and it is working fine.
