none
DPM Client 0x80070005 Issue RRS feed

  • Question

  • Hi Everywone,

     

    I am really struggling with one System that just balantly refuses to work correctly. According to the DPMClientProtectionCurr.log the following does not occur:

     

    1484    0B64    12/06    14:43:36.316    33    dlsclientprotectionfactory.cpp(247)    [0000000000378940]        ACTIVITY    Principal name HOST/DH-W7.xxx.xx@xxx.xx
    1484    0B64    12/06    14:43:36.332    03    service.cpp(298)    [00000000000BFD70]        ACTIVITY    CService::AnnounceServiceStatus
    1484    0790    12/06    14:43:36.659    33    dlsclientprotection.cpp(703)    [00000000003789A0]        NORMAL    Connecting to DPM Server: (NAS-EDV.xxx.xx)
    1484    0790    12/06    14:43:37.328    33    dlsclientprotection.cpp(786)    [00000000003789A0]        WARNING    Failed: Hr: = [0x80070005] : Failed to set client OS details - ClientName:DH-W7.xxx.xx, ClientOSVersion:6.1.7601, OSType:2, AgentVersion: 3.0.7706.0
    1484    0790    12/06    14:43:37.328    33    dlsclientprotection.cpp(239)    [00000000003789A0]        WARNING    Failed: Hr: = [0x80070005] : F: lVal : ConnectToDPMServer(bstrClientMachineName, &pIUnknown, &fConnectionSuccessful, &dCurrentStatus, exceptionResult)

     

    The DPM Server can Contact the Client and the Client knows the Server is there. If an older client ist installed, the server offers an update, and installs it correctly. Both can ping each other. However, when the Server tells the client to Synch, the client reports it has not been initialized.

     

    Further Things done:

     

    • DCOM Reset
    • DPM Client Deinstall (Including Registry etc.)
    • DPM Client Reinstall
    • DPM Server Client Deinstall, Removal of Protection Group, Change of Protection Group
    • Client installed under local admin, domain admin, domain user (with admin rights)

    The result is the above error message and I really want to know why.

     

     


    • Edited by Eerazor Tuesday, December 6, 2011 3:36 PM
    Tuesday, December 6, 2011 3:36 PM

Answers

  • The Solution is a Simple one. Format the Computer that is affected by this error and then do the entire Procedure again. This solves the issue. This seems the ONLY way to solve this particular issue. Thanks to those that attempted to help at the beginning.
    • Marked as answer by Eerazor Thursday, April 12, 2012 10:22 AM
    Thursday, April 12, 2012 10:22 AM

All replies

  • Hi,

    Are you getting an error similar to this one:

    "The consistency check failed to trigger for client datasource as client initialization is pending. This will happen automatically when the client computer connects to the dpm server. (id: 32521)"

    If so, try running "dpmsync -DataCopied" on the DPM server and then sync the client. Let us know if this helps.

     

    Thanks,

    Marc

    • Proposed as answer by MarcReynolds Wednesday, December 7, 2011 1:07 PM
    Tuesday, December 6, 2011 8:30 PM
  • Hi Marc,

     

    thank you. I have run dpmsync on the server. As soon as the affected colleague is back in-house, I will let you know what happens.

     

    And yes, I am the getting server-sided error message you mentioned.

     

     

    Wednesday, December 7, 2011 10:35 AM
  • Hi Marc,

     

    ok I have done as instructed numerous times. The error message stated above remains. The DPM UI states that the administrator has not configured the backup. The DPM Server stats the same error message you mentioned.

     

    I have also restarted the DPM client and reinstalled it a few times, the issue remains unfortunately.

     

    Any other help is greatly appriciated because I am at a complete loss.

     

    Following another Thread, I have also attempted a Server-sided Push, which did not solve the issue either. 134 PCs are fine, just this one... the big boss one is being a pain. Not good.


    • Edited by Eerazor Thursday, December 8, 2011 11:08 AM
    Thursday, December 8, 2011 10:04 AM
  • Hi,

    As a test could you create a new protection group and add the problematic client to the new PG and test?

    Thanks,

    Marc

     

     

    Thursday, December 8, 2011 4:30 PM
  • Hi Marc,

     

    thank you. Have tried that also to no avail. The only other alternative I see is formating the affected client, and starting anew, which is not really an option (since all their data is supposed to be protected and not).

     

    Open for suggestions.

    Friday, December 9, 2011 10:03 AM
  • Hi,

    Are you logged into the client as user in the local administrator group when you try to sync?

     

    What error do you get when you attempt to sync from the DPM server?

    The error you are getting is showing an access denied (0X80070005)

    1484 0790 12/06 14:43:37.328 33 dlsclientprotection.cpp(786) [00000000003789A0] WARNING Failed: Hr: = [0x80070005] : Failed to set client OS details - ClientName:DH-W7.xxx.xx, ClientOSVersion:6.1.7601, OSType:2, AgentVersion: 3.0.7706.0

    Is it possible this client has the same NetBIOS name as another protected client or server?

    Thanks,

    Marc

    Tuesday, December 13, 2011 9:05 PM
  • I Marc, I had thought you had given up on me. Much appriciated.

     

    I checked:

    DHCP, DNS, Active Directory. Only one Entry found. So no, no duplicate whatsoever.

     

    I have found a second machine with this problem. Exact same issue (The DPM Server does not report an error because the mashine never managed to build a replication). What those two mashines have in common is the fact that the new client was installed manually. While all the others had the old client installed and then an update. Yet, doing the same with these two mashines, results in a big "FU" from the DPM Client.

     

    Other tips like selecting protective folders and then deselecting them again does not work on either, as they get the message that the Administrator has not configured them. It makes sense, looking at a configuration file from a working client and comparing it to these two, has the result, that the working one has an updated ClientProtectionDetails.xml and PSDataSourceConfig.xml. These are updated it seems on a daily basis on working clients. The non working ones have the installation timestamp and remain unchanged then. That explains at least the error as to WHAT he is trying to change.

     

    Question now is is - is there anyway to change that? I have given Full User Rights (manually) to the DPM Directory on the Client as well as Full Server Rights there too (ie. The Server can do what it wants there) yet the error prevails.

    Thursday, December 15, 2011 9:30 AM
  • Another Update:

     

    I have kicked the corresponding Computer out of the Domain after removing the DPM Client from the Computer and its entry on the Server. I then renamed said computer, put it back into the domain and installed the client again.

     

    Now a new issue has arisen. After setting setdpmname the DPM server is unable to communicate with the DPM Server.

    Monday, January 2, 2012 11:02 AM
  • The Solution is a Simple one. Format the Computer that is affected by this error and then do the entire Procedure again. This solves the issue. This seems the ONLY way to solve this particular issue. Thanks to those that attempted to help at the beginning.
    • Marked as answer by Eerazor Thursday, April 12, 2012 10:22 AM
    Thursday, April 12, 2012 10:22 AM
  • The Solution is a Simple one. Format the Computer that is affected by this error and then do the entire Procedure again. This solves the issue. This seems the ONLY way to solve this particular issue. Thanks to those that attempted to help at the beginning.

    What do you mean by "format the computer"? Reload the OS?
    Thursday, August 22, 2013 7:15 PM