Troubleshooting Event 2080 MSExchange ADAccess

Maybe a bit of a strange one.
We have 1 x Exchange 2010 server and 2 x Domain controllers configured identically (to the best of my knowledge)
When we look in the Application log at the AD Topology, we see the following for the domain controllers
In-site
server1.domain.local CDG177101171
server2.domain.local --G117101171
Out-of-site
<blank>
What could be the reason that there are hyphens where there should be CD on server2.domain.local
According to this article http://howdouc.blogspot.co.uk/2011/01/exchange-active-directory-topology.htmlserver2.domain.local
can not be used as a domain controller for Exchange?
How do we go about fixing the issue?
Thanks in advance

Also I can also telnet to the following ports from the exchange server to Server 2
389/TCP/UDP (LDAP)
3268/TCP (LDAP GC)
88/TCP/UDP (Kerberos)
53/TCP/UDP (DNS)
135/TCP (RPC netlogon)

Similar Messages

Event 2193, MSExchange ADAccess

Hi,
After updating our Exchange 2013 SP1 servers to CU6 we get a lot of these errors in the Application log on them. All our DCs except two that is on the same site as the Exchange servers, is in the error messages. It is a bit random in time but each
DC gives an error about every 25 minutes on both Exchange servers. Any idea?
Event Id: 2193
Source: MSExchange ADAccess
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=3576). Suitability check failed for server xxxxxx.domain.local with an exception. Error: System.InvalidOperationException: GetDomainControllerInfo() called on an invalid handle.
at Microsoft.Exchange.Win32.SafeDomainControllerInfoHandle.GetDomainControllerInfo()
at Microsoft.Exchange.Data.Directory.TopologyDiscovery.SuitabilityVerifier.CheckNetLogon(SuitabilityCheckContext context) (in CheckNetLogon).

Hi,
From your description, I recommend you use the Dcdiag to check your DC health at first and verify if there is any issue with the DCs.
Here is an article about Dcdiag for your reference.
Dcdiag
http://technet.microsoft.com/en-us/library/cc731968.aspx
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

MSExchange ADAccess 2080

Hi All,
We have two Exchange 2013 servers set up in DAG with 2 DC's running in a single site. We had to reboot DC1 and before it came backup MAIL1 then crashed and rebooted.
Checking out the logs before the crash I can see that when DC1 was rebooted MAIL1 was unable to locate another DC in the site, even though there are two.
Checking the MSExchange ADAccess errors when DC1 was back online, MAIL1 is only reporting the following:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=64668). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
DC1.domain.com CDG 1 7 7 1 0 1 1 7 1
Where as MAIL2 remained online and reports:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=164764). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
DC1.domain.com CDG 1 7 7 1 0 1 1 7 1
DC2.domain.com CDG 1 7 7 1 0 1 1 7 1
All services etc failed over using DAG when MAIL1 went offline so this side isn't an issue but i'm trying to locate why MAIL1 is only reporting seeing DC1 and not DC2.
Thanks.

Hi,
I agree with Nagendra, you should run dcdiag on DC2 and check the result.
Beside run dcdiag , I also recommend you check the DNS SRV record, or try to reboot dc2 and check if ok.
Thanks.
Niko Cheng
TechNet Community Support

Installing Exchange 2013 SP1 - Errors MSExchange ADAccess & MSExchange Common

The topology first:
AD-server + Exchange-server
What I am trying to do is just install a full version of Exchange 2013 sp1.
But the problem is that install wizard freezes on the "initializing setup" page. Also eventviewer gives 2 different error messages, MSExchange ADAccess & MSExchange Common.
MSExchange ADAccess:
The description for Event ID 4027 from source MSExchange ADAccess 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:
ExSetup.exe
2964
Get Servers for mydomain.com
TopologyClientTcpEndpoint (localhost)
3
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:01.9984949. TCP error code 10061: No connection could be made because
the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.ICommunicationObject.Open()
   at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
   at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
the message resource is present but the message is not found in the string/message table
MSExchange Common:
The description for Event ID 106 from source MSExchange Common 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:
2
Time in Resource per second
MSExchange Activity Context Resources
The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.get_RawValue()
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()
Last worker process info : Last worker process info not available!
Processes running while Performance counter failed to update:
1044 VSSVC
1064 spoolsv
4032 notepad
1416 svchost
700 dwm
3100 SMSvcHost
3616 msdtc
2564 csrss
336 csrss
424 winlogon
244 smss
688 LogonUI
2556 Taskmgr
596 svchost
1124 inetinfo
1920 svchost
1652 SMSvcHost
1400 svchost
2916 taskhostex
492 lsass
2688 dwm
396 wininit
484 services
1104 svchost
388 csrss
384 svchost
1896 svchost
3052 svchost
744 svchost
1180 mmc
3404 conhost
1800 explorer
3668 Setup
552 svchost
712 svchost
2864 svchost
2964 ExSetup
2948 rdpclip
2592 winlogon
900 svchost
808 svchost
4 System
1164 mqsvc
0 Idle
Performance Counters Layout information: FileMappingNotFoundException for category MSExchange Activity Context Resources : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange
activity context resources. Error Details: 2
   at Microsoft.Exchange.Diagnostics.FileMapping..ctor(String name, Boolean writable)
   at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
the message resource is present but the message is not found in the string/message table

I solved this problem or at least managed to get a workaround for it.
I tried to install Exchange using rdp connection and the installation media was mapped on my local computer. After I copied it to server itself, everything started to work and now I am able to send emails.

Every morning receive Event Source MSExchange Common ID 4999

Every morning at 2/2/2012 2:06:02 AM
for weeks now we receive Event Source MSExchange Common ID
SBS 2011
Standard – Exchange 2010 => build 14.01.0355.002 (Update Rollup 6 for Exchange Server 2010 SP1)
Event Details:
Watson report about to be sent for process id: 12000, with parameters: E12, c-buddy-RTL-AMD64, 14.01.0355.001, BPA, M.E.Data.Directory, M.E.D.D.DSAccessTopologyProvider..ctor, S.IO.FileLoadException, 72f, 14.01.0355.001. ErrorReportingEnabled:
False
This is an Intel machine so we are not sure why there is “AMD64” in the details - This Event does not seem to cause any problem that we can detect.
Anyone tried
- Exchange Server 2010 SP2 December 4, 2011 Build 14.2.247.6 on a SBS2011 Standard yet? -
Since one of the KB articles – I found says -
Maybe -
http://support.microsoft.com/kb/2447629 (Rollup 3 but we have 6)

Hi,
It seems that the issue is related to the special characters in the database name cause an
IndexOutOfRangeException exception. This exception crashes the
MSExchangeServicesAppPool application pool.
For more detailed information, you could refer to the article below:
Title: Event ID 4999 is logged on an Exchange Server 2010 Client Access server (CAS)
URL:
http://support.microsoft.com/kb/2665115
From the KB article resolution, you need to obtain Interim Update (IU) by contacting Microsoft Customer Service and Support.
Regards,
James
James Xiong
TechNet Community Support

2601, 2604, and 2501 MSExchange ADAccess Event IDs when a Microsoft Exchange server restarts

I traced the problem to my Failover Cluster Manager. The cluster was Offline and the IP for the DAG was not available.
Under Cluster Core Resources, the cluster was shown to Offline.
Right-click and select Bring this resource Online.
WC

Sorry, what's the question here? There could be multiple connectivity reasons behind and it seems in your case it was cluster resource...
ransient DNS failures
Transient issues with Domain Controllers
Transient network connectivity issues
Network switches that have the PortFast functionality disabled on the ports to which the Exchange servers connect
Reference : http://support.microsoft.com/kb/2025528
Blog |
Get Your Exchange Powershell Tip of the Day from here

Event 4999, MSExchange Common

Hi All,
I am running Ms Exchange 2010 with SP1 in Windows Server 2008 R2 SP1 x64.
One host with role CAS+HT and another host with role Mailbox.
Everyday i see many Event 4999 in the log and I am afraid something might not been configured properly though there are no issue when operational.
Below is the details :
Watson report about to be sent for process id: 3880, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, M.Exchange.Imap4, M.Exchange.Diagnostics, M.E.D.ExEventLog.LogEvent, System.ArgumentException, ea87, 14.01.0218.011.
I've search across the forum but there were no similar error messages for what i have.
Anybody got a hint what this error is about ?
Thanks.

Hi,
We can see in the error you posted that you are running Exchange 2010 SP1 (14.01.0218.011=SP1).
SP1 hasn't been supported since 1/8/2013 and you really should bring your server up to a supported level (read SP3).
See:
Exchange 2010 Lifecycle
Can't say for sure if that will fix the error you are seeing, but over the years (and rollups) there have been many fixes related to Event 4999
Microsoft Exchange Server 2010 Service Pack 3 (SP3)
http://www.microsoft.com/en-us/download/details.aspx?id=36768
Update Rollup 7 for Exchange Server 2010 Service Pack 3
http://support.microsoft.com/kb/2961522
Post back if you still see the error after patching your server(s)
Martina Miskovic

Event Log Trigger on New-Mailbox Event in MSExchange Management Event Log and Email in HTML Format

I created a custom event view and created "Attach Task to this custom view" task scheduler job based on the custom view. Whenever a new user is created a receive the email however, the body of the email is blank. I'd like to pass the event detail
into the body of the email as HTML. Any assistance on how to create a script to accomplish is much appreciated.

Did you find an answer to this question yet?
¯\_(ツ)_/¯

Issues After Disabling IPv6 on Your NIC on SBS 2008

If you uncheck the IPv6 protocol from your network interface card on your Windows SBS 2008 server you may see the following issues after a reboot:
Microsoft Exchange services fail to start
Server hangs at “Applying Computer Settings…” (can eventually logon after 30 – 60 minutes)
Network icons show as offline
Some or all of the following events
Application Log Events
Source: MSExchange ADAccess
Event ID: 2114
Task Category: Topology
Level: Error
Description:
Process MAD.EXE (PID=2088). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185,
“Microsoft LDAP Error Codes.” Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
Source: MSExchange ADAccess
Event ID: 2601
Task Category: General
Level: Warning
Description:
Process MSEXCHANGEADTOPOLOGY (PID=952). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,…>
– Error code=80040a01.
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
Source: MSExchange ADAccess
Event ID: 2102
Task Category: Topology
Level: Error
Description:
Process MAD.EXE (PID=2088). All Domain Controller Servers in use are not responding: SBS.sbs2008.local
Source: MSExchange ADAccess
Event ID: 2105
Task Category: Topology
Level: Warning
Description:
Process MAD.EXE (PID=2088). Exchange Active Directory Provider failed to obtain DNS records for domain sbs2008.local. DNS Priority and Weight for the Domain Controllers in this domain will be set to the default values 0 (priority) and 100 (weight).
Source: MSExchange ADAccess
Event ID: 2114
Task Category: Topology
Level: Error
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=952). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge
Base article 218185, “Microsoft LDAP Error Codes.” Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
Source: MSExchangeFBPublish
Event ID: 8197
Task Category: General
Level: Error
Description:
Error initializing session for virtual machine SBS. The error number is 0x80040a01. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.
Source: MSExchangeTransportLogSearch
Event ID: 7005
Task Category: General
Level: Error
Description:
Microsoft Exchange couldn’t read the configuration from the Active Directory directory service because of error: Failed to load config due to exception: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Exchange Topology service on server
localhost did not return a suitable domain controller.
System Log Events
Source: Service Control Manager
Event ID: 7044
Task Category: None
Level: Warning
Description:
The following service is taking more than 16 minutes to start and may have stopped responding: Microsoft Exchange System Attendant
Source: Service Control Manager
Event ID: 7022
Task Category: None
Level: Error
Description:
The Microsoft Exchange Transport service hung on starting.
Source: Service Control Manager
Event ID: 7024
Task Category: None
Level: Error
Description:
The Microsoft Exchange Information Store service terminated with service-specific error 0 (0×0).

Hi,
Based on your description, it seems to be the same as the following blog.
Issues
After Disabling IPv6 on Your NIC on SBS 2008
Did you mean that encounter the same issue? If so, there is a resolution in that blog, please check if can
help you solve the issue.
If any other issue exists or any update, please don’t hesitate to let me know and provide more details. It
will help me understand clearly.
Best regards,
Justin Gu

Exchange 2013 Information Store Service not starting

This is the event viewer error: Event 4027 Msexchange AdAccess.
This is the description in spanish of the event:
Proceso w3wp.exe (PID= 2788). Error en la solicitud WCF (Get Servers for xxxxx) al servicio de topología de Active Directory de Microsoft Exchange en el servidor (TopologyClientTcpEndpoint (localhost))

Hello. We rebooted our Exchange 2013 Server and now Information Store Service is not starting among other main services.
When I try to start manually the service it turns an error 2414. I found out in some pages that enabling IPv6 should make it work but in my case it doesn't.
Any idea?
This topic first appeared in the Spiceworks Community

MSExchange Mid-Tier Storage, Event id 10100 and 6002

I have installed Exchange 2013 standard version in clean single domain structure with two Windows 2012 domain controllers and about 60 users that all have mailbox on the Exchange server.
I’m getting MSExchange Mid-Tier Storage warning in event viewer 20 to 30 times a day.
It’s event id 10100 and 6002, mostly 10100.
Everything seems to be working but I want to get rid of this warning.
Detailed.
Log Name:      Application
Source:
MSExchange Mid-Tier Storage
Date:
4.2.2013 02:23:32
Event ID:      10010
Task Category: ResourceHealth
Level:
Warning
Keywords:      Classic
User:
N/A
Computer:      somecomputer.somedomain.com
Description:
Process: MSExchangeDelivery (1624), Db:ca5fd10f-3da0-4d83-96f3-a18387b678de,C:2,BT:00:00:00,
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchange Mid-Tier Storage" />
    <EventID Qualifiers="32768">10010</EventID>
    <Level>3</Level>
    <Task>6</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-02-04T02:23:32.000000000Z" />
    <EventRecordID>224585</EventRecordID>
    <Channel>Application</Channel>
    <Computer>somecompter.somedomain.com</Computer>
    <Security />
</System>
<EventData>
    <Data>Process: MSExchangeDelivery (1624), Db:ca5fd10f-3da0-4d83-96f3-a18387b678de,C:2,BT:00:00:00,</Data>
</EventData>
</Event>

I still have these warnings. I did not create any extra connectors
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 16:04:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 15:57:24
ITSPECSRV
3028
Waarschuwing
MSExchangeApplicationLogic
Application
16-7-2013 15:34:56
ITSPECSRV
3028
Waarschuwing
MSExchangeApplicationLogic
Application
16-7-2013 15:34:56
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 15:34:43
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 15:32:30
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 15:04:44
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 14:53:52
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 14:37:34
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 14:34:39
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 14:09:10
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 13:39:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 13:19:44
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 13:17:21
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 12:54:51
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 12:44:44
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 12:29:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 12:23:51
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 12:04:43
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 12:03:50
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 11:38:50
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 11:34:44
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 11:19:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 11:16:49
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 10:54:43
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 10:41:49
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 10:14:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 10:06:49
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 9:59:40
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 9:47:18
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 9:39:42
ITSPECSRV
3028
Waarschuwing
MSExchangeApplicationLogic
Application
16-7-2013 9:34:57
ITSPECSRV
3028
Waarschuwing
MSExchangeApplicationLogic
Application
16-7-2013 9:34:57
ITSPECSRV
3028
Waarschuwing
MSExchangeApplicationLogic
Application
16-7-2013 9:34:57
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 9:08:47
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 9:04:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 8:44:39
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 8:17:17
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 7:58:46
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 7:54:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 7:39:47
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 7:19:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 7:08:51
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 6:59:44
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 6:09:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 5:57:14
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 5:54:40
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 5:34:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 5:23:44
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 4:49:41
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 4:48:43
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 4:14:44
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 4:09:18
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 3:49:41
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 3:43:42
ITSPECSRV
3028
Waarschuwing
MSExchangeApplicationLogic
Application
16-7-2013 3:34:58
ITSPECSRV
3028
Waarschuwing
MSExchangeApplicationLogic
Application
16-7-2013 3:34:58
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 3:29:43
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 3:28:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 3:04:45
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:54:36
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 2:53:42
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:53:36
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:52:18
ITSPECSRV
7032
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 2:48:55
ITSPECSRV
7031
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 2:48:34
ITSPECSRV
5011
Waarschuwing
Microsoft-Windows-WAS
System
16-7-2013 2:47:59
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:47:49
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:46:49
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:45:48
ITSPECSRV
2003
Fout
Microsoft-Windows-IIS-W3SVC-PerfCounters
Application
16-7-2013 2:45:11
ITSPECSRV
2001
Fout
Microsoft-Windows-IIS-W3SVC-PerfCounters
Application
16-7-2013 2:44:57
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:44:48
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:43:48
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:42:48
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:41:19
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:39:48
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 2:39:44
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:38:48
ITSPECSRV
4109
Fout
MSExchange ADAccess
Application
16-7-2013 2:37:43
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 2:37:30
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:36:48
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:35:48
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:34:48
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:33:48
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:32:48
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:31:15
ITSPECSRV
5011
Waarschuwing
Microsoft-Windows-WAS
System
16-7-2013 2:26:59
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 2:18:49
ITSPECSRV
4109
Fout
MSExchange ADAccess
Application
16-7-2013 2:03:48
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 2:03:44
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:03:08
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:02:08
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 2:00:22
ITSPECSRV
7032
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:57:12
ITSPECSRV
7031
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:57:03
ITSPECSRV
5011
Waarschuwing
Microsoft-Windows-WAS
System
16-7-2013 1:56:16
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 1:55:21
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 1:48:16
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 1:46:46
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 1:45:27
ITSPECSRV
7032
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:42:13
ITSPECSRV
7031
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:42:04
ITSPECSRV
5011
Waarschuwing
Microsoft-Windows-WAS
System
16-7-2013 1:41:15
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 1:40:56
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 1:34:45
ITSPECSRV
4109
Fout
MSExchange ADAccess
Application
16-7-2013 1:33:13
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 1:32:25
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 1:31:24
ITSPECSRV
7009
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:30:44
ITSPECSRV
7000
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:30:44
ITSPECSRV
1309
Waarschuwing
ASP.NET 4.0.30319.0
Application
16-7-2013 1:30:21
ITSPECSRV
7009
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:29:55
ITSPECSRV
7000
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:29:55
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 1:28:21
ITSPECSRV
7009
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:27:50
ITSPECSRV
7000
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:27:50
ITSPECSRV
7009
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:27:20
ITSPECSRV
7000
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:27:20
ITSPECSRV
7031
Fout
Microsoft-Windows-Service Control Manager
System
16-7-2013 1:26:50
ITSPECSRV
5011
Waarschuwing
Microsoft-Windows-WAS
System
16-7-2013 1:26:00
ITSPECSRV
906
Waarschuwing
ESE
Application
16-7-2013 1:21:28
ITSPECSRV
906
Waarschuwing
ESE
Application
16-7-2013 1:13:53
ITSPECSRV
906
Waarschuwing
ESE
Application
16-7-2013 1:10:20
ITSPECSRV
9042
Waarschuwing
MSExchange Assistants
Application
16-7-2013 0:59:45
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 0:44:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 0:42:07
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 0:23:20
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
16-7-2013 0:09:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 23:57:07
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 23:38:25
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 23:19:40
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 23:17:18
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 22:54:17
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 22:13:11
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 21:52:23
ITSPECSRV
3028
Waarschuwing
MSExchangeApplicationLogic
Application
15-7-2013 21:34:58
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 21:16:16
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 20:59:41
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 20:42:04
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 20:39:43
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 20:14:44
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 19:44:45
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 19:43:08
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 19:19:41
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 19:17:14
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 18:59:44
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 18:49:14
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 18:44:42
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 18:19:43
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 18:08:07
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 17:59:41
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 17:47:00
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 17:29:41
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 17:09:43
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 16:44:45
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 16:29:13
ITSPECSRV
6002
Waarschuwing
MSExchange Mid-Tier Storage
Application
15-7-2013 16:19:46
Leo

Exchange 2007 OWA Error after installing Service Pack 3 (MSExchange OWA event 65)

Hi everyone, I have multiple servers in Exchange 2007 SP1, Windows Server 2003 SP2 64bit.
I installed SP3 and RU15 a CAS / HUB server and now I access OWA, showing the below error:
Outlook Web Access did not initialize. There has been an event for the system administrator can resolve the problem. Contact the support of the organization.
Object reference not set to an instance of an object.
Request
URL: https: // mailserver01: 443 / owa / auth / error.aspx url = https: // mailserver01 / owa / & reason = 0
Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: Object reference not set to an instance of an object.
Call stack
in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager () in Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication () in Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart (Object sender,
EventArgs e)
Inner Exception
Exception type: System.NullReferenceException
Exception message: Object reference not set to an instance of an object.
Call stack
in Microsoft.Exchange.Clients.Owa.Core.Configuration.CheckPublicFolders (ADSystemConfigurationSession session, ADObjectID [] pfdbIds, Boolean & allLegacy, Boolean & allLater) in Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor (ADSystemConfigurationSession
session, String virtualDirectory , String WebSiteName, ADObjectID distinguishedName, Boolean isPhoneticSupportEnabled) in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration () in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager
In server events next event is logged
Event Type: Error
Event Source: MSExchange OWA
Event Category: ADNotifications
Event ID:. 65
Date: 12/27/2014
Time: 7:20:54
User: Not available
Team: mailserver01
Description:
There was an error loading the configuration parameters of Outlook Web Access. Virtual directory "owa". Website: "Default Web Site".
Error message:
"Object reference not set to an instance of an object."
HOW CAN I SOLVE THIS?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hello
everyone,
thank you
for
answering,
finally
opened
with
Microsoft
support
case
and
showed
me
that
delete
servers
from
ADSEDIT.
I deleted
the
servers
that
should
not
be
and
immediately
everything
started
to
work
properly
Many
thanks to
all
for
the
help
Microsoft Certified IT Professional Server Administrator

Event ID 2142, 2077, 2069 MSExchangeADTopology Exchange 2013

Hello,
I have just inherited a slightly abused new server as part of my job and it looks like the previous admin was using a live single domain as a test bed.
From what I have been able to determine this windows 2008R2 server started life as a single name domain (no FQDN) that had exchange 2013 running on it (sin I know). A domain rename was performed and from what I can tell it did change the domain name to
a FQDN environment. (it went for COMPANY to COMPANY.COM)
I have been able to clean up most of the other ghosts in the machine except when it comes to exchange. I get event ID 2142(error), 2077 (info), and 2069 (info) repeatedly it cycles every 2 minutes:
Log Name: Application
Source: MSExchangeADTopology
Date: 4/18/2013 11:42:39 AM
Event ID: 2142
Task Category: Topology
Level: Error
Keywords: Classic
User: N/A
Computer: SERVER2013.COMPANY
Description:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=13460) Forest COMPANY.com. Topology discovery failed, error details
No Suitable Directory Servers Found in Forest COMPANY.com Site Default-First-Site-Name..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeADTopology" />
<EventID Qualifiers="49156">2142</EventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-18T16:42:39.000000000Z" />
<EventRecordID>4918254</EventRecordID>
<Channel>Application</Channel>
<Computer>SERVER2013.COMPANY</Computer>
<Security />
</System>
<EventData>
<Data>Microsoft.Exchange.Directory.TopologyService.exe</Data>
<Data>13460</Data>
<Data>COMPANY.com</Data>
<Data>No Suitable Directory Servers Found in Forest COMPANY.com Site Default-First-Site-Name.</Data>
</EventData>
</Event>
Log Name:      Application
Source:        MSExchangeADTopology
Date:          4/18/2013 11:42:39 AM
Event ID:      2077
Task Category: Topology
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      SERVER2013.COMPANY
Description:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=13460) Forest COMPANY.com. Exchange Active Directory Provider could not find any suitable domain controller servers in either the local site 'Default-First-Site-Name' or the following sites:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeADTopology" />
    <EventID Qualifiers="16388">2077</EventID>
    <Level>4</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-04-18T16:42:39.000000000Z" />
    <EventRecordID>4938976</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER2013.COMPANY</Computer>
    <Security />
</System>
<EventData>
    <Data>Microsoft.Exchange.Directory.TopologyService.exe</Data>
    <Data>13460</Data>
    <Data>COMPANY.com</Data>
    <Data>Default-First-Site-Name</Data>
    <Data>
    </Data>
</EventData>
</Event>
Log Name:      Application
Source:        MSExchangeADTopology
Date:          4/18/2013 11:42:39 AM
Event ID:      2069
Task Category: Topology
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      SERVER2013.COMPANY
Description:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=13460) Forest COMPANY.com. Exchange Active Directory Provider couldn't find any suitable Global Catalog servers in either the local site 'Default-First-Site-Name' or the following sites:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeADTopology" />
    <EventID Qualifiers="16388">2069</EventID>
    <Level>4</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-04-18T16:42:39.000000000Z" />
    <EventRecordID>4938977</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER2013.COMPANY</Computer>
    <Security />
</System>
<EventData>
    <Data>Microsoft.Exchange.Directory.TopologyService.exe</Data>
    <Data>13460</Data>
    <Data>COMPANY.com</Data>
    <Data>Default-First-Site-Name</Data>
    <Data>
    </Data>
</EventData>
</Event>
It looks to me that exchange is still looking for the old domain name. Does anyone know how to point it to the correct domain name?
Exchange is currently down and I am unable to log into EAC, OWA or Exchange Management Powershell. I am also unable to un-install exchange as it is reporting active mailboxes and I can't delete them because I am unable to log in.
My overall goal is to remove exchange from this server and put it on a separate server but until I can get exchange working to a point where I can remove the mailboxes, I am stuck.
Any and all help appreciated.
Hummedan

Thank you for your advise on correcting my issue. I created the subnet and assigned it to the Default-First-Site-Name as there weren't any subnets listed.
Upon reboot I checked the event log and I am still receiving the event log entries as above; however, I am now receiving a few new errors along with them and they are repeating (4027 error and 3176 action). Here are the additional errors:
Log Name:      Application
Source:        MSExchange ADAccess
Date:          4/22/2013 9:52:48 AM
Event ID:      4027
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER2013.COMPANY
Description:
Process msexchangerepl.exe (PID=8016). WCF request (Get Servers for COMPANY.com) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure
that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details
An error occurred during forest discovery (COMPANY.com). ----> No Suitable Directory Servers Found in Forest COMPANY.com Site Default-First-Site-Name.
   at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.Discover()
   at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.DoWork(CancellationToken cancellationToken)
   at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.Execute(CancellationToken joinedToken)
   at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.<>c__DisplayClass6.<StartExecuting>b__4()
   at System.Threading.Tasks.Task.Execute()
   at Microsoft.Exchange.Directory.TopologyService.Common.Extensions.WrapAndRethrowException(Exception exception, LocalizedString errorMessage)
   at Microsoft.Exchange.Directory.TopologyService.TopologyDiscoveryManager.EndGetTopology(IAsyncResult ar)
   at Microsoft.Exchange.Directory.TopologyService.TopologyService.InternalEndGetServersForRole(IAsyncResult result)
   at Microsoft.Exchange.Directory.TopologyService.TopologyService.<>c__DisplayClassa.<EndGetServersForRole>b__9()
   at Microsoft.Exchange.Directory.TopologyService.TopologyService.ExecuteServiceCall(Action action)
Log Name:      Application
Source:        MSExchangeRepl
Date:          4/22/2013 9:52:48 AM
Event ID:      3176
Task Category: Action
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER2013.COMPANY
Description:
The Microsoft Exchange Replication service attempted to start the Active Manager RPC server but failed because an error occurred when attempting to read the Exchange Servers universal security group SID from Active Directory. Error:
The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details An error occurred during forest discovery (COMPANY.com)..
Log Name:      Application
Source:        MSExchange ADAccess
Date:          4/22/2013 9:52:48 AM
Event ID:      4027
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER2013.COMPANY
Description:
Process MSExchangeSubmission.exe (PID=10708). WCF request (Get Servers for COMPANY.com) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition,
make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details
An error occurred during forest discovery (COMPANY.com). ----> No Suitable Directory Servers Found in Forest COMPANY.com Site Default-First-Site-Name.
   at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.Discover()
   at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.DoWork(CancellationToken cancellationToken)
   at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.Execute(CancellationToken joinedToken)
   at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.<>c__DisplayClass6.<StartExecuting>b__4()
   at System.Threading.Tasks.Task.Execute()
   at Microsoft.Exchange.Directory.TopologyService.Common.Extensions.WrapAndRethrowException(Exception exception, LocalizedString errorMessage)
   at Microsoft.Exchange.Directory.TopologyService.TopologyDiscoveryManager.EndGetTopology(IAsyncResult ar)
   at Microsoft.Exchange.Directory.TopologyService.TopologyService.InternalEndGetServersForRole(IAsyncResult result)
   at Microsoft.Exchange.Directory.TopologyService.TopologyService.<>c__DisplayClassa.<EndGetServersForRole>b__9()
   at Microsoft.Exchange.Directory.TopologyService.TopologyService.ExecuteServiceCall(Action action)

Exchange 2010 - Event ID 2107 Warning

We have a multi-forest environment configured with a forest to forest selective authentication trust with two separate Exchange Orgs. One of our HT Servers is generating Event ID: 2107 with Source: MSExchange ADAccess and Task Category:
Topology. It states:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1272). Exchange Active Directory Provider failed to obtain an IP address for DS server <Server name>, error 11004 (WSANO_DATA (The requested name is valid and was found in the database, but it does not have
the correct associated data being resolved for.)). This host will not be used as a DS server by Exchange Active Directory Provider.
The DC listed in the error is in a different forest from the HT server reporting the error.
Why would it be trying to populate this DC in its listing for Directory access? The error has ceased, there are no connectivity issues, but I'm just curious what is going on here.
The only interaction going on between these to Orgs is Availability service communication. Not sure if this is the reason for this.
Any insight, would be greatly appreciated.
Thanks!

Hi,
Based on my research, This Error event indicates that Active Directory Provider did not obtain an IP address for an Active Directory server. This host will not be used as an Active Directory server by DSAccess. This could be caused by network problems. This
is a critical error if there are no other domain controllers available for load balance:
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=2107&EvtSrc=MSExchange+ADAccess
For the error code, except with the resolutions in the above article, we can also use network monitor to find the root cause.
According to your description, you are doubting why the server listed is the DC in another forest.
And I’d like to confirm the following information:
1. Do you install your Exchange server on DC?
2. Is the DC global controller?
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

ADAccess validation errors

Hi
We recently migrated from Exchange 2003 to 2010 and we are getting repeated errors in the event log from MSExchange ADAccess. They come in pairs (I think because I set logging to expert) of the form:
Process Microsoft.Exchange.AddressBook.Service.exe (PID=20860). Object CN={security group},OU=Security Groups,OU=MyBusiness,DC={domain},DC=local read from server1.{domain}.local failed validation. Attribute: ExchangeLegacyDN. Error message: You must provide
a value for this property.. Invalid data: .
Process Microsoft.Exchange.AddressBook.Service.exe (PID=20860). Recipient object CN={security group},OU=Security Groups,OU=MyBusiness,DC={domain},DC=local read from server1.{domain}.local failed validation. A partially valid object will be returned.
Set event logging level for Validation category to Expert to get additional events about each failure.
(I have removed the names of the domain and groups).
All the errors correspond to security groups. These groups were accidently given email addresses during the migration but I have removed all Exchange attributes from them now. I think the ExchangeLegacyDN attribute in the error is a typo which should read
LegacyExchangeDN, as all the groups have this value but it is <Not Set>.
These errors only started appearing after I installed Blackberry Server Express on the new Exchange server. A load of them will appear together in the application log and I think they correspond to the group membership of a Blackberry enabled user.
Any ideas?
Oli

Symptom: Warning 2158 and 2161 appear repeatedly for the objects that have already
mail-disabled, and the legacyDN is null
Cause: This can happen after you've mail-disabled the object but there're still references
to it in other AD objects
Resolution: The issue will be fixed in the later service pack
James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact [email protected]

Troubleshooting Event 2080 MSExchange ADAccess

Similar Messages

Maybe you are looking for