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

Similar Messages

Failed to roll HTTP log file Error at Startup WL 8.1

Hi people, i´m having the following error on the Weblogic 8.1 console at startup , the applications works fine but i´m always having this:
####<Oct 19, 2004 6:44:12 PM CDT> <Error> <HTTP> <computerName> <portalServer> <ExecuteThread: '11' for queue: 'default'> <<WLS Kernel>> <> <BEA-101242> <Failed to roll HTTP log file for the Web server: portalServer.
java.io.IOException: Failed to rename log file on attempt to rotate logs
     at weblogic.servlet.logging.LogManagerHttp.rotateLog(LogManagerHttp.java:200)
     at weblogic.servlet.logging.LogManagerHttp.keepStatsAndRollIfNecessary(LogManagerHttp.java:349)
     at weblogic.servlet.logging.LogManagerHttp.log(LogManagerHttp.java:391)
     at weblogic.servlet.internal.HttpServer.log(HttpServer.java:1137)
     at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1192)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2590)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
Does anyone know what do i need to do in order to solve this problem??
thanks a lot
Guillermo De La Rosa

I'm having the same error message. I also noticed that the server is running a bit slower and that beasvc.exe is using more memory that usual.Has anyone logged a technical support case??
Thanks.
####<Sep 20, 2005 10:15:28 AM EDT> <Info> <HTTP> <ddca2401> <myserver> <ExecuteThread: '44' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-101047> <[ServletContext(id=17209502,name=apps,context-path=/apps)] /*: Using standard I/O>
####<Sep 20, 2005 10:15:28 AM EDT> <Error> <HTTP> <ddca2401> <myserver> <ExecuteThread: '44' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-101242> <Failed to roll HTTP log file for the Web server: myserver.
java.io.IOException: Failed to rename log file on attempt to rotate logs
     at weblogic.servlet.logging.LogManagerHttp.rotateLog(LogManagerHttp.java:200)
     at weblogic.servlet.logging.LogManagerHttp.keepStatsAndRollIfNecessary(LogManagerHttp.java:349)
     at weblogic.servlet.logging.LogManagerHttp.log(LogManagerHttp.java:388)
     at weblogic.servlet.internal.HttpServer.log(HttpServer.java:1153)
     at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1197)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2574)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Hello. I keep my IPhoto library (about 90GB) on an external HD and am trying to back it up to another external drive. Both are formatted Mac OS Extended (Case-sensitive, Journaled). Recently, backup has failed from the start due to error 36. Howtoresolve?

Hello. I keep my iPhoto library (about 90GB) on an external HD and am trying to back it up to another external drive. Both are formatted Mac OS Extended (Case-sensitive, Journaled) and both check out when scanned with Disk Utility. Recently, backup has failed from the start due to error 36. Any ideas how to resolve? Also, what's the maximum recommended size for an iPhoto library file? Thx!

Since you can't drag the library to the other EHD for the backup see if you can duplicate it (if you have enough room on the drive) by selecting it and typing Command+d (duplicate).
If you do rebuild the library without a backup and it goes awry you won't lose your photos but you may lose your orgnaizational efforts. So try the following:
Fix #1
Launch iPhoto with the Command+Option keys held down and rebuild the library.
Select the options identified in the screenshot.
Fix #2
Using iPhoto Library Manager to Rebuild Your iPhoto Library
Download iPhoto Library Manager and launch.
Click on the Add Library button, navigate to your Home/Pictures folder and select your iPhoto Library folder.
Now that the library is listed in the left hand pane of iPLM, click on your library and go to the File ➙ Rebuild Library menu option
In the next window name the new library and select the location you want it to be placed.
Click on the Create button.
Note: This creates a new library in the location of your choosing based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments but not books, calendars or slideshows. The original library will be left untouched for further attempts at fixing the problem or in case the rebuilt library is not satisfactory.
NOTE: Fix 2 above might be the method you might want to try first with iPLM creating the new library on your second EHD. If it works that would get your backup copy on the second EHD at the same time as repairing it. If it does'nt work then go back to Fix 1.
OT

Log aborts, with Failed to open log file error

Flash Media server version 2.0.3 periodically fails to open
the log file and aborts logging. This seems to occur post log file
roll time as it occurs at c.01:50. Does anyone else have a similar
issue ?
I am running Falsh Media Server on windows 2003 server SE!
Any help would be much appreciated.

Are you trying to run this code from job or something? Check if account executing the package has access to the path. Also check if path value passed is correct. If its a remote system path pass it in UNC format (ie //machine/...)
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

SQL Server 2012 Developer Edition will not install. Setup files don't even get copied completely. Win 8.1. ACT instance is loaded & can't be deleted. From log file: Error: Action "PreMsiTimingConfigAction" failed during execution.

SQL Server 2012 Developer Edition will not install. Setup files don't even get copied completely. Win 8.1. ACT instance is loaded & can't be deleted. From log file: Error: Action "PreMsiTimingConfigAction" failed during execution.

Hello,
I am glad it worked.
Thank you for visiting MSDN forums!
Regards,
Alberto Morillo
SQLCoffee.com

'failed to open the PDF file' error - Indesign CS3 on Mac

Hi,
Whenever I place PDFs that were created by any other app besides indesign or Illustrator I get a 'failed to open the PDF file' error, previously these PDFs were fine to place but all of a sudden they're not... Help?
I'm not too keen on opening in Illustrator and resaving for the rest of the foreseeable future either...
Jared

Thanks for the reminder, Scott.
http://indesignsecrets.com/failed-to-open-pdf-error-show-options-to-fix-it.php
Bob

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.

Error vss writers exchange 2010 windows backup

I have this error, when running windows backup on server with exchange 2010:
Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {400de426-a419-459f-a953-91026051bf91}
   State: [8] Failed
   Last error: Retryable error
I've rebooted the server several times, but without success.
Does anyone have any idea?
Thank you
Cristiano Ianiri

Hi,
Do you have any running AV software? If there is, please set the AV Exclusion on database file or disable AV temporarily.
From the description, you have restarted server several times. It didn't work. To narrow down the issue, could you please restart the Microsoft Exchange Information Store service again on the server where you did backup at your convenience?
After that, please run the VSSadmin list writers command to determine whether the writer state returns to a stable state.
Besides, please check the database that you want to backup to see if it is in healthy state. You can use the get-mailboxdatabasecopystatus cmdlet to check this.
If you have checked steps above, please increase the diagnostic logging level for the Exchange Writer and check if there is any clues.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

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

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

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 Windows Server 2012 NLB and DAG on the same server

Hi all, I am installing Exchange 2013 infrastructure with two servers.
Both servers have the CAS and Mailbox roles.
For mounting on High Availability, will create a DAG.
Client Access I have no external Network Load Balancer.
I thought about installing the NLB servers in the DAG members, this could not be done before.
I do not know if in Windows Server 2012 and Exchange 2013
Can I install NLB on members of a DAG?
regards
Microsoft Certified IT Professional Server Administrator

Hi,
I’m afraid that WNLB and DAG cannot coexist in the same server. Because WNLB is incompatible with Windows failover clustering. If we're using an Exchange 2010 DAG and we want to use WNLB, we need to have the Client Access server role and the Mailbox server
role running on separate servers.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/ff625247(v=exchg.141).aspx
Thanks,
Angela Shi
TechNet Community Support

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

Windows Backup still failing with 0x81000032 error

I have been trying for days to fix this problem. Tried all suggested fixes, I have 40GB free on both the disks I want to backup (of sizes 200GB and 362GB), I am trying to backup to a 2TB usb disk with 766GB free. All disks are NTFS, I have changed drive
letters and names of backup disk and computers data partition.
Ran "chkdsk /f" which required a reboot, ran "sfc /scannow".
I have zipped and uploaded recent Errors.evtx to a zipped file (fail.zip) although I have omitted 4 events, which were user profile service warnings which said " 1 user registry handles leaked from \Registry\User" ...ect I omitted these as I was
worried there may have been sensitive info in them. backup has worked fine until a couple weeks ago when this happened.
https://www.dropbox.com/sh/l1d1txpl19aq9yy/AACdRVCylOmTCnpOpAjmKdRGa Thanks, Harry
mountain climber

Hi,
The error information is:
Windows Backup skipped backing up system image because one of the critical volumes cannot be included
for backup. Check that volume is online and is formatted NTFS. (0x81000032)
Typically, critical volumes include the boot volume and the system volume. Let’s check the following
path to find the target volume:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsBackup\Status
And collect Windows Backup log in following path:
%windir%\Logs\WindowsBackup
Alex Zhao
TechNet Community Support

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

Similar Messages

Maybe you are looking for