• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 11711
  • Last Modified:

Why can't the Exchange Management Console contact the Exchange Server?

Last night after a reboot of the server (added RAM to server) my Exchange 2010 EMC gets stuck when attempting to connect or search for the "on-premises exchange server". The server the EMC is on IS the exchange server. It originally tries to connect to the Exchange server (Servername.contoso.com) which is the exchange server and is the same server the EMC is on. But after that it just moves to the "Searching for on-premises exchange server" and nothing happens. I have restarted all the Exchange services and even rebooted the server again.

Thoughts?
0
agentkolb
Asked:
agentkolb
1 Solution
 
Glen KnightCommented:
This is normally down to a DNS problem.

Check the server has a valid Windows DNS server in it's TCP/IP configuration and no other entries then restart the NETLOGON service.

Also make sure it can contact a Global Catalogue server.

Another possible cause is that it doesn't have the correct permissions.

Check the DOMAIN\Exchange Servers group is listed in the default domain controller policy under Computer Configuration > Windows Settings > User Rights Assignment > Manage auditing and security

then restart the exchange services
0
 
Alan HardistyCommented:
Please create a new test user account on your domain and add this user to the administrators and Organization Management groups.
Logout and then login as this test user you just created and see if you can launch the EMC without any problems.
If you can, then you may have a corrupt profile and creating a new Admin account profile (copying the existing one) was the way that resolved this issue for me.
0
 
agentkolbAuthor Commented:
DNS comes up clean and clear. I've restarted the netlogon service and that didnt work.

It can contact a GC server and it also is a GC server.

I've checked the Group Policy as stated and that is also correct.

Alan, I did try a new user and that didn't fix the issue either.

If I let the EMC just run and wait - after about 10 minutes this pops up:

Connecting to remot server failed with the following error message : the client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the desintation is WinRM service, run the following command on the destination to analyze and configure WinRM service: "winrm quickconfig", for more information see the about_remote_troubleshooting help topic. It was running the command 'discover-exchangeserver -useWIA $true -surppressError $true'.

When I run winrm quickconfig like it says I get this error:

C:\Windows\system32>winrm quickconfig
WinRM already is set up to receive requests on this machine.
WSManFault
    Message = The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled.

Error number:  -2144108250 0x80338126
The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled.

Thoughts?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Glen KnightCommented:
Can you confirm the Exchange server computer is a member of the group specified in the Group Policy?
Also check the policy is being applied by running rsop.msc
0
 
agentkolbAuthor Commented:
Yes and yes. Both are correct.
0
 
Glen KnightCommented:
0
 
agentkolbAuthor Commented:
When I run the following in Powershell:
winrm set winrm/config/client `@`{TrustedHosts=`"`*`"`}

I get this:
WSManFault
    Message = The WinRM client cannot complete the operation within the time specified. Check if the machine name is val
id and is reachable over the network and firewall exception for Windows Remote Management service is enabled.

Error number:  -2144108250 0x80338126
The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reac
hable over the network and firewall exception for Windows Remote Management service is enabled.

Still does not work. And before you ask, yes there is an exception in the firewall.

Thanks!
0
 
Glen KnightCommented:
From the server can you ping itself by name?
0
 
agentkolbAuthor Commented:
yes
0
 
Glen KnightCommented:
The Remote Management service is started?

What SP level are you at with Exchange?
0
 
agentkolbAuthor Commented:
Yes it is and there is no SP for Exchange 2010. Just Exchange 2010 Version 14.00.0639.021
0
 
Glen KnightCommented:
Sorry didn't realise it was 2010!

There is a rollup available.
0
 
Glen KnightCommented:
Can you try these troubleshooting steps here: http://technet.microsoft.com/en-us/library/dd351136.aspx
0
 
agentkolbAuthor Commented:
None of those troubleshooting steps seemed to help
0
 
agentkolbAuthor Commented:
The problem seems to be with WinRM not working properly. WinRM quickconfig errors out saying it cant connect. The Service is running and firewall configured properly. Thoughts?
0
 
agentkolbAuthor Commented:
The problem was with WinRM AND Antivirus.
0
 
tamaneriCommented:
This helped me too. Uninstalled AVG and it opened right up!
0
 
mooncomputersCommented:
Same here, uninstalled AVG and it opened up no problems.
Is there a way around this? We'd prefer not leave the server unprotected.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now