Migrate Exchange Server 2010 Public Folder shared calendars to Exchange Server 2013

Dear All,
I have an question about calendars under public folder migrating to new exchange server 2013. When completed the PF migration progress, will it also migrate calendars under sub-folder under PF to new PF mailbox?
For example: in exchange 2010 PF:
In exchange 2013
\Public Folder\sales\A1_calendar
--->
\ Public Folder\sales\A2_calendar
---> ?
\Public Folder\sales\A3_calendar
---> ?
\Public Folder\sales\A4_calendar
---> ?
Thanks in advance.
Regards,
Willis Wong

Hi Willis,
This forum is for general questions and feedback related to Outlook. Since your question is more related to Exchange server, I'd recommend you post a new question in the Exchange forum for further assistance:
https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Similar Messages

Exchange Server 2010 public folder - Events show in SharePoint 2010 Calendar

I want to fetch items to SharePoint 2010 Calendar from Exchange Server 2010 Public Folder Calendar called Event. How can I achieve this ?

May be you can directly fetch whole public folder in sharepoint server
http://www.amrein.com/apps/page.asp?Q=5778
If this helped you resolve your issue, please mark it Answered

Exchange 2010 public folder not showing on exchange 20003 mailbox

Hi,
I have public folder on exchange 2003 and separate public folder on exchange 2010. On exchange 2010 user mailbox, I can see both 2003 and 2010 public folders. On exchange 2003 user mailbox, I can only see 2003 public folders. It is not the permission issue
as I have given the user "owner" right and see not able 2010 public folder inless i move 2003 user mailbox to 2010 exchange.
Appreciate if anyone could help me if to point me to directions or any hotfix I can run?
Thank you very much.
Pwint

Are you using OWA or Outlook to view the public folders?
If you're using OWA, the reason you can't see the folders is that OWA in Exchange 2003 uses WebDAV, which is no longer present in Exchange 2010.
If you're using Outlook, you'll need to use the troubleshooting logs to determine the cause of the problems.
It could be related to Outlook trying to connect directly to 2010 mailbox server instead of CAS. Because normally the mailbox server is installed without the CAS role, it does not allow a direct Outlook connection. Or it could be something else,
like authentication.

Exchange Server 2010 Public Folder Error!

I found that no one can sent email to our mail-enable public folder. there's a warning like below
Delivery has failed to these recipients or groups:
([email protected]) <[email protected]>
There's a problem with the recipient's mailbox. Please try resending the message. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: EXCHUB02.domain.com
[email protected]
#550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionNotFound:16.18969:B8000000,
17.27161:0000000054000000000000000000000000000000, 255.23226:2B0A0000, 255.27962:44000000, 255.17082:BFF9FFFF, 0.25697:00000000, 4.21921:BFF9FFFF, 255.27962:FA000000, 255.1494:35000000, 255.26426:96000000, 4.18236:BFF9FFFF, 4.7974:BFF9FFFF, 255.1750:43000000,
0.26849:43000000, 255.21817:BFF9FFFF". ##
Original message headers:
Received: from EXCMAIL02.domain.com ([fe80::7c57:574e:f764:e8f7]) by
exchub02.domain.com ([::1]) with mapi; Mon, 7 Apr 2014 15:47:55 +0700
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: "Admin" <[email protected]>
To: <[email protected]>
Subject: sdasd
Thread-Topic: sdasd
Thread-Index: Ac9SPhG67LrxITcEQjufincOJHZGwg==
Date: Mon, 7 Apr 2014 15:47:55 +0700
Message-ID: <[email protected]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <[email protected]>
MIME-Version: 1.0
Did you guys know what happen to my public folder? cause i can't find the right solution for my problem.

Please check out the below thread related to your query.
http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/c1fab3bd-589d-4c7c-8807-2eda93d11c27/
Hope it helps

Exchange 2010 - Public Folder Managment

I seem to have hit a bit of a stale mate with our exchange 2010 public folder management and while i think i see things set up wrongly - i'm not sure how to fix or what the consequences are if i did (and since i haven't yet built a sandbox test environment) i thought i would ask the spiceworks community for some helps and tips.So a little back ground first :two physical locations - one UK one USStretch DAGS with US-MBX replicating to UK-CAS and UK-MBX replicating to US-CASALL servers on the same domainProblem i am trying to resolve :One of our users based here in the UK travels to and manages some US staff now. US staff put holidays into a calendar in a public folder. The UK based manager would like to see this calendar.Sounds easy right? (maybe it is and i just need a clip around the napper with the manual).When i look at the public...
This topic first appeared in the Spiceworks Community

Are you using OWA or Outlook to view the public folders?
If you're using OWA, the reason you can't see the folders is that OWA in Exchange 2003 uses WebDAV, which is no longer present in Exchange 2010.
If you're using Outlook, you'll need to use the troubleshooting logs to determine the cause of the problems.
It could be related to Outlook trying to connect directly to 2010 mailbox server instead of CAS. Because normally the mailbox server is installed without the CAS role, it does not allow a direct Outlook connection. Or it could be something else,
like authentication.

Mail delivery to Public Folders stops when Public Folder database dismounted from old server. Old server to be decommisioned.

I have 2 Exchange 2010 SP3 RU6 servers. All Mailboxes and Public Folders have been moved from the old server to the new one. If I dismount the Public Folder database from the old server, delivery to mail enabled Public Folders stops. I
believe resolving this is the last step before decommissioning this old server and uninstalling Exchange from it.
Before I delete the Public Folder database and/or uninstall Exchange from my old server, what do I need to do to setup routing/transport of email to Public Folders on my new server?
I've used the MoveAllReplicas.PS1 script successfully and believe nothing remains on the old server. Do I simply need to remove all mail enabled Public folders now with the Remove-PublicFolder EMC command? Or is it a background kind of task that
automatically updates after some period of time and then messages just start delivering directly to the new location of my Public Folders?

Hi and thanks for your suggestion, but Get-PublicFolderMoveRequest is an Exchange 2013 command. I first ran the MoveAllReplicas script, probably a month ago. I've also used the RemoveReplicaFromPFRecursive script and
still it says that Replicase still exist within the Public Folder Database that I woul like to remove from my old server to be decommissioned. I've read of other people trying to uninstall Exchange from an old server that have encountered this error,
causing the uninstall to fail.   Get-PublicFolderStatistics -Server "oldserver" | Format-List returns:
RunspaceId               : 97d4eaaa-68e5-4c5f-ab61-f56de58fc01e
AdminDisplayName         : Nntp Control Folder
AssociatedItemCount      : 0
ContactCount             : 0
CreationTime             : 6/18/2002 8:42:31 AM
DeletedItemCount         : 0
EntryId                  : 000000001A447390AA6611CD9BC800AA002FC45A0300F020D914C926D011A40900C04FD7BD87FFFFFFFF00020000
ExpiryTime               :
FolderPath               : Nntp Control Folder
IsDeletePending          : False
ItemCount                : 0
LastAccessTime           : 8/11/2014 9:28:20 PM
LastModificationTime     : 11/28/2012 5:41:45 AM
LastUserModificationTime :
LastUserAccessTime       :
Name                     : Nntp Control Folder
OwnerCount               : 0
TotalAssociatedItemSize : 0 B (0 bytes)
TotalDeletedItemSize     : 0 B (0 bytes)
TotalItemSize            : 0 B (0 bytes)
ServerName               :
StorageGroupName         :
DatabaseName             : Public Folder Database 1
Identity                 : 000000001A447390AA6611CD9BC800AA002FC45A0300F020D914C926D011A40900C04FD7BD87FFFFFFFF00020000
MapiIdentity             : 000000001A447390AA6611CD9BC800AA002FC45A0300F020D914C926D011A40900C04FD7BD87FFFFFFFF00020000
OriginatingServer        : oldserver
IsValid                  : True
Here it shows the size and count are 0 (zero), so I should be good to go. But, I am unable to remove it due to the Replicas Exist error.
Elsewhere, I found a suggestion to clear the checkmark in the OAB 'Distribution' settings regarding Public Folders, but that didn't help. I've also seen posts saying to dismount the Public Folders, rename them and when mounting,
take the option to create a blank or empty Public Folder database. When I did that, the mail enabled Public Folders did not resolve when sending emails. I had to quick mount the saved copy of my Public Folder database.
So, regarding your suggestion, does Disabling and then Enabling mail enabled folders re-associate or register them with the current Public Folder database structure?
One more thing I found is that the get-mailpublicfolder command returns an error stating a folder is corrupt.
WARNING: The object ci.walla-walla.wa.us/Microsoft Exchange System Objects/Library Vacation Calendar has been corrupted, and it's in an inconsistent state. The following validation errors happened:
WARNING: Property expression "Library Vacation Calendar" isn't valid. Valid values are: Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One
or more periods may be embedded in an alias, but each period should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII
string in the e-mail address, which is generated from such an alias.
I don't see anything in the name of the folder, unless it actually has the " character embedded in it. But what is also odd is that I don't have a folder called "Library Vacation Calendar". It may be the remnant of something in the
past of a failed attempt. I do have a folder called VacationCalendar that the Library uses, and have even exported to PST and recreated without any impact to this problem. I do not know how to clear this condition, and assume it is responsible
for the Active Replicas error I get when trying to remove the PF database.

Outlook 2010 SP2 - Error when editing shared calendar: Post Exchange 2013 CU2 Migration

Hi there,
I have a strange comportment with Outlook 2010 SP2 and Exchange 2013 CU2 and i really need your help.
Frequently, when an user (who has the good permissions for) want to edit a shared calendar (edit a meeting or add one), he has this error message:
" Cannot display the folder. Your server administrator has limited the number of items you can open simultaneously. Try closing message you have opened or removing attachments and images from unsent messages you are composing "
I see anything in the Exchange server event log but i have each time, an error message in the client event log:
" Microsoft Office14 Alerts ID 300"
Everything work very well with Outlook 2013.
Many thanks in advance for your assistance, and I am looking forward to reading from you.

Hi,
According to your description, the issue is related to your Office 2010 client.
And the issue can be resolved by installing the Microsoft Office 2010 Deployment Kit.
Here are the steps you can refer to :
1. Open a command prompt with administrative permissions.
2. Browse to the directory that contains the Offvirt.msi.
3. At the command prompt, run the following command:
msiexec /i OffVirt.msi [licensing flags]
You must enter a correct licensing flag in the following list to correctly configure the Deployment Kit. Otherwise, functionality may be incorrect.
For more information, you can refer to the following article:
http://blogs.technet.com/b/virtualworld/archive/2010/07/07/microsoft-has-encountered-an-error-with-licensing-and-will-need-to-close.aspx
If you have any question, please feel free to let me know.
Thanks,
Angela
Angela Shi
TechNet Community Support

Unable to send to Exchange 2010 Public Folder after migration

Hi ,
We have migrated exchange 2003 server to 2010 and we migrated all public folders to new exchange 2010 server. But when attempting to send an e-mail to public folder 's e-mail address It says #550 5.2.0 RESOLVER.PF.Invalid; misconfigured public folder mailbox
##. Have you got any idea ? We can see all public folders in outlook client and owa.
Regards.

Hi,
First, please verify if the public folders have replicated successfully, check item counts between replicas. You can use the get-publicfolderstatistics command.
Besides, I recommend you try to mail-disable it and then mail-enable back to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2003 to 2010 Public folder Migration issue

I have successfully replicated our Exchange 2003 public folders to our exchange 2010 public folders using the addreplica script in exchange 2010 PS. I have moved all mailboxes to use the public folders on Exchange 2010. A couple of days ago I ran the
"moveallreplicas.ps1", and the command successfully ran and has removed all replica pointers in the exchange 2010 PF database pointing to the exchange 2003 database. In Exchange 2003 ESM, I still have the replication to all the PF databases, and
the 2k3 has not been removed, nor has the public folder instances folder count changed at all. In searching through the logs I am getting this error on the exchange 2003 event viewer for applications about every minute or less.
This is an SMTP protocol log for virtual server ID 1, connection #58254. The client at "xxx.xxx.xxx.xxx" sent a "xexch50" command, and the SMTP server responded with "504 Need to authenticate first ". The full command
sent was "xexch50 1076 2". This will probably cause the connection to fail.
The client IP indicated in the error is a Exchange 2010 server with the HUB/CAS roles loaded onto it. I am not sure if this is related or not.
I see some people have ran the move all replicas from the Exchange 2003 ESM, should I do that now? Is this even something to worry about since all my mailboxes are using the PF on 2010?
Thanks for any assistance!

I have looked at KB http://support.microsoft.com/?id=843106 and
it did not resolve the issue on the Exchange 2003 server or 2010.
Last night I put in the fix for the Event ID 36885, method three of this article http://support.microsoft.com/kb/933430/en-us,
and the errors on both servers seemed to go away, but then have started back up this morning after about seven hours of no errors. I thought the registry entry would fix the issue, and it appears it did, but not sure why it would come back like this. I may
try restarting the servers tonight, but kind of confused how this could still be an issue with the registry entry in place.

Exchange 2010 Public folder database size grown upto 1.22TB

I have situation to discuss , have three exchange public folder server with 2010Ent edt. One of Pub folder dtabase has been reached 1.22TB . Problem is that we cant increase more storage as its reached over limit. We are unable to do backup as its need to
split in multiple chunk . I cant do offline defrag as if now casue of LUNs limit.
Do someone has such sitaution faced and have any recommendation is this ? I can do create a new PF database. More over I am looking some short of solution to split whole database in two part hosted by two PUB server and each database just do content replication
with each hosting own database on each server.Will really appriciate for any good suggestion. I am open for all other possibilities.
Saty

I have executed whole project to move from 2010 to 20103. Public folder was a big pain. It was 3 copy of 1.32 TB. Plan started from implementation of Archiving tool for exchange.
1- First level pulled all detail reports for PF name,size last access time ,update time ,type9 mail enable or normal.
2- Pull the report and calculate the free white space with all calculation of individual server wise, and get the actual data size ,
3- Target to one PF server holding passive copy of public folders (Not Master copy)
4- Target the public folder keeping 0KB size and create script to delete in non recurs mode so only folders which has size 0 will be delete and rest all be left just like that .
5- later target the folder size keeping huge data and foliter it out with root folder and check out the permission and reach out people if the really need the data .Get the sign off and delete it through recurs script.
If you not put recurs delete it will never allow to delete whole folder in one way.
6- Target folder which data are important and move them to shared mailbox . Using soem restore tool which can export pst of those folder and import into mailbox. Set the permission accordingly. And set Enterprise erchiving policy for that shared.Same above
two exercise need to apply for all public folders.
7- Target those folders which are in use and try to convince and move them to shared mailbox with unlimited mailbox size with EV archiving.
8- And at the end move replica of target server to master copy.
9- Once replica move is complete you can plan to delete the PF data edb file. It wont allow to delete directly as you have to go through ADSIEDIT method only.
10- while same exercise need to do for all other passive copy.
11- Create a fresh edb and now you can move pf replica content to new edb which will help to move actual data with very limited whitespace.
12- And this way whole PF will be in actual size and all junk and unwanted files/data/emails/meetings etc will be removed.
13- There will be one common issue of form created through outlook so you need to import them carefully using default system folder.

Exchange 2010 - public folder replication

Hi there.
Exchange 2010 SP3 (CU 8v2).
We would like to rid of the replication public folder messages.
Is it safe to delete those folders and they Will be automatically recreated?
We would like to get rid of those errors before we plan migration of PF to Exchange 2013 PF's.
with best regards
bostjanc

Hi,
To get rid of these warnings, I suggest to Removing and re-adding the replica for the affected public folders. To remove and add replica for server, please use this script:
RemoveReplicaFromPFRecursive.ps1 –TopPubicFolder <\folder> –Server toRemove <servername>
AddReplicatoPFRecursive.ps1 –TopPulblicFolder <\folder> -ServerToAdd <servername>
Note: Scripts are found at %SystemDrive%\Program Files\Microsoft\Exchange Server\v14\Scripts. To run a script, type the following in the Exchange Management Shell:
[PS] C:\>cd $exscripts
[PS] C:\Program Files\Microsoft\Exchange Server\Scripts>.\ RemoveReplicaFromPFRecursive.ps1
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Exchange 2010 Public folder permission issue

When i select the public folder and click the permission tab to set the permission, below error message will be pop up. This error message only happen in few sub public folder, another folder without this problem. There are two replica
in different mail store server.
Microsoft Corporation
Microsoft® Windows® Operating System
6.1.7600.16385
Exception has been thrown by the target of an invocation.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.ConstraintException: Column 'Identity' is constrained to be unique. Value 'gcr.geg.local/Managed OU/Galaxy Corporate/HR&A/Esther
Chan (Corp HR&A)' is already present.
   at System.Data.UniqueConstraint.CheckConstraint(DataRow row, DataRowAction action)
   at System.Data.DataTable.RaiseRowChanging(DataRowChangeEventArgs args, DataRow eRow, DataRowAction eAction, Boolean fireEvent)
   at System.Data.DataTable.SetNewRecordWorker(DataRow row, Int32 proposedRecord, DataRowAction action, Boolean isInMerge, Int32 position, Boolean fireEvent, Exception& deferredException)
   at System.Data.DataTable.InsertRow(DataRow row, Int64 proposedID, Int32 pos, Boolean fireEvent)
   at System.Data.DataRowCollection.Add(DataRow row)
   at Microsoft.Exchange.Management.SystemManager.WinForms.PublicFolderClientPermissionHelper.AddEntry(DataTable table, ADObjectId identity, String name, MultiValuedProperty`1 accessRights)
   at Microsoft.Exchange.Management.SystemManager.WinForms.PublicFolderClientPermissionHelper.GenerateClientPermissionDataSource(Object clientPermission)
   at lambda_method(ExecutionScope , String )
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Microsoft.Exchange.Management.SystemManager.ExpressionCalculator.CalculateLambdaExpression(ColumnExpression expression, Type dataType, DataRow dataRow, DataRow inputRow)
   at Microsoft.Exchange.Management.SystemManager.ExpressionCalculator.CalculateCore(DataRow dataRow, DataRow inputRow, IList`1 query)
   at Microsoft.Exchange.Management.SystemManager.WinForms.AutomatedDataHandlerBase.FillColumnsBasedOnLambdaExpression(String changedColumn)
   at Microsoft.Exchange.Management.SystemManager.WinForms.AutomatedDataHandlerBase.UpdateTable(DataRow row, String targetConfigObject, Boolean isOnReading)
   at Microsoft.Exchange.Management.SystemManager.WinForms.AutomatedDataHandler.OnReadData(CommandInteractionHandler interactionHandler, String pageName)
   at Microsoft.Exchange.Management.SystemManager.WinForms.DataHandler.Read(CommandInteractionHandler interactionHandler, String pageName)
   at Microsoft.Exchange.Management.SystemManager.WinForms.DataContext.ReadData(CommandInteractionHandler interactionHandler, String pageName)
   at Microsoft.Exchange.Management.SystemManager.WinForms.ExchangePage.<OnSetActive>b__0(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.ManagementConsole, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
MMCFxCommon, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Management.PublicFolders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.Exchange.Management.SystemManager, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Common, Version=14.1.214.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.ObjectModel, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Data.Directory, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Drawing.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.ManagementGUI.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Net, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Core.Strings, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Core.Strings.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Management, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Isam.Interop, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
BPA.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
BPA.UserInterface, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.ActiveDS, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.adsiis, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.Migbase, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.DKM.Proxy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.AirSync, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Approval.Applications, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.CabUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Cluster.Replay, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.ApplicationLogic, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Mapi, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Providers, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Storage, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.EdgeSync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.EdgeSync.DatacenterProviders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Extensibility.Internal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.HelpProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.InfoWorker.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Live.DomainServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MailboxReplicationService.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MessageSecurity, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MessagingPolicies.Rules, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.Native, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.StoreProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Agent.AntiSpam.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Agent.SenderId.Core, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Logging.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Sync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Sync.Worker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.TroubleshootingTool.Shared, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.UMCommon, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.RightsManagementServices.Core, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.ExSearch, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
MSExchangeLESearchWorker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Transport, Version=14.1.214.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
pspluginwkr, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Common.IL, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.ObjectModel.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Sqm, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Management.SnapIn.Esm, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Accessibility, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
PresentationFramework, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
WindowsBase, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Anonymously Hosted DynamicMethods Assembly, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
Microsoft.Exchange.Management.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35

Hi,
This issue appears to be related to
data access from their ASp.Net application.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft
Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
FIX: "Exception has been thrown by the target of an invocation"
error message
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Exchange 2010 Public Folder Calender

My current environment is an Exchange 2010 Server where we have many people out in the field that use OWA.
I have a user that wants to be able to send and receive email and invitations via a Public Folder Calender. And have her users be able to check the green check mark to accept an appointment/invitation or red X to reject and so on. The Public Folder Calender
is mail enabled but still does not give the full options as a normal mailbox would.
I dont even think this is a possible option but want to be certain.
Thanks.

Hi tspilker,
Thank you for your question.
Could you tell me any options which are missing?
Or could you tell us which functions didn’t achieve?
I suggest you send a snapshot with detail description to
[email protected] for our troubleshooting.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Exchange 2010 Public Folder import .pst

Hi
I have Exchange 2010. I exported a public folder to pst-file and then deleted it. Because i could not uninstall our 2007 servers
How do i import it again. When i do it in Outlook it says that Posts cannot be created on root level in the common information archive. Translated from Swedish.
Anyone have a step by step solution for this.
Best regards
Matthias

Hi,
How did you import the pst-file? Please try to open the pst-file in Outlook and drag and drop all items in it to your Public Folder. See:
http://www.rackspace.com/knowledge_center/article/migrating-public-folder-data
Hope this helps.
Best Regards,
Steve Fan
TechNet Community Support

How do I export public folder data from inactive exchange server?

I have migrated from SBS2003 (old) to SBS2008 (new)
Used migration wizard / answer etc... All went well, expect for the public folders; which failed.
Question: How do I retrieve the public folder information from the OLD (inactive) server and import it to the NEW server?
The OLD server has been removed from the domain. I have backups of the OLD server and its original hard drive; where the public store info is located.
I tried PDDAVAdmin.exe; did not work for me.
All help is greatly appreciated.
Bill

Hi Amit,
I did as Zoltán said; searched the Internet for edb recovery tools and found a number of companies and Software Products which might help. I also considered your option as well but I have limited experience with building a recovery server and it sounds time consuming.
Our office is small we have 10 users; we keep contact lists in the public folders. I want to restore the contact lists from the inactive source server to the active destination.
I believe the process is called "rehoming" (from the web -- "In a Windows environment, rehoming is the process of moving public folders from one Exchange server to another. It involves the creation of a replica of the public folders on the target destination server, waiting for replication to complete, and then removing the public folders from the original source server.")
Background:
We have two servers FHHSERVER (the source, SBS2003) and FHHSERVER2 (the destination, SBS2008).
I used the SBS2008 migration wizard. The important stuff in the exchange database transferred ok; all emails, schedules, tasks, notes, etc. Everything appeared to work; including public folders.
Microsoft allows a 21 day grace period to complete the migration. I believed the migration was successful so on the 21st day, I followed Microsoft’s instructions and demoted the source server, removing it from the domain.
That’s when the trouble started….
Unknown to me; the public folders remained on the old source server. I did not detect this problem since, during the 21 day migration grace period, the destination server was using the old source server to replicate public folders. As long as the old source server was active, eveyone could open public folder contact lists. After the source server was demoted, the destination server lost its replicate and now our users cannot access that information.
Another problem is that the inactive server is n o longer licensed and the Exchange console cannot connect to its stores.
It would seem to me that this problem should be relatively simple to fix. I need some way to open the public folder stores and export the contact lists. I’m not even sure where the public folder database is located on the hard drive.
I hope this explains the situation in greater detail and that you may be able to offer some insight on how I might resolve this issue.
Oh, I also tried using EXMerge but cannot seem to make it work either. <http://www.microsoft.com/downloads/details.aspx?familyid=429163EC-DCDF-47DC-96DA-1C12D67327D5&displaylang=en>
Thanks!
Bill

Migrate Exchange Server 2010 Public Folder shared calendars to Exchange Server 2013

Similar Messages

Maybe you are looking for