locked
Can't remove computers from the dashboard RRS feed

  • Question

  • I'm trying to remove a couple of computers that no longer exist on my network and I'm getting "Cannot remove the computer from the server - The removal process could not finish because of an unexpected error.  To remove this computer, run this task again."

    And of course I run the task again and get the same error.  I manually archived my existing backup database and created a new backup database thinking that might be the source of the issue - and even with a completely new and empty backup database I still get the error.  Ack!

    Anyone know of a manual process to purge old/unneeded computers from the console?  I have a new machine I'd like to add, but I'm at my 10 machine limit.  Thanks!

    Tuesday, September 25, 2012 7:35 AM

Answers

  • Hi,

    I suggest that you could download the Windows Server Solutions Log Collector Tool to verify the issue:

    Title: Windows Server Solutions Log Collector Tool

    URL: http://www.microsoft.com/en-us/download/details.aspx?id=27567

    Since the Activities are included in the Dashboard, you could verify the dashborard.log to find whether there are some clues in it.

    At the same time, please let me know whether all the computers are affected or some of them. Have you tried to remove the computer from the dashboard in SAFE MODE?

    Regards,

    James


    James Xiong

    TechNet Community Support

    • Proposed as answer by James Xiong Thursday, October 4, 2012 2:49 AM
    • Marked as answer by James Xiong Friday, October 5, 2012 2:22 AM
    Friday, September 28, 2012 5:58 AM

All replies

  • Nothing, eh?  Shoot.  Will have to do some more googling then...
    Friday, September 28, 2012 4:13 AM
  • Hi,

    I suggest that you could download the Windows Server Solutions Log Collector Tool to verify the issue:

    Title: Windows Server Solutions Log Collector Tool

    URL: http://www.microsoft.com/en-us/download/details.aspx?id=27567

    Since the Activities are included in the Dashboard, you could verify the dashborard.log to find whether there are some clues in it.

    At the same time, please let me know whether all the computers are affected or some of them. Have you tried to remove the computer from the dashboard in SAFE MODE?

    Regards,

    James


    James Xiong

    TechNet Community Support

    • Proposed as answer by James Xiong Thursday, October 4, 2012 2:49 AM
    • Marked as answer by James Xiong Friday, October 5, 2012 2:22 AM
    Friday, September 28, 2012 5:58 AM
  • Thanks James.  The machine is headless and has no local VGA so safe mode will be a challenge - I'll have to temporarily move the hard drives to a different box.

    Below is the section of the dashboard log - the following line is the only thing that stands out:  [2045020] 121230.102659.2812: ComputersPage: RemoveMachineIdentityCompletionCallback: Failed with error=ProviderNotAvailable, nativeCode=-1

    [2045020] 121230.102653.4566: ProviderFramework: Information: [0] : (current thread: 0x1f345c): Installing new PfSynchronizationContext.
    [2045020] 121230.102653.4566: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider, True, 
    [2045020] 121230.102653.4636: ProviderFramework: Information: [0] : (current thread: 0x1f345c): PfSynchronizationContext not needed.
    [2045760] 121230.102653.4746: ProviderFramework: Information: [0] : ProviderConnector: received ProviderInfo Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider net.tcp://wsbackupserver:6602/Microsoft.WindowsServerSolutions.wssg_pc_backup_server/Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider
    [2045760] 121230.102653.4756: ProviderFramework: Information: [0] : ProviderConnector: Beginning connection attempt for Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider
    [2045760] 121230.102653.4766: ProviderFramework: Information: [0] : CreateWithCallback: Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider
    [2045760] 121230.102653.4776: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
    [2045760] 121230.102653.4786: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider]
    [2045760] 121230.102653.4786: ProviderFramework: Information: [0] : Address: [net.tcp://wsbackupserver:6602/Microsoft.WindowsServerSolutions.wssg_pc_backup_server/Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider]
    [2045760] 121230.102653.4796: ProviderFramework: Information: [0] : Binding: [net.tcp]
    [2045760] 121230.102653.4796: ProviderFramework: Information: [0] : Identifier: [Microsoft.WindowsServerSolutions.wssg_pc_backup_server]
    [2045760] 121230.102653.4796: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowRemoteAccess]
    [2045760] 121230.102653.4806: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [User]
    [2045760] 121230.102653.4806: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
    [2045020] 121230.102653.4886: Backup: Trying to connect to provider Async.
    [2039128] 121230.102653.4946: Backup: Waiting for connection with the provider.
    [2045760] 121230.102653.5186: PfBinding: Information: [0] : Setting Windows ClientCredential to , *, 
    [2045760] 121230.102653.5196: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
    [2045636] 121230.102655.8608: ProviderFramework: Information: [0] : ProviderConnector: Received connection
    [2045636] 121230.102655.8618: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider
    [2045636] 121230.102655.8668: Backup: New connection detected. Try fetching all data
    [2045636] 121230.102656.7169: Backup: Connected to Provider Successfully
    [2047952] 121230.102656.8029: ProviderFramework: Information: [0] : (current thread: 0x1f3fd0): PfSynchronizationContext not needed.
    [2047952] 121230.102656.8029: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.Devices.Identity.IMachineIdentityProvider, True, 
    [2045760] 121230.102656.8089: ProviderFramework: Information: [0] : ProviderConnector: received ProviderInfo Microsoft.WindowsServerSolutions.Devices.Identity.IMachineIdentityProvider net.tcp://wsbackupserver:6602/Microsoft.WindowsServerSolutions.MachineIdentityProvider/Microsoft.WindowsServerSolutions.Devices.Identity.IMachineIdentityProvider
    [2045760] 121230.102656.8089: ProviderFramework: Information: [0] : ProviderConnector: Beginning connection attempt for Microsoft.WindowsServerSolutions.Devices.Identity.IMachineIdentityProvider
    [2045760] 121230.102656.8099: ProviderFramework: Information: [0] : CreateWithCallback: Microsoft.WindowsServerSolutions.Devices.Identity.IMachineIdentityProvider
    [2045760] 121230.102656.8109: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
    [2045760] 121230.102656.8109: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.Devices.Identity.IMachineIdentityProvider]
    [2045760] 121230.102656.8119: ProviderFramework: Information: [0] : Address: [net.tcp://wsbackupserver:6602/Microsoft.WindowsServerSolutions.MachineIdentityProvider/Microsoft.WindowsServerSolutions.Devices.Identity.IMachineIdentityProvider]
    [2045760] 121230.102656.8119: ProviderFramework: Information: [0] : Binding: [net.tcp]
    [2045760] 121230.102656.8129: ProviderFramework: Information: [0] : Identifier: [Microsoft.WindowsServerSolutions.MachineIdentityProvider]
    [2045760] 121230.102656.8129: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowRemoteAccess]
    [2045760] 121230.102656.8129: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [Machine]
    [2045760] 121230.102656.8139: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
    [2045760] 121230.102656.8189: PfBinding: Information: [0] : Adding service dns identity [WSBACKUPSERVER] in proxy endpoint.
    [2045760] 121230.102656.8379: PfBinding: Information: [0] : Assigning certificate to X509CertificateInitiatorClientCredential.
    [2045760] 121230.102656.8429: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
    [2045760] 121230.102657.5590: ProviderFramework: Information: [0] : ProviderConnector: Received connection
    [2045760] 121230.102657.5600: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.Devices.Identity.IMachineIdentityProvider
    [2045760] 121230.102657.5660: IDENTITY: Connection made
    [2045020] 121230.102657.5930: IDENTITY: First try for <RemoveMachine>b__1
    [2045020] 121230.102659.2812: ComputersPage: RemoveMachineIdentityCompletionCallback: Failed with error=ProviderNotAvailable, nativeCode=-1


    Sunday, December 30, 2012 3:56 PM
  • At the same time, please let me know whether all the computers are affected or some of them.


    I have tried to remove all of them and they all display the issue.
    Sunday, December 30, 2012 3:57 PM
  • I have the same issue. I recently changed the name of my WHS2011 machine and I think this may be related to that. Did you ever find a solution?
    Monday, May 27, 2013 1:27 PM
  • I am having exactly the same issue with WHS2011  - did you get your problem resolved elsewhere?
    Sunday, August 14, 2016 9:23 AM