How to resolve warnings and errors when upgrading from EM Library to Update Manager
The migration wizard reports that there was an error with the migration to SUM. When you view the Failed Migration report, it lists one of the following warnings or error codes.
The following table lists the error codes you could encounter and solutions or notes for each one.
Warnings
| Warning Message | Solution |
|---|---|
|
| Configure Update Manager manually (inglés). |
EM Library publishes the package {package-name} to its child libraries but does not have a CID for that package. | None. When child libraries are migrated, the parent Update Manager will be configured automatically with the relevant software subscriptions. |
Failed to migrate the EM Library updating schedule. The update manager will be configured to update using the default updating schedule. | |
A subscription policy with the name {policy-name} already exists. | None. The existing policy is reused. |
An updating policy with the name {policy-name} already exists and will be overwritten. | None. The policy has been overwritten. |
|
| Configure an equivalent updating policy by hand (inglés). |
The legacy updating policy {policy-name} has no platforms configured. | None. |
Could not find a replacement for the EM Library package {package-name} that can be updated via Sophos Update Manager. | Configure an equivalent updating policy by hand (inglés). Start using the Update Manager once the affected packages are re-created. |
Cannot identify the EM Library package available in the CID {cid-uri}. | See Retrying a failed migration to the update manager in Enterprise Console 4 (inglés). |
The migration data contains a CID with the malformed address {cid-uri}. | See Retrying a failed migration to the update manager in Enterprise Console 4 (inglés). If necessary, contact Sophos Technical Support who will fix the MigrationData.xml file by hand and then you can retry the failed migration. |
The group {group-name} was not migrated to use a new updating policy. It will continue to use the legacy updating policy {policy-name} currently assigned to it. |
Errors
| Error Message | Solution |
|---|---|
|
| Please contact Sophos Technical Support, who will help you to migrate to the new version. |
|
| Check the state of message router (inglés) on the host running Enterprise Console and the host identified by the router address. Restart any messaging system services (inglés) on both hosts, then retry the migration. |
Failed to receive a reply from the endpoint with the messaging system address {router-address} when attempting to delete migration data remotely. | Not critical. Delete the file MigrationData.xml in the SUM installation folder manually. |
Failed to send a request to the endpoint with the messaging system address {router-address} to request it to update itself after migrating the EM Library settings to the update manager. | Not critical. Make the server update itself from the “Update Managers” view in the console (inglés). |
Timed out waiting for product information. | If the problem persists: Check the state of message router (inglés) on the host running Enterprise Console and the host identified by the router address. Restart any messaging system services (inglés) on both hosts, then retry the migration. Finally, if the all else fails, Configure Update Manager manually (inglés). |
Timed out while processing migration data. | Retrying migration should usually fix the problem. |
Received invalid migration data from the endpoint with the messaging system address {router-address}. | Configure Update Manager manually (inglés). If that doesn't work, see Retrying a failed migration to the update manager in Enterprise Console 4 (inglés). Finally, if you still can't get it to work, collect the following logs to send to Sophos Technical Support:
|
Cannot migrate the EM Library settings because EM Library has no primary updating source configured. | See Retrying a failed migration to the update manager in Enterprise Console 4 (inglés). |
Cannot migrate the EM Library settings because EM Library is publishing a custom package named {package-name"}. | See Retrying a failed migration to the update manager in Enterprise Console 4 (inglés). Unsubscribe EM Library from any custom packages. |
Failed to acquire product information required to migrate the EM Library settings to the update manager. | Check the state of message router (inglés) on the host running Enterprise Console and the host identified by the router address. Restart any messaging system services (inglés) on both hosts, then retry the migration. Configure Update Manager manually (inglés). Finally, if you still can't get it to work, collect the following logs to send to Sophos Technical Support:
|
|
| Configure Update Manager manually (inglés). Also, collect the following logs to send to Sophos Technical Support:
|
Could not find a network path to the update manager's updating source {uri}, migrated equivalent of EM Library's updating source {uri}. | If the problem persists, Check your EM Library settings and make any necessary changes. |
|
| Collect the following logs to send to Sophos Technical Support:
|
Received unexpected indication that this EM Library does not have any settings that could be migrated to the update manager. The EM Library migration data should be regenerated. | See Retrying a failed migration to the update manager in Enterprise Console 4 (inglés). |
This method should never be called when there are still leagcy policies in use. | See Retrying a failed migration to the update manager in Enterprise Console 4 (inglés). |
Related articles
distribution shares, advanced options, software subscriptions, schedule, Could not find a network path, unexpected indication, regenerated, SUMSi necesita más ayuda, póngase en contacto con soporte técnico.
- Artículo ID: 59861
- Creado: 11 jun 2009
- Modificado: 7 abr 2010
