Exchange System Manager Error C0072030
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Missing Server object in System Manger Previous Versions of Exchange > Exchange 2003 and Exchange 2007 - General Discussion Question 0 Sign in to vote I am getting involved in a half completed 2003 to 2010 server migration and ran across an issue that I can not resolve. On the exchange 2003 server, when I go to the system manager and try to browse to the server under Administrative Groups...it is blank and shows an error of "there is no such object on the server" error c0072030. I have looked at ADSIedit and the server in question is still showing up correctly in the configuration/services/microsoft exchange/tab of the domain and from what I can tell, the permissions are set correctly(not 100% sure that they did not delete something). So I am stumped as to what they have done and how I can get it back without too much damage or hassle. Wednesday, April 17, 2013 6:20 PM Reply | Quote Answers 0 Sign in to vote # is the Server Object for "Exchange 2003" server available on the Configuration Partition on the ADSIEDIT? # In case if the objects exists on AD and not shown upon Exchange System Manager then, we can consider this being a permission issue. # in case if the Server Object is not Present under the First Administrative Group-> Servers then it is gone for ever and the only way to get the server back is to restore system state backup. M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This Information is provided is "AS IS" and confers NO Rights!! Marked as answer by Zi FengMicrosoft contingent staff, Moderator Tuesday, May 07, 2013 2:01 AM Wednesday, May 01, 2013 7:20 AM Reply | Quote All replies 0 Sign in to vote Hi I found a thread with the same error，perhaps you can try the solution there http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/25605
religion, or humor, but, well, mostly Exchange. Wednesday, September 14, 2005 Error in Active Directory Users and Computers when updating e-mail addresses In the environment in which http://mostlyexchange.blogspot.com/2005/09/error-in-active-directory-users-and.html I'm currently working, the OU admins in Active Directory have "Exchange View Only Admins" permissions to their respective Exchange admin groups. We have started seeing a problem when modifying e-mail addresses. When an OU-level admin modifies an e-mail address such as an SMTP on the user's E-Mail Addresses property page (using Active Directory Users and Computers), they get exchange system the following error message:Microsoft Active Directory - Exchange ExtensionAn Exchange Server could not be found in the domain.Check if the Microsoft Exchange System Attendant service is running on the Exchange Server.ID no: c10308a2Microsoft Exchange Directory - Exchange ExtensionORThere is no such object on the serverFacility: Win32ID no: c0072030Microsoft Active Directory – Exchange Extension OR (updated on 10 Sept 2006) exchange system manager There are no bindings.Facility: Win32ID no: c00706b6Microsoft Active Directory - Exchange ExtensionI'm not sure why the difference in errors occured, as I have had both reported to me for the same problem, but I suspect it is the difference between the E2K3 and E2K3 SP1 ADUC extension.I did not not realize this, but the ADUC Exchange extension contacts an Exchange server via RPC when you modify an e-mail address. It does this to verify the validity of formatting on the particular type of address you are creating.These problems started once the Exchange 2003 servers were updated to Windows 2003 SP1. Apparently, this has something to do with the services control manager and the DCOM/RPC security hardening that was done in Windows 2003 SP1. Here is a blog entry I read about this: Fun with changing E-Mail AddressesI found very little data on the Internet about this, but I did find one thread that seemed to be relevant: Could NOT change mail address after windows server 2003 sp1This article suggested running a program against the Windows
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 13 Oct 2016 21:48:01 GMT by s_ac5 (squid/3.5.20)