Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am getting the error "The Name cannot be resolved. The operation failed." for users of a certain database on our Exchange cluster for our tests to a new server migration with a Client Access Server.

The email actually worked after it was moved to a new server until we deleted the address and attempted to again resolve the user account and server. We can't get it to work at at all now.

The users cannot resolve the Microsoft Exchange Server or Mailbox when entering the info into a new account and I ran a test with the account at and the error below came up:

Testing the Name Service Provider Interface (NSPI) on the Exchange Mailbox server.
An error occurred while testing the NSPI RPC endpoint.

Test Steps

Attempting to ping RPC endpoint 6004 (NSPI Proxy Interface) on server (MailServer the account was migrated from).
The endpoint was pinged successfully.

Additional Details
RPC Status Ok (0) returned in 953 ms.
Testing NSPI "Check Name" for user against server (MailServer the account was migrated from).
An error occurred while attempting to resolve the name.

Additional Details
An unexpected error was returned from NspiResolveNames. Code: 2147500037

Auto discover is set up as well and points to the proper server to connect to but the internal server name(where you enter the account as well) shows the old server.

Any ideas would be appricated! Thanks

share|improve this question
up vote 0 down vote accepted

Figured it out. We updated the old and new server to the latest version and the problem went away. Thanks.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.