Could not bind the object with the name aa....aa, because another object with the same name has already existed in the naming service.

aa....aa: User-specified name

Description

The object with user-specified name (aa....aa) cannot be registered because another object with the same name already exists in the naming service.

When a distributed object or a context with a name is registered, the name already registered in the naming service cannot be used.

However, even if the name does not match completely, there are cases when the object can be registered and when the object cannot be registered. Each case is described below:

When the object can be registered

After assigning an optional name "A/B/C" to a certain object and deploying it, and if another object is assigned an optional name "A/B/D" and deployed, this message will not be displayed and the object can be registered without any problem. This is only because the context "A/B" with same name is used therefore another object that was newly registered is not recognized..

When the object cannot be registered

After assigning an optional name "A/B/C" to a certain object and deploying it, if another object is assigned an optional name "A/B/C/D" and deployed, this message will be displayed and the object cannot be registered. This is because an attempt is made to register the context with a name even though the distributed object is already registered in "A/B/C", therefore when another object is newly registered, it is recognized as another object.

Action

Check the erroneous user-specified name (aa....aa), change it to another name, and then re-execute the process.