locked
Reconnected Client Won't Backup RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a WS2012E server with a clean install from scratch.  There are 4 clients attached, two Win7 Home Premium, one Win7Pro, and one Win8 (non-Pro). After the initial server installation and client connects, everything was working fine... until my 18 month old granddaughter walked into my office and pushed the server's reset button. (She probably wanted to see the lights blink like her other toys!). After the server rebooted, the client backups stopped. I was able to restart the automatic client backups on three clients by disabling and then resetting up the backups. However this did not work on the fourth Win7Pro client. When a backup started on the fourth client, I got a message saying the client was not connected to the server in spite of being able to access the shared folders.

    I then uninstalled the windows connector and reboot the computer. When I then tried to log on as the user (not system administrator), I got the following message: "The security database on the server does not have a computer account for this workstation trust relationship". I tried renaming the Win7Pro client to another name but still got the same error.  I fixed that problem by logging on as a local user, "unjoining" the domain by joining a workgroup, and then rejoining the domain.  I then ran the connector program and I was back on the domain.

    However, the client backups will still not run.  If I start a backup from the launchpad, I get the following error message:"Backup cannot run because the computer cannot connect to the server.  To ensure that the backup runs, make sure that the computer can connect to the server."  However, the Dashboard shows the client computer is connected.

    From there, using the Dashboard on the server, I disabled backups on the client and then tried to set up backups again.  However, when trying to reestablish backups, I got the error message saying, "Backup cannot connect to the Windows Server Client Computer Backup Provider Service on your network computer.  If this problem presists, you may be able to resolve the issue by restarting the client computer."  After restarting the client computer, the same thing happens.  When I use the Dashboard from the client and try to reestablish backups, I get the same message.

    So it sounds like a service on the client did not get restarted or reinstalled, but I'm not sure what to look for.  Can anyone give me some hints?  Thanks in advance.

    BTW, I've installed a plexiglass shield over the server's front panel.  We are a small family business run out of our home and I don't want to lock my granddaughter out of my office!

    Thanks, Bob

    Sunday, June 9, 2013 4:50 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I think I would uninstall any services related to the domain from control panel/programs, disjoin the computer from the domain, rename the computer, (maybe even purge the old computer names from ADUC via the console), and run the http://servername/connect wizard to rejoin the station to the domain.

     

    Larry Struckmeyer[SBS-MVP]

    • Marked as answer by Andy Qi Thursday, June 20, 2013 10:06 AM
    Monday, June 10, 2013 1:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I know the network thing was a bit of a longshot, I was just trying to make sure we didn't miss anything. 

    You mentioned checking the Windows Server Client Computer Backup Provider Service on the client?  Another TechNet article for this issue on Server 2011 mentions checking the service on the Server as well, even though the error message refers to the client.  Turns out there are two services on the server, the "Windows Server Client Computer Backup Provider Service" and the "Windows Server Client Computer Backup Service". This  and another MS article on troubleshooting backups instructs you to make sure that these are both started. 

    Beyond that, a restore of the client system is the only other thing that comes to mind.


    • Marked as answer by Andy Qi Thursday, June 20, 2013 10:07 AM
    Wednesday, June 12, 2013 10:03 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Heh, despite the long name, that is in fact the actual service name it shows under services.  Try running services.msc and find "Windows Server Client Backup Provider Service," then restart it.
    Sunday, June 9, 2013 9:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for the suggestion.  I verified that the service is running, along with its two dependent process.  What should I check from here?

    Thanks, Bob

    Sunday, June 9, 2013 11:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I think I would uninstall any services related to the domain from control panel/programs, disjoin the computer from the domain, rename the computer, (maybe even purge the old computer names from ADUC via the console), and run the http://servername/connect wizard to rejoin the station to the domain.

     

    Larry Struckmeyer[SBS-MVP]

    • Marked as answer by Andy Qi Thursday, June 20, 2013 10:06 AM
    Monday, June 10, 2013 1:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I already uninstalled the connector, removed the client from the server, renamed the computer, and reinstalled the connector.  As far as "...uninstall any services related to the domain from control panel/programs", I believe the connector is the only item that would apply to.

    Backup won't start on TechNet

    Monday, June 10, 2013 5:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    just my two cents...

    First and foremost I would do a restore. Anytime the server changes configurations or isn't performing as intended after a change I would restore to backup. Since default backup settings configure two backups per day(assuming you didn't change these settings) you should be able to restore from a previous backup.

    As far as troubleshooting backups... check the system logs. logs can give you a much better idea of what is going on than just the dashboard error message. Also check the computer manager backup mmc.


    • Edited by letmebang Monday, June 10, 2013 11:50 PM
    Monday, June 10, 2013 11:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    gosh I almost forgot... make sure you are using the essentials wizards to make your configurations and not making changes that would not have been supported by the wizard. For example, turning off an IIS setting from IIS manager and now RWA no longer works... or joining and rejoining a computer to the domain without using the connector software.

    good luck.


    • Edited by letmebang Monday, June 10, 2013 11:56 PM
    Monday, June 10, 2013 11:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks.  I only use the wizards because I am not an IS type.  That's why I am using WS2012E, for the setup wizard.  Otherwise I'd be using WHS2011 if it wasn't for the 2 TB limit.

    Also, when I try to do a server system restore, it will only let me pick the latest restore, and it was made after the problem started.  If I want to do a file restore, I can pick any date I want.  If I try to do a system restore from the installation disk and then select the repair option, the server will only let me pick the most recent backup.  Any idea why that is happening?

    However, automatic client backup for the other three clients on my network is working just fine making me think the problem is with the one client, not the server.

    Backup won't start on TechNet


    • Edited by Bob Marso Tuesday, June 11, 2013 12:19 AM
    Tuesday, June 11, 2013 12:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Sorry to hear you're still having this problem.  This may be  just throwing stuff at the wall on my part, but have you tried going at it from a network troubleshooting point of view?  Say, power-cycling the router and any access point if you have them,  seeing if you can ping the PC from the server, that sort of thing?  I know you said the client was showing up on the server dashboard, but it's possible that might not give the whole picture. 
    Also, when you say you ran the connector program, do you mean the one your downloaded originally, or did you download another one after trying these other steps?  I'm wondering if the connector may be customized at the time of download according to whatever network conditions the server detects?

    • Edited by AGrush Tuesday, June 11, 2013 4:02 AM
    Tuesday, June 11, 2013 3:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    If you read my description, you'll see the network is working fine.  The other clients are not experiencing this problem, only this one client.

    The connecter used is supplied by the server, and the server has automatic updates enabled.  I have also manually forced the server to check for updates.

    The only other course of action I can think of at this time is to reinstall Windows from scratch on the client.  Does anyone else have any ideas?

    Backup won't start on TechNet

    Wednesday, June 12, 2013 5:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I know the network thing was a bit of a longshot, I was just trying to make sure we didn't miss anything. 

    You mentioned checking the Windows Server Client Computer Backup Provider Service on the client?  Another TechNet article for this issue on Server 2011 mentions checking the service on the Server as well, even though the error message refers to the client.  Turns out there are two services on the server, the "Windows Server Client Computer Backup Provider Service" and the "Windows Server Client Computer Backup Service". This  and another MS article on troubleshooting backups instructs you to make sure that these are both started. 

    Beyond that, a restore of the client system is the only other thing that comes to mind.


    • Marked as answer by Andy Qi Thursday, June 20, 2013 10:07 AM
    Wednesday, June 12, 2013 10:03 PM