Exchange 2010 Management Console Initialization failed

Hi.
I have a server running 2008R2 as a domain controller with Exchange 2010 aswell.
This is a fairly new migration from a sbs2003 server, which went very well, in regards to exchange and AD.
The management console has worked since the migration, but suddenly today it stopped working, with the following message (the message is actually from the management shell, which isn't working either.):
[dc.domain.local] Connecting to remote server failed with the following error message : The WS-Management service cannot
process the request. The system load quota of 1000 requests per 2 seconds has been exceeded. Send future requests at
a slower rate or raise the system quota. The next request from this user will not be approved for at least 975630592 milliseconds.
For more information, see the about_Remote_Troubleshooting Help topic.
IIS is working, and listening on ports 80 and 443.
All services are running. I have tride to restart IIS, Windows Remote Management, informationstore and system attendant, but still no luck.
I hope you can help me figure this out.
Anders

I got it. I had to open IIS7 and create the Default Web Site, as I'd deleted it sometime ago.
Once I did that, everything worked great! Frustrating the things we do that come back and kick us in the face for hours, months later....

Similar Messages

Exchange 2010 Management Console "Initialization failed" troubleshooting

This error:
The following error occurred when searching for On-Premises Exchange Server:
[server#.Domain] Connecting to the 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. For more information, see the about_Remote_Troubleshooting help topic
I've seen errors similar to this in these forums, but I haven't had any luck with the steps used to correct other's problems. The most recent steps I've taken are:
uninstalled and reinstalled IIS, then uninstalled and reinstalled CAS, along with various other fixes to no avail.
After installing Exchange and CAS the console was working for a couple of weeks, it died with this error after two things we can remember, although various other things may have been the cause:
1. installed a lengthy list of windows updates
2. installed the URL rewrite module: http://www.iis.net/expand/URLRewrite and set it up to rewrite http://domain to https://domain/owa, this has since been reverted and uninstalled, it still doesn't work.

Thank you for Your Post
The First Error on this Blog is the error that you are facing
http://msexchangeteam.com/archive/2010/02/04/453946.aspx
Issue:
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. For more information, see the about_Remote_Troubleshooting Help topic.
Possible causes:
1. Remote PowerShell uses Kerberos to authenticate the user connecting. IIS implements this Kerberos authentication method via a native module. In IIS Manager, if you go to the PowerShell Virtual Directory and then look at the Modules, you should see Kerbauth listed as a Native Module, with the dll location pointing to C:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll. If the Kerbauth module shows up as a Managed module instead of Native, or if the Kerbauth module has been loaded on the Default Web Site level (instead of, or in addition to, the PowerShell virtual directory), you can experience this issue. To correct this, make sure that the Kerbauth module is not enabled on the Default Web Site, but is only enabled on the PowerShell virtual directory. The entry type of "Local" indicates that the Kerbauth module was enabled directly on this level, and not inherited from a parent.
2. If the WSMan module entry is missing from the global modules section of the C:\Windows\System32\Inetsrv\config\ApplicationHost.config file, as follows:
<globalModules>
<add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" />
This will result in the WSMan module displaying as a Managed module on the PowerShell virtual directory.
To correct this, make sure that the WSMan module has been registered (but not enabled) at the Server level, and has been enabled on the PowerShell virtual directory.
3. If the user that is attempting to connect is not Remote PowerShell enabled. To check if a user is enabled for Remote PowerShell, you need to open the Exchange Management Shell with an account that has been enabled, and run the following query.
(Get-User <username>).RemotePowershellEnabled
This will return a True or False. If the output shows False, the user is not enabled for Remote PowerShell. To enable the user, run the following command.
Set-User <username> -RemotePowerShellEnabled $True

Exchange 2010 - Management Console and Shell Very slow

Heya
I have an Exchange 2010 SP3 enviroment, with 2 HUBCAs and 5 MBX servers.
This servers were 2008 R2 standard, and they were working fine.
This weekend, in order to configure DAG, i upgrade 3 of them to server 2008 R2 enterprise with dsim. Is not the first tiem i do this, and never had problems before.
After the upgrade, the server started fine, the mailboxes, the database.. everything fine.. except, de mmc and the shell.
Both, the mmc and the shell wont start. It gives me the winrm error, but because a time out.
I have installed the installed the iss-winrm feature, delete on regedit and %appdata% the "cache" for the management console, checked the firewal... and nothing worked.
Well, thats not true, in one of the servers, the Management console started working fine, but the shell, it connect, but every command i launch it takes like 10-15 minutes to execute (for example, a get-mailboxdatabase).
In the other,, no the Management console, no the shell connects, i get a winrm timeout.
I dont know were to continue cchecking why happens this, just started after changing the 2008 R2 from standard to enterprise
Thanks for the help!!

Hi,
Please check that your time is in sync as well on your Exchange Server.
Please check whether this issue caused by performance.
More details in the following article:
Understanding Memory Configurations and Exchange Performance
http://technet.microsoft.com/en-us/library/dd346700(v=exchg.141).aspx
http://technet.microsoft.com/en-us/library/dd346699(v=exchg.141).aspx
Please also paste the detailed error message without sensitive information for the further troubleshooting.
Found some related blog for your reference:
Resolving WinRM errors and Exchange 2010 Management tools startup failures
http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx
Troubleshooting Exchange 2010 Management Tools startup issues
http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange Management Console, Initialization Failed

Hi,
Today when i open the Exchange 2010sp1 EMC it gave me this error
The following error occurred while attempting to connect to the specified Exchange Server HUBC01.contoso.int
The attempt to connect to
http://HUBC01.contoso.int/powershell using "kerberos" authentication failed: connection to remote server failed with following error message: The WinRM client cannot process the request because the server name cannot be resolved. for more information see
the about_remote-troubleshooting help topic
Your quick response really appriciated,
Dilshan

Hi Dilshan,
Any updates?
Please check whether "WinRM IIS Extension" is installed in the Server Manager->Feature. If not, please install it.
Please also try to use another member of Organization Management to log on to Exchange to open EMC to test.
Frank Wang
I came across this thread when troubleshootinga a similiar problem. I login to Exchange this morning and I'm unable to open EMC and get an Initialization Failed error message. It states
The attempt to connect to http://exchange2010server/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: Access is denied.
I'm curious if the proposed solution to this thread would solve my problem. I'm a little stumped as to what could cause this, other than the fact a colleague of mine installed the Exchange management tools on his Win7 workstation. That really
is the only change that has taken place in the last week.
Any thoughts?

Unable to connect to Exchange 2010 Management console after - Exchange 2010 SP3 Rollup 7

We have been having issue with our Exchange Server 2010's Transport Service failing due to a database corruption. I was hoping that maybe applying the Roll-up 7 for Exchange might fix this issue, however after applying the patch we are unable to start the
MSExchangeMailboxAssistants "Error 1053: The service did not respond to the start or control request in a timely fashion."
Then I notice that we were unable to connect to the Management Console or through PowerShell.
Event 1000, Application Error
Faulting application name: MSExchangeMailboxAssistants.exe, version: 14.3.210.2, time stamp: 0x53e2bf34
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x5315a05a
Exception code: 0xe0434f4d
Fault offset: 0x000000000000940d
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
PowerShell error:
Exception calling "TryLoadExchangeTypes" with "2" argument(s): "Could not load file or assembly 'Microsoft.Exchange.Man
agement, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name va
lidation failed. (Exception from HRESULT: 0x8013141A)"
At C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1:75 char:92
+ $typeLoadResult = [Microsoft.Exchange.Configuration.Tasks.TaskHelper]::TryLoadExchangeTypes <<<< ($ManagementPath, $t
ypeListToCheck)
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException

Hi,
Please try the following steps to narrow down the issue:
1. Uninstall and reinstall .NET package in Exchange server.
2. Under location C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG, took a copy of Machine.Config.default, renam it to Machine.config and copy it under this path again.
3. Do IIS reset by running iisreset from a Command Prompt window.
4. Reboot the server and verify whether the Exchange services are started.
Regards,
Winnie Liang
TechNet Community Support

How do you publish Exchange 2010 Management Console on a Citrix Server?

I need to be able to remotely manage exchange throught the management console and want to publish it through Citrix. I successfully installed the console on the XenApp servers in our farm, but after publishing it, can not get the published console
to run through the Citrix Plug in or oweb interface. Any idea what I could be doing wrong? Since I can run it directory from the server, the problem must exist in the way I published it. I have checked permissions and those appear to be ok.
Thanks for the assistance.

hi,
How do you publish your EMC? Since you can't run, do you get some error information. But it seems it isn't a exchange problem. If you have installed your EMC on your another computer in you ORG. You can run it by click start. If you want to use Citrix, ask
them for help is a good idea.
hope can help you
thanks,
CastinLu
TechNet Community Support

Exchange management console initialization failure

Hi all.
One of my clients SBS 2011 standard servers downloaded some updates yesterday & since then both the Exchange Management Console & Shell fail to open. In addition mail to the smart phones no longer works. Everything else seems ok. Mail is delivered
& received via Outlook, all services are running. I have tried uninstalling the updates, but the Microsoft C++2010 Redistributable that was installed yesterday does not appear in the list of updates to uninstall. Only one of these updates is listed
which is from 2012. This is the first part of the problem to resolving this issue. There are no "hidden updates" I am sure that this update was the most likely to be causing this issue. Any clues as to how to remove this update?
The Exchange Management Console error is below.
Connecting to the 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.
Exchange Management Shell errors.
Connecting to the 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.
Connecting to the 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.
I have checked the settings as per the following possible solutions.
https://support.microsoft.com/kb/2027063?wa=wsignin1.0
I have added & removed & added the WinRM IIS extension & ran WinRM Quickconfig
I have checked Powershell directory in IIS on the problem server. Make sure SSL is not required. Allow
only Anonymous access.
I have run this command from the Windows Powershell - note the warning
set-user yourusername -remotepowershellenabled:$true
Warning: The command completed successfully but no settings of “domain.local/MyBusiness/Users/SBSUsers/User” have
been modified
Checked the ExchangeInstallPath environment variable
Checked the application pool settings in IIS are set to Local System Identity
About the only item I have not tries is to remove & reinstall the PowerShell directory. I will do this over the weekend.
This server has been in operation for almost 3 years without an issue. Microsoft updates come down & now I have been working on the issue for about 6 hours. Any other ideas?
Regards, Scott

Explore Powershell Virutal Directory , what is the size of Web.config file?
What happens if you browse Powershell VD ?
Check the Powershell Application Pool
Make sure Enable 32 bit application under advance settings is set to FALSE
Perform an IISRESET
Also refer to -
http://blogs.technet.com/b/whats_on_scotts_mind_today/archive/2012/12/07/exchange-2010-unable-to-open-exchange-management-console-initialization-failed.aspx
Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Exchange 2010 Management Pack Data Warehouse Synchronization Fails

Hi Everyone!
Has anyone had success with importing the Exchange 2010 management pack into Service Manager 2012?
When we try to import it, it fails.
Upon further investigation, the 'System Center Core Monitoring' management pack (which is not included with Service Manager 2012) is a dependency of the Exchange 2010 management pack but
after we import it from the OpsMgr 2012 media, we still get the following warning when we import the Exchange 2010 management into Service Manager 2012...
"The management pack was imported successfully.
Warnings (1):
Override verification failed, cannot find Management Pack Element : : Cannot find ManagementPackElement [Type=ManagementPackRule, ID=Microsoft.SystemCenter.Agent.MonitoringHost.PrivateBytesThreshold] in management pack ManagementPack:[Name=Microsoft.SystemCenter.2007,
KeyToken=31bf3856ad364e35, Version=6.0.6246.0]."
...and, the Exchange 2010 management pack status in the Service Manager 2012 Data Warehouse 'Management Pack' view indicates 'failed' after the MPSyncJob completes.
We have a few 'Business Services' which depend on the Exchange 2010 management pack that we are trying to synchronize from OpsMgr 2012 and we are stuck until we can get the Exchange 2010 management
successfully imported into Service Manager 2012 and have it show a status of 'Completed' the Service Manager 2012 Data Warehouse 'Management Pack' view.
Nothing useful in the
Service Manager 2012 Data Warehouse and Management servers events logs that we could see.
Any help or guidance would be GREATLY appreciated!
Regards,
JJ

Update: I Just tested with CU2 installed for SrvMgr 2012 and OpsMgr 2012 and version 14.3.38.2 of the Exchange 2010 management, but the management pack still fails to deploy to the SrvMgr 2012 data warehouse (the management pack status shows
up as 'failed' and the MPSyncJob shows the management pack as 'pending association'). The only clue I have for this problem is the folllowing warning which occurs when I import the management pack into SrvMgr 2012...
I also get the following 33519 Event ID warning in the Operations Manager event log on the data warehouse server...
~~~~~
Management pack association ignored. This does not require any action. If you continue to frequently see this warning, contact your administrator. This process will continue to retry.
Management pack ID: e2296ed5-ddbc-ebc7-3881-c5288adaa7cf
Management pack name: Microsoft.Exchange.2010
Management pack version: 14.3.38.2
Data source name: SRV
Message: Either the MP has failed deployment Or any of its references has failed deployment
~~~~~
Has anyone had success with getting the Exchange 2010 management pack imported and successfully deployed to the SrvMgr 2012 data warehouse?
The good news is that even though the Exchange 2010 management pack has a status of failed, the distributed applications in OpsMgr 2012 that depend on the Exchange management pack now show up under Configuration Items/Business Services including
all related service component objects which was what I was trying to accomplish in the first place, so for now I'll just leave the Exchange 2010 management pack in the data warehouse with a failed status.
Regards,
JJ

Error when trying to install MS Exchange 2010 Management Tools Windows 7 x64 SP1

When I try to install Exchange 2010 Management Tools on my Windows 7 Pro x64. I get the message ExSetupUI.exe has stopped working? Has anybody else gotten this message? It doesn't even load into the install screen. It is stopping before then.

Hi
Have you installed the admin tools for windows 7 and all the prerequisites? Try running the setup from an elevated prompt or "as Administrator"
for ref:
http://social.technet.microsoft.com/Forums/en-US/63880f4e-6b6e-4ea9-b3b6-8a535657288f/installing-exchange-management-tools-on-a-win-7-x64-box-getting-error-on-readiness-checks?forum=exchange2010

Forcefully delete user's "Deleted Items" from Exchange 2010 Management shell ?

After migration from Exchange 2003 to 2010 my organization's some user can't delete items from their deleted items folder, it generate a error message so how can I forcefully delete user's deleted items from their "Deleted Items folder" from
Exchange 2010 Management shell ? Thanks
Babu

Hi Babu ,
Based on my knowledge i have given some suggestions please have a look in to it.
1.We cannot use the search-mailbox command specifically for any folder in the mailbox.But we can use it for a whole mailbox.Below is the command which will copy the entire contents of the mailbox to the target folder called as "backup" .
Search-Mailbox -Identity "problematic mailbox name" -TargetMailbox "test mailbox" -TargetFolder "backup" -LogLevel Full -deletecontent
Note : Before executing the above command , please execute the below.
New-ManagementRoleAssignment -Name "Import Export_Enterprise Support" -SecurityGroup "Enterprise Support" -Role "Mailbox Import Export"
Once the above command is executed then you need to add your admin account to the security group "Enterprise Support" and then use the Search-Mailbox command to copy the entire items to the target mailbox and also it will delete all the copied
items from the original mailbox.
2.Another one option is to use the MFCMAPI tool to force delete the items on the deleted items folder.
Most importantly before doing all the above , please share me the error message what your users are facing while deleting the items from deleted items folder.
Thanks & Regards S.Nithyanandham

Exchange 2010 sp3 rollup 7 fails

Exchange 2010 sp3 rollup 7 fails. This is ran at an elevated prompt and the UAC off. This server is also logged in as the domain Administrator account.
The server currently has rollup 4 SP3 installed. I'm wondering if I should uninstall it, reboot then try the Rollup 7 SP3 update?

Hi,
Can you please post the error?
At the same time please check these.
http://technet.microsoft.com/en-us/library/ee861125(v=exchg.141).aspx
http://exchangeserverpro.com/how-to-install-updates-on-exchange-server-2010-database-availability-groups/
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2010 management tools and others

Win2k8 domain, Exchange 2010 servers
We want to move to Win8.1 but we, the admins, are preventing it because our tools like the Exchange 2010 Management tool doesn't work with Win8.0 so we're stuck with Win7.
I've googled around and most suggestion never worked.
Does Microsoft have any plans at all to have Exchange 2010 management tools and other tools we use to manage our domain work with Win8.1?

Hi Rino,
Thanks for your sharing and efforts put on this issue.
This will benefit others who encounter the similar scenario as yours.
Happy holiday~
Kate Li
TechNet Community Support

Exchange 2010 sp2 emc initialization error using "kerberos" authentication failed

We use exchange 2010 SP2.
We have 2 management stations, both w2k8 R2 SP1.
I have one mangement station on which the emc and ems works ok.
On the other management staiton (which is also in another ad site) the emc and ems don't work.
I get the following error message : The attempt to connect to
http://fqdnCasServer/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.
I have checked the time on the management station and on the exchange server and this is ok.
It is not a permissions issue because the user functions ok on the other management station.
On the bad management station I can open the emc once and after a minute I get an error message and the message access denied. From then on I can't connect any more.
What am I doing wrong?
Anyone any tips?
Thanks,
JB

This is what I get in the eventlog of the bad management station.
Log Name:      MSExchange Management
Source:        MSExchange CmdletLogs
Date:          1/10/2012 11:39:27
Event ID:      6
Task Category: (1)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.domain.com
Description:
The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Get-ExchangeServer
{Identity=Servername}
Domain/ou/ou/ou/ou/username
Exchange Management Console-Local
3080
22
00:00:00.3593888
View Entire Forest: 'True', Configuration Domain Controller: 'FQDN DC', Preferred Global Catalog: 'FQDN DC', Preferred Domain Controllers: '{ FQDN DN }'
Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'FQDN MGMTSTATION' couldn't be found on 'FQDN DC'.
Context
the message resource is present but the message is not found in the string/message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchange CmdletLogs" />
    <EventID Qualifiers="49152">6</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-10-01T09:39:27.000000000Z" />
    <EventRecordID>11</EventRecordID>
    <Channel>MSExchange Management</Channel>
    <Computer>FQDN MGMT STATION</Computer>
    <Security />
</System>
<EventData>
    <Data>Get-ExchangeServer</Data>
    <Data>{Identity=MGMT STATION}</Data>
    <Data>domain/ou/ou/ou/ou/username</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>Exchange Management Console-Local</Data>
    <Data>3080</Data>
    <Data>
    </Data>
    <Data>22</Data>
    <Data>00:00:00.3593888</Data>
    <Data>View Entire Forest: 'True', Configuration Domain Controller: 'FQDN DC', Preferred Global Catalog: 'FQDN DC', Preferred Domain Controllers: '{ FQDN DC }'</Data>
    <Data>Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'FQDN MGMT STATION' couldn't be found on 'FQDN DC'.</Data>
    <Data>Context</Data>
    <Data>
    </Data>
</EventData>
</Event>

Windows 2008 R2 - Exchange 2010 Mailbox Role Install Failed

Hi,
I have been trying to install Exchange 2010 on my Win Server 2008 R2.
I have an error when i try to install mailbox role :
The following error was generated when "$error.Clear(); $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName; $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
$dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1; if( $dismbx -ne $null) { $srvname = $dismbx.ServerName; if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" ) { Write-ExchangeSetupLog -info "Setup
DiscoverySearchMailbox Permission."; $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true }; if( $mountedMdb -eq $null ) { Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
mount-database $dismbx.Database; } $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true }; if( $mountedMdb -ne $null ) { $dmRoleGroupName = "Discovery Management"; $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupName
-DomainController $RoleDomainController -ErrorAction:SilentlyContinue; if( $dmRoleGroup -ne $null ) { Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
} } } }" was run: "Couldn't mount the database that you specified. Specified database: Mailbox Database 1527275860; Error code: An Active Manager operation failed with a transient error. Please retry the operation. Error: A transient error occurred
during discovery of the database availability group topology. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005,
ec=-1011)
[Database: Mailbox Database 1527275860, Server: serveur.domain.fr].".
Couldn't mount the database that you specified. Specified database: Mailbox Database 1527275860; Error code: An Active Manager operation failed with a transient error. Please retry the operation. Error: A transient error occurred during discovery of the database
availability group topology. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005, ec=-1011)
[Database: Mailbox Database 1527275860, Server: serveur.domain.fr].
An Active Manager operation failed with a transient error. Please retry the operation. Error: A transient error occurred during discovery of the database availability group topology. Error: Database action failed with transient error. Error: A transient error
occurred during a database operation. Error: MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005, ec=-1011)
[Database: Mailbox Database 1527275860, Server: serveur.domain.fr]
An Active Manager operation failed with a transient error. Please retry the operation. Error: MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005, ec=-1011)
[Server: serveur.domain.fr]
MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005, ec=-1011)
/prepareschema ->OK
/preparead ->OK
/preparedomain -> OK
The Account rights seems good : Domain Admins - Enterprise Admins - Schema Admins
I tried to use another installation media but no change.
I tried this : http://support.microsoft.com/kb/978776/fr
but at step 2 i have the sameerror again.
Can you help me Please :-)
tkx

Hi,
Thanks for your sharing. It's great to hear the good news.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2010 RPC over HTTPs failing with authentication error

Hi. I have my remote.xxx.co.uk domain and autodiscover.xxx.co.uk domain pointing to my SBS2011 server, have ports 25, 80, 443 open. The Microsoft Connectivity Analyzer fails with the below error.
Outlook will autodiscover happily on the local network, and works fine. Phones etc do too.
Outlook at a remote VPN connected site won't connect through autodiscover, but will if you do it manually (ignoring the RPC Proxy settings). Everything works for a while, but then I guess outlook decides to use autodiscover to complete all the connection
details, and then these machines can no longer connect to exchange as I guess they decide the speed is too slow and try to connect using RPC instead.
Users can access OWA happily, and activesync is working on phones etc.
SSL cert is a wildcard type on my domain, and certs are installed - all green and happy when visiting OWA on both remote.xxxxx.co.uk and autodiscover.xxxxx.co.uk domains.
I cannot work out why I have an authentication error for RPC?
Any advice would be great!
Testing HTTP Authentication Methods for URL https://remote.xxxxx.co.uk/rpc/rpcproxy.dll?xxxxxx.xxxxxx.local:6002.
The HTTP authentication test failed.
Additional Details
Exception details:
Message: The operation has timed out
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse()
Elapsed Time: 100065 ms

Hi.
To update.
I tried to recreate the virtual directories in the Exchange Management Console, using the recreate links and via the shell, but while they were recreated, they did not function as they should due to issues in the meta database.
I then found the following which worked.
Looking at the ActiveSync virtual directories, when running the below command, the result showed the directory was there, so I then knew to delete it.
In EMS I ran,
=> Ran "$site = [ADSI]"IIS://localhost/W3SVC/1/Root/Microsoft-Server-ActiveSync""
Result: Carriage return.
=> Ran "$site"
Result:
distinguishedName:
Path: {C:\Program Files\Microsoft\ExchangeServer\V14\Client Access\Sync}
In EMS I then ran,
=> Ran "$Site = [ADSI]"IIS://localhost/W3SVC/1/Root""
Result: Carriage return.
=> Ran "$site.Delete("IIsWebVirtualDir","Microsoft-Server-ActiveSync")"
Result: Carriage return.
=> Ran "$site.SetInfo()"
Result: Carriage return.
=> Ran "$site"
Result: Carriage return.
=> Ran "iisreset"
I then recreated the virtual directories.
In EMS I ran,
=> Ran "New-ActiveSyncVirtualDirectory -WebSiteName "Default Web Site""
Results: Successfully recreated.
=> Ran "iisreset"
I am not sure exactly, but I did this for multiple virtual directories, and everything came to life just as it should.

Exchange 2010 Management Console Initialization failed

Similar Messages

Maybe you are looking for