Solutions (36)
You may recieve the below error when try to access the OWA (Outlook Web App) published through Microsoft TMG 2010. The Outlook Web App (OWA) login page will appear without an issue, but after providing the username and password you will recieve website can not be found error. ------ The website cannot be found Technical Information (for support personal) Error Code 11001: host not found Background: This error indicates that the gateway or proxy server could not find the IP address of an upstream server. --- How to Fix: As the error indicates, this issues happens because the TMG server unable to reach the exchange server. It mostly related to the DNS resolution issue as you might have given the Exchange Server name in "this rule applies to this published site" section in "To" tab of the publishing policy. To verify the error is due to it, try testing the…
Published in
Solutions
MS has recently released the Service Pack 2 for the Exchange Management Pack, and the same has been now temporarily removed from the Download Center due to the issue of mailbox quarantining when the free space availability on the Transaction Log Drive is low. You may see the following entries on your event log, if you are affected with this issue. Log Name: Application Source: MSExchangeIS Event ID: 10018 Task Category: General Level: Error Description: The mailbox for user <guid>: /o=Contoso /ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=UserMailbox has been quarantined. Access to this mailbox will be restricted to administrative logons for the next 6 hours. Log Name: Microsoft-Exchange-Troubleshooters/Operational Source: Database Space Event ID: 5410 Level: Warning Keywords: Classic Description: The database space troubleshooter quarantined mailbox <guid> in database <DBName>. To know more about this issue, read the below blog from Exchange Team. Mailboxes on a database are Quarantined in an environment…
Published in
Solutions
When you try to run the new-TestCasConnectivityUser.ps1 script to create the test user account for the Test-OutlookWebservice and other tests in your Exchange 2010, the below error may be occure. "CreateTestUser : Mailbox could not be created. Verify that OU ( Users ) exists and that password meets complexity requirements" The error will continue to generate even though if you give complex password. This is because, there could be another OU exists in your organization with the name "Users" and which creates issue to the script.All you need to do is to update the assigned value to the $OrganizationalUnit variable with "domain.local/Users" in the new-TestCasConnectivityUser.ps1. Run the script again, and it should create the test user successfully. -Praveen
Published in
Solutions
You may receive NDR something similar to below when sending emails from your Outlook 2007/2010. 'This email address is being protected from spambots. You need JavaScript enabled to view it.' (MAILTO:This email address is being protected from spambots. You need JavaScript enabled to view it.) IMCEAMAILTO-xxx%2B40xxx%This email address is being protected from spambots. You need JavaScript enabled to view it.> A problem occurred and this message couldn't be delivered. Check to be sure the e-mail address is correct. If the problem continues, please contact your helpdesk. Diagnostic information for administrators: Generating server: ExHub.ed.local This email address is being protected from spambots. You need JavaScript enabled to view it. #550 5.4.4 ROUTING.NoConnectorForAddressType; unable to route for address type ## If you give a close look, you can see mailto parameter in those emails are creating issues. When we type an email address inside the square brackets after the Mailto: header, the email address is displayed as an incorrect hyperlink which causes the NDR to generate. Microsoft has released hotfix for this issue and is available to download here, Office 2010 - http://support.microsoft.com/kb/2597052 Office 2007 - http://support.microsoft.com/kb/2475888 -Praveen
Published in
Solutions
Microsoft has released a fix to resolve the issue for "EMC (Ex 2010 / 2007) fail to close with the error "You must close all dialog boxes before you can close Exchange Management Console" when IE9 is installed. The issue details have already discussed in the below post. Did Your EMC (Ex 2010 / 2007) fail to close with the error "You must close all dialog boxes before you can close Exchange Management Console"? Below blog can direct you to obtain the hotfix from Microsoft support, currently it is not available for public download. A fix for the interoperability issues between Exchange 2007 and 2010 EMC and IE9 is now available -Praveen
Published in
Solutions
There was a blog from Exchange Team about this issue last day, it normally appears after you install IE9 on the machine where you have the Exchange 2010 or Exchange 2007 management tools installed. The error message is, “You must close all dialog boxes before you can close Exchange Management Console”, though there are no property windows left open. There is no solution/workaround has been really in place now, however the team is working on to provide us with a fix on this as soon as possible. Read Exchange Team post for more updates on this -Praveen
Published in
Solutions
I have seen few queries on exchange forums about this issue on exchange 2010. The scenario is, An external user (e.g. “This email address is being protected from spambots. You need JavaScript enabled to view it.”) is able to send email to all users of the organization but not to a specific user "This email address is being protected from spambots. You need JavaScript enabled to view it.". At the same time some other user from the same external domain (e.g. "This email address is being protected from spambots. You need JavaScript enabled to view it.") can send email to the specific user, "This email address is being protected from spambots. You need JavaScript enabled to view it.". This scenario happens when you have an edge server present in your messaging infra or the anti-spam agents installed on your hub transport server. You may look/try one of the below reasons/options to work around or fix this issue (go one by one), The user "This email address is being protected from spambots. You need JavaScript enabled to view it." has added the external user “This email address is being protected from spambots. You need JavaScript enabled to view it.” into his/her blocked senders list of outlook client (sender restriction) by mistake. Remove it and try sending the test email again. Disable the Sender Filtering Agent (this is to isolate sender filtering configuration). See if there…
Published in
Solutions
Normally when a meeting request arrives in to the outlook inbox, they appear in the calendar as tentative MR even before they are accepted. Sometime you may see that the meeting requests are not stamping on your outlook calendar till you accept the MR. As and when we progress further on this post you will get to know how the Meeting Requests are processed in outlook when they arrive. You will also find the answer for why MRs are not displaying in outlook calendar soon they arrive in Inbox.Before I jump into the troubleshooting steps or resolutions, I would like to introduce you the outlook sniffer. Outlook Sniffer is a built-in code in outlook that keeps track of few items when they arrive into your outlook Inbox, and it performs certain action on those items. The list of items to which sniffer work with is mentioned below. Meeting invites (adding…
Published in
Solutions
