Using Exchange 2003 Enterprise.Have an issue with a number of calendar based public folders. Within a single folder we have created multiple folders, with Appointment types. These are used for booking equipment. For example: folder 1: Digital Camera folder 2: Laptop folder 3: Projector folder 4: VideoUsing Outlook we can book appointments in all folders. Using OWA we get an error on some of them (folder 1 and 3) while some work (folder 2 and 4)!!The error displayed in OWA (using either IE or Firefox) when trying to create a calendar item is: "The action can't be performed"We have checked the followed:permissions - all the same. we have even removed and reapplied all rights. Besides, you can do it using Outlook so it isn't rights.replicas - all the same.limits - There are no limits! I have tested applying limits and it still doesn't work.KB 310440 (http://support.microsoft.com/kb/310440/en-us) - all servers (front-end and back-end) have the correct registry key. Besides, it works for some folder and not others. If it was this issue all would be affected.We could recreate the folders again, because new folders work. However we have hunders, all with existing data so that isn't a good solution.Any ideas?

Hi, 1. First, please re-register msdaora.dll which is present in C:\Program files \System\oledb 2. Please use ADSIEDIT verify everyone permission should set on Org level and delegate down. You can add everyone on Org level with default permissions and click Advanced, then set them to "Apply onto this object and all child objects". Verify it inherited to store level 3. Also please check the Security list whether it entries for Everyone and Anonymous (for example, "Create public folder", "Create named properties in the information store", etc.).You can refer to a good exchange server and add the lost entries back. 4. Checked the LegacyExchangeDN Value for the working and nonworking user. Found Different. Please changed the LegacyExchangeDN. And then force the replication between DC. Note: The ADSIEdit.exe tool is an MMC snap-in that you can use to edit objects in the Active Directory database. For more information about ADSIEdit.exe, in Help and Support Center for Windows Server2003, click Tools, and then click Install Windows Support Tools Hope it helps. Xiu

Thanks Xiu for replying.As we are seeing the issue only on some of the folders, and not all of them, are your points 1 - 3 still valid? I have however checked the permissions, both on the org and on the folders. All OK.As indicated in the original post "permissions - all the same. we have even removed and reapplied all rights. Besides, you can do it using Outlook so it isn't rights."As for using ADSIEdit ... some of the folders are under the domain in the "Microsoft Exchange System Objects" folder and some are not. Using PFDAVAdmin however you can find them all and see that some have the LegacyExchangeDN and some don't. Of those that do have the LegacyExchangeDN, some work in OWA and some don't. Of those that don't have the LegacyExchangeDN property, some work with OWA and some don't.Anyway, using PFDAVAdmin I removed the LegacyExchangeDN property value from one that doesn't work in OWA, and it promptly created another value. Same result as before.Any other ideas?

Hi, For step 1,please check that dll from the problematic computer. Also I recommend you to go through step3 to check it. Xiu

Thanks XiuWe have 8+ Back-end Exchange servers. The issue is with all servers the replica of these public folders are located on. It is folder specific not server specific. Are you suggesting a dll corruption/mis-configuration/mis-registered issue could be so specific to allow appointments to be created in one folder consistently while not allowing appointments to be created in another folder consistently?I have checked the "everyone" rights and they are the same for folders that work and ones that don't.

For all those interested we solved this ourselves.Under the General properties of the public folder, viewable from Outlook, there is a section with the label "When posting to this folder, use:"Normally this should be "IPM.Appointment". On the affected public folders a custom form was selected, called "Resource Booking", even though that form is not in the Org Library.Seems Outlook can deal with this correctly but OWA can not. Solution: Changing the form back to "IPM.Appointment" resolves the public folder issue with OWA.

Glad to hear the issue has gone away. Thanks for your sharing here. Regards, -Xiu