After I try to mail enable a public folder in the Exchange System Manager, it should automatically generate an SMTP address. But when I then right-click on the folder and select Properties, I get the following error: The mail proxy for this folder can not be found. The may be due to replication delays. The mail enabled pages will not be show. ID no: c1038a21 Exchange System Manager I waited a few days and try to mail enable other public folders but I get the same error. In the application log of the Exchange Server, I have many of the following error: Event Type: Warning Event Source: MSExchangeIS Event Category: General Event ID: 9543 Date: 10/20/2010 Time: 9:25:42 AM User: N/A Computer: EXCH3 Description: Unable to create Public Folder proxy object for folder "PF Test 2" in the Active Directory. For more information, click http://www.microsoft.com/contentredirect.asp. A google search yield the following Microsoft KB article: http://support.microsoft.com/kb/328740 KB328740 that talks about the PR_PF_PROXY property not matching the GUID in the Microsoft Exchange System Object but neither this property field nor the system object exists. It appears that there is some sort of AD corruption or permissions problem with the Microsoft Exchange System Objects folder that nothing new can be created in it. I have another problem that I believe is related to this where I cannot mount any new mailbox store I try to create. With that, I get the following errors: An internal processing error has occurred. Try restarting the Exchange System Manager or Microsoft Exchange Information Store service, or both. ... ID no: c1041724 In the application log, the following errors appear: Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9546 Date: 10/6/2010 Time: 1:13:33 PM User: N/A Computer: EXCH3 Description: Failed to create the Event Registration Mailbox for Database First Storage Group\Mailbox Store (<server name>). Error - 0xbf69. For more information, click http://www.microsoft.com/contentredirect.asp. I found the following KB article and discovered a system mailbox object that I cannot locate the mailbox store of the GUID on the Exchange Server but does reference one of my Exchange Servers. http://support.microsoft.com/kb/274534 I wonder if they are related where I have AD corruption around the Microsoft Exchange System Objects folder that nothing new can be created in it. I am thinking about trying to delete that extra system mailbox object but I don't want to make things worse. Any ideas?Steve

Hi Steve, you need to ge here for resolve this issue. Please check and post if you see some more event log in event viwer for SA. XADM: Event ID 9543 Message Occurs When You Try to Create a Mail-Enabled Public Folders:: http://support.microsoft.com/kb/327841 Anil

Thanks for replying. I checked each Exchange Server and I verified that every Exchange services is using the "Local System" account. So I do not believe that this is the issue. I do not see any other application warnings or errors. Any other ideas?Steve

Hi Steve, Based on your description, I understand that you have received the error c1038a21 when you tried to enable the public folder. There are some possible causes for the c1038a21 error when creating a new public folder. 1. RUS is not stamping public folders with proxy addresses. 2. The Microsoft Exchange System Objects folder is not located in the root of the domain. 3. The ExchangeApplicationPool has been deleted from IIS. Please follow the steps to isolate the issue: Step1: Create a new user. In Active Directory Users and Computers (ADUC), create a new user with mailbox. After some time, go to the Properties page of this user and click Exchange Addresses tab. Check to see if the user has been stamped with the correct email address. If not, it may be the RUS issue. Step2: Check the Microsoft Exchange System Objects folder. Start ADUC, click View -> Advanced Features. Expand the domain, make sure the Microsoft Exchange System Objects folder is listed in the left pane. Right click Properties and click on Security tab, make sure Exchange Domain Servers, Exchange Enterprise servers have full permission to the container. Authenticated users group has the Read permission to this folder. Step3: Check the ExchangeApplicationPool. Start IIS manger, expand Application Pools -> ExchangeApplicationPool, and make sure it's running. In the right pane, make sure the /Exchange, /Exadmin, /ExchWeb, /ExchWeb/Bin, /Public is running under this application. I look forward to hearing from you. Best regards, Serena

Thanks for replying Serena. I am able to create email addresses for new users so I don't think it is step 1. Step 2 seems to be the problem. Exchange Domain Servers is not listed and Exchange Enterprise server only has "special" permissions. Authenticates users do have read permissions. It appears that the permissions are all off. I remember someone else in my company mentioning that they had AD corruption due to a an offline domain controller coming back online after an long period of time which resulted in tombstone records and AD permissions being altered. It looks like we still have corruption from this. Can someone list what the default permissions for the Microsoft Exchange System Objects folder should be?Steve

Hi Steve, First, thanks for your reply. The second, for your specific issue, I recommend you perform the following action: Step1: Stop and restart each of the Exchange services: System Attendant service Exchange Information Store Service Step2: Run Exchange 2003 Setup again with the /DomainPrep switch. This will correct the membership/permissions required for Exchange server. Last, here are some articles will help you, Working with Public Folder and Mailbox Permission: http://technet.microsoft.com/en-us/library/aa996122(EXCHG.65).aspx (mostly in the part of Maintaining the Minimum Permissions Required for Mail-Enable Public Folders) Working with Store Permission in Microsoft Exchange Server and Exchange Server 2003: http://www.microsoft.com/downloads/en/details.aspx?familyid=2ae266f0-16b7-40d7-94d9-c8be0e968a57&displaylang=en Please feel free to let me know if you have any questions, and it is my pleasure to have a further discussion with you. Best regards, Serena

Thanks for your reply Serena. This is very helpful. For Step1: I have 3 back-end servers and 3 front-end servers. Do I stop and restart the SA and IS services on each individual Exchange Server? Can these services be running when I perform the /DomainPrep again? These servers have been rebooted recently so do you think this is necessary? For Step 2: Beside correcting the permissions, is there any effect to existing mailbox stores or public folders that I need to be concerned about? My main concern is that I do not make the Exchange environment worse. Current mailbox stores are mounted and I can create new mailboxes but I cannot mount any newly created mailbox stores nor mail-enable any public folder. ThanksSteve

Hi Steve, Thank you for your reply. I am very happy to work with you. If you have already rebooted your server, you can ignore the step1. And for the second scene, in your last post, you said the Exchange domain servers do not display when you click the security tab. We all know that, domainprep will create the Exchange domain servers, so it is why I recommend you run domainprep. The document does not indicate that domainprep will affect the mailboxes. Here are some references for you, Forestprep and Domainprep Explained in Detail: http://www.msexchange.org/tutorials/Forestprep-Domainprep-Explained.html How to Run Exchange Server 2003 DomainPrep: http://technet.microsoft.com/en-us/library/aa997526(EXCHG.65).aspx How to Verify that ForestPrep and DomianPrep Completed Successfully in Exchange 2000 Server or Exchange Server 2003: http://support.microsoft.com/kb/274737 Please feel free to let me know if you have any questions. Best regards, Serena

I didn't run the domainprep but I did give full control permissions for Exchange Domain Servers and Exchange Enterprise Servers to the Microsoft Exchange System Objects folder and the problem is now fixed! I am now able to mail enable public folders and new mailbox stores are mounting. Thank you so much!Steve

Actually, I still have a problem where the mail-enabled public folders are not getting an automatically generated email address from the RUS. It looks like I could probably manually create an email address for them but it is not auto generating. Do you think I need to set more permissions elsewhere?Steve

Hi Steve, Well done. The right permission is the prerequisites of creating mailbox or public folder. We should grant the Exchange Domain server and Exchange Enterprise servers full control permission, Authenticated users group should be granted the Read permission to the folder. And then please check out the interval time of RUS by following the steps below: Open the Exchange System Manager. Click the Recipients Navigate to the Recipient Update Services. Right-click the Recipient Update Service (Enterprise Configuration) and Recipient Update Service (SOFT) and choose Properties. Chose “Always run” in the Update interval field of the General tab. And here are more information about how to troubleshooting RUS. Troubleshooting the Recipient Update Service (RUS) using Event Logs – Part 1: http://msexchangeteam.com/archive/2004/07/07/175444.aspx Troubleshooting the Exchange Recipient Update Service (RUS): http://www.msexchange.org/articles/Troubleshooting-Exchange-Recipient-Update-Service-RUS.html Please feel free to let me know if you have any questions. Best regards,

I still have not resolve my RUS issue with public folders. The RUS is generating email addresses for new user account but not for new mail-enabled public folders. I manually created an SMTP and x.400 email address for a new public folder but it is not showing up in the Global Address List at all. I enabled diagnostic logging for MSExchangeAL and MSExchangeSA to maximum for the options the articles above describe and I see no entries at all for MSExchangeAL. I don't see any other error message related to this. I created a few more test mail-enabled public folders and they do not get email addresses either. Any ideas?Steve

The Best Practice Analyzer is reporting that the 'gatewayproxy' attribute does need to be cleared out of the Recipient Update Services. Do you think this is the problem? Here is the message: The 'gatewayProxy' attribute for Recipient Update Service 'Recipient Update Service (Enterprise Configuration)' contains old data that was not fully processed. I would think this needs to be fixed anyway but I am not sure why this would cause public folders from getting new email addresses while new users can. Steve

Hi Steve, Have you read the following KB article? If not, please refer to the following KB to clear gatewayProxy attribute. The gatewayProxy Attribute on the Recipient Update Service Object is not Cleared: http://support.microsoft.com/kb/821743/en-us I look forward to hearing your update. Best regards, Serena