Interface Error 0x6d9
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Online 2010 Other Versions Library Forums Gallery We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Exchange Server 2007 Troubleshooting Outlook Web Access Issues Outlook Web Access Issues Users Receive an Error Message When They Try To Log On to Outlook Web Access Through the Client Access Server Role in Exchange 2007 Users Receive an Error Message When They Try To Log On to Outlook Web Access Through the Client Access Server Role in Exchange 2007 Users Receive an Error Message When They Try To Log On to Outlook Web Access Through the Client Access Server Role in Exchange 2007 32-Bit ASP.NET on a 64-Bit System Causes Outlook Web Access to Fail Exchange Server 2007 OWA URL Redirection Does Not Work HTTP 400 Bad Request Error When You Access an Exchange 2007 Mailbox Outlook Web Access Did Not Initialize and Event ID 64 is Logged in the Application Log on the Client Access Server Outlook Web Access Returns an Unexpected Response Proxying to a Client Access Server Fails After RedirectToOptimalOWAServer Is Set to False Users Cannot Access the Global Address List in Outlook Web Access Users Cannot Log On to
FORUM, Actually I practice in Exchange2007 by useing VMWare Workstaiton. First I installed Windows Server2003, then MSExchange2007. every thing was good. when I tried to acsess https://localhost/owa. I got this message Outlook Web Access did not initialize. An https://technet.microsoft.com/en-us/library/dd577063(v=exchg.80).aspx event has been logged so that the system administrator can resolve the issue. Please contact technical support for your organization. Exchange Active Directory Topology Service on server localhost cannot be contacted via RPC interface. Error 0x6D9. with these http://forums.msexchange.org/m_1800517879/printable.htm Details Request Url: https://localhost:443/owa/auth/error.aspx?replaceCurrent=1&url=https%3a%2f%2flocalhost%2fowa User host address: 127.0.0.1 Exception Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException Exception message: Exchange Active Directory Topology Service on server localhost cannot be contacted via RPC interface. Error 0x6D9. Call stack Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager() Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication() Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart(Object sender, EventArgs e) Inner Exception Exception type: Microsoft.Exchange.Data.Directory.ADTransientException Exception message: Exchange Active Directory Topology Service on server localhost cannot be contacted via RPC interface. Error 0x6D9. Call stack Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetServersForRole(String[] currentlyUsedServers, ADServerRole role, Int32 serversRequested, Int32[]& mapping) Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetConfigDCInfo(Boolean throwOnFailure) Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetConfigDCInfo() Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateConfigNamingContexts() Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId) Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator, CreateObjectsDelegate arrayCreator) Microsoft.Exchange.Data.Directory.ADSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxRes
DC who are also both global catalog and dns servers. When i shut down the dc1 and then reboot exchange, the exchange server http://www.networksteve.com/exchange/topic.php/exchange_2007_does_not_use_second_Domain_Controller/?TopicId=13337&Posts=6 stops at "applaying computer settings" When i then restart dc1 10 seconds https://www.petri.com/forums/forum/server-operating-systems/sbs-2000-2003-2008-2011/67411-sbs-2008-disable-exchange-errors after i can login at dc1 the exchange server is also ready for login. The exchange server does not use dc2 and i found several information in the eventlog. dc1 CDG 1 7 7 1 0 1 1 7 1 dc2 - - G 1 1 7 1 0 interface error 0 1 7 1 Roles: The second column shows whether or not the particular server can be used as a configuration domain controller (column value C), a domain controller (column value D), or a global catalog server (column value G) for this particular Exchange server --------> why can dc2 not be used as D---->domain controller? dc2 IS a Domain Controller with interface error 0x6d9 G--->global catalog. I also tried to fix the SACL right column but i dont know why it does not work. I edited on dc2 the security, added exchange server to security and allowed the "READ NTSECURITY DESCRIPTOR" with ADSIedit on dc2. What is the feature "C"-->configuration domain controller---> I read in an other forum that it is not necessary to configure a special configuration domain controller on exchange, exchange would find the config DC by itself. A few weeks ago i tried to fix that problem with "configuration domain controller" entry and i set it to NULL but that did not work so i set it back again to ntsrik03. **************************************************************************************************************************************** Exchange Config setings get with "get-exchangeServer -status | fl on the exchangeserver Name : NTSRIK09 DataPath : C:\Program Files\Microsoft\Exchange Server\ Mailbox Domain : company.net Edition : Standard ExchangeLegacyDN : /o=company/ou=Exchange Administrative Gro up (FYDIBOHF23SPDLT)/cn=Configuration/cn=Se rvers/cn=NTSRIK09 Fqdn : ntsrik09.company.net IsHubTransportServer : True IsClientAccessServer : True IsExchange2007OrLater : True IsEdgeServer : False IsMailboxServer : True IsMemberOfCluster : No IsProvisionedServer : False IsUnifiedMessagingServer : False NetworkAddress : {ncacn_vns_spp:NTSRIK09, netbios:NTSRIK09, ncacn_np:NTSRIK09, ncacn_spx:NTSRIK09, ncac n_ip_tcp:ntsrik09.company.net,