http://www.msexchange.org/articles/Finding-Duplicate-SMTP-Addresses.html
Shows how to find an email address within the Exchange infrastructure.
http://www.msexchange.org/articles/Finding-Duplicate-SMTP-Addresses.html
Shows how to find an email address within the Exchange infrastructure.
Setting up a second exchange server in the same routing group, all installed fine, however, after moving a mailbox to the new server and then sending an email to the mailbox, the mail got stuck in the queue on the first server.
Checked the common things like DNS, firewall ports etc. all looked fine. But still the mail would not go, also tried to send a mail from the new mailbox to a mailbox on the old server. Still no joy.
The two servers where on separate networks, with a Cisco 857 ADSL router at each site and a IPSec site to site VPN between them. Full all open IP access allowed from each server to each other. Couldn’t see the problem.
Then I found this from Microsoft: http://support.microsoft.com/kb/919091
Cause 5 – The IP inspect rule, on each of the routers I had one for SMTP. This appeared to be blocking an SMTP verb or something and causing the connection to stall with this strange error in the queue viewer on each server: the semaphore timeout period has expired.
Solution: I removed the IP Inspect rule from each router, (you will still probably need a tcp inspect to allow outbound smtp to the net. Rebooted the routers, and restarted smtp on each exchange server (just to be sure) and hey presto. Mails started to flow.
Now i can see about setting up a routing group connector!
This is not quite a how to, more a ramble of what I did one morning to try to resolve the problem with attempting to exmerge some psts in to an exchange server.
http://support.microsoft.com/?id=292509
http://support.microsoft.com/default.aspx?scid=kb;en-us;322312
First set the permissions then started to get this error:
Error configuring message service (MSPST MS) (MAPI_E_EXTENDED_ERROR) (CMapiSession::CreateEMSPSTProfile)
It appears to be a problem with the opening of the pst.
Then checked if there were any read only permissions on the pst file, nope added everyone full access to the file just to make sure.
Still getting the same error message.
Apparenltly the new outlook 2003 format for psts is incompatible with exmerge, to resolve this you need to
Create a new .pst file that is compatible with Outlook 97-2002.
On the File menu, point to New, and then click Outlook Data File.
To create a Microsoft Outlook Personal Folders File (.pst) that is compatible with Outlook 97-2002, click Outlook 97-2002 Personal Folders File (.pst), and
then click OK.
In the File name box, type a name for the file, and then click OK.
In the Name box, type a display name for the .pst folder.
Select any other options you want, and then click OK.
The name of the folder associated with the data file appears in the Folder List (Folder List: Displays the folders available in your mailbox. To view
subfolders, click the plus sign (+) next to the folder. If the Folder List is not visible, on the Go menu, click Folder List.). To view the Folder List, on
the Go menu, click Folder List. By default, the folder is called Personal Folders.
In theory the version of psts that are made by exmerge should be correct, this only looks like a problem with a import directly from outlook.
This looks like it will work now, however im getting this error now, (which I have seen before and at least know something about.)
Error opening message store (MSEMS). Verify that the Microsoft Exchange Information Store service is running and that you have the correct permissions to log
on. (0×8004011d)
This can be resolved by just adding the “send as” and “recieve as” permissions on the everyone group to the mailstore, but this is the nasty bodge way.
http://support.microsoft.com/kb/322312/
This says to delegate Exchange Full Administrator to the exmerge group and then restart the IIS Admin Service.
Also make sure that the emerge group has all the allow permission boxes checked, probably not necessary but its worth doing just to get the thing to work.
This doesnt work though.
The problem is the permissions are set for the exmerge group as having both “send as” & “recieve as” allow but also deny too. The deny will always get
prefference. I need to stop the inheriting permissions somehow.
To do this I did this to add the security tab:
Security Tab Not Available on All Objects in System Manager
View products that this article applies to.
Article ID : 259221
Last Review : April 25, 2005
Revision : 1.3
This article was previously published under Q259221
SUMMARY
In Exchange System Manager, the Security tab is displayed in an object’s properties. However by default, the Security tab is displayed only on the following
objects:
• Address Lists
• Global Address Lists
• Databases (Mailbox stores and Public Folder stores)
• Top Level Public Folder Hierarchy
MORE INFORMATION
To display the Security tab on all objects, you must add the following registry key.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot
guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
1. Start Registry Editor (Regedt32.exe).
2. Locate the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Exchange\ExAdmin
3. On the Edit menu, click Add Value, and then add the following registry value:
Value Name: ShowSecurityPage
Data Type: REG_DWORD
Value: 1
4. Quit Registry Editor.
This change takes effect immediately; you do not need to restart Exchange System Manager. This change only affects the currently logged on user. If the
ShowSecurityPage value is not present or is set to 0, the Security tab is available only on the objects listed in the “Summary” section.
Now you can set the permissions at the root of the exchange organisation and remove those pesky “send as” & “receive as” permissions from the exmerge group.
Restarted the IIS admin and the Microsoft SA, to restart all the other settings and refresh the permissions.
Didn’t work.
The administrator user (that I am using for exmerge) also had the deny permissions set so I removed those and then restarted the iis admin service and the
microsoft sa too.
Didn’t work.
The domain admins and enterprise admins which is the account is also a group of also had the deny permissions set so I removed those and then restarted the
iis admin service and the microsoft sa too.
Did this and now the exmerge worked perfectly. However it is not the best way to have done it as anybody with admin privilages can do whatever they like to
the exchange system
So I readded the permissions for deny on “Send as” and “recieve as” for the administrator, domain admins and enterprise admins. Bounced IIS admin and also
the sa.
It looks like you need to make the exmerge group a universal group, this cannot be done when you are running in windows 2000 mixed mode, you need to raise
the functional level of your domain to Windows 2000 Native or windows 2003 only.
Once this is done, you can create a universal security group, or change your current exmerge group to use universal.
None of the settings microsoft suggest work, i’ve checked the other server and can’t see how it can possibly work.
removed the delgate permissions for exmerge group off the root.
Then readded them on the server directly.
This also did not work.
here’s how I fixed it.
Removed all that I had done up till now.
Added the exmerge group onto the mailbox store directly.
Set the permissions how I needed them.
IMPORTANT: logged off and on again. This updates stuff.
Now I could exmerge fine, a very long winded and strange one I must say.