locked
Windows 10 anniversary update breaks WHS connector install RRS feed

  • Question

  • My backups on my windows 10 PC stopped when I installed the anniversary update.. I uninstalled the connector  and have now got the dreaded "WHS connector has encountered an unexpected error. Click Close to undo..."

    I have trolled all over the net for a solution and most of the solutions point to Windows 7 issues.

    Is there anything else I can do short of doing a full reinstall or going back to pre-anniversary update?

    I see this error  in my event view: "Product: Windows Home Server 2011 Connector - Update 'Update Rollup for Microsoft Windows (KB2757014)' could not be installed. Error code 1603. Additional information is available in the log file C:\ProgramData\Microsoft\Windows Server\Logs\ClientCore.msi.log."


    Friday, August 12, 2016 2:40 AM

Answers

  • Hi

    I had trouble with this myself but I found out that the problem was that  the following folder is missing:

    C:\Windows\System32\Task\Microsoft\Windows\Windows Server

    When I created Windows Server folder in C:\Windows\System32\Task\Microsoft\Windows\ the installation went without an error.

    I think the reason is that the Windows Server folder exist inside th Task Scheduler program but not on the filesystem.

    Arild


    Arild


    • Edited by Arild Wednesday, August 31, 2016 9:56 PM
    • Proposed as answer by illiam Thursday, September 1, 2016 3:12 PM
    • Marked as answer by Jeff Barnett Thursday, September 1, 2016 6:11 PM
    Wednesday, August 31, 2016 8:58 PM

All replies

  • Hi,

    According to your description, my understanding is that Connector failed to be installed on Widows 10 after anniversary update, with error "WHS connector has encountered an unexpected error. Click Close to undo...".

    Reference - SBS 2011: Troubleshooting Client Deployment (also applied to WHS 2011) – to further narrow down this problem:
    http://social.technet.microsoft.com/wiki/contents/articles/3941.sbs-2011-troubleshooting-client-deployment.aspx

    Best Regards,
    Eve Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, August 12, 2016 9:41 AM
  • Did you install the UEFI patch on WHS before the client update?

    I have it done long ago, and updating my home machine to Windows 10 AE did absolutely not show up with any issues.

    Best greetings from Germany
    Olaf

    Friday, August 12, 2016 2:49 PM
  • I too have this same error. I was instructed that WHS connector needs to be reinstalled after an upgrade and my attempt to do so after the anniv upgrade resulted in the same error.

    Looking through the logs, it seems that the error is thrown when the patch 'KB2757014-amd64.msp' attempts to patch 'BkDrvIns.exe' and cannot find it. Unfortunately, looking through the payload of the connector installer, this is not one of the files enclosed in ClientCore.msi. The closest is \Windows Server\Bin\BackupDriverInstaller.exe.

    Link to logs(3): http://pastebin.com/st1VjiQd



    • Edited by KenV2 Monday, August 15, 2016 5:00 PM
    Monday, August 15, 2016 5:00 PM
  • Well, the message tells something different than "cannot find":

    "The File 'BkDrvIns.exe' is not marked for installation."

    This kind of message I have seen mainly, if some Installer version was not cleaned from the registry from former installation.

    For such cases there was a tool, Microsoft Installer Cleanup Utility, which since then disappeared from Microsofts download pages due to side effects (which mainly happened if people did not know what they do).

    If you have access to the tool, you can try to remove the Connector entry and if it exists the above KB from the shown list and after that attempt the installation again. Otherwise you could try to delete that stuff from the registry directly, if you even more know, what you do.

    Best greetings from Germany
    Olaf

    Tuesday, August 16, 2016 10:29 AM
  • OK, I seem to have interpreted the log wrong.

    On line 1778 it states 'Doing action: RollbackBackupDriver' and then later 'The File 'BkDrvIns.exe' is not marked for installation.'

    I interpreted this as it was trying to rollback something that wasn't installed.

    Googling 'BkDrvIns.exe' comes up with absolutely nothing, which I found kind of amazing. And searching my entire server and W10 installation including .cab files also never finds that file, which seems somewhat mysterious to me.

    Tuesday, August 16, 2016 9:57 PM
  • Well, taking your advice and cleaning up any failed installations seemed to have helped with the initial error,

    However I am encountering another fatal error.

    Details at: http://pastebin.com/47Fgan0P

    In essence: After

    "Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIA4E9.tmp, Entrypoint: CAQuietExec"

    I get:

    "Exception has been thrown by the target of an invocation. ---> System.IO.DirectoryNotFoundException: The system cannot find the path specified."

    I don't have a directory named 'C:\WINDOWS\Installer' on either the client or the server, unless it is transiently created by the installer during the installation process.

    Wednesday, August 17, 2016 2:41 PM
  • Sure you have it. It is only one of those hidden system files and folders.

    Type C:\Windows\Installer in address bar of File Explorer and hit Enter.

    Best greetings from Germany
    Olaf

    Wednesday, August 17, 2016 3:27 PM
  • Yes, I discovered it's hidden. However the *.tmp file is not present. The actual filename seems to change for each attempt, so I would assume that it is somehow randomized.

    Unfortunately, the installer still fails with the same error each time.

    Thursday, August 18, 2016 11:15 AM
  • This tmp thing should not be a file, but a subfolder.

    So something should be extracted into that folder during installation and it isn't, therefor an item not found exception is raised.

    If I find the time, I will attempt a connector installation on my upgraded tablet, which has never seen WHS.

    Best greetings from Germany
    Olaf

    Thursday, August 18, 2016 11:24 AM
  • Thanks!

    Saturday, August 20, 2016 12:17 PM
  • Some further investigating shows that even thought the error shows that it cannot find the path, it is indeed transiently created:

    MSI (s) (EC:64) [16:43:55:904]: Executing op: ActionStart(Name=AddScheduledTasks,,)
    MSI (s) (EC:64) [16:43:55:904]: Executing op: CustomActionSchedule(Action=AddScheduledTasks,ActionType=3073,Source=BinaryData,Target=CAQuietExec,CustomActionData="C:\Program Files\Windows Server\Bin\runtask.exe" /asm:"%ProgramFiles%\Windows Server\Bin\ClientSetupCommon.dll" /class:Microsoft.WindowsServerSolutions.ClientSetup.ScheduledTasks.ClientTasks /method:AddScheduledTasks /task:AddScheduledTasks /suppressException:true)
    MSI (s) (EC:64) [16:43:55:905]: Creating MSIHANDLE (30) of type 790536 for thread 29796
    MSI (s) (EC:C8) [16:43:55:906]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI19DF.tmp, Entrypoint: CAQuietExec
    MSI (s) (EC!C8) [16:43:56:061]: Creating MSIHANDLE (31) of type 790531 for thread 25288
    CAQuietExec:  System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.DirectoryNotFoundException: The system cannot find the path specified. (Exception from HRESULT: 0x80070003)
    MSI (s) (EC!C8) [16:43:56:061]: Closing MSIHANDLE (31) of type 790531 for thread 25288
    MSI (s) (EC!C8) [16:43:56:061]: Creating MSIHANDLE (32) of type 790531 for thread 25288
    CAQuietExec:     at TaskSchedulerV2.ITaskFolder.RegisterTaskDefinition(String Path, ITaskDefinition pDefinition, Int32 flags, Object UserId, Object password, _TASK_LOGON_TYPE LogonType, Object sddl)
    MSI (s) (EC!C8) [16:43:56:061]: Closing MSIHANDLE (32) of type 790531 for thread 25288
    MSI (s) (EC!C8) [16:43:56:061]: Creating MSIHANDLE (33) of type 790531 for thread 25288
    CAQuietExec:     at Microsoft.WindowsServerSolutions.Common.ProviderFramework.SchedulerVersion2.RegisterTask(TaskDefinition definition)
    MSI (s) (EC!C8) [16:43:56:061]: Closing MSIHANDLE (33) of type 790531 for thread 25288
    MSI (s) (EC!C8) [16:43:56:061]: Creating MSIHANDLE (34) of type 790531 for thread 25288
    CAQuietExec:     at Microsoft.WindowsServerSolutions.ClientSetup.ScheduledTasks.ClientTasks.AddScheduledTasks()
    MSI (s) (EC!C8) [16:43:56:061]: Closing MSIHANDLE (34) of type 790531 for thread 25288
    MSI (s) (EC!C8) [16:43:56:061]: Creating MSIHANDLE (35) of type 790531 for thread 25288
    CAQuietExec:     --- End of inner exception stack trace ---
    MSI (s) (EC!C8) [16:43:56:061]: Closing MSIHANDLE (35) of type 790531 for thread 25288
    MSI (s) (EC!C8) [16:43:56:061]: Creating MSIHANDLE (36) of type 790531 for thread 25288
    CAQuietExec:     at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor)
    MSI (s) (EC!C8) [16:43:56:061]: Closing MSIHANDLE (36) of type 790531 for thread 25288
    MSI (s) (EC!C8) [16:43:56:061]: Creating MSIHANDLE (37) of type 790531 for thread 25288
    CAQuietExec:     at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments)
    MSI (s) (EC!C8) [16:43:56:061]: Closing MSIHANDLE (37) of type 790531 for thread 25288
    MSI (s) (EC!C8) [16:43:56:061]: Creating MSIHANDLE (38) of type 790531 for thread 25288
    CAQuietExec:     at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
    MSI (s) (EC!C8) [16:43:56:061]: Closing MSIHANDLE (38) of type 790531 for thread 25288
    MSI (s) (EC!C8) [16:43:56:061]: Creating MSIHANDLE (39) of type 790531 for thread 25288
    CAQuietExec:     at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Program._invokeMethod(Type classType, MethodInfo mi)
    MSI (s) (EC!C8) [16:43:56:061]: Closing MSIHANDLE (39) of type 790531 for thread 25288
    MSI (s) (EC!C8) [16:43:56:061]: Creating MSIHANDLE (40) of type 790531 for thread 25288
    CAQuietExec:     at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Program.Main(String args)
    MSI (s) (EC!C8) [16:43:56:061]: Closing MSIHANDLE (40) of type 790531 for thread 25288
    MSI (s) (EC!C8) [16:43:56:076]: Creating MSIHANDLE (41) of type 790531 for thread 25288
    CAQuietExec:  Error 0x80131604: Command line returned an error.
    MSI (s) (EC!C8) [16:43:56:076]: Closing MSIHANDLE (41) of type 790531 for thread 25288
    MSI (s) (EC!C8) [16:43:56:076]: Creating MSIHANDLE (42) of type 790531 for thread 25288
    CAQuietExec:  Error 0x80131604: CAQuietExec Failed
    MSI (s) (EC!C8) [16:43:56:076]: Closing MSIHANDLE (42) of type 790531 for thread 25288
    CustomAction AddScheduledTasks returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (EC:C8) [16:43:56:076]: Closing MSIHANDLE (30) of type 790536 for thread 29796
    MSI (s) (EC:64) [16:43:56:076]: Creating MSIHANDLE (43) of type 790531 for thread 29796
    08/20/2016 16:43:56.076 [30444]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 393

    File/Directory Monitor:

    ...
    Deleted (8/20/2016 4:43:55 PM): C:\Windows\Logs\WindowsUpdate\WindowsUpdate.20160810.152733.172.1.etl
    Modified (8/20/2016 4:43:55 PM): C:\Windows\Logs\WindowsUpdate\WindowsUpdate.20160820.163435.124.1.etl
    Modified (8/20/2016 4:43:55 PM): C:\Windows\Prefetch\RUNTASK.EXE-79B9D074.pf
    New (8/20/2016 4:43:55 PM): C:\Windows\Installer\MSI19DF.tmp
    Deleted (8/20/2016 4:43:56 PM): C:\Windows\Installer\MSI19DF.tmp
    Deleted (8/20/2016 4:43:57 PM): C:\Windows\Installer\MSI8C3.tmp
    New (8/20/2016 4:43:57 PM): C:\Windows\Temp\~DF61324AE3B888C091.TMP
    Deleted (8/20/2016 4:43:57 PM): C:\Windows\Temp\~DF564B37ADB7A77BCB.TMP
    New (8/20/2016 4:43:57 PM): C:\Windows\Temp\~DF4B19564CA100558B.TMP
    Deleted (8/20/2016 4:43:57 PM): C:\Windows\Installer\SourceHash{C1E4D639-4A33-4314-809E-89BD0EF48522}

    Sunday, August 21, 2016 10:32 AM
  • Olaf - where do I find the information on UEFI patch on WHS?

    Greetings from Canada

    Jeff


    Monday, August 22, 2016 8:24 PM
  • Hi,

    A hotfix is available to add backup support for UEFI-based computers to back up to servers that are running Windows Home Server 2011:
    https://support.microsoft.com/en-us/kb/2781272

    Best Regards,
    Eve Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, August 25, 2016 6:13 AM
  • Hi,

    A hotfix is available to add backup support for UEFI-based computers to back up to servers that are running Windows Home Server 2011:
    https://support.microsoft.com/en-us/kb/2781272

    Best Regards,
    Eve Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    I did apply this hot fix and one pc runs the Anniverary Update fine and the connector works. HOweever on a second pc initially the connector worked after the update to Windows 10 anniversary. However the client backup failed with the message that the Client computer backup provider service failed to start. The event log was not ver helpful but a noticed several .NET errors in the event log as well - is this all related? I tried reinstalling the connected but it got me back to the point of this whole thread - I could not install the connector

    I have no issue running this in Windows 10 but it appears the update breaks several things on my computer. Is there anything I can do to try and fix the .Net framework issues?

    Saturday, August 27, 2016 3:08 PM
  • Hi,

    >Is there anything I can do to try and fix the .Net framework issues?
    Reference blog “Introducing the Microsoft .NET Framework Repair Tool” and try to repair .Net Framework related problem:

    https://blogs.msdn.microsoft.com/dotnet/2014/04/28/introducing-the-microsoft-net-framework-repair-tool/

    >However the client backup failed with the message that the Client computer backup provider service failed to start.
    For this error message, in general, you may check to see if Client computer backup provider service dependent service is running. Or, have a manually restarting.

    Best Regards,
    Eve Wang


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 30, 2016 5:38 AM
  • Hi

    I had trouble with this myself but I found out that the problem was that  the following folder is missing:

    C:\Windows\System32\Task\Microsoft\Windows\Windows Server

    When I created Windows Server folder in C:\Windows\System32\Task\Microsoft\Windows\ the installation went without an error.

    I think the reason is that the Windows Server folder exist inside th Task Scheduler program but not on the filesystem.

    Arild


    Arild


    • Edited by Arild Wednesday, August 31, 2016 9:56 PM
    • Proposed as answer by illiam Thursday, September 1, 2016 3:12 PM
    • Marked as answer by Jeff Barnett Thursday, September 1, 2016 6:11 PM
    Wednesday, August 31, 2016 8:58 PM
  • After installing the anniversary update on my second computer, backups would not work. I uninstalled

    the build 1607 so the backups would work. After reading Arild’s post, I copied the Windows Server folder

    from C drive and put on my desktop. I reinstalled the anniversary update and again the machine would

    not do backups. I checked the Windows folder and the Windows Server folder was missing. I then

    copied the Windows Server folder on my desktop and put it into Windows folder. I restarted the computer

    and now everything works as it should. The connector works so I haven’t tried to reinstall it.

    Thanks Arild

    Thursday, September 1, 2016 3:14 PM
  • Hi,

    >Is there anything I can do to try and fix the .Net framework issues?
    Reference blog “Introducing the Microsoft .NET Framework Repair Tool” and try to repair .Net Framework related problem:

    https://blogs.msdn.microsoft.com/dotnet/2014/04/28/introducing-the-microsoft-net-framework-repair-tool/

    >However the client backup failed with the message that the Client computer backup provider service failed to start.
    For this error message, in general, you may check to see if Client computer backup provider service dependent service is running. Or, have a manually restarting.

    Best Regards,
    Eve Wang


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    I did the net framework repair and the connectors works fine - back up does not work as the  client computer backup server will not start. This is the error I get from the event viewer which I do not understand:

    The 'Windows Server Client Computer Backup Provider Service' service (WSS_ComputerBackupProviderSvc) failed while starting.  Additional error information: Unhandled exception in OnStart: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.DirectoryNotFoundException: The system cannot find the path specified. (Exception from HRESULT: 0x80070003)
       at TaskSchedulerV2.ITaskFolder.RegisterTaskDefinition(String Path, ITaskDefinition pDefinition, Int32 flags, Object UserId, Object password, _TASK_LOGON_TYPE LogonType, Object sddl)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.SchedulerVersion2.RegisterTask(TaskDefinition definition)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.ScheduledTaskManager.UpdateScheduledTask(Boolean forceUpdate)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.ScheduledTaskManager.CheckCompliance(Boolean forceUpdateScheduledTask)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.ScheduledTaskManager.OnStart()
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.PCBackupClientProviderRoot..ctor()
       --- End of inner exception stack trace ---
       at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
       at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.ServiceModel.Description.ServiceDescription.CreateImplementation(Type serviceType)
       at System.ServiceModel.Description.ServiceDescription.SetupSingleton(ServiceDescription serviceDescription, Object implementation, Boolean isWellKnown)
       at System.ServiceModel.Description.ServiceDescription.GetService(Type serviceType)
       at System.ServiceModel.ServiceHost.CreateDescription(IDictionary`2& implementedContracts)
       at System.ServiceModel.ServiceHostBase.InitializeDescription(UriSchemeKeyedCollection baseAddresses)
       at System.ServiceModel.ServiceHost..ctor(Type serviceType, Uri[] baseAddresses)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderHost.<>c__DisplayClass2.<.ctor>b__0()
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderHost..ctor(Type providerType, String providerId, IList`1 serviceContractInterfaces, ProviderFrameworkConfigurator configurator)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.PCBackupClientProviderMain.CreateProviderHosts()
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderServiceBase._OpenHosts()


    • Edited by Jeff Barnett Thursday, September 1, 2016 5:49 PM
    Thursday, September 1, 2016 5:49 PM
  • Hi

    I had trouble with this myself but I found out that the problem was that  the following folder is missing:

    C:\Windows\System32\Task\Microsoft\Windows\Windows Server

    When I created Windows Server folder in C:\Windows\System32\Task\Microsoft\Windows\ the installation went without an error.

    I think the reason is that the Windows Server folder exist inside th Task Scheduler program but not on the filesystem.

    Arild


    Arild


    Arild you are brilliant - this is the answer - I followed what iliam did and his solved my problem - Yes!!!!!!!!!!!!!!!!
    Thursday, September 1, 2016 6:12 PM
  • ... this:

    When I created Windows Server folder in C:\Windows\System32\Task\Microsoft\Windows\ the installation went without an error.

    Fixed the problem for me.

    After 'Googling' around for 3 days I found this thread and it solved my problem (root error exact the same as the initial post.

    Thank you o much, Great!


    Dirk Kuehl

    Friday, September 16, 2016 9:12 PM
  • Hi

    I had trouble with this myself but I found out that the problem was that  the following folder is missing:

    C:\Windows\System32\Task\Microsoft\Windows\Windows Server

    When I created Windows Server folder in C:\Windows\System32\Task\Microsoft\Windows\ the installation went without an error.

    I think the reason is that the Windows Server folder exist inside th Task Scheduler program but not on the filesystem.

    Arild


    Arild


    Arlid,

    I've NO idea how you ever discovered that problem, but simply adding that empty folder allowed my Connector to install, so I now have Lights-Out monitoring and Backups again!!

    Thanks a million!!!!!

    Ron


    Ron

    Saturday, September 17, 2016 2:36 AM
  • YES!  Arild, you are a computer GOD.  After weeks of trying every "fix" on the WEB, including hours on the phone with M$ Answers, the simply addition of an empty folder allowed me to re-install the connection software again after the installation of WIN10 AU!  I again have both the Launchpad and the Dashboard.  I now need to setup the backup process again.
    • Edited by 1 BigGuy Saturday, September 24, 2016 11:48 PM
    Saturday, September 24, 2016 9:42 PM
  • Creating this the folder in Tasks has now fixed two of my WIN10 AU desktops.  I had to fiddle some, start services and configure backups again, to get the backups working.  All seems to be well between the server connector and WIN10 AU now.

    I feel like I'm a beta tester for M$.

    Sunday, September 25, 2016 6:48 PM
  • I added the directory the first day, to two computers.  turned off IPv6.  They functioned fine.  then the next day I received an error about the backup process not working.  Tried to manual start the service and it failed.  So uninstalled connector on one machine to reinstall it (I have the folder created), and the connector fails to install now.  I can find no further information, but I'm getting the exact error where it can't run the process with "Quiet" in it.  But I've done everything in this thread.  No success.
    Tuesday, September 27, 2016 10:15 PM
  • Amazed that worked...

    Thanks for the post.

    • Proposed as answer by VoIPgate Saturday, October 1, 2016 10:37 PM
    Saturday, October 1, 2016 10:36 PM
  • Fixed my issue. Found a "Tasks_Migrated" folder with the windows server folder populated. Copied the Windows Server directory from here into both the system32/tasks... and system32/task... under the appropriate Microsoft directory and the connector installed without a hitch.  It also backed up without issue.  On the 2nd computer where I didn't uninstall the connector, but had backup issues, I repeated the copy of the populated "windows Server", rebooted, and the backup worked again with no issue.

    So just adding the folder didn't work for me.  I had to make sure the old files were put  back into it.

    Hope this helps others...

     
    Monday, October 3, 2016 5:18 PM
  • Thankyou

    Worked very well

    Simon

    Saturday, October 29, 2016 12:14 AM
  • Thanks,

    Worked for me on WHS 2008 R2 as well.

    Sunday, November 20, 2016 7:00 PM
  • Thank you. Added the folder and connector installed without any problems.
    Tuesday, December 20, 2016 2:13 PM