Filter
Top Products
ANR3238E command: This object cannot be renamed because it is associated with one or
more configuration profiles.
Explanation: This message is issued on a configuration manager when an attempt
is made to rename an object that is associated with one or more configuration
profiles. Associated objects cannot be renamed because the enterprise configuration
facility does not support renaming of objects.
System Action: The command fails and server operation continues.
User Response: If you must change the object name you can delete the object,
define it with a new name, and then define a profile association to the new object
(unless a wildcard profile association already exists). This will cause the object to
be deleted and re-defined on managed servers with subscriptions to the profiles with
which this object is associated.
ANR3350W Locally defined domain domain name contains at least one node and cannot be
replaced with a definition from the configuration manager.
Explanation: During configuration refresh processing the indicated locally defined
domain could not be replaced with a definition from the configuration manager. The
domain definition was not replaced because the domain still contains one or more
assigned nodes.
System Action: Refresh processing continues, but this domain is not replaced. The
system will attempt to replace the local domain during later configuration refresh
operations.
User Response: If you want existing nodes to be assigned to the domain from the
configuration manager, you can temporarily assign them to another domain. After
the domain definition has successfully been propagated from the configuration
manager, reassign the nodes to the new domain. Alternatively, if you want to
prevent further attempts to replace the local domain definition during configuration
refresh processing, delete the subscription to the profiles with which domain domain
name is associated.
ANR3351W Managed domain domain name contains at least one node and cannot be deleted
during configuration refresh processing.
Explanation: During configuration refresh processing, the enterprise configuration
facility attempted to remove the indicated domain because it has been deleted from
the configuration manager or because the profile association no longer exists. The
domain could not be deleted on the managed server because it still contains one or
more nodes.
System Action: Refresh processing continues, but this domain is not deleted. The
system will attempt to delete the domain during later configuration refresh
operations.
466
Version 3 Release 7