Exchange 2013 migration ends as Failed but the migration is OK

Hi
After Exchange 2013 SP1 I started getting this error when migration users to 2013 or within 2013.
We are now at CU5 and the problem remains.
When a migrations has come to the Synced or Successful state the ECP shows status Failed!
If you view details you see the right status. In the report you see no errors, all looks good.
So you you just synced a mailbox you have to complete the migration from PowerShell.
I see no event in the log about this.
I tried recreating the arbitration mailbox but no luck.
Is more a cosmetic problem but a bit annoying!
Anyone seen this?
Regards
Robert

Hi Robert,
Does the issue happen to all migrated mailboxes or just some specific mailbox?
Please click Refresh
Please use the Exchange Management Shell to display migration user statistics:
Get-MigrationUser -Identity [email protected] | FL
Get-MigrationUserStatistics -Identity TestUser@ contoso.com -IncludeReport | FL
Here is an article about Migration status report in EAC:
http://technet.microsoft.com/en-us/library/jj898491(v=exchg.150).aspx
If possible, please also collect the EAC screenshot about your issue and the commands results here without sensitive information for further analysis.
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

High Amount of Spam on Exchange 2013 - Content Filtering is Enabled but Pfizer Spam Filling Up Everyone's Mailboxes

Hello
Previously I used Exchange 2010 with Forefront Threat Protection installed and this used to do a good job of stopping all the spam.
However since updating to Exchange 2013 earlier this year and enabling the integrated spam filtering everyone noticed a sudden increase in the amount of spam which was getting through which has been bad for a long time.
We have been living with it but in the last 3 weeks everyone has started getting about 40 emails a day from Pfizer for Viagra. All these seem to defeat the content filtering as Viagra is spelt with an extra I and the email address is always different.
Also images in emails are blocked by default but somehow all the images on these spam messages appear for everyone.
I am not sure the spam filtering is working at all and I'm not sure how to tell as ForeFront gives you a nice graphical dashboard but I can find nothing similar to this in Exchange and PowerShell seems the only way to configure the limited functionality
of the content filter.
Is there any way to get rid of these messages as it doesn't look very good when they are constantly popping up for everyone?
Thanks
Robin
Robin Wilson

Hello ManU
Thanks for the reply.
I have checked the logs and see this quite often:
AcceptMessage,,SCL,not available: policy is disabled
But other times it says this:
RejectMessage,550 5.7.1 Message rejected as spam by Content Filtering
Which seems to indicate it is rejecting some.
This is what one of the email headers look like:
Received: from RWS-MAIL.rwsservices.net (192.168.2.151) by
RWS-MAIL.rwsservices.net (192.168.2.151) with Microsoft SMTP Server (TLS) id
15.0.775.38 via Mailbox Transport; Sat, 28 Dec 2013 10:59:26 +0000
Received: from RWS-MAIL.rwsservices.net (192.168.2.151) by
rws-mail.rwsservices.net (192.168.2.151) with Microsoft SMTP Server (TLS) id
15.0.775.38; Sat, 28 Dec 2013 10:58:38 +0000
Received: from [90.169.106.204] (90.169.106.204) by mail.rwsservices.net
(192.168.2.151) with Microsoft SMTP Server id 15.0.775.38 via Frontend
Transport; Sat, 28 Dec 2013 10:58:37 +0000
Date: Sat, 28 Dec 2013 12:05:58 +0200
From: US.Pfizer eStore <[email protected]>
To: robin.wilson <[email protected]>
Message-ID: <[email protected]>
Subject: Dear robin.wilson up to 65% OFF!
X-Mailer: Airmail (223)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="dd2ee3ea_586bb9e4_6f04"
Return-Path: [email protected]
X-MS-Exchange-Organization-PRD: 001-taxis.co.uk
X-MS-Exchange-Organization-SenderIdResult: Neutral
Received-SPF: Neutral (rws-mail.rwsservices.net: 90.169.106.204 is neither
permitted nor denied by domain of [email protected])
X-MS-Exchange-Organization-Network-Message-Id: e8825204-1f32-48be-a331-08d0d1d30209
X-MS-Exchange-Organization-SCL: 1
X-MS-Exchange-Organization-PCL: 2
X-MS-Exchange-Organization-Antispam-Report: DV:3.3.13223.464;SID:SenderIDStatus Neutral;OrigIP:90.169.106.204
X-EXCLAIMER-MD-CONFIG: 079171ba-394f-46d5-a160-56e416712e8e
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: rws-mail.rwsservices.net
X-MS-Exchange-Organization-AuthAs: Anonymous
The emails use a different sender email address every time and there is always a poem in very light grey writing in the body of the email. The drugs are always misspelt as well. Is this why these are getting through?
Thanks
Robin
Robin Wilson

Exchange 2013 Window Backup failure - fails to clean up log files - error FFFFFFFC

Hello,
We currently have an Exchange 2013 - Exchange 2007 coexistence setup.
1x Windows Server 2008 R2 with Exchange 2007 CAS/HUB
1x Windows Server 2008 R2 with Exchange 2007 MBX
1x Windows Server 2008 R2 with Exchange 2013 CU 3 (all roles)
Since our current backup solution (Symantec Backup Exec 2010 R3) does not support backing up Exchange 2013 CU3 databases, we are using the builtin Windows Backup feature to backup the Exchange 2013 CU3 databases.
This has functioned for a while, until all of a sudden, the log files are not cleared anymore, causing our log disk to fill up.
Our Exchange 2013 server looks like this:
C: Windows + Exchange installation
D: Databases
E: Database Log Files
F: Archive Databases
G: Archive Database Log Files
S: Dedicated backup volume
The backup is scheduled to run every day at 21:00 hours, performing a full VSS backup of D:,E:,F: and G: to the volume S:
Windows backup log says the backup completed with exceptions, leaving the Exchange logs untouched and filling the drive.
The Windows Backup Command Line tools are NOT installed since they are not compatible with Exchange 2013.
In the eventvwr we can see the following error:
The Microsoft Exchange Replication service VSS Writer (Instance a33ec440-7f12-4c50-806b-1bc5ceaf8aad) failed with error FFFFFFFC when processing the backup completion event.
The command VSSADMIN LIST WRITERS displays the following:
Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {cf84a907-76dc-428c-90e0-c18a3f9db493}
   State: [1] Stable
   Last error: Retryable error
Restarting the Microsoft Exchange Replication (MSExchangeRepl) clears the writer error, same with a reboot, however the error comes backup after the next backup.
Any thoughts on how to resolve this issue?
Thanks.

Hello,
Here is a blog for your reference.
http://blogs.technet.com/b/timmcmic/archive/2012/03/11/exchange-and-vss-my-exchange-writer-is-in-a-failed-retryable-state.aspx
If there is any useful information after you change the logging to expert, please free let me know.
Cara Chen
TechNet Community Support

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email
I am running Exchange 2013 and I have an end user who connects to it via Outlook 2010. All was going well till he went to forward an email and he noticed that the From button appeared and auto populated the sender's email address.
I have clicked the Empty Auto Complete List in Outlook's Send messages... still displayed the From tab when forwarding.
I recreated the profile in outlook... same thing.
I created the profile with outlook 2013... same thing.
There is only one user profile setup in Outlook.
(I know the from tab usually appears when you have multiple profiles setup in Outlook and/or when you configure the "From" tab.)
I opened the end user's email in Exch 2013's OWA... what was different here was when I clicked on the email and it opened, it did NOT have the Reply or Forward option... and it displayed as a "Draft" email.
Does anyone have any ideas?

So are you saying that the from button is filling the option with the original senders address (eg the person who sent the message to your user), or that it's filling in the your users address (in which case I don't understand what the issue is, since
it IS going from your user)?

Exchange 2013 SP1: Fix for failing MSExchangeTransport service

We had a newly updated Exchange 2013 SP1 that would not start the Transport service
"Netstat -b" showed that a service was listening to port 25 on all IP's (0.0.0.0:25) and when the service could not get the port, it would die, and Exchange would attempt to restart it over and over.
After many tears, I found this solution:
Through the console or the ECP, check the Frontend receive connectors and find the one that is listening on 0.0.0.0:25, which is probably the Default Frontend Receive. Disable it.
Restart the MSExchangeTransport and MSExchangeTransportFrontEnd services.
If both services restart normally, troubleshooting is complete.
We use several custom connectors carried forward from the previous installation, which was SBS 2008. If this applies to you, take notice.

Normally, the Default Frontend Receive Connector (0.0.0.0:25) is the messaging entry point for your organization (I am assuming that you have a single MBX/CAS server).
1. If you disable the Default Frontend Receive Connector (0.0.0.0:25), you block inbound email.
2. Most probably, the cause for your problem are the Custom Receive Connectors. Check their type, and if it is Hub Transport, delete and re-create them as Front End Receive connectors.
Step by Step Screencasts and Video Tutorials

I used scripting brigde to add a movie that has size bigger than 5GB, exactly after two minutes iTunes return a failed, but the processing of the file is actually added to iTunes Library successfully. The copying take more than 5 minutes to complete. Why?

I used scripting brigde to add a movie that has size bigger than 5GB, exactly after two minutes iTunes return a failed, but the processing of the file is actually added to iTunes Library successfully. The copying take more than 5 minutes to complete. Why the iTunes Scripting Brigde returned failed when it is actually success? It occurred exactly 2 minutes after submit the request to Scripting Brigde. Is this 2 minutes related to the Apple Event time out? if it does, how do I get around this problem? thx

I can tell you that this is some of the absolutely worst customer service I have ever dealt with. I found out from a store employee that when they are really busy with calls, they have third party companies taking overflow calls. One of those companies is Xerox. What can a Xerox call center rep possibly be able to authorize on a Verizon account? I'm Sure there is a ton of misinformation out there due to this. They don't note the accounts properly or so everyone can see them. I have been transferred before and have asked if they work for Verizon or a third party also and was refused an answer so, apparently they aren't required to disclose that information. I spent a long time in the store on my last visit and it's not just customers that get the runaround. It happens to the store employees as well and it's beyond frustrating.

After Migration Exchange 2013 does not send mail outside the organization

Dear,
After Migration Exchange 2010 to exchange 2013. We does not send email from the organization but we can received mail from others organization.
Delivery has failed to these recipients or groups:
[email protected] ([email protected]) The server has tried to deliver this message,
without success, and has stopped trying. Please try sending this message again. If the problem continues, contact your helpdesk.
Diagnostic information for administrators:
Generating server: OGMAIL.domain.net Receiving server: gmail.com (2607:f8b0:400c:c01::1a)
[email protected] 6/11/2014 10:16:10 AM - Remote Server at gmail.com (2607:f8b0:400c:c01::1a) returned '550 4.4.7 QUEUE.Expired; message expired' 6/11/2014
10:03:49 AM - Remote Server at gmail.com (2607:f8b0:400c:c01::1a) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10051, Win32 error code: 10051." Attempted failover
to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 2607:f8b0:400c:c01::1a:25'
Original message headers:
Received: from OGMAIL.domain.net (192.168.10.12) by ogmail.domain.net
(192.168.10.12) with Microsoft SMTP Server (TLS) id 15.0.847.32; Mon, 9 Jun
2014 16:13:30 +0600
Received: from OGMAIL.domain.net ([::1]) by ogmail.domain.net ([::1]) with
mapi id 15.00.0847.030; Mon, 9 Jun 2014 16:13:30 +0600
From: Administrator <[email protected]>
To: Administrator <[email protected]>
CC: IT.HW-Masudur Rahman-MRT <[email protected]>, "[email protected]"
<[email protected]>
Subject: RE: Migration batch mrtmove has completed successfully.
Thread-Topic: Migration batch mrtmove has completed successfully.
Thread-Index: AQHPd1JEcid9YEi4F0ue6m1039EwR5top+xp
Date: Mon, 9 Jun 2014 10:13:29 +0000
Message-ID: <[email protected]>
References: <[email protected]>
In-Reply-To: <[email protected]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.10.2]
Content-Type: multipart/alternative;
boundary="_000_6b0d846f503942d99d44be9aff8d6adfogmaildomainnet_"
MIME-Version: 1.0
Queue viewer:
Identity: ogmail\8786\3470333575194
Subject: testing
Internet Message ID: <[email protected]>
From Address: [email protected]
Status: Active
Size (KB): 4
Message Source Name: SMTP:Default OGMAIL
Source IP: 192.168.10.12
SCL: -1
Date Received: 6/23/2014 3:22:49 PM
Expiration Time: 6/25/2014 3:22:49 PM
Last Error:
Queue ID: ogmail\8786
Recipients: [email protected];2;2;[{LRT=};{LED=};{FQDN=};{IP=}];0;CN=SendMail,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=net;0
Md. Ramin Hossain

What I notice is Queue expired. The message is not going out.
Failed to connect. Winsock error code: 10051, Win32 error code: 10051." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.
This error states that It tried to connect to the target system but failed to connect out.
Is Exchange 2013 server added in the firewall rule to send communication over port 25?
Do you have use Front end proxy checkbox checked on the Send connector to internet that was created on 2013 (if created)?
If use front end proxy checkbox is checked, then you need to add permissions for your CAS server's IP in the Firewall for outbound port 25 rule. As it appears that the mail is originating from CAS to the firewall. If that checkbox is not checked, we need
to add the Mailbox server's IP on the outbound rule for port 25.

Exchange 2013 /m:recoverserver constantly failing due to MSExchangeSubmission.exe

Hi all,
I am trying to recover my lab Exchange 2013 server after removing a component of IIS messed all IIS functions, including all virtual directories.
The server is running on Hyper-V so I have removed and rebuilt the OS disk whilst the Exchange data resides on a separate disk. I've reset the computer account in AD and then run the command:
setup /m:recoverserver /targetdir:"d:\Program Files\Microsoft Exchange\v15" /DoNotStartTransport /IAcceptExchangeServerLicenseTerms
I have now done this a number of times and on each occasion it fails when attempting to start the Microsoft Exchange Transport Submission service. The error in the event log is as follows:
Log Name:      Application
Source:        Application Error
Date:          30/03/2013 20:18:53
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HV-E2K13
Description:
Faulting application name: MSExchangeSubmission.exe, version: 15.0.516.29, time stamp: 0x506956b8
Faulting module name: Microsoft.Exchange.Net.ni.dll, version: 15.0.516.27, time stamp: 0x5064072e
Exception code: 0xc00000fd
Fault offset: 0x0000000000639d07
Faulting process id: 0x1cc8
Faulting application start time: 0x01ce2d83cbb5568e
Faulting application path: D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll
Report Id: 0a1e3a42-9977-11e2-93f1-00155d0a4b05
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-03-30T20:18:53.000000000Z" />
    <EventRecordID>112812</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HV-E2K13</Computer>
    <Security />
</System>
<EventData>
    <Data>MSExchangeSubmission.exe</Data>
    <Data>15.0.516.29</Data>
    <Data>506956b8</Data>
    <Data>Microsoft.Exchange.Net.ni.dll</Data>
    <Data>15.0.516.27</Data>
    <Data>5064072e</Data>
    <Data>c00000fd</Data>
    <Data>0000000000639d07</Data>
    <Data>1cc8</Data>
    <Data>01ce2d83cbb5568e</Data>
    <Data>D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe</Data>
    <Data>C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll</Data>
    <Data>0a1e3a42-9977-11e2-93f1-00155d0a4b05</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>
Any thoughts?
Paul

Hi,
Im dealing with the same errors when i'm trying to restore our productive mailbox from a disaster.
I've tried everything listed here but last Milind Naphade commentary.
I'm in that right now, i ll tell if it's working soon.
Ty!
Hi Again. It Failed to start MSExchangeSubmission.exe
Here is the event on eventvwr (Some details on spanish wich is the language of my server)
Nombre de la aplicación con errores: MSExchangeSubmission.exe, versión: 15.0.516.29, marca de tiempo: 0x506956b8
Nombre del módulo con errores: Microsoft.Exchange.Net.ni.dll, versión: 15.0.516.27, marca de tiempo: 0x5064072e
Código de excepción: 0xc00000fd
Desplazamiento de errores: 0x000000000062f697
Identificador del proceso con errores: 0x7d0
Hora de inicio de la aplicación con errores: 0x01cfac0a0bb16a68
Ruta de acceso de la aplicación con errores: C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeSubmission.exe
Ruta de acceso del módulo con errores: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\b028905d8fd3faa99c9801b69b1500da\Microsoft.Exchange.Net.ni.dll
Identificador del informe: 4a9638fc-17fd-11e4-9404-000c29f101d8
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:
ExchangeSetup.log ends with:
[07/30/2014 15:19:10.0220] [1] The following 1 error(s) occurred during task execution:
[07/30/2014 15:19:10.0220] [1] 0. ErrorRecord: El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.
[07/30/2014 15:19:10.0220] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.
en Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
en Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
en Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
en Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
en Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
en Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
en Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[07/30/2014 15:19:10.0236] [1] [ERROR] The following error was generated when "$error.Clear();
start-SetupService -ServiceName MSExchangeSubmission
" was run: "El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.".
[07/30/2014 15:19:10.0236] [1] [ERROR] Service 'MSExchangeSubmission' failed to reach status 'Running' on this server.
[07/30/2014 15:19:10.0236] [1] [ERROR-REFERENCE] Id=MailboxServiceControlLast___23a36fed7b6947e0906f388b5a90135c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[07/30/2014 15:19:10.0251] [1] Setup is stopping now because of one or more critical errors.
[07/30/2014 15:19:10.0251] [1] Finished executing component tasks.
[07/30/2014 15:19:10.0267] [1] Ending processing DisasterRecovery-MailboxRole
[07/30/2014 15:19:10.0282] [0] No se completó la operación de instalación de Exchange Server. Puede encontrar más detalles en ExchangeSetup.log ubicado en la <SystemDrive>: carpeta \ExchangeSetupLogs.
[07/30/2014 15:19:10.0282] [0] End of Setup
[07/30/2014 15:19:10.0282] [0] **********************************************
Any suggestion please??? idk what else can i do!

Exchange 2013 SP1 readiness check failing

Trying to install our first Exchange 2013 SP1 server on Windows 2012 R2 in our datacentre, the readiness check fails with:
Error:
The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
There are many more errors relating to Enterprise admin rights etc.
Please note that:
My account is Domain admin, Schema admin and Enterprise admin member, it always has been.
I tried the built-in AD Administrator which of course is part of the groups as well, no difference.
Active Directory is at 2008 R2 for domain and forest functional levels.
I tried rejoining the new Exchange designated server to the domain
I've installed RSAT-ADDS, the Managed API 4.0 and all the other windows roles via powershell
There is a local domain controller that is a global catalog server on the new Exchange server subnet
I tried running the Exchange Setup on a different server on the same subnet as where the active 2010 Exchange server resides as well as the FSMO AD role holder resides, this works fine. I even did the AD prep from there no problem, that made no difference
on the datacentre server
AD replicates fine between the FSMO role holder and the Datacentre (no errors in dcdiag or repadmin /showrepl)
This error is in the event log:
The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ExSetupUI.exe
6724
Get Servers for domain.local
TopologyClientTcpEndpoint (localhost)
3
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0475315. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.ICommunicationObject.Open()
at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
the message resource is present but the message is not found in the string/message table

So I decided to re-install the OS, worked perfectly now. Only difference from before would be:
SCCM hasn't pushed SCEP 2012 to the new build of the same server yet
The original server was installed in a different AD site and then it was physically mode and reassigned to an new AD site and subnet
I might have installed the pre-reqs in a slightly different order (RSAT-ADDS, all the IIS etc things via powershell
and then the UCM API 4.0. (saw few comments that the order of how you install them matters in other forums).
10 or so Microsoft Windows updates haven't installed on the new OS build yet.
Other than that, its identical. But if its not broken don't fix it, perhaps the above can help someone else though.

Move Mailboxes from Exchange 2007 to Exchange 2013 (Could not find a valid mailbox migration for esta organization)

Hi all, I am in full migration from Exchange 2007 to Exchange 2013 and everything went correctly.
I have migrated several mailboxes and are working well. But a few days ago, when I try to migrate a mailbox I get the following error and can not migrate:
"Could not find a valid mailbox migration for this organization"
Do you know that you can be?
regards
Microsoft Certified IT Professional Server Administrator

Hi,
From your description, the issue should be related to the migration mailbox. I recommend you check if the following account is existed in ADUC.
Migration.8f3e7716-2011-43e4-96b1-aba62d229136
If this account does not exist, you need to run setup /prepareAD and then enable this migration mailbox to check the result.
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

Exchange 2013 Edge Transport install fails

I'm trying to install the Edge Transport for Exchange 2013 but it gets to step 7 of 9:
then give's the following error
Error:
The following error was generated when "$error.Clear();
new-ExchangeServer
" was run: "Value cannot be null.
Parameter name: Cannot get child of ADObjectId: this is a GUID based ADObjectId.".
Then in event viewer I have the following two events.
Watson report about to be sent for process id: 260, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, ExSetupUI, M.E.Data.Directory, M.E.D.D.ADObjectId.GetChildId, System.ArgumentNullException, 2ac6, 15.00.0847.031.
ErrorReportingEnabled: True
and
Exchange Server component Edge Transport Role failed.
Error: Error:
The following error was generated when "$error.Clear();
new-ExchangeServer
" was run: "Value cannot be null.
Parameter name: Cannot get child of ADObjectId: this is a GUID based ADObjectId.".
I've rebuilt the server but since it has something to do with the GUID I assumed it wouldn't work but I was grasping at straws and it didn't fix the issue.
I can run the setup again and it does finish but it doesn't show up in the list of servers in the ecp management. I've yet to find a solution on this issue if anyone has a suggestion or two it would be greatly appreciated.

Thanks for response.
when I run Get-ExchangeServer I get the following
Name Site ServerRole Edition AdminDisplayVersion
Exchange03 Edge Standard... Version
15.0 (Bu...
and the errors that are in the log
[02/17/2015 20:06:33.0084] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: ADAM is installed on this machine; only the Microsoft Exchange Edge Transport server role may be installed. See the Exchange setup log
for more information on this error.
[02/17/2015 20:07:50.0288] [1] The following 1 error(s) occurred during task execution:
[02/17/2015 20:07:50.0288] [1] 0. ErrorRecord: Service SMTPSVC was not found on computer '.'.
[02/17/2015 20:07:50.0288] [1] The previous errors were generated by a non-critical task and will be ignored.
then I have a load of error that failed to load dependency below is a small sample
[02/17/2015 20:07:57.0648] [2] Process standard output: Installing assembly C:\Program Files\Microsoft\Exchange Server\V15\bin\edgetransport.exe
Failed to load dependency Microsoft.Management.OData of assembly Microsoft.Exchange.Configuration.ObjectModel, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception
from HRESULT: 0x80070002)
Failed to load dependency Microsoft.Ceres.InteractionEngine.Processing.BuiltIn of assembly Microsoft.Exchange.Data.Storage, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified.
(Exception from HRESULT: 0x80070002)
Failed to load dependency Microsoft.Ceres.NlpBase.RichTypes of assembly Microsoft.Exchange.Data.Storage, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception
from HRESULT: 0x80070002)
Failed to load dependency System.IdentityModel.Tokens.Jwt of assembly Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception from
HRESULT: 0x80070002)
Failed to load dependency Microsoft.Passport.RPS of assembly Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception from HRESULT:
0x80070002)
Thanks

Exchange 2013 CU 6 update fails on transport service

i ran the update and it keeps getting the following error and i cannot find any info on the error
Exchange Server component Mailbox role: Transport service failed.
Error: Error:
The following error was generated when "$error.Clear();
          $feVdirName = "PowerShell (Default Web Site)";
          $beVdirName = "PowerShell (Exchange Back End)";
          $vdirName = "PowerShell";
          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";
          get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory
-DomainController $RoleDomainController;
          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back
End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");
          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false
-WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";
        " was run: "System.ArgumentException: The virtual directory 'PowerShell' already exists under 'MST-MAIL1.fibigroup.net/Exchange Back End'.
Parameter name: VirtualDirectoryName
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Hi,
Thanks for your response.
The error explains that the virtual directory 'PowerShell' already exists, so we need to remove the 'PowerShell' under "Default Web Site" and "Exchange Back End" firstly, and then continue to upgrade the Exchange 2013 CU6.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013: owa page shows up but returns bad request when logged in

Environment: Exchange 2013 CU6 /Windows Server 2012 R2
Just installed the patch yesterday, owa and ecp was working fine after the install but it broke for some reason.
was able to get ecp and powershell running but still cant up owa.
owa website can be accessed online, but once logged in it will throw errors below:
Firefox:bad request
IE:https://mail.domain.com/owa/auth.owa
tried to recreate Virtual directories for ecp and owa but to no avail.
both default website authentication shows basic,forms and fba (for ecp/owa)
checked IIS settings: no redirection details for both http redirect by default didnt touch it as well.
just wondering if anyone experienced the same and how they got it to be resolved, also is there a way to check what is the current authentication method for the backend server
not sure if i am checking it correctly but when i go to IIS>exchange back end, i cannot enable basic and forms as the same time...
thanks in advance

Hi,
From your description, I recommend you use the following cmdlet to change the authentication method of the "owa" virtual directory to Windows authentication.
Set-Owavirtualdirectory -identity "servername\owa (Exchange Back End)" -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false
And then run the following command on both the Client Access and Mailbox servers to restart IIS and check the result.
iisreset /noforce
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Users moved from Exchange 2007 to Exchange 2013 unable to access mails on the mobile devices

New mailbox if created on Exchange 2013 works fine. But moved users from Ex2k7 to EX2k13 do not works. Here are the errors on the exchange server 2013 IIS logs:
For android -- DevOS:Android_S110_Error:System.ArgumentOutOfRangeException_ADWR
For iphone -- DevOS:iOS+8.1.1+12B436_S110_Error:System.ArgumentOutOfRangeException_As
Exhange 2013 is on Cumulative update CU6
Any clue.

Hi,
have you tried to recreate activesync profile?For IOS devices you could try to reset Network setting by doing the following:
Settings
General
Reset
Reset network settings
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Exchange 2013: Content Index State Failed

I am running two, two node DAG's with Exchange 2013.
One DAG pair is running 5 databases with Server 2012 Standard and the second DAG pair is running Server 2008 R2 SP1 Standard with a single shared database.
No matter what I try, ALL 6 databases show "ContentIndexState: Failed" with "ContentIndexErrorMessage: An internal error occurred for the database or its index.".
I have tried rebuilding the indexes manually, automatically and manually copying the database files between servers. I also receive errors when trying to failover the databases because the content index state is failed.
In my test environment I have a very similar setup working fine with no issues.
Please let me know what I can try to get this resolved.
The error I receive when running the following set of commands is:
suspend-MailboxDatabaseCopy dag2db1\mbox1
update-MailboxDatabaseCopy dag2db1\mbox1 -deleteexistingfiles
[PS] C:\Windows\system32>update-mailboxdatabasecopy dag2db1\mbox1 -deleteexistingfiles
Confirm
Are you sure you want to perform this action?
Updating database copy DAG2DB1\MBOX1 on server MBOX1
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): a
WARNING: Seeding of content index catalog for database 'DAG2DB1' failed. Please verify that the Microsoft Search (Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: Therevwas no endpoint listening
at net.tcp://localhost:17063/Management/SeedingAgent-0A2745DF-4522-42AB-9115-5DDE9EDEF1C612/Single that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details..
[PS] C:\Windows\system32>

Hi Folks,
Here we go;
"On
August 14th, we announced the removal of the
MS13-061 Security Update for Exchange Server 2013 due to an issue where the patch changed settings for the search infrastructure, placing the content index for all databases into a failed state. As of today, we have released updated security updates
for both Exchange 2013 RTM CU1 and Exchange 2013 RTM CU2."
Details below;
http://blogs.technet.com/b/exchange/archive/2013/08/27/now-available-updated-release-of-ms13-061-security-update-for-exchange-server-2013.aspx
Yavuz Eren Demir
After installing this patch (Exchange2013-KB2874216-v2-x64-en.msp) seeding of the databases was impossible.
Error:
warning
Seeding of content index catalog for database 'Database02' failed. Please verify that the Microsoft Search (Exchange) and
the Host Controller service for Exchange services are running and try the operation again. Error: Could not connect to net.tcp://localhost:3863/Management/SeedingAgent-F293698C-B2D0-40CA-A2C3-FB37982E708712/Single. The connection attempt lasted for a time
span of 00:00:02.0592000. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:3863. .
Looking at the two services mentioned in this warning I've noticed the Microsoft Exchange Search Host Controller (HostControllerService)
was disabled
After Changing it to Automatic and enabling it, the problem was salved

Exchange 2013 migration ends as Failed but the migration is OK

Similar Messages

Maybe you are looking for