Category: Failed to connect to an exchange server in the current site 2010

Skip to main content. Select Product Version. All Products. This issue occurs if a management scope in your Exchange Online environment is assigned to the user who is opening the Exchange Management Console.

Management scopes are typically used to limit which user accounts certain administrators can make changes to.

To work around this issue, do one of the following, as appropriate for your situation: Use remote PowerShell to manage your Exchange Online organization. If there are no Exchange servers in your on-premises environment, you can use Exchange Server as the hybrid server.

In Exchange Online, remove the management scope from the management role that's assigned to the user or group who is using the Exchange Management Console. For more information about working with management scopes, see Understanding management role scopes. Still need help? Last Updated: Nov 18, Was this information helpful?

Yes No. Tell us what we can do to improve the article Submit. Your feedback will help us improve the support experience. Australia - English.

failed to connect to an exchange server in the current site 2010

Bosna i Hercegovina - Hrvatski. Canada - English. Crna Gora - Srpski. Danmark - Dansk. Deutschland - Deutsch. Eesti - Eesti.

Error when you try to connect to Exchange Online by using an SMTP client

Hrvatska - Hrvatski. India - English. Indonesia Bahasa - Bahasa. Ireland - English. Italia - Italiano. Malaysia - English. Nederland - Nederlands. New Zealand - English. Philippines - English. Polska - Polski. Schweiz - Deutsch. Singapore - English.

South Africa - English. Srbija - Srpski. Suomi - Suomi.Skip to main content. Select Product Version. All Products. When you try to connect to Microsoft Exchange Online by using a Simple Mail Transfer Protocol SMTP client, you receive an error message that states that the Exchange Online server is unknown, cannot be located, or is configured incorrectly. The text of the error message varies, depending on the kind of client or connection that's used. Here's one example of an error message that you may receive: Sending of message failed.

The server may be incorrectly configured. Please verify that your SMTP server settings are correct and try again. Make sure that SMTP clients connect to smtp. Still need help? Go to Microsoft Community. Last Updated: Nov 18, Was this information helpful? Yes No. Tell us what we can do to improve the article Submit. Your feedback will help us improve the support experience. Australia - English.

Bosna i Hercegovina - Hrvatski. Canada - English. Crna Gora - Srpski. Danmark - Dansk. Deutschland - Deutsch. Eesti - Eesti. Hrvatska - Hrvatski. India - English.

Indonesia Bahasa - Bahasa. Ireland - English. Italia - Italiano. Malaysia - English. Nederland - Nederlands. New Zealand - English. Philippines - English. Polska - Polski.

failed to connect to an exchange server in the current site 2010

Schweiz - Deutsch. Singapore - English. South Africa - English. Srbija - Srpski.CategoryInfo : OpenError: System. Your IIS settings may be off. The problem is when I try to open Exchange Management Shell, I get the error listed in the original post.

The cert went in ok and everything seems to be running except, I can't get into powershell or EMC. I selected Y and I got the following error:. It is for a specific address. Actually, it is a renewal from GoDaddy. The old one was about to expire so I have to renew and then redownload the cert.

I think exchange services and IIS both use the cert. I am not sure how I can verify that however. As you can tell, I am not very familiar with certificates. OWA may still be working properly because it may be using your old cert that may still be valid. After each error is resolved, close this window and re-run the tool to check for additional problems.

I checked the link you sent me to check the Exchange services but it is referring to EMC which I am I having problem starting. Not sure what else I missed. I tried that without success. I have recreated the Powershell Virtual Directory a couple of times already and made sure that the Require SSL is not check but still have the same issue. Finally pulled the trigger yesterday and called Microsoft with an incident. I spent about 4 hours yesterday with their tech and at the end, they told me that I need to upgrade my Exchange from SP1 to SP3.

So today, that is the plan. Sorry to hear you had to call Microsoft. Hopefully their suggestion will work for you. Honestly, I feel bad, I should have recommended to you to make sure Exchange was fully patched and upgraded.

So far, close to 12 hours, finally got the upgrade to run but the error still persist. Getting my money's worth. On my 2nd day with MS support. Straight 10 hours so far but still have the same issue. I am not feeling too bad now even though it is still not working, at least it is not an easy fix.

They updated the server to SP3, the tried taking out the SSL, they try removing the powershell virtual directory and putting it back in, they uninstalling and reinstalling winRM IIS Extension, they even try replacing the web. Still, not working. Luckily, everything else is working so might have to continue this next week.

Gotta say that the support guy at MS is really nice. He worked over an hour past his scheduled time to try to get this to work. EMC is back up and running again as of Friday night. The MS support tech stayed on the case 2 hours pas his regular schedule just to get this case resolved. Not sure how he actually resolved it. He mentioned something about deleting the web. So if this ever comes up again, we'll know to check the web. Interesting spot to break. Would have been interesting to compare the difference in the "broken" file, versus the "refreshed" file.Keep in touch and stay productive with Teams and Officeeven when you're working remotely.

Learn how to collaborate with Office Tech support scams are an industry-wide issue where scammers trick you into paying for unnecessary technical support services. You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service number.

New-PSSession : [exch. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. Did this solve your problem?

Yes No. Sorry this didn't help. April 14, Keep in touch and stay productive with Teams and Officeeven when you're working remotely. Site Feedback. Tell us about your experience with our site. Error:- New-PSSession : [exch. I have the same question 0.

Bill Smithers Replied on April 3, Volunteer Moderator. Thanks for marking this as the answer. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. How satisfied are you with this response?

failed to connect to an exchange server in the current site 2010

This site in other languages x.Skip to main content. Select Product Version. All Products. The article only applies to the Outlook connection issues that are caused by the RPC encryption requirement.

Unable to open the Outlook window. The set of folders could not be opened. Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The connection to the Microsoft Exchange Server is unavailable.

Outlook must be online or connected to complete this action. The information store could not be opened. Outlook could not log on. Check to make sure you are connected to the network and are using the proper server and mailbox name.

The action could not be completed. The name could not be resolved.

Failed to connect to an Exchange server in the current site.

Note If you are using one of the automated methods Group Policy or a. Select your profile, and then click Properties. In the Microsoft Exchange dialog box, select the Security tab. Show all. Outlook One of the possible causes is that you are using Microsoft Office Outlook and you disable the Encrypt data between Microsoft Office Outlook and Microsoft Exchange profile setting.

The default configuration for Exchange Server requires RPC Encryption from the Outlook Client, this prevents the client from being able to connect. Last Updated: Apr 9, Was this information helpful?

Yes No. Tell us what we can do to improve the article Submit.As was discussed in the previous related blog post " Troubleshooting Exchange Management Tools startup issues ", in Exchange the Management tools are dependent on IIS. As was discussed in that blog, we have seen situations where the management tool connection to the target Exchange server can fail, and the error that is returned can be difficult to troubleshoot. This generally but not always happens when Exchange is installed on an IIS server that is already in service, or when changes are made to the IIS server settings post Exchange Install.

The situation is further complicated by the fact that some of the errors presented have similar wording; most seem to originate with WinRM Windows Remote Managementand in some cases different root problems can produce the exact same error message.

In other words, depending on how knowledgeable you are with these errors, troubleshooting them is all around I was approached by a good friend of mine and he asked what I thought we could do to make these errors a little easier to troubleshoot.

The EMTshooter runs on the local target Exchange server and attempts to identify potential problems with management tools connection to it.

The troubleshooter runs in 2 stages.

Configure Autodiscover service in Exchange 2016

If it identifies a problem with one of the pre-checks it will make a recommendation for resolving the problem. If the pre-checks pass, the troubleshooter will go ahead and try to connect to the server in the exact same way that the management tools would. If that connection attempt still results in a WinRM-style error, the troubleshooter will attempt to compare that error to a list of stored strings that we have taken from the related support cases that we have seen.

If a match is found, the troubleshooter will display the known causes of that error in the CMD window. Here is an example of how this might look like:. When I was designing the troubleshooter, I could have just written a little error lookup tool that handed over the appropriate content for the error you were getting, but I felt that was not as robust of a solution as I was aiming for and not much of a learning experience for me.

So the tool runs active pre-checks before moving on to the error look-up. The amount of pre-checks it can run depends on the flavor of OS you are running on and the options you have installed on it, such as WMI Compatibility. Basically, I have taken all of the documentation that has been created on these errors to date, and created a tool that will make the information available to you based on the error or problem it detects.

Hopefully this will cut down on the amount of time it takes to resolve those problems. When you run the EMTshooter it will log events in the event log. All results that are displayed in the CMD window are also logged in the event log for record keeping. Depending on your current settings, you may need to adjust the execution policy on your computer to run the troubleshooter, using:.

This version of the troubleshooter needs to run on the Exchange Server that the management tools are failing to connect to. While our final goal is that the troubleshooter will be able to run anywhere the Exchange Management tools are installed, the tool isn't quite there yet. We have seen instances where corruption in the PowerShell vdir or in IIS itself has resulted in errors that seemed to be caused by something else. For instance, we worked on a server that had an error that indicated a problem with the PowerShell vdir network path.

Outlook connection issues with Exchange mailboxes because of the RPC encryption requirement

But the path was correct. Then we noticed that the PowerShell vdir was missing all its modules, and quite a few other things. Somehow the PowerShell vdir on that Exchange Server had gotten severely WinRM was returning the best error it could, and the troubleshooter took that error and listed the causes. None of which solved the problem.Need support for your remote team? Check out our new promo! IT issues often require a personalized solution. Why EE? Get Access. Log In. Web Dev. NET App Servers.

We help IT Professionals succeed at work. Exchange - Connecting to remote server failed with the following error message : Access is denied. Medium Priority. Last Modified: Enter the server FQDN where you want to connect. Connecting to the remote server failed with the following error message: Access is denied. Its weird because we are not denied access all the time. It seems to be very intermittant.

Hope someone can shed some light? Start Free Trial. View Solution Only. Commented: Not the solution you were looking for? Getting a personalized solution is easy. Ask the Experts. Since it is intermittent, I would check and make sure the time on the Exchange servers are in sync with your domain controllers. Check logs and see if you have any time sync errors. Time sync issues will create Kerberos authentication errors. Author Commented: Hi, Thanks a lot.

The time turned out to be 5 minutes and 5 seconds out!! Explore More Content. Solution Exchange delivery failed. Get your personalized solution. Ask The Experts. Explore More Content Explore courses, solutions, and other research materials related to this topic. Our Company Why EE? Experts Exchange Take hold of your future. All rights reserved. Covered by US Patent.