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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MM4.0 with MAPI event 1849 for the last few weeks - requires a reboot

Status
Not open for further replies.

ayavauser

Technical User
Sep 22, 2005
388
US
We have done several MM4.0 systems without these issues 6 or so in the last year this one is just kicking my a**

We have a site that is MM4.0 w/exch 2007 that has been having event 1319 ( off-line from peer exchange) and then 10 minutes later MAPI 1849 event where we have to reboot the MAS to resolve other times the 1319 is resolved on its on as it was the data vendor rebooting the exchange.

Event 1849 has happened 6 times since early February and nothing prior as it was installed in December seems to happen every 5 or 7 days as if some type of log or buffer gets full ?


in most cases I have noticed the system at 100% CPU usage where a stop and start of the MAS service will not resolve as services shows it nether as started or stopped.

I see a resolve for MM3.1 with just such an issue that more or less seems to be the issue as well.

Patch MM310901 (Service Pack 9 Patch 1)but it resolves the issue on MM3.1


PSN002249U ( MM3.1 )

the message code has been improved to use the MAPI Global Catalog reconnect feature . This allows for reconnection if the domain controller nominated by the exchnage server becomes unavailable. the offline duration is the duration where the domain controller cannot service the NSPI requests. However if the duration is more then 10 minutes , alarming will restart the Messaging Application Server ( MAS ) service allowing another domain controller to be nominitaed by Exchange

alarming update to restart the MAS service when an 1849 event occurs due to peer directory server going offline


also had an issue with Event MMAUDIT failed : Event 1863 ( 1st and only time was 2 days ago )

The MMAUDIT service could not be read its configuration from the VMD .
HRESULT Error: 8004502

MMAUDIT failed issue first and only time happened on 03/31 but this maybe because it’s not enabled on the VMSC I will enable this as this may help in trouble shooting the issue

I could not open VMSC or even the port monitor

Task manager system at 100% CPU usage

has anyone run into this with MM4.0 ?

cheers: )


ayavauser
 
I think this is an issue with the 2007. What software is the 2007 and AD running on 2003 or 2008 server?

2008 is not supported and will cause all types of issues.

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
Ken ,
great thought but they are running 2003 on all servers as always thank you for you reply - I see service SP 3 resolves some issues as this is on SP 2

wi00076022 - The messaging code has been improved to use the MAPI Global Catalog reconnect feature. This allows for a reconnection if the domain controller nominated by the Exchange server becomes unavailable. If that domain controller subsequently becomes available, MM does return online against the Exchange server. The offline duration is the duration where the domain controller cannot service the NSPI requests. However, if this duration is more than 10 minutes, alarming will restart the MAS service allowing for another Domain Controller to be nominated by Exchange.


cheers : )



ayavauser
 
Ken,
Avaya came out with SP 4 for MM4.0( MM400400 )and this seems be a light at the end of the tunnel .....

wi00246282 – Alarming needs to restart the MAS Service when an 1849 event is generated.


on another note with regards to AD / Exchange 2007 on Windows Server 2008 you need SP 4 (MM400400 )& SP4 patch 2 ( MM404002 )

ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/mm/MM4_0/MM400402_Release_Notes.htm


With the release of this patch, the support for Active Directory and Exchange 2007 running on Windows Server 2008 platform has been added. Additional configuration information can be found in “Support for Active Directory and Exchange 2007 running on Windows Server 2008 platforms” under Modular Messaging 4.0 White Papers on support.avaya.com. This support does not include the MAS being installed on a Windows 2008 server.

as always thank you to all -


" I learned everything I needed to know about being a Father by ......watching mine "

ayavauser
 
Texeric & Ken ,
Sorry for the delay as I wanted to wait awhile before I replied to be sure but since loading SP 3 we have not had the issue with MAPI event 1849 where we had to reboot the MAS to restore normal service.

I have seen a few offline ( 1319 ) and online ( 1320 ) events for short durations but this was due to work being done on exchange ( rebooted )other then that all seems fine with this system my only thoughts are the MAPI Global Catalog reconnect feature improvement seems to have helped.

Data vendor says nothing changed on their end with regards to peer mail server or peer directory server.


cheers:)

ayavauser
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top