Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 229
  • Last Modified:

Exchange user logging into outlook

I have one specific user that I can not locate an error I am receiving.  

I created the user as I normally do on the Exchange server that has AD as a secondary role, then created the mailbox.

I can login to the OWA just fine, however, when I try to connect with outlook (2010 on windows 7 32-bit) it continues to prompt for the password.

I tried creating another user and connecting, which worked fine.

We work in a fully virtualized environment with linked clones that have a a separate persistent disk.  I have deleted and rebuilt the user, email box, desktop and disk with no change in behavior.

If i try, for example on the OWA to change the password, i get the following error "This feature isn't supported in the light version of Outlook Web App.
This feature isn't supported if Outlook Web App is set to maximize the blind or low vision experience.".

I am not using the light version. If I do use the light version and do the same thing, I get this error
"A problem occurred while trying to change the password.
Click here to continue working.
The domain name of the user couldn't be retrieved"

This has never happened before and seems to be limited to this user only.  I thought maybe an email or AD cleanup would help, but have been a bit nervous of that process.

Any insight would be helplful.
0
tommy porter
Asked:
tommy porter
  • 6
  • 2
1 Solution
 
Don ThomsonCommented:
Have you checked the HOSTS file to see if the Exch Server is being redirected on that PC?

Have you tried to logon to exchange from another PC?
0
 
tommy porterAuthor Commented:
I checked the HOSTS file and there was nothing there.  However, I checked a desktop of one that works and it was the same.  Trying that user on a different laptop and not a linked clone yields the same behavior.



# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#      127.0.0.1       localhost
#      ::1             localhost
0
 
Don ThomsonCommented:
Could it be that Exchange thinks it's a reserved name. Try a slight variation of the name
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
tommy porterAuthor Commented:
I tried a variation of the name as well, with the same results.  I tried a completely different on (my own) on the vm and it worked no issues.  

I created a new username along the same lines:  jz****2 along with the same name with a 2 at the end, just to try something different.
0
 
tommy porterAuthor Commented:
I found this site:  http://www.concurrency.com/infrastructure/removing-ghost-mailboxes-from-exchange-with-remove-mailbox-and-storemailboxidentity/

There were 4 copies of the original name and one copy of the new name and am purging them.
0
 
tommy porterAuthor Commented:
Update - we had to restore the exchange server last week.  it seems that all accounts created after (retested with multiple new accounts) are displaying the same issues.

I searched the errors i was receiving in the OWA and everything I am finding is pointing me towards SYSPREP.  I can't change the password on those accounts through OWA but I can on any created before then.
0
 
tommy porterAuthor Commented:
Ran a DCDIAG on the server.  Found that the replication service was in a paused state after the server restore from backup.

Rebooted the Exchange server and the replication service started.  Shortly after, I was able to then log on as normal on all accounts created after server restore.

Thanks for all the help.
0
 
tommy porterAuthor Commented:
Found the error.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now