Exchange 2010 EMC Failed Initialization

Hi
Server 2008 64bit SP2 running on hyper V
Just done an install of exch2010 on a vanilla test DC 2008, passed all the readiness checks after installing all the bits and pieces. I also ran the following:
1) winrm quickconfig
2) For a server that will have the typical installation of Client Access, Hub Transport, and the Mailbox role:
sc config NetTcpPortSharing start= auto
ServerManagerCmd -ip Exchange-Typical.xml -Restart
all seemed to install OK but when I try and start the EMC when clicking on the "Microsoft Exchange ON-Premises" I get an initialization failure with the following detail:
The following error occured when searching for On-Premises exchange server:
[testdc08.company.com] Connecting to remote server failed with the following message : The WSMan client
cannot process the request. Proxy is not supported under http transport. Change the transport to https and
specify valid proxy information and try again. For more information , see the about troubleshooting help topic
I understand this stuff is to do with remote managing exchange servers across the internet, but in my case I am trying to simply access the exchange server (on the DC) from the DC???
Can anyone shed light on this install of doom,
thanks

Dear All,
I have faced same issue with my exchange 2010 server on Windows 2008 R2 O/S. There is some problem in my winhttp settings (proxyycfg). To resolve this issue I deleted WinHttpSettings from registry keys. It will reset it to default. Below is the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHttpSettings
-->Delete WinHttpSettings
Regards,
Khurram Awal Khan
Senior System Engineer
Alnafitha Int.
Hi Khurram
This worked for use as well. Thank you

Similar Messages

Exchange 2010, khi: failed to execute Troubleshoot-DatabaseSpace.ps1 Error formatting a string: Format string is not supported

Hi,
Exchange 2010 MP fails to run Troubleshoot-DatabaseSpace.ps1. Results in a Warning with "Error formatting a string: Format string is not supported". The EventNumber is 402. The Microsoft article it points to is useless at http://technet.microsoft.com/en-us/library/749e0eac-ebb2-41e3-8fa2-4a03a1bd3571.aspx
Run ".\Troubleshoot-DatabaseSpace.ps1 -Server MailboxServer.domain.com -MonitoringContext" and works fine.
Any help appreciated.
thanks

Hi,
Before the newer MP release, we can disable these 4 monitor via override and this should not run the Troubleshoot-DatabaseSpace.ps1 :
KHI: Failed to execute Troubleshoot-DatabaseSpace.ps1.
KHI: The database copy is low on database volume space and continues to grow. The volume is under 25% free
KHI: The database copy is low on database volume space and continues to grow. The volume has reached error levels under 16% free.
KHI: The database copy is low on database volume space and continues to grow. The volume has reached critical levels 8% free.
Alex Zhao
TechNet Community Support

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....

Exchange 2010 EMC and EMS errors - BLOCKED by software restriction

EMC has this message:
Initialization failed "Execution calling 'GetSteppablePipeline" with "1" arguement: File D:\program files\Microsoft\Exchange Server\V14\RemoteScripts\ConsoleInitialize.ps1 cannot be loaded because its execution is blocked
by software restriction policies"
EMS has this error:
"There were errors in loading the format data file: D:\Program Files\Microsoft\Exchange 2010\V14\Bin\exchange.format.ps1x
ml, , D:\Program Files\Microsoft\Exchange 2010\V14\Bin\exchange.format.ps1xml : File skipped because of the following validation exception: File D:\Program Files\Microsoft\Exchange 2010\V14\Bin\exchange.format.ps1xml cannot be loaded because its execution is
blocked by software restriction policies. For more information, contact your system administrator."
All other powershell scripts work just fine. It is not the execution policy. That is set properly. Authenticode returns valid on the files. There are no settings it GPO to control or cause this. Email working fine. It just started
after a reboot for updates. Any other thoughts before I spend $500 for a call?
Server2008 Standard SP2
Update Rollup 4 v2 for Exchange Server 2010 SP2
Thank you

The long and short of it was Microsoft Certificates didn't update and were expired. I was not given a reason why this happened but the final solution after Microsoft spent 2 weeks on this was to first reinstall Exchange Service Pack 3, reboot. Install
update rollup 8, and reboot. This fixed the EMC but not the shell. Then they reinstalled the rollup 8 again and one more reboot. Everything now works. I'd say with all the other little tweaks they looked at as possible suspect and "other
things" they fixed in their efforts to solve this, I defiantly got my money's worth. Despite not really knowing what really caused the issue in the first place

Apple Mail 6.2 Exchange 2010 Delete Fail

When deleteting an email in Apple Mail 6.2 setup to use Exchange 2010 with MAPI, the following error message is displayed:
The message "X" could not be moved to the mailbox "Trash folder name".
An error occurred while moving messages to mailbox "Trash folder name".
To reproduce this problem I loaded a mailbox with 30k of emails. I then deleted 4000 messages, and while the client was still syncing (visibly you could see it syncing the activity window) - I deleted some of the same messages again.
The sync process stopped, the activity window stopped showing any activity and my emails which were previously marked for deletion remained visible.
Now when I try to delete the emails I previously deleted, I receive the error as above and the messages are not deleted.
If I delete other messages that were not previously marked for deletion I do not receive the error.
To remove the messages that were causing the error I had to "Command-X" to cut them from the folder and bypass the trash.

Hi Andrew,
I tried to understand your message but failed to. I'm sorry. Just clicking "rebuild" worked for me to restore behavior that hadn't been working. It only took a few seconds.
That said, it was only days later that all of my correspondance stored on the Exchange server disappeared, and 123Together, my Exchange service provider, said "Since you are on a Mac the database may gotten corrupted and synched to the server that is why the data in the mailbox and subfolder you may not see. We can have our admin do a restore of the mailbox as we can go back for a restore point up to 5 days, there is a admin fee of 160.00 hr anywhere from 1-3 hours of work please let us know if you would like to proceed." I was not happy.
So I probably agree with what you are saying!
Larry

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 SP3 Failing to Install "The remote procedure call failed"

I am getting an error while trying to upgrade the first Mailbox server in the organization to SP3. The CAS and HUB servers already upgraded without any issues. Any help is greatly appreciated.
Here is the exchange setup logs output:
[11/15/2014 09:10:52.0512] [2] Creating Server Object with DN = /dc=xxx/dc=xxx/cn=Configuration/cn=Services/cn=Microsoft Exchange/cn=xxx/cn=Administrative Groups/cn=Exchange Administrative Group (xxxx)/cn=Servers/cn=xxxxxx
[11/15/2014 09:10:52.0512] [2] Status code check (f:\14.03.0123\sources\dev\admin\src\libs\ds\x_dob.cxx:3370)
           Error code 0X8000500D (20493): This property can't be found in the cache.
[11/15/2014 09:10:52.0528] [2] Leaving ScCreateServerObject
[11/15/2014 09:10:52.0528] [2] Entering ScSetServerNetworkAddresses
[11/15/2014 09:10:52.0528] [2] Entering ScGetServerDNSNameFromDS
[11/15/2014 09:11:11.0482] [2] ScUserDNFromLoginName (f:\14.03.0123\sources\dev\admin\src\libs\exsetup\exmisc.cxx:1441)
           Error code 0XC00706BE (1726): The remote procedure call failed.
[11/15/2014 09:11:11.0482] [2] ScGetServerDNSNameFromDS (f:\14.03.0123\sources\dev\admin\src\libs\exsetup\dsmisc.cxx:3481)
           Error code 0XC00706BE (1726): The remote procedure call failed.
[11/15/2014 09:11:11.0482] [2] Leaving ScGetServerDNSNameFromDS
[11/15/2014 09:11:11.0482] [2] ScSetServerNetworkAddresses (f:\14.03.0123\sources\dev\admin\src\udog\excommon\ptudutil.cxx:1028)
           Error code 0XC00706BE (1726): The remote procedure call failed.
[11/15/2014 09:11:11.0482] [2] Leaving ScSetServerNetworkAddresses
[11/15/2014 09:11:11.0482] [2] CAtomServer::ScAddOrRefreshDSObjects (f:\14.03.0123\sources\dev\admin\src\udog\exsetdata\components\server\a_server.cxx:288)
           Error code 0XC00706BE (1726): The remote procedure call failed.
[11/15/2014 09:11:11.0482] [2] CAtomServer::ScAddDSObjects (f:\14.03.0123\sources\dev\admin\src\udog\exsetdata\components\server\a_server.cxx:354)
           Error code 0XC00706BE (1726): The remote procedure call failed.
[11/15/2014 09:11:11.0482] [2] CBaseAtom::ScReinstall (f:\14.03.0123\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:815)
           Error code 0XC00706BE (1726): The remote procedure call failed.
[11/15/2014 09:11:11.0482] [2] Leaving CBaseAtom(Microsoft Exchange Server-Level Objects)::ScReinstall
[11/15/2014 09:11:11.0482] [2] Service = '' CBaseServiceAtom::ScReinstall (f:\14.03.0123\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:242)
           Error code 0XC00706BE (1726): The remote procedure call failed.
[11/15/2014 09:11:11.0482] [2] Leaving CBaseServiceAtom(Microsoft Exchange Server-Level Objects)::ScReinstall
[11/15/2014 09:11:11.0482] [2] mode = 'Reinstall' (61955) CBaseAtom::ScSetup (f:\14.03.0123\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:537)
           Error code 0XC00706BE (1726): The remote procedure call failed.
[11/15/2014 09:11:11.0482] [2] ScSetupAtom (f:\14.03.0123\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:882)
           Error code 0XC00706BE (1726): The remote procedure call failed.
[11/15/2014 09:11:11.0482] [2] Leaving ScSetupAtom
[11/15/2014 09:11:11.0482] [2] [ERROR] An error occurred with error code '3221685950' and message 'The remote procedure call failed.'.
[11/15/2014 09:11:11.0482] [1] The following 1 error(s) occurred during task execution:
[11/15/2014 09:11:11.0482] [1] 0. ErrorRecord: An error occurred with error code '3221685950' and message 'The remote procedure call failed.'.
[11/15/2014 09:11:11.0482] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '3221685950' and message 'The remote procedure call failed.'.
[11/15/2014 09:11:11.0482] [1] [ERROR] The following error was generated when "$error.Clear();
   buildToBuildUpgrade-ExsetdataAtom -AtomName Server -DomainController $RoleDomainController
" was run: "An error occurred with error code '3221685950' and message 'The remote procedure call failed.'.".
[11/15/2014 09:11:11.0482] [1] [ERROR] An error occurred with error code '3221685950' and message 'The remote procedure call failed.'.
[11/15/2014 09:11:11.0482] [1] [ERROR-REFERENCE] Id=AllADRolesCommon__ExsetdataServer Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/15/2014 09:11:11.0482] [1] Setup is stopping now because of one or more critical errors.
[11/15/2014 09:11:11.0482] [1] Finished executing component tasks.
[11/15/2014 09:11:11.0529] [1] Ending processing Install-MailboxRole
[11/15/2014 09:14:12.0977] [0] End of Setup
[11/15/2014 09:14:12.0977] [0] **********************************************
Additionally here is the 2 errors that are showing up in the event viewer for MSExachange Management:
Exchange Management Console-Local
2652
45
00:00:18.9698426
View Entire Forest: 'True', Configuration Domain Controller: 'domaincontroller.xxx.xxx', Preferred Global Catalog: 'domaincontroller.xxx.xxx', Preferred Domain Controllers: '{ domaincontroller.xxx.xxx }'
Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '3221685950' and message 'The remote procedure call failed.'.
0
Exchange Management Console-Local
2652
9
00:00:37.7834262
View Entire Forest: 'True', Configuration Domain Controller: 'domaincontroller.xxx.xxx', Preferred Global Catalog: 'domaincontroller.xxx.xxx', Preferred Domain Controllers: '{ domaincontroller.xxx.xxx }'
Microsoft.Exchange.Management.Deployment.ScriptExecutionException: The following error was generated when "$error.Clear(); buildToBuildUpgrade-ExsetdataAtom -AtomName Server -DomainController $RoleDomainController
" was run: "An error occurred with error code '3221685950' and message 'The remote procedure call failed.'.". ---> Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '3221685950' and message 'The
remote procedure call failed.'. --- End of inner exception stack trace ---
0
Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '3221685950' and message 'The remote procedure call failed.'.

Hi,
Please try to remove the Water mark and Action keys under
HKLM\SOFTWARE\Microsoft\Exchangeserver\V14\MailboxRole
After that, reboot the server and rerun the set up.
This issue due to Exchange failed set up was trying to resume the previously failed setup rather than starting completely over.
Best Regards.

Exchange 2010 EdgeSync Failed, Can't connect to LDAP

Hi Guys,
I'm currently trying to check my edgesync and it's failing because it can't contact the LDAP service. I've disabled the firewalls on my AD server, my exchange server and my Edge server.
AD LDS and IIS are installed. I'm on edge as local administrator in workgroup computer.
The certificates on my edge and exchange aren't identical. I've created and copied the XML files across and imported it from the HT server in edge subscriptions.
I can't understand how it can't connect given that all servers can ping eachother and the firewalls are all disabled. Can anybody advise anything I can do to test ports being blocked in case some service is reserving those ports?
Many thanks,
Elliot

Hi,
I have created a test environment to deploy Exchange 2013 sp1 and I get same problem.
I have disabled IPv6 on DNS (in my case also AD) server and edge server and I was able to configure everything properly.
Mihai

Addition of Exchange 2013 server to Exchange 2010 organization broke Exchange

This is somewhat of an emergency, since Exchange is down completely for us right now.
I just migrated from SBS2003 to Exchange 2010 on Windows 2012 over last weekend. Everything is now stable, and SBS2003 is shut down. Now I am attempting to migrate from Exchange 2010 to Exchange 2013.
The plan was this:
Install Exchange 2013 on another server (Windows 2008R2)
Wait until everything is replicated
Remove the Exchange 2010 server from the organization
Uninstall Exchange 2010
Install Exchange 2013 on the Windows 2012 server
Wait until everything is replicated
Remove Exchange 2013 from the Windows 2008R2 server
But here is what actually happened:
Installed all Exchange 2013 prerequisites on the Windows 2008R2 server
Began Exchange 2013 server setup on the Windows 2008R2 server. Included both Mailbox & CAS roles
At step 11 of 15 (not sure what that was, though), received this error message:
Error: The following error was generated when "$error.Clear();
netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
" was run: "The term 'netsh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.".
And setup halted. I ran the netsh command via the command prompt, and it correctly said something about four rules being created or updated (not sure of exact verbiage). Now, when I try to restart setup, it says it is in the middle and will try to complete
but stays at 0%. But here is the most immediate issue:
Now I cannot access e-mail from any workstations (says Exchange server is unavailable)
Opening EMC on the Exchange 2010 server: I get as far as Microsoft Exchange -> Microsoft Exchange On-Premises and get this error:
The attempt to connect to http://[Exchange 2010 FQDN]/PowerShell using "Kerberos authentication failed: Processing data from remote server [Exchange 2010 FQDN] failed with the following error message:
Couldn't find Enterprise Organizaiton container. (Note that it refers to the local server as remote server)
I get an event 7031 on the Exchange 2010 server: The Microsoft Exchange Service Host service terminated unexpectedly
Opening the Exchange Management Shell on the Exchange 2010 server yields the same message regarding "Couldn't find the Enterprise Organization container..."
It also says, "Connecting to [Exchange 2013 server FQDN], then says connected to that server. Opening EMS on the Exchange 2013 server seems to connect correctly to the Exchange 2013 server, but there is no EM Console available there.
At this point, I am lost. I will continue to research this online but may have to call Microsoft soon, since we are entirely down at the moment. Any help is much appreciated!

All of the above, I believe. And E2003 is on the DC (and functioning just fine); E2012 on a member server (this is a very small environment--they have only the DC, a DB2 database server, and a lightly-used and old terminal server). I just spent 12 hours
on the phone with MS support on this issue, and it has now come down to this: the Exchange 2013 installation will not run to completion. It has failed repeatedly at a few points today, all related to the shell being unable to access Windows EXEs or environment
variables with variations on this error:
"...not recognized as the name of a cmdlet, function, script file, or operable program..." for each of these:
netsh (windows exe)
sc.exe (windows exe)
hostname (windows command that returns workstation name)
These all work from the command prompt. I am currently stuck on sc.exe failing on each attempt to install Exchange 2013 or Exchange 2013 SP1. Nor can I just remove it--it insists on attempting to proceed with installation even with the manual command-line
argument to remove it instead.
At this point, I am awaiting a night call back from Microsoft support, since the technician that worked on it with me for 12 hours today had to go home.

Exchange 2010 setup problems

I am having some issues and I am need some help please. I tried to setup exchange on a local server yesterday (2010) and 1/2 way through it throught a ton of errors where I could not find some items. So ok I said it would not even uninstall without giving
me grief. I then did a manual uninstall of 2010 since I couldnt get 2010 to even install on the new server without doing so. I then setup a new virtual server today and tried to reinstall it. but am still getting an error and here is the logs.
[04/27/2014 07:48:55.0235] [2] Active Directory session settings for 'initialize-ExchangeUniversalGroups' are: View Entire Forest: 'True', Configuration Domain Controller: '69-64-71-40.ketelaaraccounting.com', Preferred Global Catalog: '69-64-71-40.ketelaaraccounting.com',
Preferred Domain Controllers: '{ 69-64-71-40.ketelaaraccounting.com }'
[04/27/2014 07:48:55.0235] [2] Beginning processing initialize-ExchangeUniversalGroups -DomainController:'69-64-71-40.ketelaaraccounting.com' -ActiveDirectorySplitPermissions:$null
[04/27/2014 07:48:55.0267] [2] Used domain controller 69-64-71-40.ketelaaraccounting.com to read object DC=ketelaaraccounting,DC=com.
[04/27/2014 07:48:55.0282] [2] Used domain controller 69-64-71-40.ketelaaraccounting.com to read object CN=Configuration,DC=ketelaaraccounting,DC=com.
[04/27/2014 07:48:55.0282] [2] Used domain controller 69-64-71-40.ketelaaraccounting.com to read object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ketelaaraccounting,DC=com.
[04/27/2014 07:48:56.0031] [2] Used domain controller 69-64-71-40.ketelaaraccounting.com to read object OU=Microsoft Exchange Security Groups,DC=ketelaaraccounting,DC=com.
[04/27/2014 07:48:56.0125] [2] [ERROR] Unexpected Error
[04/27/2014 07:48:56.0125] [2] [ERROR] The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:ed5aa0f9-643b-43d8-bdeb-5e6c0f327703,CN=Deleted Objects,DC=ketelaaraccounting,DC=com on the otherWellKnownObjects attribute
in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ketelaaraccounting,DC=com points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.
[04/27/2014 07:48:56.0156] [2] Ending processing initialize-ExchangeUniversalGroups
[04/27/2014 07:48:56.0156] [1] The following 1 error(s) occurred during task execution:
[04/27/2014 07:48:56.0156] [1] 0. ErrorRecord: The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:ed5aa0f9-643b-43d8-bdeb-5e6c0f327703,CN=Deleted Objects,DC=ketelaaraccounting,DC=com on the otherWellKnownObjects
attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ketelaaraccounting,DC=com points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.
[04/27/2014 07:48:56.0156] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:ed5aa0f9-643b-43d8-bdeb-5e6c0f327703,CN=Deleted
Objects,DC=ketelaaraccounting,DC=com on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ketelaaraccounting,DC=com points to an invalid DN or a deleted object. Remove the entry, and then
rerun the task.
[04/27/2014 07:48:56.0156] [1] [ERROR] The following error was generated when "$error.Clear();
initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
" was run: "The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:ed5aa0f9-643b-43d8-bdeb-5e6c0f327703,CN=Deleted Objects,DC=ketelaaraccounting,DC=com on the otherWellKnownObjects attribute in the container
object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ketelaaraccounting,DC=com points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.".
[04/27/2014 07:48:56.0156] [1] [ERROR] The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:ed5aa0f9-643b-43d8-bdeb-5e6c0f327703,CN=Deleted Objects,DC=ketelaaraccounting,DC=com on the otherWellKnownObjects attribute
in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ketelaaraccounting,DC=com points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.
[04/27/2014 07:48:56.0156] [1] [ERROR-REFERENCE] Id=443949901 Component=
[04/27/2014 07:48:56.0156] [1] Setup is stopping now because of one or more critical errors.
[04/27/2014 07:48:56.0156] [1] Finished executing component tasks.
[04/27/2014 07:48:56.0187] [1] Ending processing Install-ExchangeOrganization
[04/27/2014 07:48:56.0187] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[04/27/2014 07:48:56.0203] [0] End of Setup
[04/27/2014 07:48:56.0203] [0] **********************************************
Im really lost I can not find the entry it is complaining about no matter how hard I look. I really need help I would rather not scrap all my hard work.
Ted

Hi,
Based on my research, we can try to firstly check the otherWellKnownObjects attribute in order to resolve the issue:
1.) Go to Start -> Run -Type LDP.exe -> click OK
2.) Click Connection -> Connect and then click OK
3.) Click Connection -> Bind and then click OK
4.) Click View -> Tree and for the BaseDN select CN=Configuration,DC=DomainName,DC=local and click OK
5.) In the left-pane expand the Configuration partition -> Services -> Microsoft Exchange
6.) Right-click the object Microsoft Exchange and then click Modify
7.) In the Attribute box type otherWellKnownObjects
8.) In the Values box type B:32:9C5B963F67F14A4B936CB8EFB19C4784:CN=ExchangeLegacyInterop\0ADEL:90d1a283-ed42-4ddf-8402- f0dbef0290b2,CN=Deleted Objects,DC=CAO,DC=local (The invalid DN reference you
want to delete)
9.) Select the Delete radio button
10.) Click the Enter button
11.) The Entry List text box will populate with [Delete] and the selected attribute and its value in steps 7 & 8.
12.) Click on the Run button
And here are some references:
http://blogs.technet.com/b/winde76/archive/2012/06/10/prepare-ad-creates-duplicate-security-groups.aspx
http://social.technet.microsoft.com/Forums/exchange/en-US/2fd295db-f84e-4c7b-a1cb-03fa0433d95f/exchange-2010-install-setup-preparead-fail?forum=exchangesvrdeploylegacy
http://social.technet.microsoft.com/Forums/exchange/en-US/7f0f2ea5-73f0-4a61-8f9f-728f11eea98b/exchange-2010-install-fails-preparead
Thanks,
Angela Shi
TechNet Community Support

Exchange 2010 New Address List insufficient access rights

Hi,
I have tried to perform two actions within our new Exchange 2010 system and they fail with the same error.
The first was to convert an existing Address Lists using LDAP to OPATH
I used the following command:
set-addresslist "Exchange 2010 Test" -recipientfilter {(recipienttype -eq "MailUniversalSecurityGroup") -or (recipienttype -eq "MailUniversalDistributionGroup") -and (name -like "exchange2010.*")}
I get the error Access is Denied Active Directory response 00000005: SecErr: DSID-031521D0, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
I also get the same error when I use the Exchange 2010 EMC to try and create a new address list. Note I have no problems managing address lists from Exchange 2003.
I have seen plenty of articles about the making sure that the user performing the action has the "Include inheritable permissions from this objects parent".
I did check my Exchange admin user and this was not ticked. Turns out that because I was also a domain admin so my account was in a protected group (Domain admins) the tick box was continually being removed.
I created a new Exchange user that was in the Exchange Organization Administrators security group, made sure the above box was ticked on the account but this did not fix the problem.
I have however noticed in Adsiedit that the "CN=All Address Lists" container does not have the "Include inheritable permissions from this objects parent" ticked. I suspect that this might be the issue but I don't want to tick it
in case it breaks my address lists.
Should the inherit box be ticked on the "CN=All Address Lists" container?. It is ticked on all the containers under the "CN=All Address Lists" container.
At present the only Exchange permissions on the container are:
Exchange Admins: Full Control
Exchange Domain Servers: Read
Exchange Services: Full Control
I think that crucially the "Exchange Trusted Subsytem" security group is not listed
I have added my new Exchange account with Full control permissions but this has not made a difference
Your hopefully
Matt

Hi Matt,
From your description, I would like to clarify the following things:
1. "Include inheritable permissions from this object's parent" should be checked.
2. "Exchange Trusted Subsystem" should be added to the All Address Lists container.
So you are in the right direction.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2003 and Exchange 2010 Coexistence Activesync Issue

Hello,
I am currently on the progress of migrating mails from Exchange 2003 SP2 to Exchange 2010 SP3. Before I can do actual migration, I need to make sure that OWA and Activesync works when Exchange 2010 becomes Internet facing.
Right now Exchange 2003 is Internet facing while Exchange 2010 is internal LAN only. OWA login from Exchange 2010 to a mailbox in Exchange 2003 works fine. However, trying to open a mailbox in Exchange 2003 from Exchange 2010 Activesync fails.
Activesync login from Exchange 2010 to a mailbox in Exchange 2010 works fine, as well as logging in from Exchange 2003 to mailbox in Exchange 2003.
Tests using AccessMyLAN ActiveSync Tester using Exchange 2010 as entry point are inconclusive. The test shows the app successfully contacting ActiveSync version 6.5 which is Exchange 2003, but results in "Activesync detected, but not correctly configured."
Tests using Test-ActiveSyncConnectivity from Exchange 2010 reveals Error HTTP 400 when contacting Exchange 2003. The cmdlet also shows it successfully contacting Activesync version 6.5 (Exchange 2003).
I have searched around, installed hotfix KB937031, enabled Integrated Windows Authentication on Exchange 2003 Microsoft-Server-Activesync, disabled Require SSL for Microsoft-Server-Activesync and exchange-oma, yet I still can't connect to a mailbox inside
Exchange 2003 through ActiveSync 2010. Website Multiple Identities for port 80 has been set correctly. Exchange 2003 has Forms-Based Authentication Enabled and is the one thing we haven't tried disabling yet.
We want to make sure everything works first, then make Exchange 2010 Internet facing, and finally do the mail migration. We do not want to migrate everyone in a single sitting. Please if anyone have ideas any help is welcomed!

Exchange 2010 will proxy ActiveSync for Exchange 2003. For OWA, it will redirect, so you need a legacy redirect URL. You can test all of this internally without changing your Internet connection. For ActiveSync you can use a WiFi connection.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Out Of Office error ++ Exchange 2010 SP3 just installed sbs2011

Hello
Just recent tried to install sp1 for Exchange 2010, this failed, and ended up in installing SP3, and this went ok.
Ok, by meaning, the installation itself went OK, but the former SP1 isntallation broke a couple of things, and some was adopted to the SP3 isntalaltion.
The main issue now, is that OOF does not work.
Application log:
Event code: 3008
Event message: A configuration error has occurred.
Event time: 20.09.2014 01:20:01
Event time (UTC): 19.09.2014 23:20:01
Event ID: 93ea814206eb4f118aa76ae313723983
Event sequence: 2
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/ROOT-1-130556424012983549
Trust level: Full
Application Virtual Path: /
Application Path: C:\inetpub\wwwroot\
Machine name: SERVER
Process information:
Process ID: 640
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: ConfigurationErrorsException
Exception message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. (C:\Program
Files\Microsoft\Exchange Server\V14\ClientAccess\owa\web.config line 37)
at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
at System.Web.Configuration.RuntimeConfig.GetSectionObject(String sectionName)
at System.Web.Configuration.RuntimeConfig.GetSection(String sectionName, Type type, ResultsIndex index)
at System.Web.Configuration.RuntimeConfig.get_Identity()
at System.Web.HttpContext.SetImpersonationEnabled()
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
Request information:
Request URL: https://localhost:443/Exchange
Request path: /Exchange
User host address: ::1
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 9
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
at System.Web.Configuration.RuntimeConfig.GetSectionObject(String sectionName)
at System.Web.Configuration.RuntimeConfig.GetSection(String sectionName, Type type, ResultsIndex index)
at System.Web.Configuration.RuntimeConfig.get_Identity()
at System.Web.HttpContext.SetImpersonationEnabled()
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
Custom event details:
And if i browse to https://localhost/Exchange on the SBS2011 server i get:
Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.
Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current
web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".

<configuration>
<system.web>
<customErrors mode="RemoteOnly"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<configuration>
<system.web>
<customErrors mode="On" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
Tried a couple of things in IIS, amongst Set Application Pool .NET to 2 from 4
But i am not a IIS guy, so i am out of luck here, and hope some one may help.
Best regards.

Found something, regardig OOF error.
My Autodiscover is configured:
[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl
Identity : SERVER\EWS (Default Web Site)
InternalUrl : https://remote.domain.no/EWS/Exchange.asmx
ExternalUrl : https://remote.domain.no/EWS/Exchange.asmx
And when i test via the Outlook Test E-mail AutoConfiguration it fails:
Autosearch to https://remote.domain.com/Autodiscover/Autodiscover.xml Fails (0x800C8203)

Failure installing SP3 on Exchange 2010

Good evening,
Following TechNet closely I'm currently in the process of moving my exchange 2010 environment to 2013. I have single exchange server on a SBS 2011 box. Sadly I've failed at the first hurdle installing SP3, the result is that my Exchange 2010
is refusing all client connections.
During the SP3 install I passed all prerequisites but during the actual upgrade it failed at the Hub Transport Role with the following error:
Summary: 8 item(s). 3 succeeded, 1 failed.
Elapsed time: 00:20:46
Language Files
Completed
Elapsed Time: 00:10:25
Restoring services
Completed
Elapsed Time: 00:00:02
Languages
Completed
Elapsed Time: 00:03:32
Hub Transport Role
Failed
Error:
The following error was generated when "$error.Clear();
          Write-ExchangeSetupLog -Info "Creating SBS certificate";
          $thumbprint = [Microsoft.Win32.Registry]::GetValue("HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\Networking", "LeafCertThumbPrint", $null);
          if (![System.String]::IsNullOrEmpty($thumbprint))
            Write-ExchangeSetupLog -Info "Enabling certificate with thumbprint: $thumbprint for SMTP service";
            Enable-ExchangeCertificate -Thumbprint $thumbprint -Services SMTP;
            Write-ExchangeSetupLog -Info "Removing default Exchange Certificate";
            Get-ExchangeCertificate | where {$_.FriendlyName.ToString() -eq "Microsoft Exchange"} | Remove-ExchangeCertificate;
            Write-ExchangeSetupLog -Info "Checking if default Exchange Certificate is removed";
            $certs = Get-ExchangeCertificate | where {$_.FriendlyName.ToString() -eq "Microsoft Exchange"};
            if ($certs)
              Write-ExchangeSetupLog -Error "Failed to remove existing exchange certificate"
          else
            Write-ExchangeSetupLog -Warning "Cannot find the SBS certificate";
        " was run: "The certificate with thumbprint 355E62E464DCF42A08BCB7A8CF39C819D42B760E was not found.".
The certificate with thumbprint 355E62E464DCF42A08BCB7A8CF39C819D42B760E was not found.
Click here for help...
http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
Elapsed Time: 00:06:46
Client Access Role
Cancelled
Mailbox Role
Cancelled
Management Tools
Cancelled
Finalizing Setup
Cancelled
The setup log shows the following details:
Ending processing Get-ExchangeCertificate
[07/31/2013 20:50:46.0516] [1] The following 1 error(s) occurred during task execution:
[07/31/2013 20:50:46.0516] [1] 0. ErrorRecord: The certificate with thumbprint 355E62E464DCF42A08BCB7A8CF39C819D42B760E was not found.
[07/31/2013 20:50:46.0516] [1] 0. ErrorRecord: System.InvalidOperationException: The certificate with thumbprint 355E62E464DCF42A08BCB7A8CF39C819D42B760E was not found.
[07/31/2013 20:50:46.0531] [1] [ERROR] The following error was generated when "$error.Clear();
          Write-ExchangeSetupLog -Info "Creating SBS certificate";
          $thumbprint = [Microsoft.Win32.Registry]::GetValue("HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\Networking", "LeafCertThumbPrint", $null);
          if (![System.String]::IsNullOrEmpty($thumbprint))
            Write-ExchangeSetupLog -Info "Enabling certificate with thumbprint: $thumbprint for SMTP service";
            Enable-ExchangeCertificate -Thumbprint $thumbprint -Services SMTP;
            Write-ExchangeSetupLog -Info "Removing default Exchange Certificate";
            Get-ExchangeCertificate | where {$_.FriendlyName.ToString() -eq "Microsoft Exchange"} | Remove-ExchangeCertificate;
            Write-ExchangeSetupLog -Info "Checking if default Exchange Certificate is removed";
            $certs = Get-ExchangeCertificate | where {$_.FriendlyName.ToString() -eq "Microsoft Exchange"};
            if ($certs)
              Write-ExchangeSetupLog -Error "Failed to remove existing exchange certificate"
          else
            Write-ExchangeSetupLog -Warning "Cannot find the SBS certificate";
        " was run: "The certificate with thumbprint 355E62E464DCF42A08BCB7A8CF39C819D42B760E was not found.".
[07/31/2013 20:50:46.0531] [1] [ERROR] The certificate with thumbprint 355E62E464DCF42A08BCB7A8CF39C819D42B760E was not found.
[07/31/2013 20:50:46.0531] [1] [ERROR-REFERENCE] Id=SbsBridgeHeadComponent___6464a0ee0fd04f6b893a3c81d7eb3f26 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup\SBS
[07/31/2013 20:50:46.0531] [1] Setup is stopping now because of one or more critical errors.
[07/31/2013 20:50:46.0531] [1] Finished executing component tasks.
[07/31/2013 20:50:46.0594] [1] Ending processing Install-BridgeheadRole
My application event log is flooded with the following error:
Log Name:      Application
Source:        Microsoft-Windows-IIS-W3SVC-WP
Date:          31/07/2013 21:59:43
Event ID:      2280
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SRV-SBS.lawrencedavid.local
Description:
The Module DLL C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\auth\exppw.dll failed to load. The data is the error.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-IIS-W3SVC-WP" Guid="{670080D9-742A-4187-8D16-41143D1290BD}" EventSourceName="W3SVC-WP" />
    <EventID Qualifiers="49152">2280</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-07-31T20:59:43.000000000Z" />
    <EventRecordID>975085</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>SRV-SBS.lawrencedavid.local</Computer>
    <Security />
</System>
<EventData>
    <Data Name="ModuleDll">C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\auth\exppw.dll</Data>
    <Binary>05000000</Binary>
</EventData>
</Event>
I've tried to re-register exppw.dll following instructions in the TechNet forums but this hasn't helped to restore functionality or complete the SP3 installation. Any guidance would be most appreciated. Thanks in advance!

Hi RicChapman,
From the event log files, I recommend you do as follows to check the result.
1.disabling all the exchange services
2.clearing both the apps and system logs
3.restarting the server
4.reinstall the Exchange 2010 SP3
Here are some case threads for your reference.
exchange 2010 SP2 failed in SBS 2011 Standard Ed
http://social.technet.microsoft.com/Forums/en-US/018bacbd-cbec-4117-82e2-7247eba57099/exchange-2010-sp2-failed-in-sbs-2011-standard-ed
The Module DLL C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\auth\exppw.dll failed to load
http://social.technet.microsoft.com/Forums/exchange/en-US/686d1a90-a016-4a4c-ae2e-6725914a5d5a/the-module-dll-cprogram-filesmicrosoftexchange-serverv14clientaccessowaauthexppwdll-failed
Additional article for your reference.
Exchange Server 2010 is in evaluation mode after installation or repair in SBS 2011 Standard
http://support.microsoft.com/kb/2527626
Hope it helps.
Best regards,
Amy

Exchange 2010 - 2013 Coexistence Issues

I am migrating from Exchange 2010 to Exchange 2013, the Exchange 2013 is built in a different Geo-location site with its dedicated domain controllers in the new site. I have confirmed the mail flow between Exchange 2010 and 2013 mailboxes. I am able to discover
Exchange 2010 servers from 2013 environment via Get-ExchangeServer shell command. However, I am not to discover Exchange 2013 servers from 2010 environment.
I need to configure Outlook Anywhere and Service Connection Point (Autodiscover) on Exchange 2010 to accept connections from Exchange 2013 servers.
Any suggestions would be much appreciated, thanks!

Hi ,
Please have a look in to the below mentioned blog after reading that blog i came to know few things .
I am not sure ,i thought exchange 2013 servers will not be displayed in exchange 2010 management shell.
Better and advisable method is to configure your exchange 2010 and 2013 servers via EAC or Shell in exchange 2013.
http://exchangeserverpro.com/exchange-server-2010-2013-migration-managing-co-existence-environment/
Taken from the above blog :
You can’t use the Exchange 2010 EMC to manage Exchange 2013 objects and servers. While customers upgrade to Exchange 2013, we encourage them to use the EAC to:
Manage Exchange 2013 mailboxes, servers, and corresponding services.
View and update Exchange 2010 mailboxes and properties.
View and update Exchange 2007 mailboxes and properties.
We encourage customers to use Exchange 2010 EMC to create Exchange 2010 mailboxes.
We encourage customers to use Exchange 2007 EMC to create Exchange 2007 mailboxes.
Customers can continue to perform management tasks using the Exchange Management Shell and script tasks.
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2010 EMC Failed Initialization

Similar Messages

Maybe you are looking for