If Add2Exchange was working and now it's not, post here.

5/14/2010 3:43:10 AM
Gravatar
Total Posts 1

error creating public to private relationship with exchange 2010

[MAPI_E_Logon_Failed(80040111)]

Number:-2147221231

Location 5

Build 7,4,104

 

Add to exchange installed on server 2008 64bit connecting to a exchange 2010 server, latest CDO, User not hidden from the GAL.

The CAS is on a seperate box from the HUB/MB Server, the A2E user can connect to the it's mb through the cas server just fine and see the public folders but I get the above error connecting to the private mailboxes.

I followed the prereq procedures from kb article A2E_188

5/18/2010 11:17:20 AM
Gravatar
Total Posts 53
Use the links in the footer below to keep up to date via our newsfeed or Facebook.

Re: error creating public to private relationship with exchange 2010

Hello,

Please verify for me the basic diagnostics described here:

http://support.diditbetter.com/support-troubleshooter.aspx

Then verify that you have completed each of the steps in A2E_188:

  • The Exchange Rollup level on each of your Exchange servers is rollup 3.  This can be verified by opening Exchange Management Console on each, opening Help > About and verifying that the Exchange version is 14.0.694.0
  • That the CDO version is 6.5.8165.0
  • All Exchange servers have been rebooted
  • UAC has been disabled via the registry key on the Add2Exchange server
  • That the Add2Exchange server has been rebooted
  • The service account is part of the Administrators group but not Domain Administrators
  • The service account is part of View-Only Organization Management
  • That you have logged onto the zAdd2Exchange mailbox via Outlook or OWA at least once
  • That the two Add-ADPermission commands completed successfully and with the correct container name
  • That the mailboxes in question are descendants of the specified container (Users)
  • That the public folder, throttling policy and address book configurations have also been completed

Please supply the outputs of the commands so I can verify the result.

Thanks,

Ted

6/1/2010 9:47:58 AM
Gravatar
Total Posts 2

Re: error creating public to private relationship with exchange 2010

 I'm getting the same error with the same symptoms. It can connect to the Public folders but not any mailboxes. Running Exchange 2010 and followed the A2E 188 guide. Our Exchange roles are all on the same physical box.

 

Here are my Diagnostics results:

INFO diags\rundiags.py 2010-06-01 09:00:14,532 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:00:14,532 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:00:14,532 Test Result Message
INFO diags\rundiags.py 2010-06-01 09:00:14,532 ---- ------ -------
INFO diags\rundiags.py 2010-06-01 09:00:14,532 CDO Location Verified Exchange 2003/2007 Standalone CDO
INFO diags\rundiags.py 2010-06-01 09:00:14,532 Threading Model Verified
INFO diags\rundiags.py 2010-06-01 09:00:14,532 --------------------
INFO diags\rundiags.py 2010-06-01 09:00:14,532 Completed. Successfully verified registration.
INFO diags\rundiags.py 2010-06-01 09:00:14,532 --------------------------------------------------------------------------------
WARNING diags\rundiags.py 2010-06-01 09:00:17,546 Group membership cannot be verified. Inspect group membership manually. Report follows:
INFO diags\rundiags.py 2010-06-01 09:00:17,546 Required groups:
INFO diags\rundiags.py 2010-06-01 09:00:17,546 ----------------
WARNING diags\rundiags.py 2010-06-01 09:00:17,546 A2ESecurityGroup False
INFO diags\rundiags.py 2010-06-01 09:00:17,546 Administrators True
INFO diags\rundiags.py 2010-06-01 09:00:17,546 Domain Users True
INFO diags\rundiags.py 2010-06-01 09:00:17,546 Pre-Windows 2000 Compatible Access True
INFO diags\rundiags.py 2010-06-01 09:00:17,546
INFO diags\rundiags.py 2010-06-01 09:00:17,546 Extra groups:
INFO diags\rundiags.py 2010-06-01 09:00:17,546 ------------------
WARNING diags\rundiags.py 2010-06-01 09:00:17,546 G-GLOBAL-OutlookCachedModeDisable
WARNING diags\rundiags.py 2010-06-01 09:00:17,546 S-APP-Add2Exchange
WARNING diags\rundiags.py 2010-06-01 09:00:17,546 View-Only Organization Management
INFO diags\rundiags.py 2010-06-01 09:00:17,546 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:00:17,937 Total System Memory: 1.00 GiB
WARNING diags\rundiags.py 2010-06-01 09:00:17,937 System memory meets minimum requirements but less than recommended. Recommended at least 2GB of system RAM.
INFO diags\rundiags.py 2010-06-01 09:00:17,937 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:00:17,953 Drive Free Space (GiB) Meets minimum
INFO diags\rundiags.py 2010-06-01 09:00:17,953 ----- ---------------- -------------
INFO diags\rundiags.py 2010-06-01 09:00:17,953 C:\ 6.83 True
INFO diags\rundiags.py 2010-06-01 09:00:17,953 Root drive meets or exceeds minimum requirements for Add2Exchange install.
INFO diags\rundiags.py 2010-06-01 09:00:17,953 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:00:17,983 Successfully found .NET installation. Report follows:
INFO diags\rundiags.py 2010-06-01 09:00:17,983 Microsoft .NET Framework 3.5 SP1
INFO diags\rundiags.py 2010-06-01 09:00:17,983 Microsoft .NET Framework 3.0 Service Pack 2
INFO diags\rundiags.py 2010-06-01 09:00:17,983 Microsoft .NET Framework 2.0 Service Pack 2
INFO diags\rundiags.py 2010-06-01 09:00:17,983 Microsoft .NET Framework 3.5 SP1
INFO diags\rundiags.py 2010-06-01 09:00:17,983 Hotfix for Microsoft .NET Framework 3.5 SP1 (KB953595)
INFO diags\rundiags.py 2010-06-01 09:00:17,983 Hotfix for Microsoft .NET Framework 3.5 SP1 (KB958484)
INFO diags\rundiags.py 2010-06-01 09:00:17,983 Update for Microsoft .NET Framework 3.5 SP1 (KB963707)
INFO diags\rundiags.py 2010-06-01 09:00:17,983 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:00:19,624 Successfully verified database.
INFO diags\rundiags.py 2010-06-01 09:00:19,624 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:00:19,967

INFO diags\rundiags.py 2010-06-01 09:00:19,967 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

INFO diags\rundiags.py 2010-06-01 09:00:19,967 Microsoft SQL Server 2005 - 9.00.4053.00 (Intel X86)
INFO diags\rundiags.py 2010-06-01 09:00:19,967 May 26 2009 14:24:20
INFO diags\rundiags.py 2010-06-01 09:00:19,967 Copyright (c) 1988-2005 Microsoft Corporation
INFO diags\rundiags.py 2010-06-01 09:00:19,967 Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
INFO diags\rundiags.py 2010-06-01 09:00:19,967 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:00:20,654 Successfully verified processor affinity.
INFO diags\rundiags.py 2010-06-01 09:00:20,654 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:46:19,694 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:46:19,694 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:46:19,694 Test Result Message
INFO diags\rundiags.py 2010-06-01 09:46:19,694 ---- ------ -------
INFO diags\rundiags.py 2010-06-01 09:46:19,694 CDO Location Verified Exchange 2003/2007 Standalone CDO
INFO diags\rundiags.py 2010-06-01 09:46:19,694 Threading Model Verified
INFO diags\rundiags.py 2010-06-01 09:46:19,694 --------------------
INFO diags\rundiags.py 2010-06-01 09:46:19,694 Completed. Successfully verified registration.
INFO diags\rundiags.py 2010-06-01 09:46:19,694 --------------------------------------------------------------------------------
WARNING diags\rundiags.py 2010-06-01 09:46:21,351 Group membership cannot be verified. Inspect group membership manually. Report follows:
INFO diags\rundiags.py 2010-06-01 09:46:21,351 Required groups:
INFO diags\rundiags.py 2010-06-01 09:46:21,351 ----------------
WARNING diags\rundiags.py 2010-06-01 09:46:21,351 A2ESecurityGroup False
INFO diags\rundiags.py 2010-06-01 09:46:21,351 Administrators True
INFO diags\rundiags.py 2010-06-01 09:46:21,351 Domain Users True
INFO diags\rundiags.py 2010-06-01 09:46:21,351 Pre-Windows 2000 Compatible Access True
INFO diags\rundiags.py 2010-06-01 09:46:21,351
INFO diags\rundiags.py 2010-06-01 09:46:21,351 Extra groups:
INFO diags\rundiags.py 2010-06-01 09:46:21,351 ------------------
WARNING diags\rundiags.py 2010-06-01 09:46:21,351 G-GLOBAL-OutlookCachedModeDisable
WARNING diags\rundiags.py 2010-06-01 09:46:21,351 S-APP-Add2Exchange
WARNING diags\rundiags.py 2010-06-01 09:46:21,351 View-Only Organization Management
INFO diags\rundiags.py 2010-06-01 09:46:21,351 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:46:21,601 Total System Memory: 1.00 GiB
WARNING diags\rundiags.py 2010-06-01 09:46:21,601 System memory meets minimum requirements but less than recommended. Recommended at least 2GB of system RAM.
INFO diags\rundiags.py 2010-06-01 09:46:21,601 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:46:21,648 Drive Free Space (GiB) Meets minimum
INFO diags\rundiags.py 2010-06-01 09:46:21,648 ----- ---------------- -------------
INFO diags\rundiags.py 2010-06-01 09:46:21,648 C:\ 6.85 True
INFO diags\rundiags.py 2010-06-01 09:46:21,648 Root drive meets or exceeds minimum requirements for Add2Exchange install.
INFO diags\rundiags.py 2010-06-01 09:46:21,648 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:46:21,711 Successfully found .NET installation. Report follows:
INFO diags\rundiags.py 2010-06-01 09:46:21,711 Microsoft .NET Framework 3.5 SP1
INFO diags\rundiags.py 2010-06-01 09:46:21,711 Microsoft .NET Framework 3.0 Service Pack 2
INFO diags\rundiags.py 2010-06-01 09:46:21,711 Microsoft .NET Framework 2.0 Service Pack 2
INFO diags\rundiags.py 2010-06-01 09:46:21,711 Microsoft .NET Framework 3.5 SP1
INFO diags\rundiags.py 2010-06-01 09:46:21,711 Hotfix for Microsoft .NET Framework 3.5 SP1 (KB953595)
INFO diags\rundiags.py 2010-06-01 09:46:21,711 Hotfix for Microsoft .NET Framework 3.5 SP1 (KB958484)
INFO diags\rundiags.py 2010-06-01 09:46:21,711 Update for Microsoft .NET Framework 3.5 SP1 (KB963707)
INFO diags\rundiags.py 2010-06-01 09:46:21,711 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:46:22,493 Successfully verified database.
INFO diags\rundiags.py 2010-06-01 09:46:22,493 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:46:23,697

INFO diags\rundiags.py 2010-06-01 09:46:23,697 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

INFO diags\rundiags.py 2010-06-01 09:46:23,697 Microsoft SQL Server 2005 - 9.00.4053.00 (Intel X86)
INFO diags\rundiags.py 2010-06-01 09:46:23,697 May 26 2009 14:24:20
INFO diags\rundiags.py 2010-06-01 09:46:23,697 Copyright (c) 1988-2005 Microsoft Corporation
INFO diags\rundiags.py 2010-06-01 09:46:23,697 Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
INFO diags\rundiags.py 2010-06-01 09:46:23,697 --------------------------------------------------------------------------------
INFO diags\rundiags.py 2010-06-01 09:46:24,540 Successfully verified processor affinity.
INFO diags\rundiags.py 2010-06-01 09:46:24,540 --------------------------------------------------------------------------------
 

 

 

6/1/2010 10:16:09 AM
Gravatar
Total Posts 158

Re: error creating public to private relationship with exchange 2010

Looks like all that is missing is Exchange Organizational Administrators

add it from an account that can, log off, back on as the Service Account, and wait a minute for Exchange to apply the security principle and it should work as desired.

Exchange 2010 has the Exchange 2007 permissions AND the 2010 permissions

 

6/1/2010 10:46:04 AM
Gravatar
Total Posts 158

Re: error creating public to private relationship with exchange 2010

Also:

Did you get the latest cdo? The files are located here:
ftp://ftp.diditbetter.com/Exchange/ExchangeMapiCdo.EXE

uninstall the old
reboot
install the new
reboot

the files are dated 4/5/2010

and are REQUIRED to connect now to 2010
 

6/1/2010 12:29:19 PM
Gravatar
Total Posts 2

Re: error creating public to private relationship with exchange 2010

1. Added A2E account to Org Admins 

2. Verified I'm using the correct cdo.

But I still get the same MAPI error.

6/2/2010 1:13:09 PM
Gravatar
Total Posts 53
Use the links in the footer below to keep up to date via our newsfeed or Facebook.

Re: error creating public to private relationship with exchange 2010

The technical bulletin for Exchange 2010 permissions has been updated.  The process for adding "Send As" permissions to the user mailboxes has been updated, correcting an issue with the old process.  This may resolve your issue.

You can find the updated bulletin at:

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

The updated section is Assign Rights in Exchange to the Add2Exchange Service Account near the end of the document.  The change is that the rights were previously being assigned to the zAdd2Exchange service account, which is incorrect.  The rights need to be assigned to the Active Directory container that holds the users with mailboxes.  The new process makes this easier by using Active Directory Users and Computers to make the change rather than the more confusing PowerShell command.

Please let us know if this addresses your issue.