Exchange 2013 homeMTA attribute missing

Hi all,
I noticed if I create a user mailbox on exchange 2013 and check the users properties in ADSI Edit, the homeMTA attribute is missing? Is this normal?
If a user mailbox is create on exchange 2007 I can see the homeMTA attribute. But as soon as I migrate the mailbox over to exchange 2013 it disappears?
Why is there no homeMTA attribute for mailboxes on exchange 2013?
Environment:
Windows Server 2008 SP2 Domain Controller
Exchange 2007 + SP3
Exchange 2013 + CU3
Thank you

Hi,
We are in the process of configuration BES 5 with 2013 and got stuck during the installation. We are new to Exchange environment as we are now migrating from Lotus Domino. We have followed the same documents mentioned by Steve but could not succeed with
the installation as it is stuck at MAPI setting page. We also could not complete few steps mentioned in the pre-requisites and was told by our service provider that we are getting stuck because of this missing pre-requisites. We were not able
to complete the Task1 and Task 3 as mentioned in
KB33413. In Task 1 we are not able to set the value for IISAuthenticationMethods       {Basic, Ntlm, Negotiate}Ntlm .
Have applied the commands as advised at the end of the Task 1, restarted the services and server but no luck. It is showing blank in our case. In Task3 we were having the
HomeMTA attribute as not set and was supposed to copy the attributes from the other two fields. Would like to clarify how we could copy these two values to one field, is it one after another with a comma or space?
Also, we were told by the Service provider that they have limited support for Exchange 2013 SP1 version. Can somebody please verify if it works with the same? Kindly help.

Similar Messages

  • What happend New-MailboxExportRequest cmdlet in exchange 2013 SP1 is missing?

    Cmdlet New-MailboxExportRequest is not recognize cmdlet in Exchange 2013 SP1
    How can i do export mailbox to pst file in exchange 2013 SP1?

    You might be facing this issue because of not having the rights to execute the New-MailboxExportRequest CMDLET.
    Follow the steps given below in order to export the mailboxes into PST file
    1. Open the Exchange Console and run:
    New-ManagementRoleAssignment -Name "Import Export PST" -SecurityGroup "Organization Management" -Role “Mailbox Import Export"
    This will generate a new role group called Import Export PST to the Oranization Management group with the role Mailbox Import Export.
    You should Close and Restart the Exchange Management System again so that the changes made will get reflected in the settings, otherwise you will still get the same erroriIf not
    restarted. Now move to the next steps.
    2. Assign “Mailbox Import Export” role to it.
    3.  Add Desired Users to Role Group
    4.  Create Network Share ( Exchange Trusted Subsystem group has read/write permission to NTFS Permissions)
    5. Run PS New-MailboxExportRequest
    6. Monitor New-MailboxExportRequest
    Verify PST File has been created on the network Share and you are done.
    If you get the same error again, then there will be some hardware or software issues due to which you are not able to export mailboxes into PST files. In that case, you can make
    use of any third party tool like Stellar Phoenix EDB To PST converter, which will help you to export your exchange database files to PST files easily and quickly. You can try this software by downloading its demo directly from their site http://www.stellarinfo.com/email-repair/edb-pst-converter.php

  • Exchange 2013 SP1 database missing?? New install of Exchange 2007 co-exist

    Hi all,
    Finally got Exchange 2013 SP1 installed except I am not so sure I have a database. This is installed on a Server 2008 system and is co-existing with Exchange 2007.
     When I go to SERVERS and DATABASES I don't have anything listed. When I click SERVERS on the left hand pane and SERVERS at the top I see both servers, 2007 and 2013. But when I double click my new Exchange Server 2013 name I get the error:
    The operation couldn't be performed because object '*\ExchangeServerName' couldn't be found on 'FirstDCName.mydomain.com'
    Why would I get this error? The install itself was problematic so I am concerned something is broke.
    Thank you in advance.

    Hello,
    Firstly, I recommend you check if the server name "*\ExchangeServerName" exists on DC via ADUC (select Computers).
    Secondly, please run the get-exchangeserver | fl name cmdlet to check your exchange server name.
    And then please check the exchange setup log to check if the exchange 2013 server is installed successfully. If not, please check if there is any error in setup log.
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Exchange 2013 Public Folder Missing in Outlook

    Hello,
    i have succesfully migrated from Exchange 2010 to Exchange 2013.
    Everything was running after i migrated the public folders they disappeared on the Clients after starting Outlook 2013.
    We are able to see the public Folders in OWA but not in Outlook.
    Anybody know this Problem and can help?
    regards
    René

    Hi,
    Based on the description, everything was running after you migrated from Exchange 2010 to Exchange 2013. When you upgraded from Outlook 2010 to Outlook 2013, you couldn't see public folders in Outlook 2013. However, you could see public folders in Outlook
    2010, but you couldn't expand it. OWA worked well.
    If I misunderstood your concern, please feel free to let me know.
    About "No we had migrated to Office 2013 before but tested it now with Outlook 2010.", was the Outlook 2010 client a remaining Outlook 2010 client?
    Did the issue affect all users or some of them?
    Could you please switch between online mode and cached mode to check the result?
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 Domain Prep Fails: Setup /prepareschema, setup /PrepareAD, Setup /PrepareDomain

    Whenever I try to prep for a 2013 exchange install I always get:
    "earlier versions of the server roles that are installed were detected"
    whenever I try to run Setup /prepareschema OR setup /PrepareAD OR Setup /PrepareDomain
    I am working on a Server 2012 standard machine with Exchange 2010 currently installed. This server is a DC (bad I know), DNS, DHCP.
    I am trying to prep the domain so that I can install Exchange 2013 on a VM and eventually remove Exchange 2010 from the organization altogether.
    There are no other domain controlelrs in the domain. The domain started life as a SBS 2003 machine which was demoted and removed once the server 2012 box was up with exchange 2010 running.
    Any help would be greatly appreciated.
    Here is some info that may help:
    1. PrePare Schema
    Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
    Ran setup /PrepareSchema
    This command should perform the following tasks:
    A: Connects to the schema master and imports LDAP Data Interchange Format (LDIF) files to update the schema with 
    Exchange 2013 specific attributes. The LDIF files are copied to the Temp directory and then deleted after they are imported 
    into the schema.
    B: Sets the schema version (ms-Exch-Schema-Verision-Pt) to a Exchange 2013 value.
    This command fails with: Earlier versions of server roles that were installed were detected.
    First I confirmed that administrator account for domain is a member of schema admins and enterprise admins.
    Next I ran asdiedit.
    I navigated to: "CN=ms-Exch-Schema-Version-Pt,CN=Schema,CN=Configuration,DC=BDA,DC=LAN"
    and reviewed the current "rangeUpper" attribute.
    The ms-Exch-Schema-Verision-Pt is not updated to CU3 range Upper setting.
    The current range upper 14734 which means its still at Exchange 2010 SP3 settings. 
    In short, updaing the schema fails.
    2. Prepare Active Directory
    Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
    setup /PrepareAD [/OrganizationName:<organization name>]
    This command fails with: Earlier versions of server roles that were installed were detected.
    schema update version 56
    I began reviewing the long, long list of the following containers and objects under
     CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
    which are required for Exchange 2013:
    missing cn=Auth Configuration
    missing CN=ExchangeAssistance
    missing CN=Monitoring Settings
    missing CN=Monitoring Settings
    missing CN=Monitoring Settings
    missing CN=Workload Management Settings
    Checked Management role groups within the Microsoft Exchange Security Groups OU
    missing Compliance Management group  --- Manually created this entry
    Step 3 Prepare Domain:
    Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
    Ran setup /PrepareDomain
    This command fails with: Earlier versions of server roles that were installed were detected.
    confirmed the following:
    ObjectVersion property fails as it is still set to Echange 2010 sp3 -  13040
    You have a new global group in the Microsoft Exchange System Objects container called Exchange Install Domain Servers-DONE
    The Exchange Install Domain Servers group is a member of the Exchange Servers USG in the root domain.-DONE
    On each domain controller in a domain in which you will install Exchange 2013, the Exchange Servers USG has permissions 
    on the Domain Controller Security Policy\Local Policies\User Rights Assignment\Manage Auditing and Security Log policy.-DONE
    Thanks.

    Whenever I try to prep for a 2013 exchange install I always get:
    "earlier versions of the server roles that are installed were detected"
    Hi,
    That tells us that you are trying to run the prep on your combined DC and Exchange 2010 Server - That will not work. Run it on the Server where you plan to install Exchange 2013.
    It is not mandatory to run this before the actuall Exchange install - It will run automatically for you, if it hasn't been done already and if you are logged on with an account with the proper permissions.
    Martina Miskovic

  • Error Extending 2012 R2 AD Schema for Exchange 2013 RTM/CU6/CU7 (for Office 365 attributes)

    Hello all,
    I am a sysadmin at a 3 campus school, and am trying to extend our AD schema to include Exchange 2013 attributes so that we can configure groups synced to Office 365 using DirSync. However it keeps failing at the same point each time.
    I have tried with RTM first, and then CU6, but I keep getting the same error and am unsure how to fix it.
    "repadmin /showrepl" says that our 3 DCs are replicating with no issues, and I'm trying to extend the schema using an "Enterprise Admin"/"Schema Admin" account on our schema master DC.
    Our domain/forest functional level is Server 2008R2, and we do not have an Exchange server set up already - if that helps.
    The PowerShell error is:
    PS C:\Users\rbbr\Desktop\Exchange> .\setup /PrepareSchema /IAcceptExchangeServerLicenseTerms
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 6 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis COMPLETED
    Configuring Microsoft Exchange Server
    Extending Active Directory schema FAILED
    The following error was generated when "$error.Clear();
    install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema89.ldf")
    " was run: "Microsoft.Exchange.Configuration.Tasks.TaskException: There was an error while running 'ldifde.exe' to impor
    t the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\schema89.ldf'. The error code is: 8245. More details can be
    found in the error file: 'C:\Users\rbbr\AppData\Local\Temp\ldif.err'
    at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object ta
    rget, String helpUrl)
    at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchemaFile(String schemaMasterServer, String
    schemaFilePath, String macroName, String macroValue, WriteVerboseDelegate writeVerbose)
    at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePip
    elineIfFailed)".
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    And ldif.err says:
    Entry DN: CN=ms-DS-GeoCoordinates-Altitude,CN=Schema,CN=Configuration,DC=kurnai,DC=lan
    Add error on entry starting on line 452: Unwilling To Perform
    The server side error is: 0x20bb Schema update failed: duplicate OID.
    The extended server error is:
    000020BB: SvcErr: DSID-032603C0, problem 5003 (WILL_NOT_PERFORM), data 8379
    An error has occurred in the program
    The schema attribute "CN=ms-DS-GeoCoordinates-Altitude,CN=Schema,CN=Configuration,DC=kurnai,DC=lan" does exist in the schema, but I don't know what to do or where to go from here.
    Any assistance would be greatly appreciated.

    I just tried .\setup /PrepareAD /OrganizationName:kurnaicollege /IAcceptExchangeServerLicenseTerms, and got the exact same error as above. 
    Is there a way to delete the offending schema attributes, or to force its overwrite or something?
    EDIT: I am also getting these eventvwr errors when running /PrepareAD, if it helps:
    The description for Event ID 106 from source MSExchange Common cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    2
    Proxy Instance Count
    MSExchange ServiceProxyPool
    The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
    at System.Diagnostics.PerformanceCounter.InitializeImpl()
    at System.Diagnostics.PerformanceCounter.get_RawValue()
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()
    Last worker process info : Last worker process info not available!
    Processes running while Performance counter failed to update:
    2756 vds
    3540 NBBPassThruAuth_Helper
    4168 dwm
    1224 NBBPassThruAuth_Helper
    776 MsMpEng
    2940 dllhost
    3924 NBBPassThruAuth_Helper
    376 wininit
    1556 dns
    4900 taskhostex
    368 csrss
    2152 miiserver
    756 dwm
    1452 Microsoft.ActiveDirectory.WebServices
    1704 conhost
    1540 svchost
    4492 conhost
    740 LogonUI
    3716 notepad
    3888 WmiPrvSE
    140 NBBPassThruAuth_Helper
    1712 sqlservr
    3484 msseces
    916 svchost
    1116 sqlwriter
    1312 setup
    1508 dfsrs
    2492 explorer
    520 svchost
    712 WmiPrvSE
    4388 mmc
    2088 dfssvc
    1692 MSOIDSVCM
    704 conhost
    960 svchost
    304 csrss
    4440 NBBPassThruAuth_Helper
    3648 conhost
    884 svchost
    1080 vmtoolsd
    3440 conhost
    5012 NBBPassThruAuth_Helper
    3632 dllhost
    476 lsass
    1852 NBBPassThruAuth
    2836 svchost
    4016 winlogon
    468 services
    3028 vmtoolsd
    860 conhost
    1644 MSOIDSVC
    3416 conhost
    852 conhost
    2624 Microsoft.Online.DirSync.Scheduler
    2820 svchost
    4592 ServerManager
    1236 iashost
    636 svchost
    2800 svchost
    4768 ExSetup
    1812 msdtc
    1416 spoolsv
    4760 NBBPassThruAuth_Helper
    1016 svchost
    1992 ntfrs
    3368 powershell
    608 svchost
    1592 ismserv
    3756 csrss
    404 winlogon
    204 smss
    4 System
    988 rdpclip
    0 Idle
    Performance Counters Layout information: FileMappingNotFoundException for category MSExchange ServiceProxyPool : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange serviceproxypool. Error Details: 2
    at Microsoft.Exchange.Diagnostics.FileMapping..ctor(String name, Boolean writable)
    at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
    the message resource is present but the message is not found in the string/message table
    The description for Event ID 106 from source MSExchange Common cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    1
    Average Latency
    MSExchange ServiceProxyPool
    The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
    at System.Diagnostics.PerformanceCounter.InitializeImpl()
    at System.Diagnostics.PerformanceCounter.IncrementBy(Int64 value)
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.IncrementBy(Int64 incrementValue)
    Last worker process info : Last worker process info not available!
    Processes running while Performance counter failed to update:
    4136 NBBPassThruAuth_Helper
    2756 vds
    4168 dwm
    1224 NBBPassThruAuth_Helper
    776 MsMpEng
    2940 dllhost
    3924 NBBPassThruAuth_Helper
    376 wininit
    1556 dns
    4900 taskhostex
    368 csrss
    2152 miiserver
    756 dwm
    4260 conhost
    1452 Microsoft.ActiveDirectory.WebServices
    1540 svchost
    4488 conhost
    740 LogonUI
    3716 notepad
    3888 WmiPrvSE
    140 NBBPassThruAuth_Helper
    1712 sqlservr
    3484 msseces
    916 svchost
    1116 sqlwriter
    1312 setup
    1508 dfsrs
    2492 explorer
    2688 NBBPassThruAuth_Helper
    520 svchost
    3472 conhost
    712 WmiPrvSE
    4388 mmc
    2088 dfssvc
    1692 MSOIDSVCM
    704 conhost
    960 svchost
    304 csrss
    3648 conhost
    884 svchost
    1080 vmtoolsd
    3836 WmiPrvSE
    5012 NBBPassThruAuth_Helper
    3632 dllhost
    476 lsass
    1852 NBBPassThruAuth
    2836 svchost
    4016 winlogon
    468 services
    3028 vmtoolsd
    860 conhost
    1644 MSOIDSVC
    3416 conhost
    852 conhost
    2624 Microsoft.Online.DirSync.Scheduler
    2820 svchost
    4592 ServerManager
    1236 iashost
    4580 NBBPassThruAuth_Helper
    636 svchost
    2800 svchost
    4768 ExSetup
    1812 msdtc
    1416 spoolsv
    3776 NBBPassThruAuth_Helper
    1016 svchost
    1992 ntfrs
    3368 powershell
    608 svchost
    1592 ismserv
    3756 csrss
    404 winlogon
    204 smss
    4 System
    988 rdpclip
    4436 conhost
    0 Idle
    Performance Counters Layout information: FileMappingNotFoundException for category MSExchange ServiceProxyPool : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange serviceproxypool. Error Details: 2
    at Microsoft.Exchange.Diagnostics.FileMapping..ctor(String name, Boolean writable)
    at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
    the message resource is present but the message is not found in the string/message table
    The description for Event ID 106 from source MSExchange Common cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    1
    Base for Average Latency
    MSExchange ServiceProxyPool
    The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
    at System.Diagnostics.PerformanceCounter.InitializeImpl()
    at System.Diagnostics.PerformanceCounter.IncrementBy(Int64 value)
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.IncrementBy(Int64 incrementValue)
    Last worker process info : Last worker process info not available!
    Processes running while Performance counter failed to update:
    4136 NBBPassThruAuth_Helper
    2756 vds
    4168 dwm
    1224 NBBPassThruAuth_Helper
    776 MsMpEng
    2940 dllhost
    3924 NBBPassThruAuth_Helper
    376 wininit
    1556 dns
    4900 taskhostex
    368 csrss
    2152 miiserver
    756 dwm
    4260 conhost
    1452 Microsoft.ActiveDirectory.WebServices
    1540 svchost
    4488 conhost
    740 LogonUI
    3716 notepad
    3888 WmiPrvSE
    140 NBBPassThruAuth_Helper
    1712 sqlservr
    3484 msseces
    916 svchost
    1116 sqlwriter
    1312 setup
    1508 dfsrs
    2492 explorer
    2688 NBBPassThruAuth_Helper
    520 svchost
    3472 conhost
    712 WmiPrvSE
    4388 mmc
    2088 dfssvc
    1692 MSOIDSVCM
    704 conhost
    960 svchost
    304 csrss
    3648 conhost
    884 svchost
    1080 vmtoolsd
    3836 WmiPrvSE
    5012 NBBPassThruAuth_Helper
    3632 dllhost
    476 lsass
    1852 NBBPassThruAuth
    2836 svchost
    4016 winlogon
    468 services
    3028 vmtoolsd
    860 conhost
    1644 MSOIDSVC
    3416 conhost
    852 conhost
    2624 Microsoft.Online.DirSync.Scheduler
    2820 svchost
    4592 ServerManager
    1236 iashost
    4580 NBBPassThruAuth_Helper
    636 svchost
    2800 svchost
    4768 ExSetup
    1812 msdtc
    1416 spoolsv
    3776 NBBPassThruAuth_Helper
    1016 svchost
    1992 ntfrs
    3368 powershell
    608 svchost
    1592 ismserv
    3756 csrss
    404 winlogon
    204 smss
    4 System
    988 rdpclip
    4436 conhost
    0 Idle
    Performance Counters Layout information: FileMappingNotFoundException for category MSExchange ServiceProxyPool : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange serviceproxypool. Error Details: 2
    at Microsoft.Exchange.Diagnostics.FileMapping..ctor(String name, Boolean writable)
    at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
    the message resource is present but the message is not found in the string/message table
    The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    ExSetup.exe
    4768
    Get Servers for kurnai.lan
    TopologyClientTcpEndpoint (localhost)
    3
    System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.1106192. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
    at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    --- End of inner exception stack trace ---
    Server stack trace:
    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
    at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
    at System.ServiceModel.ICommunicationObject.Open()
    at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
    at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
    the message resource is present but the message is not found in the string/message table
    The description for Event ID 106 from source MSExchange Common cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    2
    Time in Resource per second
    MSExchange Activity Context Resources
    The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
    at System.Diagnostics.PerformanceCounter.InitializeImpl()
    at System.Diagnostics.PerformanceCounter.get_RawValue()
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()
    Last worker process info : Last worker process info not available!
    Processes running while Performance counter failed to update:
    2756 vds
    4168 dwm
    776 MsMpEng
    2940 dllhost
    376 wininit
    1556 dns
    4900 taskhostex
    368 csrss
    2152 miiserver
    756 dwm
    1452 Microsoft.ActiveDirectory.WebServices
    1540 svchost
    4488 conhost
    740 LogonUI
    3716 notepad
    3888 WmiPrvSE
    1712 sqlservr
    3484 msseces
    916 svchost
    1116 sqlwriter
    1312 setup
    1508 dfsrs
    2492 explorer
    2688 NBBPassThruAuth_Helper
    520 svchost
    712 WmiPrvSE
    2088 dfssvc
    1692 MSOIDSVCM
    960 svchost
    304 csrss
    4436 conhost
    884 svchost
    1080 vmtoolsd
    3836 WmiPrvSE
    4388 mmc
    3632 dllhost
    476 lsass
    1852 NBBPassThruAuth
    2836 svchost
    4016 winlogon
    468 services
    3028 vmtoolsd
    1644 MSOIDSVC
    3416 conhost
    2624 Microsoft.Online.DirSync.Scheduler
    2820 svchost
    4592 ServerManager
    1236 iashost
    636 svchost
    2800 svchost
    4768 ExSetup
    1812 msdtc
    1416 spoolsv
    3776 NBBPassThruAuth_Helper
    1016 svchost
    1992 ntfrs
    3368 powershell
    608 svchost
    1592 ismserv
    3756 csrss
    404 winlogon
    204 smss
    4 System
    988 rdpclip
    0 Idle
    Performance Counters Layout information: FileMappingNotFoundException for category MSExchange Activity Context Resources : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange activity context resources. Error Details: 2
    at Microsoft.Exchange.Diagnostics.FileMapping..ctor(String name, Boolean writable)
    at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
    the message resource is present but the message is not found in the string/message table
    The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    Get-OrganizationRelationship
    kurnai.lan/Kurnai/Morwell/Users/Techs/Robert Brandon
    Local-Exchange Management Console-Unknown
    4768 ExSetup.exe
    34
    00:00:00.0938055
    View Entire Forest: 'True', Configuration Domain Controller: 'C-Server1.kurnai.lan', Preferred Global Catalog: 'C-Server1.kurnai.lan', Preferred Domain Controllers: '{ C-Server1.kurnai.lan }'
    Microsoft.Exchange.Data.Directory.SystemConfiguration.OrgContainerNotFoundException: Couldn't find the Enterprise Organization container.
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetRootOrgContainer(String partitionFqdn, String domainController, NetworkCredential credential)
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetRootOrgContainerId(String partitionFqdn, String domainController, NetworkCredential credential)
    at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.get_RootOrgContainerId()
    at Microsoft.Exchange.Configuration.Tasks.GetTenantADObjectWithIdentityTaskBase`2.InternalStateReset()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    ServerOperation
    Ex31B4F7
    False
    0 objects execution has been proxied to remote server.
    0
    ActivityId: a2ea62f0-d687-4594-bb1a-bcd9642a6308
    en-US
    the message resource is present but the message is not found in the string/message table
    The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    Get-OrganizationRelationship
    kurnai.lan/Kurnai/Morwell/Users/Techs/Robert Brandon
    Local-Exchange Management Console-Unknown
    4768 ExSetup.exe
    34
    00:00:00.0312685
    View Entire Forest: 'True', Configuration Domain Controller: 'C-Server1.kurnai.lan', Preferred Global Catalog: 'C-Server1.kurnai.lan', Preferred Domain Controllers: '{ C-Server1.kurnai.lan }'
    Microsoft.Exchange.Data.Directory.SystemConfiguration.OrgContainerNotFoundException: Couldn't find the Enterprise Organization container.
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetRootOrgContainer(String partitionFqdn, String domainController, NetworkCredential credential)
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetRootOrgContainerId(String partitionFqdn, String domainController, NetworkCredential credential)
    at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.get_RootOrgContainerId()
    at Microsoft.Exchange.Configuration.Tasks.GetTenantADObjectWithIdentityTaskBase`2.InternalStateReset()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    ServerOperation
    Ex31B4F7
    False
    0 objects execution has been proxied to remote server.
    0
    ActivityId: a2ea62f0-d687-4594-bb1a-bcd9642a6308
    en-US
    the message resource is present but the message is not found in the string/message table
    The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    Get-AcceptedDomain
    kurnai.lan/Kurnai/Morwell/Users/Techs/Robert Brandon
    Local-Exchange Management Console-Unknown
    4768 ExSetup.exe
    20
    00:00:00
    View Entire Forest: 'True', Configuration Domain Controller: 'C-Server1.kurnai.lan', Preferred Global Catalog: 'C-Server1.kurnai.lan', Preferred Domain Controllers: '{ C-Server1.kurnai.lan }'
    Microsoft.Exchange.Data.Directory.SystemConfiguration.OrgContainerNotFoundException: Couldn't find the Enterprise Organization container.
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetRootOrgContainer(String partitionFqdn, String domainController, NetworkCredential credential)
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetRootOrgContainerId(String partitionFqdn, String domainController, NetworkCredential credential)
    at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.get_RootOrgContainerId()
    at Microsoft.Exchange.Configuration.Tasks.GetTenantADObjectWithIdentityTaskBase`2.InternalStateReset()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    ServerOperation
    Ex31B4F7
    False
    0 objects execution has been proxied to remote server.
    0
    ActivityId: a2ea62f0-d687-4594-bb1a-bcd9642a6308
    en-US
    the message resource is present but the message is not found in the string/message table
    The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    Get-AcceptedDomain
    kurnai.lan/Kurnai/Morwell/Users/Techs/Robert Brandon
    Local-Exchange Management Console-Unknown
    4768 ExSetup.exe
    20
    00:00:00
    View Entire Forest: 'True', Configuration Domain Controller: 'C-Server1.kurnai.lan', Preferred Global Catalog: 'C-Server1.kurnai.lan', Preferred Domain Controllers: '{ C-Server1.kurnai.lan }'
    Microsoft.Exchange.Data.Directory.SystemConfiguration.OrgContainerNotFoundException: Couldn't find the Enterprise Organization container.
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetRootOrgContainer(String partitionFqdn, String domainController, NetworkCredential credential)
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetRootOrgContainerId(String partitionFqdn, String domainController, NetworkCredential credential)
    at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.get_RootOrgContainerId()
    at Microsoft.Exchange.Configuration.Tasks.GetTenantADObjectWithIdentityTaskBase`2.InternalStateReset()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    ServerOperation
    Ex31B4F7
    False
    0 objects execution has been proxied to remote server.
    0
    ActivityId: a2ea62f0-d687-4594-bb1a-bcd9642a6308
    en-US
    the message resource is present but the message is not found in the string/message table
    The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    Install-ExchangeSchema
    -LdapFileName "Setup\Data\schema89.ldf"
    kurnai.lan/Kurnai/Morwell/Users/Techs/Robert Brandon
    Local-Exchange Management Console-Unknown
    4768 ExSetup.exe
    98
    00:00:02.1887925
    View Entire Forest: 'True', Configuration Domain Controller: 'C-Server1.kurnai.lan', Preferred Global Catalog: 'C-Server1.kurnai.lan', Preferred Domain Controllers: '{ C-Server1.kurnai.lan }'
    Microsoft.Exchange.Configuration.Tasks.TaskException: There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\schema89.ldf'. The error code is: 8245. More details can be found in the error file: 'C:\Users\rbbr\AppData\Local\Temp\ldif.err'
    at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
    at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchemaFile(String schemaMasterServer, String schemaFilePath, String macroName, String macroValue, WriteVerboseDelegate writeVerbose)
    at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    7
    ExA2B06D
    False
    0 objects execution has been proxied to remote server.
    0
    ActivityId: f2ed251d-8d4a-480b-9b98-7b53d4adbcad
    en-US
    the message resource is present but the message is not found in the string/message table
    The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    Install-ExchangeSchema
    -LdapFileName "Setup\Data\schema89.ldf"
    kurnai.lan/Kurnai/Morwell/Users/Techs/Robert Brandon
    Local-Exchange Management Console-Unknown
    4768 ExSetup.exe
    98
    00:00:00
    View Entire Forest: 'True', Configuration Domain Controller: 'C-Server1.kurnai.lan', Preferred Global Catalog: 'C-Server1.kurnai.lan', Preferred Domain Controllers: '{ C-Server1.kurnai.lan }'
    Microsoft.Exchange.Configuration.Tasks.TaskException: There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\schema89.ldf'. The error code is: 8245. More details can be found in the error file: 'C:\Users\rbbr\AppData\Local\Temp\ldif.err'
    at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
    at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchemaFile(String schemaMasterServer, String schemaFilePath, String macroName, String macroValue, WriteVerboseDelegate writeVerbose)
    at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    7
    ExA2B06D
    False
    0 objects execution has been proxied to remote server.
    0
    ActivityId: f2ed251d-8d4a-480b-9b98-7b53d4adbcad
    en-US
    the message resource is present but the message is not found in the string/message table
    The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    Install-ExchangeOrganization
    -Industry "NotSpecified" -PrepareDomain "True" -DomainController "C-Server1.kurnai.lan" -ActiveDirectorySplitPermissions $null -PrepareOrganization "True" -PrepareSchema "True" -OrganizationName "kurnaicollege"
    kurnai.lan/Kurnai/Morwell/Users/Techs/Robert Brandon
    Local-Exchange Management Console-Unknown
    4768 ExSetup.exe
    31
    00:03:01.8261106
    View Entire Forest: 'True', Configuration Domain Controller: 'C-Server1.kurnai.lan', Preferred Global Catalog: 'C-Server1.kurnai.lan', Preferred Domain Controllers: '{ C-Server1.kurnai.lan }'
    Microsoft.Exchange.Management.Deployment.ScriptExecutionException: The following error was generated when "$error.Clear();
    install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema89.ldf")
    " was run: "Microsoft.Exchange.Configuration.Tasks.TaskException: There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\schema89.ldf'. The error code is: 8245. More details can be found in the error file: 'C:\Users\rbbr\AppData\Local\Temp\ldif.err'
    at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
    at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchemaFile(String schemaMasterServer, String schemaFilePath, String macroName, String macroValue, WriteVerboseDelegate writeVerbose)
    at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)". ---> Microsoft.Exchange.Configuration.Tasks.TaskException: There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\schema89.ldf'. The error code is: 8245. More details can be found in the error file: 'C:\Users\rbbr\AppData\Local\Temp\ldif.err'
    at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
    at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchemaFile(String schemaMasterServer, String schemaFilePath, String macroName, String macroValue, WriteVerboseDelegate writeVerbose)
    at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    --- End of inner exception stack trace ---
    7
    Microsoft.Exchange.Configuration.Tasks.TaskException: There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\schema89.ldf'. The error code is: 8245. More details can be found in the error file: 'C:\Users\rbbr\AppData\Local\Temp\ldif.err'
    at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
    at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchemaFile(String schemaMasterServer, String schemaFilePath, String macroName, String macroValue, WriteVerboseDelegate writeVerbose)
    at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    Ex88D115
    False
    0 objects execution has been proxied to remote server.
    0
    ActivityId: f2ed251d-8d4a-480b-9b98-7b53d4adbcad
    en-US
    the message resource is present but the message is not found in the string/message table

  • Exchange 2013 - Attachments in *.EML files missing in non-cached mode

    Hello
    Our client recently upgraded from Exchange 2010 to Exchange 2013. Since the migration they have had issues with an archiving system they use. Bascially the archiving system creates .eml files of journaled emails.
    The issue our client has is when Outlook is running in non-cached exchange mode any attachments within these .eml files are missing when the eml file is opened. If they change to cached mode the attachments show up fine.
    It's almost identical to the following issue I found while browsing the net:
    http://social.technet.microsoft.com/Forums/office/en-US/b9a390a9-e014-4098-ad6e-dd377a53422a/office-2010-exchange-2010-attachments-in-emlemails-are-invisible?forum=outlook
    Aside from the Exchange version this is exactly what is happening for our client. Is anyone aware of whether the same issue fixed in Rollup update 5 for Exch 2010 SP1 is still present in Exchange 2013?
    Our client has already said they don't want everyone using cached exchange so I can't tell them that. Is there a way to manually fix the issue or are we going to have to move back to Exchange 2010 while a patch is sent out? Does anyone know exactly what
    the issue is?
    Many thanks in advance.

    Hi,
    I know there was this issue with Exchange 2010, but haven't noticed the same issue in Exchange 2013. The suggestion would be to keep Exchange fully updated - It seems you have done so.
    I'm not sure when SP1 will be released, you may post this question to Exchange forum since it may be more related:
    http://social.technet.microsoft.com/Forums/exchange/en-US/home?category=exchangeserver
    Thanks,
    Melon Chen
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here

  • Exchange 2013 - Folders missing when importing PST to archive mailbox

    Hello,
    I'm having an issue when importing PST files to an Exchange 2013 archive mailbox using the command "New-MailboxImportRequest
    test -FilePath '\\server\e$\ArchiveExport\test.pst' -IsArchive -BadItemLimit 5 -ErrorAction Stop"
    The import is running without an error and shows the status complete. The size of the archive mailbox is exactly the same like the size
    of the PST file!
    But when I check the users archive mailbox some folders are missing. It seems that this happens only to default folders like "Inbox"
    or "Sent Items". Other folders are visible.
    The mailbox import log shows the following:
    16.01.15 16:31:56 [server] Merging folder '/Top of Personal Folders/Inbox [Inbox]' into '/Inbox [Inbox]'.
    16.01.15 16:31:56 [server] Copying 3 items, 4.789 KB (4,904 bytes). Skipping 0 items, 0 B (0 bytes).
    If I start the import process again the log says the following:
    16.01.15 16:46:54 [server] Merging folder '/Top of Personal Folders/Inbox [Inbox]' into '/Inbox [Inbox]'.16.01.15
    16:46:54 [server] Copying 0 items, 0 B (0 bytes). Skipping 3 items, 4.789 KB (4,904 bytes).
    So it seems that the mails are really there but just not visible.
    I did some tests:
    When  I import the PST file directly to the users mailbox (without parameter -IsArchive) I can see all content of the PST file.
    When I add the parameter -TargetRootFolder "Testfolder" the whole PST content shows up correctly under that folder.
    Can anyone explain this?
    Regards

    Hi PhilippMair,
    Thank you for your question.
    If all subfolders were merged, we could use OWA to check if the missing folders is appeared. If we could see missing folders by OWA, I suggest we recreate outlook profile and reset outlook view.
    In order to troubleshooting, I suggest we collect the import log to analysis if the subfolder of Inbox or Sent Item is exported.
    In my test lab, inbox has three subfolders, there are 123,456,789; when I import PST file, I will see the following log:
    1/20/2015 7:32:31 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox' into '/Top of Information Store/Inbox'.
    1/20/2015 7:32:31 AM [EXCH2-CU1] Copying 18 items, 302.3 KB (309,594 bytes). Skipping 0 items, 0 B (0 bytes).
    1/20/2015 7:32:32 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox/123' into '/Top of Information Store/Inbox/123'.
    1/20/2015 7:32:32 AM [EXCH2-CU1] Copying 5 items, 62.21 KB (63,699 bytes). Skipping 0 items, 0 B (0 bytes).
    1/20/2015 7:32:33 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox/456' into '/Top of Information Store/Inbox/456'.
    1/20/2015 7:32:33 AM [EXCH2-CU1] Copying 1 items, 6.908 KB (7,074 bytes). Skipping 0 items, 0 B (0 bytes).
    1/20/2015 7:32:33 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox/789' into '/Top of Information Store/Inbox/789'.
     1/20/2015 7:32:33 AM [EXCH2-CU1] Copying 1 items, 21.31 KB (21,820 bytes). Skipping 0 items, 0 B (0 bytes).
    We could check if there are any subfolder which would not be merged and copied. If your import log has any abnormal, I suggest you send log file 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 2013 new batch migration missing option

    I installed exchange 2013 for a client about a month ago.
    Everything went well and they are using the New exchange .
    When using the new migration batch option I discovered I had an 3 option on the " start the batch" screen.
    The option was to " Start the batch automatically after time: " and it let me choose a time to start it.
    This option work great for those boxes I need to move at night.
    I am in the process of doing the same thing for a different client and the above option is missing.
    Does anyone know why I do not have this option. I have done the install the same as the first one.
    Installed using CU5. and all install options and config in the same.
    I look forward to your input

    Hi,
    What’s your Exchange version?
    I tested in my lab, Exchange 2013 CU1, there is no the “Start the batch automatically after time:” option to choose.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 SP1 cu8 - mssing cmdlet - Get-SendConnector command missing, cannot change smart host port

    Hi Everybody,
    For some reason my Exchange 2013 SP1 cu8 are missing a bunch of cmdlets.
    When i run the exchange powershell and get all the cmdlet command - i noticed all the send and receive connectors are missing.
    This all started when i needed to change the smart host port for a client because their internet provider was blocking port 25.
    So i did the traditional cmdlet
    Get-SendConnector
    Set-SendConnector -Indentity "connector name" -Port 551
    Both commands i get "The term Get-SendConnector is not recognized as the name of a cmdlet, function, etc"
    When i type Get-ExCommand
    Any reference to SendConnector and ReceiveConnector are not on the list.
    Am I missing somethings?  This is a classic example why GUI and cmdlet functions should both be available and not just on cmdlets.
    I went on other Exchange 2013 SP1 cu7 servers to see, and they all have the Send and Receive connectors in the cmdlets.
    The only difference with this particular setup, is that this is the first Exchange 2013 on-premise installation with Windows 2012 r2 Small Business Essentials.  However, i very much doubt the on-premise installation add-on to SBS would cause any issues
    to missing cmdlets.
    I searched all over the internet and found nothing.
    Now my biggest fear is to re-install Exchange and import the mailboxes manually.
    Any help is greatly appreciated.
    MattLok

    Hello
    check role asigment for your user:
    Get-ManagementRoleAssignment -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "administrator" }
    sorry my english

  • Object-Owner missing in Public Folder Calenders after Transition to Exchange 2013 SP1

    Hi there,
    we transfered all Public Folders from Exchange 2003 to 2010 to 2013 SP1. We have some Calendars with PublicFolderClientPermission Author witch includes EditOwnedItems and DeleteOwnedItems
    Unfortunately the Author Rights wont work after migration. it seems like the creator of the object got lost.
    since i never notices that in transitions from exchange 2003 to 2010, i think that should be related to the exchange 2013 transition.
    Can anybody approve or disprove that behavior?
    thanks alot

    Noticed now in the Exchange 2013 Event Logs that we're getting quite a few of these warnings:
    "Process <Select one exchange releated process>.exe (PID=<whatever>). Object [CN=Public Folder Database,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso,CN=Microsoft
    Exchange,CN=Services,CN=Configuration,DC=contoso,DC=local]. Property [PublicFolderDatabase] is set to value [contoso.local/Configuration/Deleted Objects/Public Folder Database
    DEL:ca62a715-05b2-4b08-ae0f-7f7c4b7e4cc3], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible."
    If i take a look at that mailbox database it's obvious that it's pointing towards the old Public Folder Database, which is quite interesting as Exchange 2013 isn't supposed to used that value at all (according to http://technet.microsoft.com/en-us/library/bb123971(v=exchg.150).aspx):
    [PS] C:\Windows\system32>Get-MailboxDatabase -Identity "Mailbox database" | fl
    PublicFolderDatabase                         : contoso.local/Configuration/Deleted Objects/Public Folder Database
        DEL:ca62a715-05b2-4b08-ae0f-7f7c4b7e4cc3
    I'm assuming this is what happens when messing around with ADSIEdit :) So, further ADSIEdits to set that value to null on the existing Mailboxdatabases, or anyone have any other suggestions?

  • Missing ECP directory in Exchange 2013/2010

    Hi Folks,
    I have an exchange 2013 and 2010 server running in a domain.
    I was trying to log into the Exchange Admin Centre on Exchange 2013. After typing the credentials the page just refreshed and set the prompt back in the password field.
    Doing a Get-ECPVirtualDirectory results in the message "An IIS directory entry couldn't be created. The error message is Access is denied", Category Info: Not Installed (myserver\ecp (Default Web Site):ADObjectId). FSComputername:(name of exchange
    2010 server).
    I am unable to either create or remove the ECP directory (although it claims one exists).  Opening the exchange management console on my 2010 server shows OWA is set up, but the ECP entry is blank.
    If I try and login to OWA I get the login screen, but after entering credentials I just get HTTP 400 bad request.
    In IIS on my 2013 server, there is an ecp directory with just a web.config and auth directory under the default website, there is also an ecp directory (containing contents) under the 'Exchange Back End' site.
    Does anyone know how to go about re-creating the ECP directory etc.
    Regards
    Andy

    Hi Andy
    Ensure that Microsoft Exchange Security Groups and Exchange Trusted Subsystem group should be a  member of the local admins and restart the server
    Steps:
     Launch IIS Manager Navigate to -> Web Sites -> Default Web Site Right Click on Default Web Site and choose Permissions Add Exchange Trusted Subsystem and grant Full Control Restart IIS Restart the server
    If none of the above works then try the following
    First remove the affected one 
    Get-ECPVirtualDirectory | Remove-ECpvirtualDirectory
    Then create a new one by following below 
    http://technet.microsoft.com/en-us/library/dd351218(v=exchg.150).aspx
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
    (MVP)

  • Seemingly successful install of Exchange 2013 SP1 turns into many errors in event logs after upgrade to CU7

    I have a new Exchange 2013 server with plans to migrate from my current Exchange 2007 Server. 
    I installed Exchange 2013 SP1 and the only errors I saw in the event log seemed to be long standing known issues that did not indicate an actual problem (based on what I read online). 
    I updated to CU7 and now lots of errors have appeared (although the old ones seem to have been fixed so I have that going for me). 
    Currently the Exchange 2013 server is not in use and clients are still hitting the 2007 server.
    Issue 1)
    After each reboot I get a Kernel-EventTracing 2 error.  I cannot find anything on this on the internet so I have no idea what it is.
    Session "FastDocTracingSession" failed to start with the following error: 0xC0000035
    I did read other accounts of this error with a different name in the quotes but still can’t tell what this is or where it is coming from.
    Issue 2)
    I am still getting 5 MSExchange Common 106 errors even after reregistering all of the perf counters per this page:
    https://support.microsoft.com/kb/2870416?wa=wsignin1.0
    One of the perf counters fails to register using the script from the link above.
    66 C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\InfoWorkerMultiMailboxSearchPerformanceCounters.xml
    New-PerfCounters : The performance counter definition file is invalid.
    At C:\Users\administrator.<my domain>\Downloads\script\ReloadPerfCounters.ps1:19 char:4
    +    New-PerfCounters -DefinitionFileName $f
    +    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo         
    : InvalidData: (:) [New-PerfCounters], TaskException
        + FullyQualifiedErrorId : [Server=VALIS,RequestId=71b6bcde-d73e-4c14-9a32-03f06e3b2607,TimeStamp=12/18/2014 10:09:
       12 PM] [FailureCategory=Cmdlet-TaskException] 33EBD286,Microsoft.Exchange.Management.Tasks.NewPerfCounters
    But that one seems unrelated to the ones that still throw errors. 
    Three of the remaining five errors are (the forum is removing my spacing between the error text so it looks like a wall of text - sorry):
    Performance counter updating error. Counter name is Count Matched LowFidelity FingerPrint, but missed HighFidelity FingerPrint, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The
    exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Performance counter updating error. Counter name is Number of items, item is matched with finger printing cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown
    is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Performance counter updating error. Counter name is Number of items in Malware Fingerprint cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException:
    The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Issue 3)
    I appear to have some issues related to the healthmailboxes. 
    I get MSExchangeTransport 1025 errors for multiple healthmailboxes.
    SMTP rejected a (P1) mail from 'HealthMailbox23b10b91745648819139ee691dc97eb6@<my domain>.local' with 'Client Proxy <my server>' connector and the user authenticated as 'HealthMailbox23b10b91745648819139ee691dc97eb6'. The Active Directory
    lookup for the sender address returned validation errors. Microsoft.Exchange.Data.ProviderError
    I reran setup /prepareAD to try and remedy this but I am still getting some.
    Issue 4)
    I am getting an MSExchange RBAC 74 error. 
    (Process w3wp.exe, PID 984) Connection leak detected for key <my domain>.local/Admins/Administrator in Microsoft.Exchange.Configuration.Authorization.WSManBudgetManager class. Leaked Value 1.
    Issue 5)
    I am getting MSExchange Assistants 9042 warnings on both databases.
    Service MSExchangeMailboxAssistants. Probe Time Based Assistant for database Database02 (c83dbd91-7cc4-4412-912e-1b87ca6eb0ab) is exiting a work cycle. No mailboxes were successfully processed. 2 mailboxes were skipped due to errors. 0 mailboxes were
    skipped due to failure to open a store session. 0 mailboxes were retried. There are 0 mailboxes in this database remaining to be processed.
    Some research suggested this may be related to deleted mailboxes however I have never had any actual user mailboxes on this server. 
    If they are healthmailboxes or arbitration mailboxes that might make sense but I am unsure of what to do on this.
    Issue 6)
    At boot I am getting an MSExchange ActiveSync warning 1033
    The setting SupportedIPMTypes in the Web.Config file was missing. 
    Using default value of System.Collections.Generic.List`1[System.String].
    I don't know why but this forum is removing some of my spacing that would make parts of this easier to read.

    Hi Eric
    Yes I have uninstalled and reinstalled Exchange 2013 CU7 for the 3<sup>rd</sup> time. 
    I realize you said one issue per forum thread but since I already started this thread with many issues I will at least post what I have discovered on them in case someone finds their way here from a web search.
    I have an existing Exchange 2007 server in the environment so I am unable to create email address policies that are defined by “recipient container”. 
    If I try and do so I get “You can't specify the recipient container because legacy servers are detected.”
     So I cannot create a normal email address policy and restrict it to an OU without resorting to some fancy filtering. 
    Instead what I have done is use PS to modify extensionAttribute1 (otherwise known as Custom Attribute 1 to exchange) for all of my users. 
    I then applied an address policy to them and gave it the highest priority. 
    Then I set a default email address policy for the entire organization. 
    After reinstalling Exchange all of my system mailboxes were created with the internal domain name. 
    So issue number 3 above has not come up. 
    For issue number one above I have created a new thread:
    https://social.technet.microsoft.com/Forums/office/en-US/7eb12b89-ae9b-46b2-bd34-e50cd52a4c15/microsoftwindowskerneleventtracing-error-2-happens-twice-at-boot-ex2013cu7?forum=exchangesvrdeploy
    For issue number four I have posted to this existing thread where there is so far no resolution:
    https://social.technet.microsoft.com/Forums/exchange/en-US/2343730c-7303-4067-ae1a-b106cffc3583/exchange-error-id-74-connection-leak-detected-for-key?forum=exchangesvradmin
    Issue number Five I have managed to recreate and get rid of in more than one way. 
    If I create a new database in ECP and set the database and log paths where I want, then this error will appear. 
    If I create the database in the default location and then use EMS to move it and set the log path, then the error will not appear. 
    The error will also appear (along with other errors) if I delete the health mailboxes and let them get recreated by restarting the server or the Health Manager service. 
    If I then go and set the retention period for deleted mailboxes to 0 days and wait a little while, these will all go away. 
    So my off hand guess is that these are caused by orphaned system mailboxes.
    For issue number six I have posted to this existing thread where there is so far no resolution:
    https://social.technet.microsoft.com/Forums/exchange/en-US/dff62411-fad8-4d0c-9bdb-037374644845/event-1033-msexchangeactivesync-warning?forum=exchangesvrmobility
    So for the remainder of this thread we can try and tackle issue number two which is the perf counters. 
    The exact same 5 perf counter were coming up and this had been true each time I have uninstalled and reinstalled Exchange 2013CU7. 
    Actually to be more accurate a LOT of perf counter errors come up after the initial install, but reloading the perf counters using the script I posted above reduces it to the same five. 
    Using all of your suggestions so far has not removed these 5 remaining errors either.  Since there is no discernible impact other than these errors at boot I am not seriously bothered by them but as will all event log errors, I would prefer
    to make them go away if possible.

  • Exchange 2013 - Quota notifications problem

    Hello,
    First of all I want to express mild disappointment with the way quota notification alerts are documented on Technet for Exchange 2013. The only reference I could find is that QuotaNotificationSchedule parameter of the Set-MailboxDatabase cmdlet no longer
    does anything: "This parameter has been deprecated in Exchange 2013 and it no longer does anything.".
    The only other reference I could find is this forum post:
    http://social.technet.microsoft.com/Forums/exchange/en-US/f30bb2ca-91ab-4e69-a8b6-720e6a8a5b83/exchange-2013-quota-notification-message-not-sent-during-schedule?forum=exchangesvrgeneral
    where it says: "Quota messages are generated once the user log in to mailbox in exchange 2013."
    However, Microsoft Press published a book in 2013 "Inside Out: Microsoft Exchange Server 2013: Mailbox and High Availability" where QuotaNotificationSchedule parameter is being referenced as a working parameter which controls when Quota notification
    are being sent.
    My experience says that the forum post is correct.
    Now onto the problem.
    While our customer was still on Exchange 2010 they were the victims of this issue:
    http://support.microsoft.com/kb/2480474/en-us which could easily be fixed with
    CheckWarningQuota registry key.
    Now we have migrated those mailboxes to Exchange 2013 and again, users are not receiving quota notification e-mails. Only a few users receive quota notifications e-mails and those are users that got their mailbox created on the new Exchange 2013 system.
    Migrated users do not receive notifications. We have tried CheckWarningQuota on Exchange 2013 but it does nothing. Our theory is that mailbox flag introduced in Exchange 2010 SP1 is migrated with the mailboxes to Exchange 2013 and is the
    reason why we are not receiving quota notifications again.
    I appreciate thoughts and comments.
    Regards,
    Dinko

    CU8 addresses this issue, however, only for mailboxes not yet moved to 2013: https://support.microsoft.com/en-us/kb/303695
    Mailboxes already moved will have to be manually fixed. The issue is they are missing their lcid (location ID). For whatever reason, the attribute does not make it across from 2010 to 2013. However, if you move the mailbox again to another 2013 database,
    it fills in the lcid automatically. That is one workaround, but not necessarily a good one for people who have migrated a ton of their users already. So what do you do?
    In the KB article, it shows you how to identify the users who are missing their LCID by doing the following in the exchange management shell:
    #first load in the ManagedStoreDiagnosticFunctions, you will need this for the get-storequery cmdlet to work.
    . .\'C:\Program Files\Microsoft\Exchange Server\V15\Scripts\ManagedStoreDiagnosticFunctions.ps1'
    #then generate the list of all mailboxes with an LCID of 0.
    $mbxs = get-mailbox –resultsize unlimited| ? {$_.exchangeversion.exchangebuild.major -ge 15}
    $mbxsq = $mbxs | %{Get-StoreQuery -Database $_.database -query "select * from Mailbox where Mailboxguid = '$($_.ExchangeGuid)'"}
    $mbxsq | ? {$_.lcid -eq 0} |fl displayname, mailboxguid, lcid
    You can modify the script to dump the list to a text file if you need to.
    Now, to address this, I simply populated the lcid for all my mailboxes. All of mine were en-US or lcid 1033, so it was easy to set them all at once. I just grabbed all Exchange 2013 mailboxes and applied the language (en-US) and DateFormat (MM/dd/yyyy) to
    them (replace DOMAIN with your domain name) which in turn sets the lcid to 1033:
    $mailboxes = get-mailbox -resultsize unlimited| ? {$_.exchangeversion.exchangebuild.major -ge 15}
    ($mailboxes).SamAccountName| %{set-MailboxRegionalConfiguration "DOMAIN\$_" -Language en-us -DateFormat MM/dd/yyyy} | FT -a
    Incidentally, if you have already migrated all of your 2010 mailboxes, and you are on at least Exchange 2013 CU6, that script will resolve the issue whether you apply CU8 or not. CU8 fixes it for any other mailboxes that have not yet been migrated to 2013.
    Hopefully this help you out.
    Chris Allen
    Microsoft Support Escalation Engineer

  • Exchange 2013 Untrusted Cross-Forest Availability Intermittently Working

    Goal:
    I’m attempting to configure cross-forest availability for Exchange 2013 using the instructions here:
    http://technet.microsoft.com/en-us/library/bb125182%28v=exchg.150%29.aspx
    At the very bottom of the page are three different methods.  I have tried the first (per-user) and the third (untrusted) methods, with identical results.  For various unfortunate reasons, I am unable to use the Microsoft Federated Gateway for availability
    information (although that is configured in the production domain and I would use it if it were possible). 
    Situation:
    When attempting to view availability information in either OWA or Outlook, the free/busy information typically isn’t visible.  If you open and close Outlook a few times, creating meetings with the users in other domains, sometimes the other user’s information
    will be visible, and sometimes it will not.  When it is not, the area is filled with diagonal lines and hovering over it says “No Information”.  The situation is the same in both Adatum trying to access Contoso, and in Contoso trying to access either
    Adatum or Fabrikam.
    I’m currently close to finishing up my third week with Microsoft Support on this issue, and am starting over with a third first level support person.  They are quickly eroding what little confidence I had in them already.  I’m posting here because
    I’m desperate, and web searches for my errors turn up zero results.  I fear this method of availability sharing doesn’t actually work correctly in Exchange 2013 as Microsoft is pushing organizations to use the Microsoft Federated Gateway, but I’d love
    to heave about anyone getting this to work, or not.
    Setup:
    There are three separate domains I am working with (names changed to protect the innocent).  Contoso.local is the production domain, containing Exchange 2007 and Exchange 2013 SP1 servers.  Adatum.local is a test domain set up fresh with Exchange
    2013 SP1.  Fabrikam.com is a remote Exchange system that I others are connecting to without issue using Exchange 2010.
    The Contoso and Adatum domain controllers are running Windows Server 2008 R2 SP1 and are running at a 2008 R2 functional levels.  The Exchange 2013 servers are all at SP1 (results were the same prior to SP1), and the OS is Windows Server 2012. 
    Contoso has two sites, connected via 10Gbps links, and ~10ms latency, with Exchange 2013 CAS and mailbox servers in both sites.  Adatum has a single site, and has two CAS and two mailbox servers.  Fabrikam has one internet facing server to connect
    to.  A handful of contacts have been created in both Contoso and Adatum for the other domains, to select to view availability.
    Contoso and Adatum domains sit on different subnets, but there is no firewall or filtering between their subnets.  Routing between them is completely unimpeded.  The Fabrikam server sits on another network across the internet, but firewalls have
    been configured and I can browse the availability website from the Contoso CAS servers.
    The CAS servers were originally set up to be load balanced, but working with Microsoft they’ve had me specify a single CAS server for autodiscover/EWS/ECP/OWA/etc in both Contoso and Adatum.  The number of actual users on Exchange 2013 in Contoso is
    ~10.  In Adatum, there are only a handful of mailboxes configured.  The Exchange 2007 servers in Contoso are using Public Folders for free/busy replication for other domains right now, and we don’t care at the moment if they can use the 2013 availability. 
    None of our testing/configurations have involved the Exchange 2007 servers.  There are no SPNs configured for the other domains in AD.
    Errors:
    There are three basic errors that are returned in Outlook diagnostics.  The first is the timeout error.  For a given mailbox server, the first time it is queried for availability information for a remote domain (after some amount of time of being
    idle) it might not respond for 70 seconds (actually somewhere between 69 and 70 seconds each time when viewing the IIS logs), and eventually fails with the timeout error.  If it doesn’t timeout, then it will respond with the Correct Response.
    Once a particular mailbox server has timed out, it will typically immediately return the first Availability Error for all subsequent calls.  Less frequently, it will return Availability Error 2.  If a mailbox server returns the first Availability
    Error, then it will continue to return that error until it times out again or starts working.  Similarly, if a mailbox server returns the second Availability Error, then it will continue to return that error until it times out again or starts working.
    If an IISRESET is performed on a mailbox server, then it will either timeout at the next cross-forest availability request, or work.  There is never an issue accessing availability information for users in the same domain as the request.
    If the remote Exchange is in an errored state, then the response includes the error.  For example, if the mailbox servers in the remote domain are turned off, and the local mailbox server that you are querying happens to be responding correctly
    for the remote domain, then it will return an error about how no mailbox servers are available in adatum.local to service the request.
    There are no Event Log errors that correspond to failed requests of any type.  IIS logs don’t show anything beyond what is shown in the Outlook diagnostics.  There are no DNS or Active Directory Replication errors in the Event Logs.
    Timeout error:
    CalendarEvents       : {}
    ViewType             : None
    MergedFreeBusyStatus : {}
    WorkingHours         :
    Result               : Error
    ErrorCode            : ErrorTimeoutExpired
    ErrorMessage         : Microsoft.Exchange.InfoWorker.Common.Availability.TimeoutExpiredException: Request could not be processed in time. Timeout occurred during 'LookupRecipientsBatchBegin'.
                           . Name of the server where exception originated: Mailbox01
    ErrorDetails         : {}
    ErrorProperties      : {}
    Availability Error:
    CalendarEvents       : {}
    ViewType             : None
    MergedFreeBusyStatus : {}
    WorkingHours         :
    Result               : Error
    ErrorCode            : ErrorProxyRequestProcessingFailed
    ErrorMessage         : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AutoDiscoverFailedException:
    AvailabilityAddressSpace 'adatum.local' couldn't be used because the Autodiscover endpoint couldn't be discovered.
                           . Name of the server where exception originated: Mailbox01
    ErrorDetails         : {}
    ErrorProperties      : {}
    Availability Error 2:
    CalendarEvents       : {}
    ViewType             : None
    MergedFreeBusyStatus : {}
    WorkingHours         :
    Result               : Error
    ErrorCode            : ErrorProxyRequestProcessingFailed
    ErrorMessage         : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AddressSpaceNotFoundException:
    Configuration information for forest/domain swelab.wayad.corp.wayport.net could not be found in Active Directory.
                              at Microsoft.Exchange.InfoWorker.Common.Availability.TargetForestConfigurationCache.FindByDomain(OrganizationId
    organizationId, String domainName)
                              at Microsoft.Exchange.InfoWorker.Common.Availability.QueryGenerator.GetTargetForestConfiguration(EmailAddress
    emailAddress)
                           . Name of the server where exception originated: Mailbox02
    ErrorDetails         : {}
    ErrorProperties      : {}
    Working:
    CalendarEvents       : {Microsoft.Exchange.WebServices.Data.CalendarEvent}
    ViewType             : FreeBusyMerged
    MergedFreeBusyStatus : {Free, Free, Free, Free...}
    WorkingHours         : Microsoft.Exchange.WebServices.Data.WorkingHours
    Result               : Success
    ErrorCode            : NoError
    ErrorMessage         :
    ErrorDetails         : {}
    ErrorProperties      : {}
    Start : 04/09/2014 00:00:00
    End : 04/12/2014 00:00:00
    Subject :
    Location :
    Testing Methodologies:
    While it is possible to dig through Outlook diagnostics and OWA, we ended up scripting out these requests to save time.  Microsoft support refuses to use the scripts, but they produce the same output that it takes them days to find in the logs, so I’ll
    post them here to help anyone in the future.
    Through reading the documentation and experimenting, it appears that the Exchange 2013 CAS servers really do just proxy availability requests from the client to the mailbox servers.  At least by default, it seems to pick a mailbox server in the same
    site, but which mailbox server in the site appears to be random.  It will typically pick the same one repeatedly for a while.
    The first script uses the Microsoft Exchange Web Services Managed API 2.1.
    http://www.microsoft.com/en-us/download/details.aspx?id=42022
    You specify a source email address, and a target address in the remote domain, and it creates a SOAP request that it sends to a CAS server of the source email address.  The CAS proxies the request to the mailbox server which either responds with a failure
    or the free/busy data.
    The second script takes the XML SOAP request generated by the first script, and uses that to query a mailbox server directly.  That allows you to test specific mailbox servers that are working or failing, instead of randomly using whichever mailbox
    server the CAS happens to select.  I generated a SOAP request with the first script that I knew had some data, and then copy/pasted it into the second script to verify if data was being returned.
    I’ve deleted and recreated the availability address spaces in Contoso and Adatum for each other and Fabrikam multiple times.  I’ve reset the password in the OrgWideAccount in both Adatum and Contoso, and viewed the lastBadPassword attribute in both
    ADs to verify it wasn’t failing authentication.  (A failed authentication also generates a 401 error that is returned to the client.)  I can access the availability site of the other domain using the credentials of the OrgWideAccount without any
    errors ever.
    First Script:
    # Import the Exchange Web Services module
    Import-Module -Name "C:\Program Files (x86)\Microsoft\Exchange\Web Services\2.1\Microsoft.Exchange.WebServices.dll"
    # Create the services object used to connect to Exchange
    # You can specify a specific Exchange version, which I had to do to connect to 2007
    # Exchange2007_SP1
    # Exchange2010
    # Exchange2010_SP1
    # Exchange2010_SP2
    # Exchange2013
    # $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1
    # $Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
    $Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService
    $Service.UseDefaultCredentials = $true
    # Specify an SMTP address. The autodiscover URL from the associated mailbox will be used to connect to Exchange
    # This is used to distinguish resolving from the 2007 server versus 2013
    #$Service.AutodiscoverUrl("[email protected]") # For Exchange 2007
    $Service.AutodiscoverUrl("[email protected]") # For Exchange 2013
    # Increase the amount output at the end to include the SOAP commands
    $Service.TraceEnabled = $true
    # Specify time frame to get free/busy for
    $StartTime = [DateTime]::Parse([DateTime]::Now.ToString("yyyy-MM-dd 0:00"))
    $EndTime = $StartTime.AddDays(7)
    # Create the various objects needed to perform the EWS request
    $drDuration = new-object Microsoft.Exchange.WebServices.Data.TimeWindow($StartTime,$EndTime)
    $AvailabilityOptions = new-object Microsoft.Exchange.WebServices.Data.AvailabilityOptions
    $AvailabilityOptions.RequestedFreeBusyView = [Microsoft.Exchange.WebServices.Data.FreeBusyViewType]::DetailedMerged
    $Attendeesbatch = New-Object "System.Collections.Generic.List[Microsoft.Exchange.WebServices.Data.AttendeeInfo]"
    $attendee = New-Object Microsoft.Exchange.WebServices.Data.AttendeeInfo($userSMTPAddress)
    # Specify SMTP addresses of accounts to request availability for
    #$Attendeesbatch.Add("[email protected]")
    $Attendeesbatch.Add("[email protected]")
    #$Attendeesbatch.Add("[email protected]")
    #$Attendeesbatch.Add("[email protected]")
    # Clear out old results so that a failed request doesn't show information still
    $availresponse = ""
    # Request the availability information from Exchange
    $availresponse = $service.GetUserAvailability($Attendeesbatch,$drDuration,[Microsoft.Exchange.WebServices.Data.AvailabilityData]::FreeBusy,$AvailabilityOptions)
    # Show summary information that would include errors
    $availresponse.AttendeesAvailability
    # Show all of the appointments in the requested time period
    foreach($avail in $availresponse.AttendeesAvailability){
    foreach($cvtEnt in $avail.CalendarEvents){
    "Start : " + $cvtEnt.StartTime
    "End : " + $cvtEnt.EndTime
    "Subject : " + $cvtEnt.Details.Subject
    "Location : " + $cvtEnt.Details.Location
    Second Script:
    # Change the server in this URL to specify which mailbox server to access
    $url = 'https://mailbox01.contoso.local:444/EWS/Exchange.asmx'
    # Uncomment the below lines if you want to query EWS using credentials other than
    # the ones used to run the script.
    #If(!(Test-Path variable:global:cred))
    # $cred = Get-Credential
    function Execute-SOAPRequest
    [Xml] $SOAPRequest,
    [String] $URL
    write-host "Sending SOAP Request To Server: $URL"
    $soapWebRequest = [System.Net.WebRequest]::Create($URL)
    # These appear to be the only things needed in the headers when making the request
    $soapWebRequest.ContentType = 'text/xml;charset="utf-8"'
    $soapWebRequest.Accept = "text/xml"
    $soapWebRequest.Method = "POST"
    If(Test-Path variable:global:cred)
    $soapWebRequest.Credentials = $cred
    Else
    $soapWebRequest.UseDefaultCredentials = $true
    write-host "Initiating Send."
    $requestStream = $soapWebRequest.GetRequestStream()
    $SOAPRequest.Save($requestStream)
    $requestStream.Close()
    write-host "Send Complete, Waiting For Response."
    $resp = $soapWebRequest.GetResponse()
    $responseStream = $resp.GetResponseStream()
    $soapReader = [System.IO.StreamReader]($responseStream)
    $ReturnXml = [Xml] $soapReader.ReadToEnd()
    $responseStream.Close()
    write-host "Response Received."
    return $ReturnXml
    # The specing and line returns in the below variable are important for some reason
    # For example, there must be a line return after the @' on the first line, or it's invalid...
    # Change the line with this:
    # <t:Address>[email protected]</t:Address>
    # to the email address in the domain you want to query
    $soap = [xml]@'
    <?xml version="1.0" encoding="utf-8"?>
    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
    <t:RequestServerVersion Version="Exchange2013_SP1" />
    <t:TimeZoneContext>
    <t:TimeZoneDefinition Name="(UTC-06:00) Central Time (US &amp; Canada)" Id="Central Standard Time">
    <t:Periods>
    <t:Period Bias="P0DT6H0M0.0S" Name="Standard" Id="Std" />
    <t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/1" />
    <t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/2007" />
    </t:Periods>
    <t:TransitionsGroups>
    <t:TransitionsGroup Id="0">
    <t:RecurringDayTransition>
    <t:To Kind="Period">Dlt/1</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>4</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>1</t:Occurrence>
    </t:RecurringDayTransition>
    <t:RecurringDayTransition>
    <t:To Kind="Period">Std</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>10</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>-1</t:Occurrence>
    </t:RecurringDayTransition>
    </t:TransitionsGroup>
    <t:TransitionsGroup Id="1">
    <t:RecurringDayTransition>
    <t:To Kind="Period">Dlt/2007</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>3</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>2</t:Occurrence>
    </t:RecurringDayTransition>
    <t:RecurringDayTransition>
    <t:To Kind="Period">Std</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>11</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>1</t:Occurrence>
    </t:RecurringDayTransition>
    </t:TransitionsGroup>
    </t:TransitionsGroups>
    <t:Transitions>
    <t:Transition>
    <t:To Kind="Group">0</t:To>
    </t:Transition>
    <t:AbsoluteDateTransition>
    <t:To Kind="Group">1</t:To>
    <t:DateTime>2007-01-01T06:00:00.000Z</t:DateTime>
    </t:AbsoluteDateTransition>
    </t:Transitions>
    </t:TimeZoneDefinition>
    </t:TimeZoneContext>
    </soap:Header>
    <soap:Body>
    <m:GetUserAvailabilityRequest>
    <m:MailboxDataArray>
    <t:MailboxData>
    <t:Email>
    <t:Address>[email protected]</t:Address>
    </t:Email>
    <t:AttendeeType>Required</t:AttendeeType>
    <t:ExcludeConflicts>false</t:ExcludeConflicts>
    </t:MailboxData>
    </m:MailboxDataArray>
    <t:FreeBusyViewOptions>
    <t:TimeWindow>
    <t:StartTime>2014-04-03T00:00:00</t:StartTime>
    <t:EndTime>2014-04-10T00:00:00</t:EndTime>
    </t:TimeWindow>
    <t:MergedFreeBusyIntervalInMinutes>30</t:MergedFreeBusyIntervalInMinutes>
    <t:RequestedView>DetailedMerged</t:RequestedView>
    </t:FreeBusyViewOptions>
    </m:GetUserAvailabilityRequest>
    </soap:Body>
    </soap:Envelope>
    $ret = Execute-SOAPRequest $soap $url
    # Uncomment out one of the below two lines to get output in different alternative formats
    #$ret | Export-Clixml c:\temp\1.xml;Get-Content c:\temp\1.xml
    #$ret.InnerXml
    # If the request is successful, show the appointments, otherwise show the failure message
    If ($ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessage.ResponseClass -eq 'Success')
    $ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.FreeBusyView.CalendarEventArray.CalendarEvent
    Else
    $ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessage

    In this case, the SMTP domain is the same as the AD domain.  If the wrong domain were configured then the connection would never work, as opposed to sometimes work.
    RunspaceId            : abb30c12-c578-4770-987f-41fe6206a463
    ForestName            : adatum.local
    UserName              : adatum\availtest
    UseServiceAccount     : False
    AccessMethod          : OrgWideFB
    ProxyUrl              :
    TargetAutodiscoverEpr :
    ParentPathId          : CN=Availability Configuration
    AdminDisplayName      :
    ExchangeVersion       : 0.1 (8.0.535.0)
    Name                  : adatum.local
    DistinguishedName     : CN=adatum.local,CN=Availability Configuration,CN=Wayport,CN=Microsoft
                            Exchange,CN=Services,CN=Configuration,DC=contoso,DC=local
    Identity              : adatum.local
    Guid                  : 3e0ebc2c-0ebc-4be8-83d2-077746180d66
    ObjectCategory        : contoso.local/Configuration/Schema/ms-Exch-Availability-Address-Space
    ObjectClass           : {top, msExchAvailabilityAddressSpace}
    WhenChanged           : 4/15/2014 12:33:53 PM
    WhenCreated           : 4/15/2014 12:33:35 PM
    WhenChangedUTC        : 4/15/2014 5:33:53 PM
    WhenCreatedUTC        : 4/15/2014 5:33:35 PM
    OrganizationId        :
    OriginatingServer     : dc01.contoso.local
    IsValid               : True
    ObjectState           : Unchanged

Maybe you are looking for