Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Outlook has found more than one" pop up when editing/saving contacts
We have an executive user who when accessing contacts via Outlook client, upon editing a contact and then trying to close/save the changes, Outlook would try to verify the name of the contact but would be unable to find a match.
The really odd part is that the name it is trying to check isn't the contact that you've just edited.
For example: If I edited John Doe, when I saved the contact, the pop up says, that Outlook found more than one Ralph Malph.
Further, the person Outlook is referencing Ralph Malph doesn't exist in contacts.
His admin, has editing access to his contacts and I saw this behavior on her pc, outlook client but within his contacts.
I created an outlook profile for the Exec on another laptop saw this same behavior.
And of course, I've witnessed the behavior directly on the production machine the exec uses.
There's no rhyme or reason, and the next day the problem was gone, but it came back a few days later.
Attached is an example of the message. In this case, Outlook was unable find a match for "Jane Done"... but I was in John Smith's contact information.
I have fooled with the address book order, but that doesn't change the behavior.
Outlook 2007 SP3
Exchange 2010
The really odd part is that the name it is trying to check isn't the contact that you've just edited.
For example: If I edited John Doe, when I saved the contact, the pop up says, that Outlook found more than one Ralph Malph.
Further, the person Outlook is referencing Ralph Malph doesn't exist in contacts.
His admin, has editing access to his contacts and I saw this behavior on her pc, outlook client but within his contacts.
I created an outlook profile for the Exec on another laptop saw this same behavior.
And of course, I've witnessed the behavior directly on the production machine the exec uses.
There's no rhyme or reason, and the next day the problem was gone, but it came back a few days later.
Attached is an example of the message. In this case, Outlook was unable find a match for "Jane Done"... but I was in John Smith's contact information.
I have fooled with the address book order, but that doesn't change the behavior.
Outlook 2007 SP3
Exchange 2010
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Having the same problem on another PC is leading to a "server" problem - in you case probably a mailbox problem.
You coud try, if having proper access to the Exchange server, to see if there is any mailbox corruption problem.
For example you could use instructions from here: Create a Mailbox Repair Request - especially the ones from section Use the Shell to detect corruptions for a mailbox to see if there is any problem with it and eventually to repair it.
You coud try, if having proper access to the Exchange server, to see if there is any mailbox corruption problem.
For example you could use instructions from here: Create a Mailbox Repair Request - especially the ones from section Use the Shell to detect corruptions for a mailbox to see if there is any problem with it and eventually to repair it.
In looking at the origin of the contacts the ones that seem to be effected were created from his admin assistants from years ago. These assistants are no longer with the company so their network accounts of course don't exist. We're thinking that the somehow some kind of check is running against these orphaned contacts. With Microsoft we were able to strip the "From" field which equals who created the contact -- then put the contact back and everything seemed fine. Still researching..
Still sorting through this but it's looking like Contacts created by admin assistants that are no longer here are the ones having the problem. The theory makes sense, but not sure why it would start all of a sudden happening now. The contacts themselves have been in his contact list for yearrrrrrrrs.
See if this article will help you: Finding Orphaned Delegates in Exchange 2007 using a powershell script.
Great news. It seems as though the contacts that are effected are those where the delegate that created the contact doesn't have an exchange mailbox.
It wasn't enough to reenable the mailbox. We had to
1. Reenable the active directory account
2. Add an actual email account to the mailbox
3. Unhide the account in the GAL
Then go into the screwed up contacts, and open one of the effected ones. Then save and close it again. Fixed.
Any contact you open and resave will be fixed but if you hide the mailbox from GAL the pop up appears again.
For example:
Steve Urkel contact is fixed if I open it and save it again.
hide or kill the mailbox and the contact is still fixed.
But if you hide/kill the mailbox and go to another effected contact the problem is there.
So basically, I have to reenable the mailboxes, add email accounts, and unhide them from GAL, then go into the user's contacts and open & resave over 700 contacts, then kill the mailboxes associated.
UGH.
It wasn't enough to reenable the mailbox. We had to
1. Reenable the active directory account
2. Add an actual email account to the mailbox
3. Unhide the account in the GAL
Then go into the screwed up contacts, and open one of the effected ones. Then save and close it again. Fixed.
Any contact you open and resave will be fixed but if you hide the mailbox from GAL the pop up appears again.
For example:
Steve Urkel contact is fixed if I open it and save it again.
hide or kill the mailbox and the contact is still fixed.
But if you hide/kill the mailbox and go to another effected contact the problem is there.
So basically, I have to reenable the mailboxes, add email accounts, and unhide them from GAL, then go into the user's contacts and open & resave over 700 contacts, then kill the mailboxes associated.
UGH.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial