2010
161 TopicsHow to Troubleshoot EWS Connection Issues Using EWS Editor
How to Troubleshoot EWS Connection Issues Using EWS Editor Problem: You get errors when you use any application to connect to (or execute a specific action upon) a mailbox or public folder via the Exchange Web Services (EWS) protocol. Solution: To verify if an error is related to application or to your environment, you can use a tool called EWS Editor to connect to the mailbox or public folder that causes errors and check if the error appears. This can be very useful in scenarios when: An application cannot establish connection to a mailbox or upload/download required data An application cannot access public folders An application cannot impersonate a mailbox – Connecting to a mailbox via EWSEditor 1. Go to the https://github.com/dseph/EwsEditor/releases and download the bin package. 2. Copy the downloaded file to the machine where application is installed and extract it. 3. Open the program and click File > New Exchange Service (Fig. 1.). Fig. 1. Creating a new EWS connection to a mailbox in EWSEditor. 4. Use the Autodiscover Email option or manually provide the Service URL by using the FQDN of the machine you are connecting to (CAS server). If you use Office 365, click the 365 Default button (Fig. 2.). Note : The Service URL for EWS should be as follows: https: machine FQDN>/EWS/Exchange.asmx for example: https://exchange.example.com/EWS/Exchange.asmx Fig. 2. Configuring the EWS connection. 5. Configure the authentication options: o Direct access: If you want to access your mailbox directly, select Use the following credentials instead of the default Windows credentials and provide the user name and password for that mailbox account (Fig. 3.). o Mailbox impersonation: If you want to connect to another mailbox by using the admin’s credentials, click Use the following credentials instead of the default Windows credentials and provide the administrator’s credentials. After that, select the Check if using EWS Impersonation checkbox and provide the primary SMTP address of the mailbox you want to access. Fig. 4. Configuring a connection to a mailbox as an administrator, by using impersonation. 6. When the configuration is complete, click OK. If the connection is successful, you will see a confirmation in the program. If the connection is not successful, the software will throw an error. The appearance of any errors means that the mailbox connection problem is not related to your application and the problem relates to your environment. If you are getting Error 500, then probably your XML configuration file for web services (including EWS) is corrupted. Please consider reverting any recent changes made to that file. Browsing a mailbox Directly after you finish configuring the connection, you get a prompt asking if you want to add the mailbox root to the tree view. Please confirm by clicking Yes (Fig. 5.). Fig. 5. The prompt that allows you to browse the mailbox content in EWSEditor. After the addition is complete, you can browse the content of your mailbox under Root\Top of Information Store (Fig. 6.). If you are getting any errors while accessing any of the folders within that container, it means that the mailbox is corrupted. Fig. 6. Browsing the content of a mailbox. Browsing public folders To browse public folders of a mailbox account that you added to the EWSEditor’s tree view, right-click the name (email address) of the mailbox at the very top of the tree, and select Add Root Folder. After selecting Identify folder by well known name, choose PublicFoldersRoot (Fig. 7.) and click OK. Fig. 7. Adding public folders to the mailbox tree view. If you are getting any errors when accessing public folders, this might mean that public folders are not yet created or their creation is still pending. However, if you are getting trouble accessing some particular public folders, it means that you are missing some of the required permissions. Reference : http://jasparrow.info/2020/08/how-to-troubleshoot-ews-connection-by-using-ews-editor/ Regards Jason60KViews1like0CommentsRoom calendar working hours not showing properly in Outlook
Hej guys, Please correct me if I am being crazy but I have an issue with the working hours display when viewing a room mailbox calendar through Outlook. In OWA and the scheduling assistant it's fine. For example, I have created a brand new room mailbox in Exchange 2016 CU4. The working hours are default at 0800 - 1700, weekdays only and PST. When viewed through Outlook the whol day is grey, when using the scheduling assistant or OWA the working hours are displayed okay. Technically this should not be an issue as I do not block booking rooms based on working hours. But the user experience is a bit crap and it could cause support cases. Any clues what to look for? Thanks in advance Neil46KViews0likes20CommentsInvalid characters in UPN and email address
Hi, Quite a large number of mailboxes are not sync to Cloud because special characters are not supported in Office 365. Is invalid character support in: - public folders where email address has special character? - distribution list? - mail contact? Thank youSolved39KViews0likes3CommentsExchange Hybrid Mailbox Migration - RecipientNotFoundPermanentException
Exchange 2010 (14.3.468.0) is already setup as Exchange Hybrid with Office 365 and is working aswell. Unfortunately some mailbox migration fail. RecipientNotFoundPermanentException: Error: Cannot find a recipient that has mailbox GUID '*************************'. Log of failed migration: 'MigrationService (im Auftrag von "***")' created move request. 'MigrationService (im Auftrag von "***")' allowed a large amount of data loss when moving the mailbox (*** bad items, *** large items). The Microsoft Exchange Mailbox Replication service '***.PROD.OUTLOOK.COM' (*** ServerCaps:***, ProxyCaps:***, MailboxCaps:, legacyCaps:***) is examining the request. Content from the Shard mailbox (Mailbox Guid: ***, Database: ***) will be merged into the target mailbox. Connected to target mailbox '***.onmicrosoft.com\*** (Primary)', database '***', Mailbox server '***.PROD.OUTLOOK.COM' Version *** (Build ***). Fatal error RecipientNotFoundPermanentException has occurred. This also happens randomly to newly created mailboxes, that we try to test to migrate - some working, others not. Log of successfully migrated mailbox. 'MigrationService (im Auftrag von "***")' created move request. 'MigrationService (im Auftrag von "***")' allowed a large amount of data loss when moving the mailbox (*** bad items, *** large items). The Microsoft Exchange Mailbox Replication service '***.PROD.OUTLOOK.COM' (*** ServerCaps:***, ProxyCaps:***, MailboxCaps:, legacyCaps:***) is examining the request. Content from the Shard mailbox (Mailbox Guid: ***, Database: ***) will be merged into the target mailbox. Connected to target mailbox '***.onmicrosoft.com\*** (Primary)', database '***', Mailbox server '***' Version *** (Build ***). Connected to source mailbox '***.onmicrosoft.com\*** (Primary)', database '***', Mailbox server '***' Version *** (Build ***), proxy server '***' *** ServerCaps:, ProxyCaps:, MailboxCaps:, legacyCaps:***. Request processing started.Solved25KViews0likes3CommentsExchange 2010 and 2016 coexistence
We've just installed Exchange server 2016 in an existing Exchange server 2010 environment. We've had an issue where the Default receive connector on the HT servers has been configured to only receive mail from certain servers for some reason, and this was stopping some users from sending mail internally. We fixed this up, but I can't get my head around why the Exchange 2016 got involved in this internal mail flow in the first place. None of the namespace or mailflow cutover has occured yet, only the intitial install of the Exchange servers, so I would have thought that internal mail flow would have been through the Exchange 2010 servers only. If anyone can let me know what happens upon the intitial installation of Exchange 2016 that cuases it to be involved in the internal mail flow, that would be great. some Technet articles describing this would be prefect.Solved18KViews0likes7Commentsunable to delete email in deleted item
I try unable to delete the email in deleted item It shows this error "Some items cannot be deleted. They were either moved or already deleted or access was denied" I also try to migrate this mailbox to office365 It shows this error : Mailbox dumpster size 30 GB (32,213,335,723 bytes) exceeds target quota 30 GB (32,212,254,720 bytes). --> Mailbox dumpster size 30 GB (32,213,335,723 bytes) exceeds Anyone have solution for this issue?17KViews0likes10CommentsHybrid Exchange change of SMTP relay connector
Hi All So we have Hybrid Exchange environment, with few 2010 Exchange boxes on-prem, 1x Exchange 2016 on-prem (as the hybrid) and O365 tenant. Until now we were using one of the EX2010 boxes as main smtp relay and it`s working great. Now we want to switch that role and move it to the hybrid 2016 Exchange. To beused by the internal scan2email, apps, etc for sending anonym. All FW rules are configured correctly. The ext IP address of the 2016 box is added as trusted connector in EXO I have send/recieve connectors configured on the 2016 box The problem: If I go and test telnet (EXO ext IP) 25 - from within the EX2010 box, I got connection and response and all is nice and shiny If I try to do the same from the hybrid 2016 box - got connection open and blank screen. Stays for about 60 seconds and then Connection closed. No need to say that it is not forwarding anything if I try lets sat scan2email from one of the printers. I found in the logs some errors saying socket error - but it doesnt make sense because the fw shows all connections as allowed and as I said the fw rules are the same for EX2010 and EX2016 boxes, the difference is that they are presented with different ext IPs, but both of them added as trusted in EXO Admin Any ideas? I cant find any other reason why it would not establish smtp connection to the EXO ?Solved14KViews0likes8CommentsExchange Management Shell: Getting title in Get-Mailbox for all results
I am trying to get a list of mailboxes that have been hidden from the GAL. The results have the contain there name, a true or false for HiddenFromAddressListsEnabled and there (job)title. The problem is that the title can only be called with Get-User. I found how to combine the two. But the result only show the Title on the last result. Sofar i have this. For testing limited to 10 Get-Mailbox -ResultSize 10 | Select Name,HiddenFromAddressListsEnabled, @{n="Title";e={(get-user $_.name).title }} Im problably missing something really simple here but i cant see it.Solved13KViews0likes3Comments432 4.2.0 STOREDRV.Deliver.Exception:MailboxInTransitException.MapiExceptionMailboxInTransit; Failed
Hi All, Many thanks in advance, we had a user whose mailbox was previously in on-prem Exchange 2010 environment and then we migrated over to Office365. Now, for some reason when a mail is being routed in the on-prem environment to her mailbox in Online, the mail for some reason gets queued up inon-prem exchange StoreDriver with recipientstatus logged as: 432 4.2.0 STOREDRV.Deliver.Exception:MailboxInTransitException.MapiExceptionMailboxInTransit; Failed to process message due to a transient exception with message Cannot open mailbox and so on... When checked with get-moverequest, got the status as completedwithwarnings. So, looking for what could be the issue on this.13KViews0likes2CommentsLogParser date-time with another fields
Hello, My name is Tomas, I try to combine SELECT With date-time but when I try to organize by group and order I have this error: Command: PS C:\Program Files (x86)\Log Parser 2.2> .\LogParser.exe "SELECT [#Fields: date-time] as date-time, REVERSEDNS(EXTRACT_PREFIX(remote-endpoint,0,':')) as RemoteSenderDNS, EXTRACT_PREFIX(remote-endpoint,0,':') as RemoteSenderIP, Count(*) as Hits FROM c:\tools\*.log GROUP BY RemoteSenderIP ORDER BY HITS DESC" -i:CSV -nSkipLines:4 ERROR: Error: Semantic Error: SELECT clause field-expression "date-time" is not an aggregate function and does not contain GROUP BY field-expressions I'm a new with Logparser, I'm trying for 6 days!!!! Thanks!12KViews0likes3Comments