Help Center/ Server Migration Service/ FAQs/ Known Errors and Solutions/ SMS.1902 Failed to Start the I/O Monitoring Module
Updated on 2024-08-31 GMT+08:00
View PDF
Share

SMS.1902 Failed to Start the I/O Monitoring Module

Symptom

When you started the Agent, you received the error message "SMS.1902 Failed to start the I/O monitoring module."

Solution

To fix the problem, perform the following operations:

  1. Uninstall the Agent and re-install it.
    1. If the Agent (Python 3) is installed, enter the AK/SK pair and SMS domain name when prompted.
    2. If the Agent (Python 2) is installed, enter the AK/SK pair and SMS domain name when prompted, as shown in Figure 1. If no prompt is displayed, double-click start.bat in the installation directory and enter the AK and SK when prompted.
      Figure 1 Entering the AK/SK pair and SMS domain name
  2. Check whether antivirus software is installed on the source server.
    1. If any antivirus or security software is installed, or the firewall is enabled, a pop-up window may be displayed indicating the I/O monitoring driver was blocked. Allow the system to run the I/O monitoring process.
    2. If there is no pop-up warning, but the driver is blocked, you need to start the I/O monitoring driver manually. Add C:\Windows\System32\drivers\HwDiskMon.sys to the trusted zone of the antivirus software and restart the Agent. If the problem persists, uninstall the antivirus software.

      Some antivirus software has persistent blocking functions and may block the driver even if disabled.

  3. Modify the configuration file to disable I/O monitoring.

    If you do not need to synchronize data, you can modify the configuration file to disable I/O monitoring.

    In the Agent installation directory config, change the value of enablesync to False in the g-property.cfg file, and then restart the Agent.

    Figure 2 Modifying the g-property.cfg file