Can't add mailbox to existing user
Hi - I just ran through the installation and have basically a new forest with 1 DC, and a separate member server for Ex2k7. Domain name is tater.com and org name (new) is Mater. Installation seemed to work fine, and I can create a new user plus mailbox in EMC and it works. However, if I try to add a mailbox to an account that was created in ADUC (plain account - no email address or anything like that added), I get an error message that pops up with "Path cannot be null. Parameter name: path". When I click ok, I get the following: Summary: 1 items. 0 succeeded, 1 failed. Elapsed time: 00:00:15 shrekFailed Error:Path cannot be null.Parameter name: path Warning:An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance of an object. Management Shell command attempted:Enable-Mailbox -Identity:'tater.com/Users/Ogre, Shrek D.' -Alias:'shrek' -Database:'CN=Mailbox Database,CN=First Storage Group,CN=InformationStore,CN=EX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Mater,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=tater,DC=com' Elapsed Time: 00:00:15 Any ideas what I'm doing wrong? Thanks! - Brian
August 2nd, 2006 9:12pm

Brian, If you launch ADUC on your Exchange server and right-click on the user account, do you have an Exchange Tasks option? If so, see if there is an option to "Remove Exchange Attributes". I know I've seen some strange oddities in the past with Exchange 2007 and existing user accounts.
Free Windows Admin Tool Kit Click here and download it now
August 2nd, 2006 10:49pm

Brian - I've repro'd this same behavior and it appears to be related to having a comma in the identity that's being passed. Can you confirm the same problem doesn't occur if the comma is not in the display name you use when you create the user (or if you rename the object in ADUC so that the "name" column doesn't contain a comma)? I've opened a bug, as this should definitely work when there's a comma in the CN. Evan Dodds
August 2nd, 2006 11:28pm

Hi Evan - yes, removing the comma did solve the problem, thanks! I used ADSIedit to set the display specifier to "lastname comma space firstname space initial period" so new accounts would use that format as we do in our production environment. For the time being I'll remove all the comma's. Thanks again!
Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2006 2:35pm

Hi Ben - I don't have any Exchange options in ADUC on the Ex2k7 server when I click on the problem user(s)- I thought all Exchange functionality was removed from ADUC?
August 3rd, 2006 2:36pm

Maybe I'm not supposed to say this, but if you re-run adminpak.msi, you'll get them back. :-D
Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2006 4:15pm

Actually, yes the problem is in the comma, but DisplayName is irrelevant here, - guilty is the FullName. Just a small correction.
September 7th, 2006 8:13pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics