Exchange Server 2010 OWA Error 405 StaticFileModule

I am running Exchange Server 2010
(Version 14.1 - Build 218.15) on Windows Server 2008 R2. This is a all-in-one-server roles installation. Everything is working fine except forms-based authentication. When enabled I get HTTP Error 405.0 "Method not allowed". The page
you are looking for cannot be displayed because an invalid method (HTTP verb) is being used.
Details are:
Module StaticFileModule
Notification ExecuteRequestHandler
Handler StaticFile
Error Code 0x80070001
Requested URL https://localhost:443/owa/auth/owaauth.dll
Physical Path C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\auth\owaauth.dll
Logon Method Basic
Logon User administrator
When in EMC, Client Access, on OWA & ECP tabs I change authentication forms-based to standard with basic check box and restart IIS the Web Access works fine.
I have already tested solutions like recreating Virtual Directories, Allow .Net 2.0, etc. I have also checked all the modules and the associated mappings in IIS one by one for every VM. I believe this is an error in a .config file. If you have encountered
a situation like this please help.

Hi Pantelis,
Please make sure that the client sends a request that contains a valid HTTP method.
1. Click Start, type Notepad in the Start Search box, right-click
Notepad, and then click Run as administrator.
Note If you are prompted for an administrator password or for a confirmation, type the password, or provide confirmation.
2. On the File menu, click Open. In the
File name box, type %windir%\system32\inetsrv\config\applicationhost.config, and then click
Open.
3. In the ApplicationHost.config file, locate the <handlers> tag.
4. Make sure that all the handlers use valid HTTP methods.
5. Save the ApplicationHost.config file.
More details to see: http://support.microsoft.com/kb/942051
Please also try to re-build OWA Virtural Directory. To see:
http://support.microsoft.com/kb/941201
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Similar Messages

Exchange Server 2010 - OWA, ECP, EWS not working

Hello,
I am evaluating exchange server 2010. I was able to install it, but now the admin websites will not render in IIS. OWA, ECP, etc. I especially want Outlook Anywhere to work. I can admin through the windows admin interface so that's not a concern.
I want users to access their email through the web as well. I checked permissions but could have them wrong. Any help is appreciated.
Thanks
John Grace

There are about twenty different types of 403 error. To see which one is happening here, you'd need to look at the IIS log files, and get the status subcode, which is the number after the 403 in the logged line.
The most common, though, is 403.4, which means 'SSL Required'. What happens if you go to
https://servername (i.e. https instead of http).
Another one is 403.6, which means that IIS has been configured to only allow access to a certain range of IP address, and the one you're trying to access it from isn't one of them.
OWA For SmartPhone

Exchange Server 2010 EMC Error

Hi, I have installed Exchange Server 2010 SP3 in Windows Server 2012 Domain Controller. After the successful installation, I am not able to view the options in the Exchange Management Console. It gives the error "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."
Can anyone help on this issue to solve this. Thanks in advance.
Regards
Babu

Hi
Installing exchange 2010 or any version on a domain controller is not recommended.
Please check that all the IIS App pools are started, the relevant services are started etc. Is this in a production environment?

Exchange Server 2010 get error HResult = -2147024891 when Accessing Virtual Directories on CAS

I've just installed a Exchange 2010 server in an Exchange 2007 server environment.
The 2007 enviroment include two exchange server "Server-A" and "Server-B"
and "Server B" has dead on hardware issue for half year.
When I go to Microsoft Exchange On-Premises -> ServerConfiguration -> Client Access and receive the following error message
An IIS directory entry couldn't be created. The error message is Access is denied. . HResult = -2147024891 It was running the command 'Get-OabVirtualDirectory'
I try run the “Get-OwaVirtualDirectory” in powershell and get following result
From the power Shell command prompt .. Run
[PS] C:\Windows\system32>Get-OwaVirtualDirectory
An IIS directory entry couldn’t be created. The error message is Access is denied.
. HResult = -2147024891
+ CategoryInfo : NotInstalled: (<Server-B\Exchange (Default Web Site):ADObjectId) [Get-OwaVirtualDirectory]
, IISGeneralCOMException
+ FullyQualifiedErrorId : 4B12EB5D,Microsoft.Exchange.Management.SystemConfigurationTasks.GetOwaVirtualDirectory
I've google that i need to add "Exchange Trusted Subsystem" as a member in local admin group in Exchange 2007
but my exchange 2007 "Server-B" already dead, how should i fix it?
Appreciate for any help!!

re-create the new virtual directories does not work for me.
still got the error
An IIS directory entry
couldn’t be created. The error message is Access is denied.
. HResult = -2147024891
+ CategoryInfo : NotInstalled: (<Server-B\Exchange (Default Web Site):ADObjectId) [Get-OwaVirtualDirectory]
, IISGeneralCOMException
+ FullyQualifiedErrorId : 4B12EB5D,Microsoft.Exchange.Management.SystemConfigurationTasks.GetOwaVirtualDirectory
I don't understand why change new exchange server 2010 setting require me to have permission to access
my dead exchange server 2007

Exchange Server 2010 Installation Error

I am installing Exchange 2010 on a fresh Windows 2008 Server, and done with all the Prerequisites. but still i am getting this error...
I have Added These commands also to powershell.
Import-Module ServerManager
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,RPC-Over-HTTP-Proxy
Still m not able to instal.
HELP:
mohit

Hello,
Please follow the Willard's suggestion.
Besides, please use dcdiag command-line tool to check if DC server run normally.
Please use telnet command-line tool to check 389 /3268 is opened on firewall.
Please restart Microsoft Exchange Active Directory Topology Service to check the result.
Cara Chen
TechNet Community Support

Exchange Server 2010 SP3 Installation with UM Language Pack Error

Hi All,
Kindly help me in this issue, When I Install Exchange Server 2010 SP3, I faced an error in UM role setup as the below,
and when i searched on it i found solution like "Download the UM language packs and tried to install directly" so i downloaded "UMLanguagePack.en-US" from the below URL:
http://www.microsoft.com/en-eg/download/details.aspx?id=36769
and when i tried to install it, i faced the below error:
also i searched on this error and i found solution in registry as the below:
Try remove registry key for the above error :
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\<Your Version >\UnifiedMessagingRole\LanguagePacks"
and after i did it, i found first error be solved and the second error still the same as the below:
Error:
A Setup failure previously occurred while installing the UnifiedMessaging role. Either run Setup again for just
this role, or remove the role using Control Panel.
Is there a solution on this issue please i wanna solve it As soon as possible?
Thanks in advance,

I solved the below error by editing in registry:
Error:
A Setup failure previously occurred while installing the UnifiedMessaging role. Either run Setup again for just this role, or remove the role using Control Panel.
Solution:
Open regedit (Start -> run), navigate to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14
Under each role, UnifiedMessagingRole, have a look for an action and watermark entry, Delete these 2 keys, and retry. it solve this error, and You can now run the installation again of your "UMLanguagePack.en-US". and its done and installed now.
After "UMLanguagePack.en-US" Installation, i tried to continue installation of Exchange Server 2010 SP3, but I faced the same first error in UM role setup as the below,
What can i Do? please help urgently.

Send As, Send on Behalf and Full Access for Exchange server 2010/2013

[This FAQ contains 2 parts]
Testing and watching the behavior of Send As, Send On Behalf and Full Access permission.
Common issue and Troubleshooting on the three permission.
[Testing and Watching]
Based on following blog, I decide to test on my lab:
Full Mailbox Access Rights + Send On Behalf = Send As ?
http://blogs.technet.com/b/ehlro/archive/2012/04/06/full-mailbox-access-rights-send-on-behalf-send-as.aspx
Description on my lab and test:
Exchange 2010 + Outlook 2010
Exchange 2013 + Outlook 2013
Senders: A01, A02, … , A07, A08
Recipient: A09
A01 grand permission to other senders.
Two methods:
a. Use A0x’s credential configure A01’s profile, then send From both A01 and A0x via Outlook. Watching result in A09’s Inbox and Sent Items which has message copy left.
b. Use A0x’s credential configure A0x’s profile, then send From both A01 and A0x via Outlook. Watching result in A09’s Inbox and Sent Items which has message copy left.
Result as following forms:
1. Exchange 2010 + Outlook 2010 / Exchange 2013 + Outlook 2013
Using A0x’s credential configure A01’s mailbox, then send From both A01 and A0x
To A09.
2. Exchange 2010 + Outlook 2010 / Exchange 2013 + Outlook 2013
Using A0x’s credential configure A0x’s mailbox, then send From both A01 and A0x
To A09.
[Common Issue]
1. [Issue]
Exchange 2010 + Outlook 2010. A01 grand A03 Send As permission. However A03 can’t send as A01 to A09 and get NDR:
You can’t send a message on behalf of this user unless you have permission to do so. Please make sure you’re sending on behalf of the correct sender, or request the necessary permission. If the problem continues, please contact your helpdesk.
Details as following pic:
[Troubleshooting]
1) Based on the NDR, it seems a permission issue. Check Send As permission, however the Send As permission configured correctly. Pic as below:
2) ince the Send As permission configured correctly, it seems the permission hasn’t been replicated. Try to restart Microsoft Exchange Information Store service. It works.
Note: The Send As permission isn’t granted until after replication has occurred. Replication times depend on your Exchange and network configuration. To grant the permission immediately, stop and then restart the Microsoft Exchange Information
Store service.
2. [Issue]
Exchange 2013 + Outlook 2013. A01 grand A03 Send As permission. However A03 can’t send as A01 to A09 and get NDR:
Your message did not reach some or all of the intended recipients.
Subject: xxx
Sent: xx/xx/2014 8:20 AM
The following recipient(s) cannot be reached: A09
This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-00000000-00000000].
Details as below:
[Troubleshooting]
1) Also check the Send As permission configuration first.
2) Then try to use A03 send as A01 to A09 via OWA. If OWA works well, it seems and issue on the Outlook client side.
3) This behavior may occur if the OAB in Outlook isn’t updated. Try to download OAB manually.
4) If doesn’t work, please close Outlook and try to delete all the OAB folder on your computer. The path of OAB folder in Win7, Win8 as below:
\Users\<UserName>\AppData\Local\Microsoft\Outlook\Offline Address Books
5) Restart Outlook.
Note: Be aware that you cannot send e-mail messages on behalf of a mailbox if the mailbox is hidden from address list. When sending a message, Exchange requires that e-mail address is resolved in the
From field.
3. [Issue]
Exchange 2010. A01 grant A0x “Send As” or “Send on Behalf” permission. A0x send as/ send on behalf of A01. The message is only copied to the Sent Items folder in A0x’s mailbox (same as the result of my test). Also cannot configure Exchange 2010 so that the
message is copied to the Sent Items folder of both A01 and A0x.
[Troubleshooting]
This issue occurs because Exchange server 2010 was designed to copy message to the Sent Items folder of the sender only. This issue can be solved by installing Exchange 2010 SP2 UR4. More details in the following KB:
Messages that are sent by using the "Send As" and "Send on behalf" permissions are copied only to the Sent Items folder of the sender in an Exchange Server 2010 environment
http://support.microsoft.com/kb/2632409/en-us
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Nice guide Mavis, I recently explored the same topic. Few things you might want to add is the type of connectivity (Cached vs Online will produce different results) and to expand further on the methods of adding the other mailbox in Outlook (additional mailbox
vs additional account defaults to different methods). Check the screenshot:
And please post this somewhere more visible, like blog/wiki page.

Exchange Server 2010 SP3 test environment - email flow to/from internet

Today I set up test environment for Exchange Server 2010 SP3 - domain controller running Windows Server 2008 R2 SP1, Exchange Server 2010 SP3 on Windows Server 2008 R2 SP1 and client computer running Windows 7 Pro SP1 x64 with Outlook Pro 2010 x64. These
machines are VMs on vSphere 5.0 cluster made of 4 esxi 5.0 hosts.
I have three years of experience in working with Exchange Server 2010 in my production environment but until recently I have not had enough resources to build a test environment. Does "testing" Exchange Server 2010 infrastructure have
a real life purpose considering the fact that only internal email flow is possible since authoritative SMTP accepted domain is not hosted anywhere thus not visible to outside world. This limited email flow combined with absence of possibility to test
ActiveSync, Outlook Anywhere, OWA from WAN, . . . really hurt and make Exchange Server rare technology that can not be tested completely before introducing something new into the production. Services that are not possible to test from the outside world are
useless and whole point of Exchange-like technologies is availability from anywhere and from whatever device.

I set up Internet Send Connector (by default this type of send connector uses DNS MX records to route email automatically). Having sent an email to my gmail account I did not receive it and in transport logs I saw that mx record was found successfully
but there is the following line:
2014-08-05T20:39:51.942Z,Internet Connector,08D17F000FE36010,1,,2a00:1450:4013:c01::1b:25,*,,"Failed to connect. Error Code: 10051, Error Message: A socket operation was attempted to an unreachable network 2a00:1450:4013:c01::1b:25"
I tried also to send an email to my production email address (we have Symantec Messaging Gateway which is used as a smart host (antispam,antimalware,content filter appliance)) but then error is:
2014-08-05T20:50:08.395Z,Internet Connector,08D17F000FE36019,1,,91.238.7.10:25,*,,"Failed to connect. Error Code: 10061, Error Message: No connection could be made because the target machine actively refused it 91.238.7.10:25"
Telnet from test exchange to 91.238.7.10 on port 25 also is not working.

Exchange Server 2010 - Authentication fails with DC

I have implemented Windows Server 2008 R2 Active Directory on Server: DC1
I have Implemented Exchange Server 2010 SP2 on Server: EMLSERVER
Previously MDeamon 5.5 was using for Messaging Services.
Manager told me he want only email server to be available after office hours.
For Exchange Server 2010 we have to power on two servers AD and EXCH.
For This reason i install AD on Exchange Server 2010 and Transfer all Roles from DC1 to EMLSERVER.
Now EMLSERVER is our AD and EXCH, and DC1 is our ADC.
To check this configuration i power off current ADC old DC (DC1).
when i try to test OWA, it was not working, and i get HTTP 500 Error, i try to troubleshoot it and finally after enabling Form Based Authentication Service HTTP 500 error has been resolved and i get OWA Page there when i try to Authenticate with Username
and Password i have got HTTP 400 error and i am sucked now.
Can anyone suggest what should i do now.

The Requirement is that I have to provide a solution that is equivalent to MDeamon 5.5, where Company have just one DC which is use for authentication and group policy on Windows and another server which is MDeamon email server.
After office hours they power off DC and just email server is power on.
Therefore new solution must fulfill the same requirement, and in this scenario I have to put DC and Email together so that there is no power overhead.
1- Yes new DC which is together with Exchange is Global Catalog.
2- All Microsoft Exchange services are running.
3- There is no smart card authentication, there is just User/Pass require to authenticate.
4- Old DC/ Current ADC has been powered off after verifying transfer of all AD roles.
5- Previously I have installed DC on DC1 server and Exchange 2010 on EMLSERVER and it was working fine.

Coldfusion 10 and Exchange Server 2010

I am using Coldfusion 10 and I have been trying to connect to Exchange server 2010.
I keep getting this error message: Unable to connect to the Exchange server using HTTP/HTTPS protocol. HTTP response code : 302
I have asked the Coldfusion hosting service to check the cacert for the required certificates and they said that all of the certificates for the hosted exchange server were installed.
If I use the serverVersion="2010" tag I get this error:
Could not connect to the exchange server with the credentials.
Exchange Server doesn't support the requested version.
The company that is hosting my exchange server account just recently upgraded their servers to Exchange Server 2010. When they were running Exchange Server 2007 and i was using Coldfusion 8 my script worked fine.
Any ideas why I am unable to connect to the exchange server now.
Below is the script that I am running.
<!DOCTYPE HTML>
<html>
<head>
<title>Untitled Document</title>
</head>
<body>
<cfoutput>
<cfset count = 0>
<cfset serverName="ex2010.gothamemail.com">
<cfset username="[email protected]">
<cfset password="xxxxxxxxxxx">
<cfexchangeconnection
          action="open"
          Protocol="https"
          connection="myExchangeConnection"
          username="#username#"
          password="#password#"
          server="#serverName#">
     <cfexchangecontact
          action = "get"
          name = "current_contacts"
          connection = "myExchangeConnection">
   <cfexchangefilter name="MaxRows" value="2781">
</cfexchangecontact>
<cfexchangeconnection action="close" connection="myExchangeConnection" />
</cfoutput>
<table width="100%" border="1">
   <tr><th>No.</th><th>UID</th><th>Firstname</th><th>Lastname</th><th>Email</th></tr>
   <cfoutput query="current_contacts">
        <cfset count = #count# + 1>
       <tr><th>#count#</th><th>#UID#</th><th>#Firstname#</th><th>#Lastname#</th><th>#Email1#</th ></tr>
   </cfoutput>
</table>
<cfexchangeconnection
     action="close"
     connection="myExchangeConnection">
</body>
</html>

You might try adding the formBasedAuth option in your cfexchangeconnection.   I has similar trouble and my solution was to add the application file with "exchangeServerVersion=2010" and to track down the location of owa on my Exchange servers.
<cfexchangeconnection
action = "open"
connection = "CurrentRandSet"
server = "webmail.***********"
username = "*******"
password = "***********"
protocol = "https"
formBasedAuthentication = "true"
formBasedAuthenticationURL = "https:/**************/owa/auth/owaauth.dll"
>

Windows Server 2008 R2 Standard "Certificate Authority Service" / Exchange Server 2010 EMC not starting and no AD connectivity for authentication.

Hello,
I am a new IT Manager at this company and need assistance big time. Their environment looks as follows:
Server 1. Domain Controller Server (Windows Server 2008 R2 Standard) running active directory.
Server 2. Email Server (Windows Server 2008 R2 Standard) running Exchange Server 2010 .
* Note. No back ups to work with aside from whats mentioned below.
DC had a virus infection causing a lot of issues on the shared network drives 2 days ago locking up all the files with a crypto ransom virus. Running Avast suppressed the infection. Had to recover the file shares which luckily had a back up.
The issue is that the Exchange Server 2 post this lost connectivity with the AD Server 1. Exchange Server 2 when launching EMC could not launch the console stating the following:
"No Exchange servers are available in any Active Directory sites. You can’t connect to remote
Powershell on a computer that only has the Management Tools role installed."
Shortly after I found that it is possible the EMC launcher was corrupt and needed to be reinstalled following another blog post. I deleted the exchange management console.msc per instructions only to discover I couldnt relaunch it because there was
no way how. So I copied another msc file that happened to be on the DC Server 1 back to Exchange Server 2 and got it to launch again.
Another post said that it might be an issue with the Domain Account for the Computer, so to delete it in the AD Server 1 only to find that rejoining it from Exchange Server 2 using Computer>Properties> Chage Settings > Change is greyed out because
it is using the Certificate Authority Service.
I tried manually re-adding the computer in AD and modeling permissions after another server in group settings but no go. After this I was unable to login to the Exchange Server 2 with domain accounts but only local admin, receiving the following Alert:
"The Trust Relationship between this workstation and primary domain failed."
I tried running the Power Shell tools on Exchange Server 2 to rejoing and to reset passwords for domain accounts as noted in some other blogs but no luck as the Server 2 could not make the connection with Server1 or other errors it kept spitting out.
I also during the investigation found the DNS settings were all altered on both the Server 1 and Server 2 which I luckily was able to change back to original because of inventorying it in the beginning when I started.
I need help figuring out if I need to rejoin the Exchange Server 2 manually by disabling the Certificate Authority Service (or removing the CA as listed here:
https://social.technet.microsoft.com/Forums/exchange/en-US/fb23deab-0a12-410d-946c-517d5aea7fae/windows-server-2008-r2-with-certificate-authority-service-to-rejoin-domain?forum=winserversecurity
and getting exchange server to launch again. (Mind you I am relatively fresh to server managing) Please help E-Mail has been down for a whole day now!
Marty

I recommend that you open a ticket with Microsoft Support before you break things more.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

SBS 2003 to 2011 Migration - Exchange Server 2010 cannot be installed

Hello,
We have a Small Business Server 2003 server that we are trying to migrate to SBS 2011 using the out of the box migration process. After the install, the SBS console showed a couple installation issues - the big one turned out to be "Exchange Server
2010 cannot be installed".
Here is the end of 'ExchangeSetup.log' showing various error messages:
[11/29/2014 23:00:07.0489] [2] Active Directory session settings for 'Get-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0490] [2] Beginning processing get-exchangeserver -Identity:'MB-MAINSERVER04' -DomainController:'MB-MAINSERVER04.Contoso.local' -ErrorAction:'SilentlyContinue'
[11/29/2014 23:00:07.0506] [2] Searching objects "MB-MAINSERVER04" of type "Server" under the root "$null".
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Preparing to output objects. The maximum size of the result set is "unlimited".
[11/29/2014 23:00:07.0522] [2] Unexpected Error
[11/29/2014 23:00:07.0522] [2] The operation couldn't be performed because object 'MB-MAINSERVER04' couldn't be found on 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0523] [2] Ending processing get-exchangeserver
[11/29/2014 23:00:07.0523] [1] Executing:
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
[11/29/2014 23:00:07.0545] [2] Active Directory session settings for 'New-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0545] [2] Beginning processing new-exchangeserver -DomainController:'MB-MAINSERVER04.Contoso.local' -Name:'MB-MAINSERVER04'
[11/29/2014 23:00:07.0599] [2] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0600] [2] Ending processing new-exchangeserver
[11/29/2014 23:00:07.0607] [1] The following 1 error(s) occurred during task execution:
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.SystemConfiguration.DefaultAdministrativeGroupNotFoundException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroup()
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroupId()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServer.PrepareDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[11/29/2014 23:00:07.0609] [1] [ERROR] The following error was generated when "$error.Clear();
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
" was run: "Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.".
[11/29/2014 23:00:07.0609] [1] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0609] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___84489810458648f5ac6e47811394a284 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/29/2014 23:00:07.0610] [1] Setup is stopping now because of one or more critical errors.
[11/29/2014 23:00:07.0610] [1] Finished executing component tasks.
[11/29/2014 23:00:07.0618] [1] Ending processing Install-BridgeheadRole
[11/29/2014 23:00:07.0626] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[11/29/2014 23:00:07.0633] [0] End of Setup
[11/29/2014 23:00:07.0633] [0] **********************************************
[11/29/2014 23:39:03.0429] [0] **********************************************
[11/29/2014 23:39:03.0435] [0] Starting Microsoft Exchange Server 2010 Setup
[11/29/2014 23:39:03.0435] [0] **********************************************
[11/29/2014 23:39:03.0456] [0] Local Time Zone: (UTC-08:00) Pacific Time (US & Canada).
[11/29/2014 23:39:03.0457] [0] Operating System version: Microsoft Windows NT 6.1.7600.0.
[11/29/2014 23:39:03.0469] [0] Setup version: 14.1.438.0.
[11/29/2014 23:39:03.0473] [0] Logged on user: Contoso2K3\Administrator.
[11/29/2014 23:39:06.0763] [0] Command Line Parameter Name='mode', Value='Install'.
[11/29/2014 23:39:06.0776] [0] ExSetupUI was started with the following command: '-mode:install'.
[11/29/2014 23:39:07.0413] [0] Setup is choosing the domain controller to use
[11/29/2014 23:39:07.0730] [0] Setup is choosing a local domain controller...
[11/29/2014 23:39:08.0459] [0] Setup has chosen the local domain controller MB-MAINSERVER04.Contoso.local for initial queries
[11/29/2014 23:39:08.0747] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use MB-MAINSERVER04.Contoso.local
[11/29/2014 23:39:08.0748] [0] Setup is choosing a global catalog...
[11/29/2014 23:39:08.0758] [0] Setup has chosen the global catalog server MB-MAINSERVER04.Contoso.local.
[11/29/2014 23:39:08.0819] [0] Setup will use the domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0820] [0] Setup will use the global catalog 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0823] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0830] [0] Exchange organization container for the organization is 'CN=Contoso2K3,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0867] [0] Setup will search for an Exchange Server object for the local machine with name 'MB-MAINSERVER04'.
[11/29/2014 23:39:08.0914] [0] No Exchange Server with identity 'MB-MAINSERVER04' was found.
[11/29/2014 23:39:09.0061] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
[11/29/2014 23:39:09.0062] [0] The following datacenter roles are unpacked:
[11/29/2014 23:39:09.0064] [0] The following roles are installed: AdminToolsRole
[11/29/2014 23:39:09.0066] [0] The local server has some Exchange files installed.
[11/29/2014 23:39:09.0320] [0] Setup will use the path 'C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1' for installing Exchange.
[11/29/2014 23:39:09.0332] [0] The installation mode is set to: 'Install'.
[11/29/2014 23:39:13.0558] [0] An Exchange organization with name 'Contoso2K3' was found in this forest.
[11/29/2014 23:39:13.0560] [0] Active Directory Initialization status : 'True'.
[11/29/2014 23:39:13.0561] [0] Schema Update Required Status : 'False'.
[11/29/2014 23:39:13.0562] [0] Organization Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0563] [0] Domain Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0564] [0] The locally installed version is 14.1.218.15.
[11/29/2014 23:39:13.0565] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V14'.
[11/29/2014 23:39:13.0920] [0] Applying default role selection state
[11/29/2014 23:39:13.0961] [0] Setup is determining what organization-level operations to perform.
[11/29/2014 23:39:13.0962] [0] Because the value was specified, setup is setting the argument OrganizationName to the value Contoso2K3.
[11/29/2014 23:39:13.0963] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V14\'.
[11/29/2014 23:39:13.0972] [0] InstallModeDataHandler has 0 DataHandlers
[11/29/2014 23:39:13.0972] [0] RootDataHandler has 1 DataHandlers
[11/29/2014 23:39:15.0491] [0] Setup encountered an exception when trying to access the setup state file: Could not find file 'C:\ExchangeSetupLogs\exchangeInstallState.xml'.
[11/29/2014 23:39:26.0117] [0] End of Setup
[11/29/2014 23:39:26.0117] [0] **********************************************
I should add that the source server's AD configuration might not be perfect due to this being the second attempt at a SBS 2011 migration install.
I'd be grateful for any help I can get on this as SBS migration has been plauged with multiple setbacks already. I really need to get this done! ;)
Thanks,
Voon

Thank you Larry and Al for your replies.
I used the 'official' migration
guide plus this page (http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/)
as my migration references. The SBS migration prep tool gave no errors on the source server when I ran it.
I have a full system drive image plus a a system state backup from before migration. Though I am very loathed to rollback the migration and attempt a new one - again. I will do some searching to see if I can resolve the Exchange server problem and continue
the migration/installation. If not, then its a system state restore for me. One of Al's links had a resource for doing a thorough check of AD - which something I'd run if I have to another migration attempt.
I am also really tempted to open up a paid MS support ticket for them to help me fix this problem. :)

When sending e-mail messages to a mail-enabled public folder that have been replicated from old Exchange Server 2000/2003/2007, Exchange Server 2010 environment mails are rejected with NDR.

Hi, I would like to share with you issue that I’ve solved regarding mail-enabled PF that migrated from Exchange 2000/2003/2007 to 2010, I’ve searched & contacted my MVP leader – there’s no official KB regarding this issue right
now, so I’m posting here in order to share this among others.
Note: There’s article(s) that talked about PF replication from Exch2000/2003/2007 to 2010 – this is the same issue as well.
Symptoms
E-mail messages that been sent to mail-enabled public folder in Exchange Server 2010 environment rejected with the following NDR:
“#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory
user wasn’t found.> #SMTP#”
Sometimes Exchange Server 2010 is documented as well Event ID 1020 on the Event Viewer with this information:
“Log Name: Application
Source: MSExchange Store Driver
Event ID: 1020
Level: Error
Description:
The store driver couldn’t deliver the public folder replication message "Hierarchy ([email protected])" because the following error occurred: The Active Directory user wasn't found.”
Cause
In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed, there is a chance that an Administrative Group (First Administrative Group or another custom Administrative
Group) remains with a Servers container, but no servers inside it.
During replication, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it's expecting a System Attendant object inside the container and when it is not found the error occurs.
Resolution
To work around the issue, delete the empty Servers container. This can't be done through Exchange System Manager. Use the ADSI Edit tool to remove it using the following steps:
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows
2003 Server, Microsoft Windows Server 2008, Microsoft Exchange 2010 Server or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes
at your own risk.
1.
Start the ADSI Edit MMC Snap-in. Click Start, then
Run, and type adsiedit.msc, and then click OK.
2.
Connect & Expand the Configuration Container [YourServer.DNSDomainName.com], and then expand
CN=Configuration,DC=DNSDomainName,DC=com.
3.
Expand CN=Services, and then CN=Microsoft Exchange, and then expand
CN=YourOrganizationName.
4.
You will see an empty Administrative Group. Expand the
CN=YourAdministrativeGroupName.
5.
Expand CN=Servers.
6.
Verify there are no server objects listed under the
CN=Servers container.
7.
Right click on the empty CN=Servers container and choose
Delete.
8.
Verify the modification, and try to send again the E-mail to the mail-enabled public folder.
Applies to
Exchange Server 2010, Standard Edition
Exchange Server 2010, Enterprise Edition
Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb
| E-mail: [email protected]

Sounds like you are looking in the wrong Administrative Group container which is why you are seeing your Exchange 2010 servers in there.
When you install Exchange 2003 only you will see a container named by default as "CN=First Administrative Group" container. But this could be named anything if you changed the Organization Name on the installation when you installed the first
Exchange 2003 server into the domain/forest.
You will notice that when you install Exchange 2010 part of the AD setup is to create a new configuration container and is named by default "CN=First Administrative Group (FYDIBOHF23SPDLT)".
So it sounds like you are not looking in the right location within ADSIEdit.
You may find the following article also helpful for this issue which is the same resolution:
http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx
I recommend though that you ensure your Exchange 2003 servers are fully uninstalled or no longer present in your environment before you go deleting the Servers container though.. The following Microsoft article will help with this:
http://technet.microsoft.com/en-gb/library/gg576862(v=exchg.141).aspx

Need help with Outlook 2013 connecting to Exchange server(2010)

Hi
I need help with Outlook 2013 and with my exchange server(2010) email account
After setting up account initially emails come in and than after an hour or two stop. My OWA is working fine with no issues. I have even created a forward rule in OWA to my GMAIL account whch works fine
However Outlook 2013 is not syncing messages, have difficulty in sending emails sometimes as it takes too long. In fact the connection also is intermittent. Even if the task bar shows connected to exchange, it seems that is not the case since new emails
and any emails I compose dont work. I have trouble shot the issue with my ISP and email service provide, but they havent resolved the issue I have also done a TraceRoute and that shows no drops or problems to he exchange server.
Can someone please help me resolve this matter so I can continue to use Outlook 2013( running Windows 8.1) in both my computers which have the identical problem
Look forward to a solution soon
Thanks

Hi Angela
Thanks for your message
To answer your questions, please note the following
a) My account is set up in Cache Mode( not online mode)
b) I am the only other user on the account
c) When the connection to the exchange server is broken, I see upon clicking connection tab that there is no information in the box, and when I press reconnect it starts showing "connecting"
d) When the connection to the server is there, it shows connection as "established"
e) Sorry I dont understand th meaning of CAS array in your environment? Can you pls explain
Since yday I have been using Outlook 2010 on desktop and Outlook 2013 on my laptop using Exchange 2013 account. So far all emails are syncing, and I can send emails from both computers. However, I am concerned that the connection can break-off anytime,
as it has done that in the past on both outlook versions. The max time it has worked without any problem is 48 hrs and than after that the same issue of not connection, not syncing and unable to send emails happens
My ISP has checked and there is no network connectivity issues. My email service provider has trouble shot the issue many times, but to no positive results. I have also changed the profile a few times, but the intermittent connectivity problem hasn't
been resolved.
Can you identify the possible causes and more importantly a working permanent solution please
Thanks
Mahesh

Exchange Server 2010: Incoming mail not delivered

I have an Exchange Server 2010 Standard with all recent patches and updates.
-It has been in service for 3 years without any issues.
-There is plenty of hard drive space for the logs and the data (over 100GB in each)
-The current size of the mail database is 150GB
-There is no registry entry in place limiting the size of the database ([url="http://technet.microsoft.com/en-us/library/bb232092.aspx"]Database Size Limit in GB as outlined here[/url]
Starting a few days ago, incoming mail is reaching the server but not being delivered to user mailboxes. Internal mail works fine when this happens. Looking at the Queue Viewer doesn't show anything abnormal. The Submission Queue shows nothing.
It is only after I reboot the Exchange Server that the Submission queue will show all the messages waiting to be delivered and they will all be delivered successfully after the reboot. The event logs do not show any error messages.
The server will continue to run fine for a few hours and then the problem starts all over again.
What could be causing this?

Any 3rd party antivirus/anti-spam software installed on the server? If so, disable and test.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange Server 2010 OWA Error 405 StaticFileModule

Similar Messages

Maybe you are looking for