There are
several reasons it may not be active:
The Microsoft Exchange Transport Service is not running
MAPI RPC is blocked between the mailbox and the Hub
The Hub Transport server has exhausted its submission threads.
For example, the mailbox server submits more traffic than the
Hub Transport can handle.
??‘
??‘
??‘
Event 1008 The Mail Submission Service cannot locate any Hub Transport servers in
the local Active Directory site. This can be caused by:
The Hub Transport server is not working
There are network or connectivity issues to the Hub Transport
server
No server in the local site is running the Hub Transport role
??‘
??‘
??‘
Part III: Working with PowerShell in a Production Environment
310
Message Tracking
Exchange uses message tracking to log activity as a message is routed throughout the system. Messages
are tracked on the Mailbox, Hub, and Edge Transport server roles. Message tracking is another useful
tool when troubleshooting message delivery. It logs each message event separately, allowing an
administrator to follow the path a message used. At each step, there are a number of fields logged
with information about the message transfer state, the recipients, and the server names. However, no
message content is stored in the tracking logs.
To configure message tracking, use the Set-TransportServer cmdlet for configuring the Hub or Edge
servers.
Pages:
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447