Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

port speed settings

Status
Not open for further replies.

ayavauser

Technical User
Sep 22, 2005
388
US
what is the best practice for the port speed on the MAS and the Network port that’s its connected to ?

100 / Full - 100 / Full

auto - auto

if allowed gig - gig



as long as there is no mismatch I would think either is fine as I have seen mismatch cause the connection to go up and down

just have an issue with losing connection to its Peer Mail store - seeing it go offline - online and at times you need to stop and start MM- MAS service to get it to come back online

seeing event 1319 - offline peer mail inaccessible

then I see event 1849 almost like clock work 10 minutes later

" the message application service has encountered an error and must be restarted to restore normal operation . The error was MAPI blocked "

this is the one that requires a stop and restart of the MM-MAS service

I have seen this on other systems as well

other times it has come online as it should as they actually were doing work on peer mail updates , reboots , etc

data vendor reports there are no issues with peer mail as users are not having email problems - explained that its the MAS is not able access its peer mail server and this is why the messages get spooled on MAS


MM4.0 with latest SP - H323 trunking
exchange 2007



cheers:)


ayavauser
 
We are seeing this also in at some sites. Is the 2007 running on 2008 server ? and if so is the AD also running on 2008 server? We cleaned some of this up by setting the nic to 100 full but we are seeing that the user is the issue on the failures

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
When a MAPI "deadlock" occurs this typically would require a reboot of the server versus a restart of the MM service. We have seen this happen where a corrupt, mailbox or mail message, item causes MAPI to lock and there for no further MAPI calls will be performed until a reboot has occurred.

The prevention of further MAPI calls will prevent messages that are taken to be delivered to Exchange as well as any MAPI calls to mailboxes to retrieve messages. This also affect MM's MAPI calls to its External Caller mailboxes for monitoring purposes (determining if Exchange is on or offline).

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top