Help Center/ Migration Center/ MgC Agent Usage Guide/ Error Codes and Solutions for MgC Agent
Updated on 2025-08-25 GMT+08:00

Error Codes and Solutions for MgC Agent

Error Codes and Solutions for MgC Agent (Formerly Edge)

Error Code

Description

Solution

agent_collector_server_netstat_process.0000

Current OS not supported.

Install the MgC Agent on the Windows server and run the collector again.

agent_collector_server_netstat_process.0001

Required parameters are missing or the parameter format is invalid.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

agent_collector_server_netstat_process.0002

Remote access to server failed. The server is stopped, the network is disconnected, or the protocols mismatch.

Ensure that the server is started and the related protocols and ports are enabled. Then try again.

agent_collector_server_netstat_process.0003

Remote access to server failed. Invalid credential.

Check whether the credential is valid. If no, correct it and try again.

agent_collector_server_netstat_process.0004

Failed to configure or create shared folder on the Windows server.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

agent_collector_server_netstat_process.0005

Failed to read CSV file with collected process and network details.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

agent_collector_server_netstat_process.0006

No results were displayed after the process collection command was executed on the Windows server. Check whether the wmic command is available on the server.

Start wmic on the server and try again.

agent_collector_server_netstat_process.0007

Collection process exception.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

agent_collector_server_netstat_process.0008

The account is locked. Try again later.

Try again later or manually unlock the account and retry.

agent_collector_server_netstat_process.0009

Failed to establish a DCOM connection with the remote node using the IP address.

Replace the IP address with the private IP address of the node and try again.

app-discovery-process-netstat-win.0007

Collection failed on all servers due to different reasons.

Review the logs to identify and resolve the faults. The possible causes are various, for example, the specified servers were shut down or unreachable, or the provided credentials were incorrect.

app-discovery-process-netstat.0003

The value of duration is smaller than that of interval.

Set interval to a value smaller than duration.

app-discovery-process-netstat.0004

interval is longer than 30 minutes.

Set duration to less than 30 minutes.

app-discovery-process-netstat.0007

No node could be connected.

Review the logs to identify and resolve the faults. The possible causes are various, for example, the specified servers were shut down or unreachable, or the provided credentials were incorrect.

app-discovery-process-netstat.0009

Invalid credential.

The credential type is not met or the credential is invalid. Check the credential.

EDGE.00250063

An exception occurred when the script was executed.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250060

Failed to execute script command.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250062

Status file not found.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250028

Failed to read status file.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250064

Empty status file.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250029

Task execution timed out.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250055

Failed to update retry status for task.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250042

Failed to query the collection task entity.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250043

DiscoveryItem or dataSourceConfig is empty.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250034

Decryption configuration error.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250035

Failed to convert configString to configMap.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250036

Blank configuration item.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250026

The collector has not been installed.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250032

Collector parameters were incorrect.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250061

Incorrect collector settings.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250059

"datasourceId" mismatch between command and task.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250056

Data source statuses not met.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250057

No resource types specified for collector.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250058

Resource IP addresses are empty.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250065

Remote status check failed.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250066

Invalid resource type.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250067

Create CSV file failed.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

EDGE.00250068

Data collected by the collector cannot be downloaded currently.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

Error Codes and Solutions for MgC Agent (Windows)

Error Code

Description

Solution

EDGE.00000001

Unknown error.

There are many possible causes for this error, for example, the network could be abnormal. Try this workflow step again. If the fault persists, contact technical support or submit a service ticket.

EDGE.00260001

Source IP address unreachable.

Check whether the access IP address is correct.

EDGE.00260002

Source WinRM unreachable.

The default WinRM ports are 5985 for HTTP and 5986 for HTTPS.

Perform the following steps to check the WinRM status, listening port, and protocol on the source server:

  1. Check the WinRM service status.
    1. Open PowerShell as an administrator. Enter PowerShell in the Windows search box, right-click Windows PowerShell, and choose Run as administrator from the shortcut menu.
    2. Run the following command to check the WinRM service status:
      Get-Service -Name WinRM
      • If the service status is Running, the WinRM service is started.
      • If the service status is Stopped, the WinRM service is not started. You can run the following command to start the WinRM service and enter y as prompted to confirm the operation:
        winrm quickconfig
  2. Check the WinRM listening port and communication protocol.

    Run the following command in PowerShell to check the WinRM configuration:

    winrm enumerate winrm/config/listener

    This command displays details about all WinRM listeners, including the listening address, port, and transmission protocol (HTTP or HTTPS).

  3. (Optional) Configure WinRM to use HTTPS.

    If a more secure connection mode is required, configure WinRM to use HTTPS. Ensure that a valid SSL certificate has been installed on the source server.

    1. Run the following command to view the installed SSL certificates and their thumbprints:
      Get-ChildItem -Path Cert:\LocalMachine\My

      Find a valid SSL certificate and record its thumbprint.

    2. Run the following command to configure WinRM to use HTTPS:
      New-Item -Path WSMan:\localhost\Listener -Transport HTTPS -Address * -CertificateThumbprint <thumbprint>

      Replace <thumbprint> with the SSL certificate thumbprint you recorded.

    3. Run the following command again to verify that WinRM has been configured to use HTTPS connections:
      winrm enumerate winrm/config/listener

EDGE.00260003

Invalid source credential.

Check whether the credential provided to the MgC Agent (formerly Edge) is correct.

EDGE.00260004

Insufficient credential permissions.

Check whether the account is in the administrator user group.

EDGE.00260005

Access source WinRM failed.

Check whether the firewall on the source server is disabled.

EDGE.00260006

Necessary components not found at source.

Check whether .NET Framework, WMI, and COM on the source server are damaged.

EDGE.00260007

Edge does not trust source server.

Run the following command on the server where the MgC Agent (formerly Edge) is installed to trust the source server:
set-item wsman:localhost\\client\\trustedhosts -value *

Error Codes and Solutions for MgC Agent (Linux)

Error Code

Description

Solution

EDGE.00261001

Source IP address unreachable.

Check whether the access IP address is correct.

EDGE.00261002

Source port unreachable.

Check whether the source port can be reached using telnet.

EDGE.00261003

SSH connection to source server failed.

Rectify the fault based on the error message. If the fault persists, contact technical support or submit a service ticket.

EDGE.00261004

Invalid source credential.

Check whether the credential provided to the MgC Agent (formerly Edge) is correct.

EDGE.00261005

Source SFTP unavailable.

Check whether the MgC Agent (formerly Edge) server can access SFTP on the source server.

EDGE.00261006

Source account directory not found.

Check whether the source account directory exists.

EDGE.00261007

tty for running sudo is not disabled.

Comment out the following default values in the source configuration file:

requiretty in the user!/etc/ssh/sshd_config file or Defaults requiretty in the /etc/sudoers file