ビデオヘルプ
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Process: w3wp.exe (3384) Module: AltirisNativeHelper.dll Source: AlertManager.ProcessInboxes Description: Inbox processing exception: Inbox authentication failed.

作成: 11 Oct 2012 | コメント数: 3

All, 

We are running NS 6..

Has anyone come accross the following error messages?  

Process: w3wp.exe (3384)
Thread ID: 4396
Module: AltirisNativeHelper.dll
Source: AlertManager.ProcessInboxes
Description: Inbox processing exception: Inbox authentication failed. -ERR Logon failure: unknown user name or bad password.
 
Process: w3wp.exe (3384)
Thread ID: 3984
Module: AltirisNativeHelper.dll
Source: AlertManager.ProcessInboxes
Description: Inbox processing exception: Inbox authentication failed. -ERR Logon failure: unknown user name or bad password.
 
Process: w3wp.exe (3384)
Thread ID: 5024
Module: AltirisNativeHelper.dll
Source: AlertManager.ProcessInboxes
Description: Inbox processing exception: Inbox authentication failed. -ERR Logon failure: unknown user name or bad password.
 
Noting that only the Thread ID is different in each of the errors listed... We have validated our Application Identity user name and password and services have been restarted.
 
Any insight would be of greate assitance.
 
Thanks in advance.
 
-Matt
 
 
 

コメント コメント数: 最新のコメントを表示

andykn101 の写真

Is it to do with your smtp gateway? Perhaps the account specified for that has had a password change or been removed from the mail server.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

toomas の写真

Processing inboxes means the incoming e-mail credentials for Helpdesk inbox.

Based on error message formatting, I would say it is exactly what the message says - a logon failure to a POP3 mailbox.

Perhaps the Helpdesk inbound mailbox credentials have changed?

dsmith1954 の写真

It could also be that your Exchange administrator disabled POP3 by mistake. Or, if you upgraded to Exchange 2010 recently, POP3 is off by default and needs to be turned back.

There's also the possiblility that Plain Text Authentication was turned off by mistake.

Your HelpDesk has to match Exchange exactly. There are some similar authentications available to Exchange, but the Exchange Account must match the HelpDesk exactly.

I went through this when we upgraded to Exchange 2010. Our admin didn't want to enable Plain Text Authentication, but he was finally convinced otherwise.