Logon failure message

3/3/2010 10:24:19 AM

Ted Lilley

Total Posts 53

View Posts

Use the links in the footer below to keep up to date via our newsfeed or Facebook.

From an email exchange with a customer:

Customer:

Event ID

Last Occurrence

Total Occurrences

Add2Exchange

1001

3/3/2010 2:20 PM

472 *

An error occurred while attempting to logon to: Exchange Server: SERVER Mailbox: ZADD2EXCHANGE Please verify that the account is valid and has the appropriate permissions. Description: [Collaboration Data Objects - [MAPI_E_LOGON_FAILED(80040111)]] Number: -2147221231 Location: 5 Build: 4.1.719 For further information/support, please visit: http://support.diditbetter.com/

Hi Ted

Can you help with this please – we are now getting this error message. I am concerned about upgrading to the latest version when the system was stable. Is this something that you have seen before?

Thanks!

Customer

My reply:

That’s means that add2exchange was unable to log onto its mailbox on the exchange server. Have you changed anything about the service account recently? Make sure it isn’t hidden from the global address list.

Usually this happens when somebody hides add2exchange from the global address list, changes a group policy which affects our account or changes a password without updating the service’s logon tab in the service manager.

Ted

Customer:

Yes – do I need to do anything else now it is “unhidden”?

Me:

No, that’s it. You can restart the service if you’d like to immediately sync, which will verify that your change took effect.

Ted

3/9/2010 2:09:16 PM

andrewc

Total Posts 2

View Posts

Re: Logon failure message

This error can also occur when the Exchange System Attendant has not been started, or has shut down for some reason (Windows Updates, Mailbox Maintenance, etc). Verfify that the Exchange System Attendant is running when this error occurs.

10/1/2010 5:23:23 AM

michel140

Total Posts 1

View Posts

Re: Logon failure message

I tried everything (read knowledge base articles, looked in the forums) to resolve this problem, but still get this message.

I think somebody started the Add2exchange console under the administrator account, but i restarted it using the zadd2exchange account.

Could you give me a step by step solution for this problem?

tx in advance

10/27/2010 12:06:19 PM

Ted Lilley

Total Posts 53

View Posts

Use the links in the footer below to keep up to date via our newsfeed or Facebook.

Re: Logon failure message

Hi Michel,

Our email monitoring system for the forums was broken by our last upgrade. While we have now fixed it, questions such as yours have gone unanswered for an unacceptably long time, for which I apologize.

We have just published a new technical bulletin dealing with this error:

http://support.diditbetter.com/kb/a2e_216.aspx

If you are still having logon failures and you are using Exchange 2007 or 2010, please see the following post for instructions on using the preinstaller to reapply the correct permissions to the service account:

http://support.diditbetter.com/Forums/Thread.aspx?pageid=1&mid=2&ItemID=2&thread=35

Responding to this post will result in an email to me now that the system has been fixed.

1/30/2011 2:36:36 PM

stkristobal

Total Posts 8

View Posts

Re: Logon failure message

Hi,

I'm having this exact error. I've set up A2E on a lab setup before deploying to a customer; and followed the guide 100%. When I try to start the console I get this error.

I've checked the LegacyDN attribute, and it looks correct to me. I've also tried running the preinstall-program; which stops on the final point (on Public Folders rights). It doesn't give an error, it just hangs.

The preinstall log says:

Add-PublicFolderClientPermission : Failed to commit the change on object "00000

0001A447390AA6611CD9BC800AA002FC45A0300FAAAF4E97E6C204188F972E7C4A94A6500000000
00010000" because access is denied.
At C:\Program Files\Microsoft\Exchange Server\Scripts\AddUsersToPFRecursive.ps1
:136 char:34
+ add-PublicFolderClientPermission <<<< -identity $_.Identity -user $user
-AccessRights $Permissions -server $_.OriginatingServer;
+ CategoryInfo : NotSpecified: (0:Int32) [Add-PublicFolderClientP
ermission], MapiAccessDeniedException
+ FullyQualifiedErrorId : 60920202,Microsoft.Exchange.Management.MapiTasks
.AddPublicFolderClientPermission

Running Ex2007; SP3, RU2 on Server 2008 R2.

Any ideas?

1/31/2011 12:22:41 PM

Ted Lilley

Total Posts 53

View Posts

Use the links in the footer below to keep up to date via our newsfeed or Facebook.

Re: Logon failure message

Hi Kristoffer,

Sorry to hear your difficulty. If you've gone through all of the materials we've provided, then I would suggest you contact us at 813-977-5739 and we can do an investigative session with you to determine whether there is a simple solution to the issue.

Thank you for posting the error log from the preinstaller as well. What I can tell you is that this particular error is "normal", by which I mean it is a byproduct of the correct functioning of the process, so it is not a pointer to the real issue. It is generated by the command we use to add our account as Owner to all public folders, which always fails on the root folder but succeeds on the rest of the tree.

Similarly, the hang issue is no additional help. Unfortunately, Microsoft's script which adds public folder rights hangs every time you run it after its first successful completion. So once the preinstaller has been run the first time, it always gets a hang on that step. Since it is MS's script which is hanging, there is little we can do about it.

Please contact us at your earliest convenience and ask for support.

1/31/2011 1:20:49 PM

TervoCharged

Total Posts 158

View Posts

Re: Logon failure message Location 5

This occurs when the add2exchange service account cannot log in to its own mailbox

It can occur for several (thousand) reasons:
The most common is that the add2exchange service account is hidden from the global address list
Unhide it if it is, log off and on and try to open the console again. Also, you MUST open the mailbox in OWA or Outlook PRIOR to opening the Console. Exchange has to make the mailbox.

Another common reason is exchange has been updated and you do not have the latest versions to take advantage of the changes
The version you are running is not current.

Please use these procedures to update Add2Exchange: http://support.diditbetter.com/kb/A2E_194.aspx
Be sure to pick the right (same) edition of add2Exchange to download and use, either Standard or Enterprise.

You will also have to make sure you update cdo, located in the preinstaller directory in the zipped download
If you need to update Add2Exchange, it is a good time to do it

http://support.diditbetter.com/kb/A2E_194.aspx

Then, when done

Stop a2e service, put on manual
Uninstall CDO
Reboot
Install the new cdo

Then stop a2e
Uninistall old
install new

If this an Exchange 2007 or 2010 install?
If so, the Preinstaller should be run on the exchange server using Exchange Command Shell. If it is run already, the messages above will come in the result text.
If you have made the account already, select the checkbox that the Account already exists
http://support.diditbetter.com/kb/A2E_214.aspx

Try these most common fixes please and if all else fails, we can assist remotely if you want or need to escalate this to Premier Support. A single session which covers up to 1 hour of remote/phone support is $199 Buy Now or the block of 4 hours (never expire until you use them) goes for $399 Buy Now. Of course, we can continue on the free mail support in the meantime.

Sorry you are having the issue and thanks for the opportunity to work with you

2/3/2011 6:39:47 AM

stkristobal

Total Posts 8

View Posts

Re: Logon failure message

I decided not to waste any more time trying to set this up in a lab environment; and decided to take the chance on installing it as a demo in the customers production environment. All is well so far, though I didn't get it to work in my lab.

Thanks for you replies!

Site Search