Skip to main content
Eptura Knowledge Center

MLS Maintenance

SVLive1 Maintenance

Uptime Best Practice

It is important that MLS maintains connectivity to Serraview endpoints. Here are a few best practice suggestions:

  • Reboot at 1am
  • Automate service restart, if stopped
  • Monitor network load, if anomaly then send alert to Serraview Administrator
  • Monitor MEM and upgrade if possible
  • Monitor CPU and upgrade if possible

To automate service to restart: 

  1. In the Start menu or Run dialog, open the Services snap-in by typing in services.msc and then press the Enter key.
  2. Find the service that you want to monitor and restart if it stops.
  3. Right-click on the service and select Properties.
  4. Click on the Recovery tab.
  5. From the First failure drop-down menu, select Restart the Service.
  6. From the Second failure drop-down menu, select Restart the Service.
  7. From the Subsequent failures drop-down menu, select Restart the Service.
  8. Set the Restart service after option to a reasonable amount of time, such as 1 minute.
  9. Click the OK button to save your changes.

Monitor the Service Control Manager (SCM)

It is possible to monitor the Service Control Manager (SCM) on a Windows Server from external servers using various tools and techniques.

One way to monitor SCM remotely is by using the Windows Management Instrumentation (WMI) protocol, which provides a way to access and manage Windows system information from remote servers. WMI allows you to query the status of services on a remote server, start or stop services, and receive notifications when a service fails.

To use WMI to monitor SCM remotely, you can use tools such as Windows PowerShell or the WMI Query tool in Microsoft Management Console (MMC). You will need to have administrative privileges on both the local and remote servers to use WMI for monitoring.

Another way to monitor SCM remotely is by using third-party monitoring tools that support Windows services. These tools provide a user-friendly interface for monitoring services on multiple servers, generating alerts when services fail, and performing other management tasks.

Some examples of third-party monitoring tools for Windows services include Microsoft System Center Operations Manager (SCOM), SolarWinds Server & Application Monitor (SAM), and Nagios Core.

Regardless of the monitoring method used, it is important to ensure that appropriate security measures are in place to protect the remote access and ensure that the remote monitoring is compliant with organizational security policies and regulations.

MLS Service Account Expiry

The MLS application runs on a server hosted within the client network. The network service account for the MLS application is usually set up to run under the NT AUTHORITY\NetworkService account.

If this is not the case and IT has assigned a service account to MLS, the password for that account needs to be set to never expire. This can be achieved by monitoring the validity of the designated service account and renewing before expiry.


Impact on Service

If the service account expires, all SVLive1 services would become immediately become unavailable with data loss throughout the duration of the outage.

MLS Server Shutdown

The MLS Server may be shut down by your IT team team due to routine maintenance. It is recommended that any shutdown of the MLS server is done outside of the hours a customer may want to collect utilization data or use Wayfinding technology. Additionaly, your IT team will need to notify the Corporate Property team of the outage.

Also, when Serraview Support team and the Client IT team are checking:

  • the connectivity between the Client's MLS and Serraview web services.
  • that the MLS is running on the Client's server.

Client IT will be instructed to perform a restart on the MLS server.


Impact on Service

If the MLS server is not running, all SVLive1 services would become immediately become unavailable with data loss throughout the duration of the outage.

Follow the instructions here to Start and Stop MLS Server.

Serraview Live Event Error

MLS not able to process the message in time and the message gets dropped/rejected.

It is expected to see these occasionally, however, if they appear consistently without any successful messages, there may be an underlying issue.

Step 1. Obtain the logs or screenshot of the logs from the client.


To find the Event Logs on the Windows Operating System complete the steps below.

The steps are written for Windows 10) and you may need your IT team to complete the steps.

  1. Right-click Windows icon and from the menu select Event Viewer. The Event Viewer displays.
  2. From the menu, expand the Windows Logs and select Application.
  3. On the right-hand panel, select Filter Current Log... The Filter Event Log dialog displays.
  4. From the Event Sources drop-down, select the SerraviewLiveAgent.
  5. Click the OK button.
  6. From the list of errors, look at the Source column for SerraviewLive.
  7. Click on one of the errors. The Event Properties dialog displays.
  8. Either take a screenshot of the error.
  9. Click the Close button to close the dialog.
  10. Kept the error selected and then from the right-hand panel, click the Save Filtered Log As.
  11. Save the log to your computer.
  12. Send log screenshot and saved log to


To find the Event Logs for Mac, refer to the external article 

Step 2. Serraview's Technical Product Support Engineer can increase queue size.

Step 3. The client can continue their day as normal and then can review the logs after 15 minutes for any improvements.

MLS throwing VLAN Timeout Error

MLS is unable to scan VLANs throwing a timeout exception error. For example:

<time> ERROR SwitchMacToPortFetcher(EasyNetQ consumer dispatch thread) - Error scanning - vlan x ... vlan-x [Exception of type 'Lextm.SharpSnmpLib.Messaging.TimeoutException' was thrown.]


  • This error appears when clients have updated their switch firmware.
  • The MLS has code that includes the @ character when scanning for VLANs or if it exists within the community string, it will crash, throwing a timeout error. 

For more details, refer to Wireup Maintenance for SVLive1.


You need to reconfigure their switches by removing the @ from the community string and the Serraview team to update the Community string field within the MLS accordingly.