For the record-
I changed the following values located in the applicationHost.config file in Windows\system32\inetsrv\config:
Section <configSections> --> <sectionGroup name="system.webServer">
All the services are running. It all looks like it should be working & there is very little, if anything in the event logs to suggest otherwise.
When trying to get to OWA, I get- "HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
Config File \\?\D:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\web.config
Which is the same as when trying to access the modules.
It just happened to me,, after the exchange 2010 rollup4 instalation, check the services, on my case, all the exchange services were disabled ( on a fresh installation) i enabled the services, and it worked fine!.
JC
Hi there,
Im having problems with Exchange 2010.
Installing it on a new Server 2008 box, on a Windows 2003 domain - with a current Exchange 2003 running. Ive followed all the normal procedures, updated the schema & domain etc.
Installation appeared fine, but running either the EMS or EMC I am getting the error: "Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid."
Ive followed many articles regarding reinstalling the WinRM feature, amongst other things. Another blog on here suggested checking settings within modules in IIS, which brings me to the problem I get there - when I attempt to access Modules within any of the Exchange sites I get the error:
This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
Which relates to any of the Web.Config files, in the site i try & open it in. eg. D:\Program Files\Microsoft\Exchange Server\v14\Client Access\Powershell\web.config line 30.
Ive followed various advice regarding editing the applicationhost.xml file, within the Inet folder, but still got nowhere.
Any ideas? Im tearing my hair out! It's a very standard installation, and Im sure im probably missing something simple - but can't see for looking!
Many thanks.
I had the same problem too, no EMC and EMS.
Editing any of the web.config 's or changing %ExchangeInstallPath% to absolute paths did not help.
In IIS - Applicationpools i had to change the version of MSExchangePowerShellAppPool from v4.0 to v2.0 and restart this app pool. Damn .NET took me hours of searching, reading hundreds of forum posts.
Christian
I had the same problem too, no EMC and EMS.
Editing any of the web.config 's or changing %ExchangeInstallPath% to absolute paths did not help.
In IIS - Applicationpools i had to change the version of MSExchangePowerShellAppPool from v4.0 to v2.0 and restart this app pool. Damn .NET took me hours of searching, reading hundreds of forum posts.
Christian
I had the same problem only nog during install.
But at one day i get the error line 30, because it was working in the past, I did the following.
- Control panel
- Uninstall a program
- Double click on Microsoft Exchange server 2010
- Uncheck the Client Access Role
- Run that process en finish
- Rename ClientAccess folder in ClientAccess.old (found in: C:\Program Files\Microsoft\Exchange Server\V14)
- Then re-install Microsoft Exchang server 2010 (from CD eg.)
- Check the ClientAccess Role
- Install and Finish
This worked for me!
Thank you Bo for your simple instruction...It works perfect.
EMS and EMC both work.
OMG. I spent 2 days trying to solve this after applying SP3 for Exchange 2010.
Your solution fixed it, George. Thanks so much.
My problem was the
The KB article didn't solve my problem but this did it.
Thanks for that, George, after 6 days of troubleshooting for me and a colleague, that was the solution!
I will add to your solution that IF WinRM-IIS-Ext has been installed/uninstalled at any time during troubleshooting, it does a far too good job cleaning up after itself, so you will need to either
1a) Install WinRM-IIS-Ext again, even though it's not an Exchange 2010 requirement
or
2a) Add a missing line to "C:\Windows\System32\inetsrv\config\applicationHost.config":
<section name="system.management.wsmanagement.config" overrideModeDefault="Allow" />
and
2b) Copy the missing schema file "C:\Windows\System32\inetsrv\config\schema\wsmanconfig_schema.xml" from another server (or get it when WinRM-IIS-Ext is installed).
check
/Jeppe
Hi there,
Im having problems with Exchange 2010.
Installing it on a new Server 2008 box, on a Windows 2003 domain - with a current Exchange 2003 running. Ive followed all the normal procedures, updated the schema & domain etc.
Installation appeared fine, but running either the EMS or EMC I am getting the error: "Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid."
Ive followed many articles regarding reinstalling the WinRM feature, amongst other things. Another blog on here suggested checking settings within modules in IIS, which brings me to the problem I get there - when I attempt to access Modules within any of the Exchange sites I get the error:
This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
Which relates to any of the Web.Config files, in the site i try & open it in. eg. D:\Program Files\Microsoft\Exchange Server\v14\Client Access\Powershell\web.config line 30.
Ive followed various advice regarding editing the applicationhost.xml file, within the Inet folder, but still got nowhere.
Any ideas? Im tearing my hair out! It's a very standard installation, and Im sure im probably missing something simple - but can't see for looking!
Many thanks.
please follw this link
http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx
I have the same issue.
Exchange 6 servers upgraded to SP1
No access to the ems / emc
Can manage platform through "not upgraded" part of the cluster
Have tried all paths - and reinstall secondary platform.
This provides a "to many RMS users" - but I suspect it ´s due to the two platforms.. ( Ex2010 / ex2010 SP1)
suspect either "AD issue" due to OCS 2K7 R2 Schema change - og some kind of mitchmatch .. which can be fixed
How Do I get this to MS support - its rather critical
AD is 2008 ( Forrest (3 domains)
Exchange is upgraded way back from 2K7 - placed in one of the sub domains
please help
WOOOOOOOOOOOOOOOOOOOOOOOWHOOOOOOOOOOOOOOOOOOO! Thank you so much George! I have been fighting this issue and it was driving me crazy!! The problem was that %ExchangeInstallDir% wasn't set as a system variable on the server. I changed the config file so that everything is an absolute path and that worked.
I wanted to see what would happen if I left the config file unchanged and just added the missing system variable (%ExchangeInstallDir%) and bounced the server. That did not resolve the issue which is strange to me. I would think that if that variable is defined then everything would work the way it should but it doesn't. The only way I could get it to work is to use absolute paths in the config file. Weird.
Not sure how to resolve your whole issue as I have a similar problem and am still working on it. But I have figured out what the line 40 error is. If you check the web.config in the powershell directory change any references of %ExchangeInstallPath% or %ExchangeInstallDir% to the absolute path.
All being well the page should load, although I get a 401 access denied from kerbauth, hopefully you'll get something more useful.
george
Hi, still no joy unfortunately, but again many thanks for the help.
When attempting to run the EMS, the event viewer logs this error - which im sure must be the crux of the problem:
Event code: 3008
Event message: A configuration error has occurred.
Event time: 8/5/2010 10:13:15 AM
Event time (UTC): 8/5/2010 9:13:15 AM
Event ID: 9e4992895bf14cdc8cccd268e0ef518b
Event sequence: 1
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/ROOT/PowerShell-2-129254731956563080
Trust level: Full
Application Virtual Path: /PowerShell
Application Path: D:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\PowerShell\
Machine name: GCLMAIL
Process information:
Process ID: 22352
Process name: w3wp.exe
Account name: NT AUTHORITY\SYSTEM
Exception information:
Exception type: ConfigurationErrorsException
Exception message: Could not load file or assembly 'Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (D:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\PowerShell\web.config line 40)
Request information:
Request URL: http://gclmail.gcl.local/powershell?serializationLevel=Full;PSVersion=2.0
Request path: /powershell
User host address: fe80::a46f:4213:a5fc:3d07GCLMAIL
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\SYSTEM
Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\SYSTEM
Is impersonating: False
Stack trace: at System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase)
at System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement)
at System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList)
at System.Web.HttpApplication.GetModuleCollection(IntPtr appContext)
at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)
Hi,
Here comes the resolution :)
1) Run the winrmquickConfig to find out if WinRM is indeed set up to receive requests on that server, and if the WinRM firewall exception is enabled.
2) Check if it is set exclusion for port 80 in the Firewall.
3) Check to seeif OWA is working. If it is not, go to IIS Manager and check the Modules:
Note: If The KerbAuth.dll module had been loaded at the Default Web Site level this can cause OWA as well as the Exchange Management tools (EMC/EMS) not to work.
-KERBAUTH should only be registered in IIS under modules on the PowerShell Site (not at the Default Site, and not at the Server level)
-KERBAUTH should only be registered as NATIVE, not as Managed at the PowerShell Site in IIS
-KERBAUTH should only be registered directly at the PowerShell Site in IIS, not Inherited.
If the Kerbauth.dll is registered as a "Managed" module not a "Native" Module, do the following:
• Remove Kerbauth from the Powershell web site as a Managed Module
• Verify if Kerbauth.dll is in the C:/Program Files/Microsoft/Exchange/V14/BIN directory.
• In IIS go to the server level and register Kerbauth.dll using the name "Kerbauth" and the path to C:/Program Files/Microsoft/Exchange/V14/BIN/KERBAUTH.DLL
• Go back to the Server level in IIS and Remove Kerbauth.
Note: We are simply removing it from the server level, and since it is registered now, it should be available at lower levels.
• Under IIS Powershell in MODULES select Manage Native Modules, and check by Kerbauth which now should appear.
• Ran IISRESET from a Command Prompt
• Try opening EMC and EMS again.
4) Check to see if the Default Web Site has HTTP Redirect setting enabled, by selecting Default Web Site on IIS, and expanding “HTTP Redirect”.
If it is enabled, try the workaround of selecting the option under “Redirect Behavior”:
“Only redirect requests to content in this directory (not subdirectories)
Note: By default the HTTP Redirect is disabled.
So, before making any change, the SE should ask the customer why they have enabled this option.
Otherwise we may cause some other problems on the customer’s environment.
Cheers,
-Gulab
Hi Alexsfe,
Some related information for you:
http://msexchangeteam.com/archive/2010/02/04/453946.aspx
http://msdn.microsoft.com/en-us/library/aa384372(VS.85).aspx
http://technet.microsoft.com/en-us/library/dd351136.aspx
If the issue still exist, I would suggest you open a ticket from MS, it would need retrieve more infomation on you server, and is difficult to post on the forum.
Or, please reinstall it with the latest OS, and latest exchange version.
Regards!
Gavin