MWI Errors

[myron.johnson]

Recent Upgrade from Unity 3.1.4 to 4.0.4sr1 Unified Messaging with Exchange 2003 partner server and all users still on an exchange 2000 server.

About 70% of users are getting event log error:

Event Type: Error

Event Source: CiscoUnity_Notifier

Event Category: Run

Event ID: 1034

Date: 12/16/2004

Time: 9:28:53 AM

User: N/A

Computer: S1RACVM1

Description:

Mailbox logon failed for user cn=ahyatt,cn=Recipients,ou=RACINE,o=Educators Credit Union. This can occur if the user's message store is unavailable. When the message store becomes available, resync the user from the SA by refreshing the MWI status on the user's Messages page.

For more information, click: http://www.CiscoUnitySupport.com/find.php

This happens when Unity resyncs all MWI's at 1:00am or when you go to a user's Messages page in SA and select refresh.

Also starting to see the following error:

Event Type: Error

Event Source: CiscoUnity_Notifier

Event Category: Run

Event ID: 1032

Date: 12/16/2004

Time: 11:19:12 AM

User: N/A

Computer: S1RACVM1

Description:

Failed to set message waiting lamp for Kim Warg, ext 6665, reason: Load from Doh failed. Turn on Doh diagnostics to troubleshoot.

For more information, click: http://www.CiscoUnitySupport.com/find.php

This error has only happened a couple of times.

Ran syscheck and everything is fine. All accounts seem to be fine.

Trying to figure this one out.

[Hin Lee]

If you are not having MWI issues, the error is erroneous. See bug CSCeg02287 AvNotifier eventid 1032 after installing ES27 or SR1

Symptom:

After installing ES27 or Sr1 for Unity 4.0(4), these errors started to appear in the Windows application

logs:

CiscoUnity_Notifier Run Error 1032 UnityServer

"Failed to set message waiting lamp for Subscriber, Unity, ext 12345, reason:

Load from Doh failed. Turn on Doh diagnostics to troubleshoot.

Conditions:

Unity 4.0(4)

Workaround:

none at this time.

Further Problem Description:

It does not appear to be an issue at this time.

Random monitoring using Port Status Monitor shows that the MWI-dialout is happening and the subscribers are not reporting incorrect MWI status.

[myron.johnson]

Above answer appears to be right for one of the errors. The other error appears to have been a problem on the Exchange 2003 server. The MTA was not started and is getting errors every couple of hours.

The errors:

Event Type: Warning

Event Source: MSExchangeIS Mailbox Store

Event Category: MTA Connections

Event ID: 2000

Date: 8/25/2004

Time: 5:09:13 AM

User: N/A

Computer: EB3AL

Description:

Verify that the Microsoft Exchange MTA service has started. Consecutive ma-open calls are failing with error 3051.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type: Error

Event Source: MSExchangeFBPublish

Event Category: General

Event ID: 8276

Date: 8/26/2004

Time: 1:00:09 AM

User: N/A

Computer: EB3AL

Description:

Site folder could not be opened for duplicate message deletion on virtual machine EB3AL. The error number is 0x8004010f.

For more information, click http://www.microsoft.com/contentredirect.asp.

We are trying to determine the cause of these.