Troubleshooting RPC_S_NO_MEMORY Error When Adding ESXi Hosts to vCenter

Introduction:

When migrating a vCenter server from one domain to another, it is not uncommon to encounter issues with adding ESXi hosts to the new vCenter. One such issue that we recently faced was an RPC_S_NO_MEMORY error while attempting to add an ESXi host to the target vCenter. In this blog post, we will explore the cause of this error and provide a solution to resolve it.

Background:

We recently repointed our vCenter server from domain XXXvcloud.local to XXXvcloudm0177.local as part of maintenance activities. After the repointing, we were unable to add ESXi hosts to the target vCenter. When attempting to add a host, we received an RPC_S_NO_MEMORY error. We tried temporary workarounds such as switching the Certificate Mode to thumbprint mode, but the issue persisted.

Cause of the Issue:

The cause of the RPC_S_NO_MEMORY error is due to the presence of old domain name records in the adcreds-domain table in the vCenter database. When the vCenter server was repointed to a new domain, the old domain name records were not removed, causing conflicts and errors when attempting to add ESXi hosts.

Solution:

To resolve the RPC_S_NO_MEMORY error, we need to update the record in adcreds-domain table with the new domain name. Here are the steps to follow:

1. Connect to the vCenter server using SSH and open a shell.

2. Run the following command to check the adcreds-domain table:

“`sql

select * from config_pairs where name = ‘adcreds-domain’

“`

This command will display the current domain name records in the adcreds-domain table.

3. Update the record in adcreds-domain table with the new domain name using the following command:

“`sql

update config_pairs set value = ‘XXXvcloudm0177.local’ where name = ‘adcreds-domain’

“`

This command will update the adcreds-domain record with the new domain name.

4. Restart the vCenter services to apply the changes:

“`bash

sudo service vpxd restart

“`

After completing these steps, we were able to add ESXi hosts to the target vCenter without any issues.

Conclusion:

In this blog post, we explored an issue where adding ESXi hosts to a vCenter server after repointing it to another domain resulted in an RPC_S_NO_MEMORY error. We identified the cause of the issue as old domain name records in the adcreds-domain table and provided a solution to update these records with the new domain name. By following these steps, you should be able to resolve the RPC_S_NO_MEMORY error when adding ESXi hosts to your vCenter server after repointing it to another domain.