Exchange Server 2010: Undeliverable Message

Dear All,
We are using exchange server 2010 to send a email to a client, however, we got this message back. How can i solve this problem?
Thanks for your attention and help!
次の受信者またはグループへの配信に失敗しました:
[email protected] 受信者の電子メールプロバイダーによって拒否されたため、メッセージを配信できませんでした。
メッセージは次の組織に拒否されました。BL2FFO11FD039.mail.protection.outlook.com。
管理者向けの診断情報:
生成サーバー: xxxx.com
[email protected] BL2FFO11FD039.mail.protection.outlook.com #<BL2FFO11FD039.mail.protection.outlook.com #5.7.0 smtp;550 5.7.0 Relay Access Denied> #SMTP#
元のメッセージヘッダー:
Received: from na01-by2-obe.outbound.protection.outlook.com (207.46.163.241)
by exch.xxxx.com (192.168.10.32) with Microsoft SMTP Server (TLS)
id 14.3.210.2; Sun, 19 Oct 2014 22:36:47 -0700
Received: from BN1AFFO11FD049.protection.gbl (10.58.52.31) by
BN1AFFO11HUB044.protection.gbl (10.58.52.155) with Microsoft SMTP Server
(TLS) id 15.0.1049.20; Mon, 20 Oct 2014 05:36:44 +0000
Received: from mgcserv4.magsaysay.com.ph (203.167.92.249) by
BN1AFFO11FD049.mail.protection.outlook.com (10.58.53.64) with Microsoft SMTP
Server id 15.0.1049.20 via Frontend Transport; Mon, 20 Oct 2014 05:36:43
+0000
Received: from Crystal ([203.167.92.232]) by
mgcserv4.magsaysay.com.ph (Lotus Domino Release 8.5.3) with ESMTP id
2014102013364607-10992 ; Mon, 20 Oct 2014 13:36:46 +0800
X-TM-IMSS-Message-ID: <[email protected]>
Received: from na01-bl2-obe.outbound.protection.outlook.com ([65.55.169.54])
by magsaysay.com.ph ([203.167.92.232]) with ESMTP (TREND IMSS SMTP Service
7.0; TLS: TLSv1/SSLv3,256bits,AES256-SHA) id 26975997000186d5 ; Mon, 20 Oct
2014 13:40:58 +0800
Received: from BL2FFO11FD041.protection.gbl (10.173.160.33) by
BL2FFO11HUB022.protection.gbl (10.173.161.46) with Microsoft SMTP Server
(TLS) id 15.0.1049.20; Mon, 20 Oct 2014 05:36:36 +0000
Received: from mail.xxxx.com (216.81.51.170) by
BL2FFO11FD041.mail.protection.outlook.com (10.173.161.137) with Microsoft
SMTP Server (TLS) id 15.0.1039.16 via Frontend Transport; Mon, 20 Oct 2014
05:36:36 +0000
Received: from na01-by2-obe.outbound.protection.outlook.com (207.46.163.236)
by exch.xxxx.com (192.168.10.32) with Microsoft SMTP Server (TLS)
id 14.3.210.2; Sun, 19 Oct 2014 22:36:28 -0700
Received: from BY2FFO11FD056.protection.gbl (10.1.14.33) by
BY2FFO11HUB055.protection.gbl (10.1.14.244) with Microsoft SMTP Server (TLS)
id 15.0.1039.16; Mon, 20 Oct 2014 05:36:15 +0000
Received: from mailgate.zzz.com (14.16.28.51) by
BY2FFO11FD056.mail.protection.outlook.com (10.1.15.193) with Microsoft SMTP
Server id 15.0.1049.20 via Frontend Transport; Mon, 20 Oct 2014 05:36:13
+0000
X-AuditID: c0a81e07-b7f5e6d000000b4e-4d-54449f4b6588
Received: from UNER2.zzz.com (unr2.zzz.com
[192.168.30.13]) by mailgate.zzz.com (Symantec Messaging Gateway) with
SMTP id CA.40.02894.B4F94445; Mon, 20 Oct 2014 13:36:11 +0800 (HKT)
Received: from UN2.zzz.com ([::1]) by UNR2.zzz.com
([::1]) with mapi id 14.01.0438.000; Mon, 20 Oct 2014 13:36:11 +0800
From: Yukihiro <[email protected]>
To: Simonu <[email protected]>, Charles
<[email protected]>
CC: Miln <[email protected]>, FSA
<[email protected]>
Subject: Re: unia s maual / MV Kett Iand
Thread-Topic: unaa sh ml / MVlettsland
Thread-Index: Ac/sEV9D2LsdkU5fRkW0Rd1v4PsvSQAFlzIA
Date: Mon, 20 Oct 2014 05:36:10 +0000
Message-ID: <D06AC01C.21F27%[email protected]>
References: <[email protected]>
In-Reply-To: <[email protected]>
Accept-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.2.140509
x-originating-ip: [192.168.30.123]
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJIsWRmVeSWpSXmKPExsVyYIUcr673fJcQg8bHChbzDrexW/R3vGG2
OPK31GLjrinMDiwePbO6WAIYo7hsUlJzMstSi/TtErgy/my9w1Zw2LJi74lOxgbGd+ZdjJwc
EgImEq27r7NA2GISF+6tZ+ti5OIQErjIKHF27jdmCGcCo8SpVw3MIFVsAtoS21rusILYIgKR
En8nzgKzmQXiJL7sPAc2SVjAWOLni0tsEDUmEvNOdzNC2EYSp55dZgKxWQRUJa5unwBm8wro
SVzdtgNsvpBAhETH9lawOZxA808+PwxmMwJd9/3UGiaIXeISlyYvYoO4WkBiyZ7zzBC2qMTL
x//A7hEFmtnc9YYRIq4kcfbZAaA5HEC9wRJ3mzgg1gpKnJz5hGUCo9gsJFNnIVTNQlIFEdaU
WL9LH6JaUWJK90N2CFtDonXOXCjbWuJq40IWZDULGDlWMQrlJmbmGOqV5mXqJhZnJuol5+du
YoREJ/sOxg9NlocYBTgYlXh4pzi5hAixJpYVV+YeYpTgYFYS4f2XARTiTUmsrEotyo8vKs1J
LT7EyMTBKdXAKPV7/zEX5dgtO6cd8N8764+UCO+vDPaVj5LWF051+GIx3/pf/dHiA0Gn+Lia
by2Se/tyVqhMYGzs1CpNAcut2bfuLIhUOqbbIDv7buL74s/XWGIu27vcYoi+dJ9BSzA9WNnH
h1NVbn+SgEDAhsL6Cyvs48Ja+1InV76xt515//fJOSLapX/uKbEUZyQaajEXFScCAFed/I2s
AgAA
Return-Path: [email protected]
X-EOPAttributedMessage: 2
X-Forefront-Antispam-Report-Untrusted: CIP:14.1.28.51;CTRY:HK;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(428002)(189002)(66654002)(199003)(252514010)(76176999)(21056001)(71186001)(31966008)(106466001)(81156004)(77096002)(95666004)(54356999)(105586002)(4396001)(50986999)(15975445006)(86362001)(83506001)(107046002)(84326002)(19617315012)(36756003)(85852003)(53416004)(92726001)(15974865002)(19580395003)(19580405001)(44976005)(101416001)(16236675004)(92566001)(87836001)(85306004)(99396003)(2656002)(46102003)(120916001)(15202345003)(20776003)(30436002)(512874002);DIR:INB;SFP:;SCL:1;SRVR:BY2FFO11HUB055;H:mailgate.zzzz.com;FPR:;MLV:sfv;PTR:014168051.static.ctinets.com;MX:1;A:0;LANG:en;
X-Exchange-Antispam-Report-Test: UriScan:;UriScan:;UriScan:;
Received-SPF: None (protection.outlook.com: zzz.com does not designate
permitted sender hosts)
Authentication-Results: spf=none (sender IP is 203.167.92.249)
[email protected];
X-Auto-Response-Suppress: DR, OOF, AutoReply
X-Matching-Connectors: 130582569966280204;(42405700-fa69-4020-a9c4-08d0e394d333);()
X-Forefront-Antispam-Report-Untrusted: CIP:216.81.51.170;CTRY:CA;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(10009020)(428002)(199003)(66654002)(252514010)(189002)(81156004)(106466001)(76176999)(54356999)(36756003)(77096002)(101416001)(53416004)(50986999)(105586002)(95666004)(31966008)(46102003)(20776003)(30436002)(19580395003)(4396001)(44976005)(19580405001)(16236675004)(6806004)(21056001)(71186001)(15974865002)(15202345003)(99396003)(84326002)(120916001)(15975445006)(83506001)(92726001)(92566001)(85852003)(86362001)(2656002)(87936001)(85306004)(107046002)(512874002)(19617315012);DIR:OUT;SFP:1101;SCL:1;SRVR:BL2FFO11HUB022;H:mail.xxx.com;FPR:;MLV:sfv;PTR:216.81.51.170.epikip.net;A:0;MX:1;LANG:en;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BL2FFO11HUB022;UriScan:;
X-Forefront-PRVS: 03706074BC
X-MIMETrack: Itemize by SMTP Server on mgcserv4/mgc(Release 8.5.3|September 15, 2011) at
10/20/2014 01:36:46 PM,
Serialize by Router on mgcserv4/mgc(Release 8.5.3|September 15, 2011) at 10/20/2014
01:36:47 PM,
Serialize complete at 10/20/2014 01:36:47 PM
X-TNEFEvaluated: 1
Content-Type: multipart/alternative;
boundary="_000_D06AC01C21F27hzzzcom_"
Content-Language: ja-JP
X-Forefront-Antispam-Report: CIP:203.167.92.249;CTRY:PH;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(428002)(252514010)(189002)(66654002)(199003)(76176999)(54356999)(86362001)(15974865002)(50986999)(85852003)(92566001)(92726001)(19617315012)(512874002)(46102003)(85306004)(97736003)(99396003)(120916001)(33186001)(53416004)(44976005)(105586002)(19580405001)(106466001)(16236675004)(77096002)(81156004)(19580395003)(95666004)(31966008)(71186001)(107046002)(21056001)(101416001)(15202345003)(84676001)(68736004)(30436002)(87836001)(2656002)(20776003)(4396001)(6806004)(84326002)(83506001)(15975445006)(36756003)(72026002);DIR:INB;SFP:;SCL:1;SRVR:BN1AFFO11HUB044;H:mgcserv4.magsaysay.com.ph;FPR:;MLV:sfv;PTR:ErrorRetry;MX:1;A:0;LANG:en;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1AFFO11HUB044;

Hi Shiloh,
According to your description, my understanding is that you send a message to external user(@xxx.com) fail.
Before going further, I'd like to ask the following question to narrow down the issue:
1. Could you send message to any other external user except xxx.com? like google.com,outlook.com.
2. Try to disable or bypass Transport Scanning in Forefront Protection 2010 and check if any helps.
You can refer to the following article to disable or bypass FPE:
http://social.technet.microsoft.com/wiki/contents/articles/407.how-to-disable-or-bypass-transport-scanning-in-forefront-protection-2010-for-exchange-server-fpe.aspx
Best regards,
Niko Cheng
TechNet Community Support

Similar Messages

When sending e-mail messages to a mail-enabled public folder that have been replicated from old Exchange Server 2000/2003/2007, Exchange Server 2010 environment mails are rejected with NDR.

Hi, I would like to share with you issue that I’ve solved regarding mail-enabled PF that migrated from Exchange 2000/2003/2007 to 2010, I’ve searched & contacted my MVP leader – there’s no official KB regarding this issue right
now, so I’m posting here in order to share this among others.
Note: There’s article(s) that talked about PF replication from Exch2000/2003/2007 to 2010 – this is the same issue as well.
Symptoms
E-mail messages that been sent to mail-enabled public folder in Exchange Server 2010 environment rejected with the following NDR:
“#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory
user wasn’t found.> #SMTP#”
Sometimes Exchange Server 2010 is documented as well Event ID 1020 on the Event Viewer with this information:
“Log Name: Application
Source: MSExchange Store Driver
Event ID: 1020
Level: Error
Description:
The store driver couldn’t deliver the public folder replication message "Hierarchy ([email protected])" because the following error occurred: The Active Directory user wasn't found.”
Cause
In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed, there is a chance that an Administrative Group (First Administrative Group or another custom Administrative
Group) remains with a Servers container, but no servers inside it.
During replication, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it's expecting a System Attendant object inside the container and when it is not found the error occurs.
Resolution
To work around the issue, delete the empty Servers container. This can't be done through Exchange System Manager. Use the ADSI Edit tool to remove it using the following steps:
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows
2003 Server, Microsoft Windows Server 2008, Microsoft Exchange 2010 Server or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes
at your own risk.
1.
Start the ADSI Edit MMC Snap-in. Click Start, then
Run, and type adsiedit.msc, and then click OK.
2.
Connect & Expand the Configuration Container [YourServer.DNSDomainName.com], and then expand
CN=Configuration,DC=DNSDomainName,DC=com.
3.
Expand CN=Services, and then CN=Microsoft Exchange, and then expand
CN=YourOrganizationName.
4.
You will see an empty Administrative Group. Expand the
CN=YourAdministrativeGroupName.
5.
Expand CN=Servers.
6.
Verify there are no server objects listed under the
CN=Servers container.
7.
Right click on the empty CN=Servers container and choose
Delete.
8.
Verify the modification, and try to send again the E-mail to the mail-enabled public folder.
Applies to
Exchange Server 2010, Standard Edition
Exchange Server 2010, Enterprise Edition
Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb
| E-mail: [email protected]

Sounds like you are looking in the wrong Administrative Group container which is why you are seeing your Exchange 2010 servers in there.
When you install Exchange 2003 only you will see a container named by default as "CN=First Administrative Group" container. But this could be named anything if you changed the Organization Name on the installation when you installed the first
Exchange 2003 server into the domain/forest.
You will notice that when you install Exchange 2010 part of the AD setup is to create a new configuration container and is named by default "CN=First Administrative Group (FYDIBOHF23SPDLT)".
So it sounds like you are not looking in the right location within ADSIEdit.
You may find the following article also helpful for this issue which is the same resolution:
http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx
I recommend though that you ensure your Exchange 2003 servers are fully uninstalled or no longer present in your environment before you go deleting the Servers container though.. The following Microsoft article will help with this:
http://technet.microsoft.com/en-gb/library/gg576862(v=exchg.141).aspx

MS Exchange server 2010 messages will be placed in the poison queue and the transport service will crash

Can any1 please help.
We have Exchange server 2010, we just upgraded it with SP3 and then the issue occers that we were unable to send n receive mail outside of our LAN...i mean from gmail or hotmail..
we have then updated with CU4 which is the latest but still messages will be placed in the poison queue and the transport service will crash.
We have disabled the antivirus also but issue remains same.
We have CAS 1 n 2 as of Clustering environment and we upgraded sp3 for both. but we did CU4 on CAS1 to see the results to resovle this issue but no luck

Hi,
Did you get any NDR message now when you send a email to outside? And vice versa.
In addtion,I recommend you telnet to port 25 to test SMTP communication.
If any question,please feel free to post here.
Thanks.
Niko Cheng
TechNet Community Support

"Message Queued for submission" performance counter high for Exchange Server 2010 Database

Hi,
We are receiving SCOM Alert as "Mail Submission service is experiencing issue: Messages Queued for Submission-sustained for 15 mins-RED (>25)".
After checking the "Messages queued for Submission" counter on the repective server it was found that the value is 66 but when we check the queue viewer we dont observe any messages stuck in Submission queue.
Would like to know what aspects can be checked here, in order to troubleshoot the issue?
The counter shows 0 value in perfmon for all other mailbox databases.
Thanks & Regards.

Hi,
This is a known issue with Exchange Server 2007 and Exchange Server 2010. We do not recommend that you use this counter for health alerts.
I recommend you refer to the following article:
http://support.microsoft.com/kb/2921142/en-us
It is caused by the MailSubmission service submits a message for delivery multiple times, the counter is incremented two times but decremented only one time. This situation can leave the counter with a positive value even though there
is no message in the queue. When you restart the service, the counter is reset.
Here is an similar thread for your reference:
http://social.technet.microsoft.com/Forums/en-US/c9b485a5-ef0e-4b9a-851e-28c4a4c0606a/msexchangeis-mailbox-messages-queued-for-submission-keeps-increasing?forum=exchangesvradminlegacy
Thanks.
Niko Cheng
TechNet Community Support

Customize the Response Message for Resource Scheduling - Sent by Microsoft Exchange Server 2010

We have a room mailbox and when one books it the organzier gets response with the following and the very botoom:
Sent by Microsoft Exchange Server 2010
I want to remove it as I dont want anybody to know what mail server we are running? thankx

Hi,
As what Andy says, it is by default and there is no method to remove it.
Sorry for any inconvenience.
Regards,
Winnie Liang
TechNet Community Support

All sub-folders in Mac Mail cannot synchronize with Exchange Server 2010

Hi all,
All sub-folders under Inbox in Mac Mail cannot be synchronized with Exchange Server 2010. There are 2GB messages size in Inbox folder and 500MB messages size under Inbox's sub-folders. All messages can be sent out and received and it can work in Outlook 2007 and Outlook 2010 normally. However, all messages in sub-folders cannot be synchronized (empty sub-folders).
Does this problem relate to message synchronization order of Mac Mail with Exchange Server? Do all sub-folders messages be synchronized after synchronization complete of Inbox? The synchronization of sub-folders will not happen if the synchronization of Inbox does not complete, doesn't it?
All messages synchronization is over internet. Can anybody help?
Thanks a lot
DT1640759

Hi,
1.please check the mailbox send and receive quota for exchange 2013 migrated mailbox.
2.Please check the email attributes of the exchange 2013 migrated mailbox because it seems to be a problem with that particular mailbox.
3.Then do the message tracking and that would be the only way to find the where the send messages has gone.
4.Please check and confirm you have an enough space on the disk where exchange queue database is residing.
I think I need to create a receive connector in the 2013 to receive from 2010 ?
No need ,by design exchange 2013 cas server default frontend receive connector will be having an
entire ipv4 and ipv6 segment and anonymous connection is checked by default.
I think I also need to create a send and receive connector for 2013 users to each other?
No need , an intra organisation send connector and the default receive connectors in exchange will be used
for internal mail flow between the exchange 2013 users.
Please reply me if you have any queries .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

SBS 2003 to 2011 Migration - Exchange Server 2010 cannot be installed

Hello,
We have a Small Business Server 2003 server that we are trying to migrate to SBS 2011 using the out of the box migration process. After the install, the SBS console showed a couple installation issues - the big one turned out to be "Exchange Server
2010 cannot be installed".
Here is the end of 'ExchangeSetup.log' showing various error messages:
[11/29/2014 23:00:07.0489] [2] Active Directory session settings for 'Get-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0490] [2] Beginning processing get-exchangeserver -Identity:'MB-MAINSERVER04' -DomainController:'MB-MAINSERVER04.Contoso.local' -ErrorAction:'SilentlyContinue'
[11/29/2014 23:00:07.0506] [2] Searching objects "MB-MAINSERVER04" of type "Server" under the root "$null".
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Preparing to output objects. The maximum size of the result set is "unlimited".
[11/29/2014 23:00:07.0522] [2] Unexpected Error
[11/29/2014 23:00:07.0522] [2] The operation couldn't be performed because object 'MB-MAINSERVER04' couldn't be found on 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0523] [2] Ending processing get-exchangeserver
[11/29/2014 23:00:07.0523] [1] Executing:
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
[11/29/2014 23:00:07.0545] [2] Active Directory session settings for 'New-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0545] [2] Beginning processing new-exchangeserver -DomainController:'MB-MAINSERVER04.Contoso.local' -Name:'MB-MAINSERVER04'
[11/29/2014 23:00:07.0599] [2] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0600] [2] Ending processing new-exchangeserver
[11/29/2014 23:00:07.0607] [1] The following 1 error(s) occurred during task execution:
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.SystemConfiguration.DefaultAdministrativeGroupNotFoundException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroup()
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroupId()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServer.PrepareDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[11/29/2014 23:00:07.0609] [1] [ERROR] The following error was generated when "$error.Clear();
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
" was run: "Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.".
[11/29/2014 23:00:07.0609] [1] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0609] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___84489810458648f5ac6e47811394a284 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/29/2014 23:00:07.0610] [1] Setup is stopping now because of one or more critical errors.
[11/29/2014 23:00:07.0610] [1] Finished executing component tasks.
[11/29/2014 23:00:07.0618] [1] Ending processing Install-BridgeheadRole
[11/29/2014 23:00:07.0626] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[11/29/2014 23:00:07.0633] [0] End of Setup
[11/29/2014 23:00:07.0633] [0] **********************************************
[11/29/2014 23:39:03.0429] [0] **********************************************
[11/29/2014 23:39:03.0435] [0] Starting Microsoft Exchange Server 2010 Setup
[11/29/2014 23:39:03.0435] [0] **********************************************
[11/29/2014 23:39:03.0456] [0] Local Time Zone: (UTC-08:00) Pacific Time (US & Canada).
[11/29/2014 23:39:03.0457] [0] Operating System version: Microsoft Windows NT 6.1.7600.0.
[11/29/2014 23:39:03.0469] [0] Setup version: 14.1.438.0.
[11/29/2014 23:39:03.0473] [0] Logged on user: Contoso2K3\Administrator.
[11/29/2014 23:39:06.0763] [0] Command Line Parameter Name='mode', Value='Install'.
[11/29/2014 23:39:06.0776] [0] ExSetupUI was started with the following command: '-mode:install'.
[11/29/2014 23:39:07.0413] [0] Setup is choosing the domain controller to use
[11/29/2014 23:39:07.0730] [0] Setup is choosing a local domain controller...
[11/29/2014 23:39:08.0459] [0] Setup has chosen the local domain controller MB-MAINSERVER04.Contoso.local for initial queries
[11/29/2014 23:39:08.0747] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use MB-MAINSERVER04.Contoso.local
[11/29/2014 23:39:08.0748] [0] Setup is choosing a global catalog...
[11/29/2014 23:39:08.0758] [0] Setup has chosen the global catalog server MB-MAINSERVER04.Contoso.local.
[11/29/2014 23:39:08.0819] [0] Setup will use the domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0820] [0] Setup will use the global catalog 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0823] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0830] [0] Exchange organization container for the organization is 'CN=Contoso2K3,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0867] [0] Setup will search for an Exchange Server object for the local machine with name 'MB-MAINSERVER04'.
[11/29/2014 23:39:08.0914] [0] No Exchange Server with identity 'MB-MAINSERVER04' was found.
[11/29/2014 23:39:09.0061] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
[11/29/2014 23:39:09.0062] [0] The following datacenter roles are unpacked:
[11/29/2014 23:39:09.0064] [0] The following roles are installed: AdminToolsRole
[11/29/2014 23:39:09.0066] [0] The local server has some Exchange files installed.
[11/29/2014 23:39:09.0320] [0] Setup will use the path 'C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1' for installing Exchange.
[11/29/2014 23:39:09.0332] [0] The installation mode is set to: 'Install'.
[11/29/2014 23:39:13.0558] [0] An Exchange organization with name 'Contoso2K3' was found in this forest.
[11/29/2014 23:39:13.0560] [0] Active Directory Initialization status : 'True'.
[11/29/2014 23:39:13.0561] [0] Schema Update Required Status : 'False'.
[11/29/2014 23:39:13.0562] [0] Organization Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0563] [0] Domain Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0564] [0] The locally installed version is 14.1.218.15.
[11/29/2014 23:39:13.0565] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V14'.
[11/29/2014 23:39:13.0920] [0] Applying default role selection state
[11/29/2014 23:39:13.0961] [0] Setup is determining what organization-level operations to perform.
[11/29/2014 23:39:13.0962] [0] Because the value was specified, setup is setting the argument OrganizationName to the value Contoso2K3.
[11/29/2014 23:39:13.0963] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V14\'.
[11/29/2014 23:39:13.0972] [0] InstallModeDataHandler has 0 DataHandlers
[11/29/2014 23:39:13.0972] [0] RootDataHandler has 1 DataHandlers
[11/29/2014 23:39:15.0491] [0] Setup encountered an exception when trying to access the setup state file: Could not find file 'C:\ExchangeSetupLogs\exchangeInstallState.xml'.
[11/29/2014 23:39:26.0117] [0] End of Setup
[11/29/2014 23:39:26.0117] [0] **********************************************
I should add that the source server's AD configuration might not be perfect due to this being the second attempt at a SBS 2011 migration install.
I'd be grateful for any help I can get on this as SBS migration has been plauged with multiple setbacks already. I really need to get this done! ;)
Thanks,
Voon

Thank you Larry and Al for your replies.
I used the 'official' migration
guide plus this page (http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/)
as my migration references. The SBS migration prep tool gave no errors on the source server when I ran it.
I have a full system drive image plus a a system state backup from before migration. Though I am very loathed to rollback the migration and attempt a new one - again. I will do some searching to see if I can resolve the Exchange server problem and continue
the migration/installation. If not, then its a system state restore for me. One of Al's links had a resource for doing a thorough check of AD - which something I'd run if I have to another migration attempt.
I am also really tempted to open up a paid MS support ticket for them to help me fix this problem. :)

How to configure Mailbox Read-Only access for Mailbox's owner on Exchange Server 2010?

I have to configure the Exchange Server 2010's mailbox to only grant Read-Only Access on the mailbox's owners. So they can only allowed to read their messages and cannot modify or remove them. Are there any references or methods to do?

Hi,alexchy8
We can make use of 2 PowerShell commands to achieve this goal.
Add-MailboxPermission and Add-MailboxFolderPermission.
Execute the Add-MailboxPermission command to delegate the read permission at mailbox level.
Execute the Add-MailboxFolderPermission command to delegate the required permissions on specific folders inside the mailbox.
You can read the following article as reference:
http://www.exchangedictionary.com/articles/assign-read-only-mailbox-permission-on-exchange-2010-2013-powershell
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety,
or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards.

Send As, Send on Behalf and Full Access for Exchange server 2010/2013

[This FAQ contains 2 parts]
Testing and watching the behavior of Send As, Send On Behalf and Full Access permission.
Common issue and Troubleshooting on the three permission.
[Testing and Watching]
Based on following blog, I decide to test on my lab:
Full Mailbox Access Rights + Send On Behalf = Send As ?
http://blogs.technet.com/b/ehlro/archive/2012/04/06/full-mailbox-access-rights-send-on-behalf-send-as.aspx
Description on my lab and test:
Exchange 2010 + Outlook 2010
Exchange 2013 + Outlook 2013
Senders: A01, A02, … , A07, A08
Recipient: A09
A01 grand permission to other senders.
Two methods:
a. Use A0x’s credential configure A01’s profile, then send From both A01 and A0x via Outlook. Watching result in A09’s Inbox and Sent Items which has message copy left.
b. Use A0x’s credential configure A0x’s profile, then send From both A01 and A0x via Outlook. Watching result in A09’s Inbox and Sent Items which has message copy left.
Result as following forms:
1. Exchange 2010 + Outlook 2010 / Exchange 2013 + Outlook 2013
Using A0x’s credential configure A01’s mailbox, then send From both A01 and A0x
To A09.
2. Exchange 2010 + Outlook 2010 / Exchange 2013 + Outlook 2013
Using A0x’s credential configure A0x’s mailbox, then send From both A01 and A0x
To A09.
[Common Issue]
1. [Issue]
Exchange 2010 + Outlook 2010. A01 grand A03 Send As permission. However A03 can’t send as A01 to A09 and get NDR:
You can’t send a message on behalf of this user unless you have permission to do so. Please make sure you’re sending on behalf of the correct sender, or request the necessary permission. If the problem continues, please contact your helpdesk.
Details as following pic:
[Troubleshooting]
1) Based on the NDR, it seems a permission issue. Check Send As permission, however the Send As permission configured correctly. Pic as below:
2) ince the Send As permission configured correctly, it seems the permission hasn’t been replicated. Try to restart Microsoft Exchange Information Store service. It works.
Note: The Send As permission isn’t granted until after replication has occurred. Replication times depend on your Exchange and network configuration. To grant the permission immediately, stop and then restart the Microsoft Exchange Information
Store service.
2. [Issue]
Exchange 2013 + Outlook 2013. A01 grand A03 Send As permission. However A03 can’t send as A01 to A09 and get NDR:
Your message did not reach some or all of the intended recipients.
Subject: xxx
Sent: xx/xx/2014 8:20 AM
The following recipient(s) cannot be reached: A09
This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-00000000-00000000].
Details as below:
[Troubleshooting]
1) Also check the Send As permission configuration first.
2) Then try to use A03 send as A01 to A09 via OWA. If OWA works well, it seems and issue on the Outlook client side.
3) This behavior may occur if the OAB in Outlook isn’t updated. Try to download OAB manually.
4) If doesn’t work, please close Outlook and try to delete all the OAB folder on your computer. The path of OAB folder in Win7, Win8 as below:
\Users\<UserName>\AppData\Local\Microsoft\Outlook\Offline Address Books
5) Restart Outlook.
Note: Be aware that you cannot send e-mail messages on behalf of a mailbox if the mailbox is hidden from address list. When sending a message, Exchange requires that e-mail address is resolved in the
From field.
3. [Issue]
Exchange 2010. A01 grant A0x “Send As” or “Send on Behalf” permission. A0x send as/ send on behalf of A01. The message is only copied to the Sent Items folder in A0x’s mailbox (same as the result of my test). Also cannot configure Exchange 2010 so that the
message is copied to the Sent Items folder of both A01 and A0x.
[Troubleshooting]
This issue occurs because Exchange server 2010 was designed to copy message to the Sent Items folder of the sender only. This issue can be solved by installing Exchange 2010 SP2 UR4. More details in the following KB:
Messages that are sent by using the "Send As" and "Send on behalf" permissions are copied only to the Sent Items folder of the sender in an Exchange Server 2010 environment
http://support.microsoft.com/kb/2632409/en-us
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Nice guide Mavis, I recently explored the same topic. Few things you might want to add is the type of connectivity (Cached vs Online will produce different results) and to expand further on the methods of adding the other mailbox in Outlook (additional mailbox
vs additional account defaults to different methods). Check the screenshot:
And please post this somewhere more visible, like blog/wiki page.

Need help with Outlook 2013 connecting to Exchange server(2010)

Hi
I need help with Outlook 2013 and with my exchange server(2010) email account
After setting up account initially emails come in and than after an hour or two stop. My OWA is working fine with no issues. I have even created a forward rule in OWA to my GMAIL account whch works fine
However Outlook 2013 is not syncing messages, have difficulty in sending emails sometimes as it takes too long. In fact the connection also is intermittent. Even if the task bar shows connected to exchange, it seems that is not the case since new emails
and any emails I compose dont work. I have trouble shot the issue with my ISP and email service provide, but they havent resolved the issue I have also done a TraceRoute and that shows no drops or problems to he exchange server.
Can someone please help me resolve this matter so I can continue to use Outlook 2013( running Windows 8.1) in both my computers which have the identical problem
Look forward to a solution soon
Thanks

Hi Angela
Thanks for your message
To answer your questions, please note the following
a) My account is set up in Cache Mode( not online mode)
b) I am the only other user on the account
c) When the connection to the exchange server is broken, I see upon clicking connection tab that there is no information in the box, and when I press reconnect it starts showing "connecting"
d) When the connection to the server is there, it shows connection as "established"
e) Sorry I dont understand th meaning of CAS array in your environment? Can you pls explain
Since yday I have been using Outlook 2010 on desktop and Outlook 2013 on my laptop using Exchange 2013 account. So far all emails are syncing, and I can send emails from both computers. However, I am concerned that the connection can break-off anytime,
as it has done that in the past on both outlook versions. The max time it has worked without any problem is 48 hrs and than after that the same issue of not connection, not syncing and unable to send emails happens
My ISP has checked and there is no network connectivity issues. My email service provider has trouble shot the issue many times, but to no positive results. I have also changed the profile a few times, but the intermittent connectivity problem hasn't
been resolved.
Can you identify the possible causes and more importantly a working permanent solution please
Thanks
Mahesh

Why the removed flag will be resumed after re-sync with MS Exchange server (2010)

Dear Sir:
     I had a big problem using Lion mail application. I like the program since it's quite simple and useful. But this problem makes me not able to work with Lion mail program continaully.
     In Lion mail, I import my office mail account which based on MS Exchange server 2010. I just found some mails (sorry I cannot fina any rule) which ever be flagged, when I try to un-flag them. The flag status will come back after re-sync with mail server. But the status doesn't happen with all mails I had. One thing I can confirm is, the "specific" mail doesn't be marked with any status after I checked them using Outlook application (both Mac Office 2011 or Windows Office 2010). Have you ever received similar feedback? Please help me to resolve this issue ASAP. Thank you.
-Joseph

When the original message is accessed using IMAP, the reply method uses the information in the
IMAP ENVELOPE to determine where to send the reply. It first looks for the Reply-To address
in the ENVELOPE, then the From address.
Interestingly, when not using IMAP, the getFrom method returns the Sender header if the From
header is empty. The IMAP-specific code doesn't do that, although perhaps it should.
It would be interesting to compare the ENVELOPE data from the protocol trace in the two cases.
The ENVELOPE data will follow this syntax:
envelope     = "(" env-date SP env-subject SP env-from SP
          env-sender SP env-reply-to SP env-to SP env-cc SP
          env-bcc SP env-in-reply-to SP env-message-id ")"
So it's the first three address fields after the Subject that are relevant. If the From and Reply-To
fields are NIL, but the Sender field has a valid address, let me know. I should probably fix the
IMAP provider to fall back to the Sender field if the From field is missing.

Exchange Server 2010: Incoming mail not delivered

I have an Exchange Server 2010 Standard with all recent patches and updates.
-It has been in service for 3 years without any issues.
-There is plenty of hard drive space for the logs and the data (over 100GB in each)
-The current size of the mail database is 150GB
-There is no registry entry in place limiting the size of the database ([url="http://technet.microsoft.com/en-us/library/bb232092.aspx"]Database Size Limit in GB as outlined here[/url]
Starting a few days ago, incoming mail is reaching the server but not being delivered to user mailboxes. Internal mail works fine when this happens. Looking at the Queue Viewer doesn't show anything abnormal. The Submission Queue shows nothing.
It is only after I reboot the Exchange Server that the Submission queue will show all the messages waiting to be delivered and they will all be delivered successfully after the reboot. The event logs do not show any error messages.
The server will continue to run fine for a few hours and then the problem starts all over again.
What could be causing this?

Any 3rd party antivirus/anti-spam software installed on the server? If so, disable and test.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange server 2010 mail limitation

Hi,
We have exchange server 2010 cashub1 and cashub2
and also we have edge1 and edge2.
my requirement is, i want all the exchange user to set limit of internal and external as 10 MB, except just 5 to 10 user we need to set limit as 50MB.
Can you please assist and provide the step by step configuration to setup the requirements.
Thanks in advance.

Does that 50MB limit apply to messages to and from the internet as well?
If so, then here is an example of one way to do this:
I would set all the limits to 50MB including the organizational limits.
Then create a hub transport rule that rejects any message with an attachment over 10MB with a rejection message and code of your choosing except when to and from a Group that you create that contains those 5-10 users who need to send messages as large as
50MB.
and, as always, test this very well before implementing!
More info:
http://technet.microsoft.com/en-us/library/bb124345(v=exchg.141).aspx
Understanding Message Size Limits
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange Server 2010 SP3 - Rollup 8 - Issue - Problems with client connections - MS Outlook 2013

Exchange Server 2010 SP3 - Rollup 8 - Issue - Problems with client connections - MS Outlook 2013
Detected Problems:
- Access denied for attached mailbox (department mailbox)
- Access denied for delete or move messages on own mailbox
- Can't send new messages with error (Error: [0x80004005-00000000-00000000])
Solution:
- Rollback to Exchange 2010 SP3 - Rollup 7
- You can rollback to Exchange 2010 SP3 - RollUp 7 in 30 min
Algunos de los destinatarios no recibieron su mensaje.
Asunto: Hola
Enviado el: 11/12/2014 8:35
No se puede localizar a los destinatarios siguientes:
'[email protected]' en 11/12/2014 8:35
Este mensaje no se pudo enviar. Inténtelo de nuevo más tarde, o póngase en contacto con el administrador de red.
Error: [0x80004005-00000000-00000000].

See the following forum thread:
https://social.technet.microsoft.com/Forums/en-US/1be9b816-b0ab-40ea-a43a-446239f8eae3/outlook-client-issues-following-exchange-2010-rollup-8

Exchange Server 2010 automatic reply once per day or once per week?

Hello,
can some tell me how often the automatic reply is send in Exchange Server 2010.
Is it once per day for each sender or once per week for each sender?
In the web some tell per week, some tell per day.
Is it possible to change the time shedule, so that each day a automatic reply is send?
Thanks,
Eduard

Hello,
after some googling and consolidating the different examples on the Internet I came up with this powershell script which is executed by the windows task scheduler once a day. The script first gathers all the mailboxes for which the out of office mechanism
is activated. Then it disables the autorepliers for these mailboxes, waits for 10 seconds (this seems to be necessary to let exchange do some housekeeping) and then reenables the autorepliers.
Warning: I have learned that this script resets the time interval of the autoreplier. Any ideas how to preserve the time settings?
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010
$objUsers = get-mailbox | Get-MailboxAutoReplyConfiguration | Where-Object {$_.AutoReplyState -eq "scheduled" }
$objUsers | %{ Set-MailboxAutoReplyConfiguration -Identity $_.identity -AutoReplyState disabled}
Start-Sleep -s 10
$objUsers | %{ Set-MailboxAutoReplyConfiguration -Identity $_.identity -AutoReplyState scheduled}
Remember to use -AutoReplyState scheduled instead of -AutoReplyState enabled to reenable. -AutoReplyState enable should only be used for permanent autorepliers and not for "out of office" messages.
Cheers,
Florian

Exchange Server 2010: Undeliverable Message

Similar Messages

Maybe you are looking for