Outlook says "The action could not be completed. The action could not be completed." (yes, twice) when Check Names pressed

Here's the scenario.

I am in a small organization using Exchange 2003 and a combination of Outlook 2002 and 2003. We migrated to a new forest topology, as we have offices in different parts of the world. We did clean installs of everything in the new domains (Win2k3, Exchange 2k3 SP1, etc). When we migrate the users' Outlook profiles from the old domain to the new, we have problems with some, but not all users. Some users, everything goes fine. The other users get this error when they click "Check Names" in the profile config:

"The action could not be completed. The action could not be completed." (yes, twice)

The Outlook Profile will open a new window when they click OK on the error message and they get another opportunity to click a different "Check Names" button. That one says: "The name could not be resolved. The action could not be completed."

To add depth, I am one of the users it works fine for (on my workstation), but if I go and setup my profile on an offending user's workstation, I get the error as well. That rules out server problems, I think.

I have looked at a number of KB articles, including: 833399, 322832, 838800 and a few others I didn't write down. Nothing seems to work. I've even re-installed (clean with reformatting) win2k3 and exchange 2k3 sp1.

The offending workstations are in the same domain as the exchange server, as are the working workstations. I can't find what the difference is between the two. This has been aggravating for 2 weeks now. Please help!

BTW: OWA and POP3 work great with everyone, including the users who can't use outlook.
Who is Participating?
ee_ai_constructConnect With a Mentor Commented:
Question answered by asker or dialog valuable.
Closed, 500 points refunded.
ee_ai_construct (replacement part #xm34)
Community Support Admin
geckoxAuthor Commented:
I figured out what was wrong. I didn't have a forwarder configured in the child domain dns servers to point to the parent domain's dns server. Once the forwarder was configured, it worked wonders. I only wish that it didn't work at all for anyone, rather than work sometimes and not others. That would have made it easier to diagnose.
I found this same thing.  It ended up being a corrupt Outlook profile.  I deleted the default Outlook profile, created a new one, and it worked.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.