Link to home
Start Free TrialLog in
Avatar of joshhough
joshhoughFlag for United Kingdom of Great Britain and Northern Ireland

asked on

SBS 2011 Exchange Management Console issues

Hi,

I've got a really frustrating problem with a server for a client.

The server is SBS2011 with windows updates etc installed. I went to create a new user using the SBS console and it failed to send them an e-mail. Thinking this was a little odd i opened EMC to find that it was failing to connect using 'Kerbos' authentication.

I managed to realise the problem was the server had AVG installed. Upon un-installing it, the error message changed to what i now have which i'm really struggling to fix. The error message reads:

The following error occurred while searching for the On-Premises Exchange Server:
[server.domain.local] Connecting to remote server failed with the following error message: The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIS $true -SurpressError $true -CurrentVersion 'Version 14.2 (Build 247.5)".

Any help would be greatly appreciated as i'm beginning to start pulling my hair out.

Thanks,

Josh
Avatar of Manpreet SIngh Khatra
Manpreet SIngh Khatra
Flag of India image

You can find your error over here

Troubleshooting Exchange 2010 Management Tools startup issues
http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx

- Rancy
Avatar of joshhough

ASKER

Unfortunatley i've been through this and it hasn't helped the issue. I've just double checked again to make sure theres nothing i'm missing, and there isnt. The environment variables are correct as are the Powershell IIS Modules and the virtual directory points to the correct location.
Here is a quick one that I worked and solved on our one of client machines

Check out in Server Manager if "WinRM IIS Extensions" are installed. If not install it. If its already there :
1. Uninstall it and Install it again.
2. Run "WinRM Quickconfig".

Regards,
Exchange_Geek
Thanks for your response.

Just tried that - do i need to restart  the server between/would it be worth it? The reason i ask is it uninstalled fine. Then i re-installed it (without restarting), ran winrm quickconfig from CMD and it produced
'WinRM already is set up to receive remote requests on this machine' and
'WinRM already is set up for remote management on this machine'

Thanks,

Josh
Restart might help sir.

Regards,
Exchange_Geek
Hi,

I uninstalled it, restarted the server, installed it and ran the CMD prompt again to get the same 'Already setup' message.

Opened EMC And still have the same error?

Thanks,

Josh
There are two other solutions mentioned in the link given by Rancy, have you tried that?

Check the service Kerberos is in started state or not.

Regards,
Exchange_Geek
Hi,
Following that link ive done the following steps:
-      Made sure Kerbauth is a module in IIS and running native
-      Added the following the the ApplicationHosts file : <add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" />
-      Opened IIS modules to find now WSMan is running ‘Native’ does this need to be running as ‘managed’?
-      Checked SSL settings and they are correct
-      Recycled MSExchangePowerShellAppPool
-      Logged on as administrator so would presume the account is powershell enabled but when I open exchange management shell it fails to connect. Type in the FQDN of the server and it changes. Try entering the command ‘Get-User Administrator.RemotePowershellEnabled’ and it says that ‘get-user’ is not a recognized CMDLET
-      There are no issues with Port Bindings either
-      I ran the WinRM enumerate winrm/config/listener cmdlet and its listening on the correct ports and IP addresses
Any more ideas?
Thanks,
Josh
Here is what I'd recommend create a second windows profile for your account and try connecting with it, seems that your windows profile might be corrupted.

Regards,
Exchange_Geek
Hi,

Just tried logging on with another admin account and EMC gives the same error. So i made a new network admin and again, opening EMC i get the same error.

Thanks,

Josh
Its more of an issue with the VD or something not anything with User account ......

- Rancy
So, that confirms that there is some mess with the server.

How about you updating the server with a roll up higher than the present - possible?

Regards,
Exchange_Geek
What else can i try? Is there a way i can rebuild part of the Virtual Directory?

Exchange as a platform is working fine. My clients are still sending/receiving e-mails fine, i just cant make any changes. So when a new employee started, i cant make them an e-mail account.

Thanks,
There are no available updates for the server - i tried that as i previously had an issue with EMC on the same machine not opening because of help files which turned out to be an issue with a windows update. Installing the new ones solved it. This time it hasnt.

Thanks,

EDIT: It appears since last week when i last updated the server rollup V4 has been released. This is installing now
Hi,

Exchange isnt set set to auto-update, its something i do manually twice a month - check the server for udates.

It's updating as we speak so i'll find out soon if updating to Rollup 4-V2 worked.

Thanks
We normally do a update every month or more as depending on the Importance of those updates ....
Please let us know how RU4 goes :)

Best Wishes :) !!

- Rancy
Just as an aside, what should the binding be for port in the default website for IIS? Should it be 127.0.0.1 or the servers local IP in this case 192.168.15.3?
Thanks
Hi,

Sorry to be back again! Looks like RU4 V2 hasnt helped. Still getting the same error message...

Is there some kind of Microsoft support procedure? I'm a MAPS subscriber so i dont know if theres anything through the partner network i could try? I'm conscious of taking up too much of your time (although any help is more than greatly appreciated!)

Thanks,

Josh
So does MAPS have some priviledge for getting some tickets with MS or what ?
Ideally a MS Pro call could cost you somewhere around 250-300 dollars i guess

- Rancy
I don't know if MAPS does - i've just had a look and it doesn't appear to so i guess im back to pulling hair out.

Is there a way to rebuild exchange? Like i said, as a live message transport system its fine, i just can't do anything with it.

Thanks,

Josh
Bes is to take a backup of the Exchange DB's and plan for weekend and i would say Reinstall with SP2 and check

- Rancy
I've just spoken to Microsoft who say MAPS includes free tech support for Business Critical issues.

I'll try that first otherwise a rebuild it is. Yippee!
Good to know you have a good MS support .... I guess its Pre support so you will surely get a good engineer or else simply get one :)

- Rancy
Its weird how a machine would pester with known solutions.

Would be interested to see what the solution is offered by MS (apart from rebuild)

-Tushar Shah
After my first 2-hour support call with Microsoft it seems they are as in the dark as i am. it appears the issue is relating to PowerShell as PowerShell commands that the technician tries to run all fail.
Exchange_Geek: Tushar Shah :)

So MS is Stumped :) Lovely

- Rancy
Ask for escalation, seems this guy doesn't have a clue to solve such issues.

Regards,
Exchange_Geek
I think you might be right! But it is odd because he referred me back to AVG to make sure the product was uninstalled properly but the AVG script fails to run correctly as PowerShell doesn't work.

Maybe there is in fact no issue with exchange and the error is simply a result of an underlying powershell issue. Strange. But i am getting annoyed with them phoning at 11pm GMT asking if i'm on site to work on the server. Sounds like Microsoft expect me to live, sleep and eat servers!
So it appears now exchange is broken. None of the users are receiving e-mails and when i login through OWA it says that the mailbox is currently unavailable. What can i try to get this working as i'm now in a minimum 2 hour queue for Microsoft to call me back again!

Thanks,

Josh
If its Urgent ask the Router to connect to some DM if possible and also i would say try with Restart of service or plan for a Reinstall if MS is so lazy

- Rancy
ASKER CERTIFIED SOLUTION
Avatar of joshhough
joshhough
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Microsoft Business Critical support solved the issue