UNSOLVED

Sigma1

updated

19 years ago

S

Sigma1

10 Posts

0

1626

August 7th, 2007 07:00

Backup Fails with RPC error

Below is the error that I am receiving. I have went through archived support forums and it stated to update to 7.4. I have done this on both the client and server and still am having this issue. It should be noted that all other backups on this client work except for the SYSTEM STATE. In addition, I have turned off any firewalls.

1 retry attempted
Registry - Error saving
39078:save: RPC error: RPC cannot encode arguments

7162:save: save of SYSTEM STATE:\ to backupserver failed

Thank you for all of your help.
  • amediratta

    2 Intern

    2014 Posts

    535

    0

    Posted August 7th, 2007 09:00

    RPC errors have a lot to do with network issues. Too much busy server can result it problematic SYSTEM STATE backups.
  • Sigma1

    10 Posts

    535

    0

    Posted August 7th, 2007 10:00

    Thank you for your response. However, this backup job is run very early in the morning, before anyone utilizes it during the day. Therefore, I do not believe it is a network performance issue. In addition, I have tried it at various times during the day.

    Thank you for al your help.
  • dpinink_silva

    2 Intern

    724 Posts

    535

    1

    Posted August 7th, 2007 11:00

    Are you using OFM? This error is reported sometimes with OFM installed, but also usually there's another line in the error, like:

    Registry - Cannot save Registry key SECURITY: 0x000000b7
    Registry - Error saving
    save: RPC error: RPC cannot encode arguments
    save: save of SYSTEM STATE:\ to

    Is this the error you're receiving?
  • Sigma1

    10 Posts

    535

    0

    Posted August 7th, 2007 12:00

    There are no other lines in the error, but how do I recognize whether or not I am using Open File Manager?
  • dpinink_silva

    2 Intern

    724 Posts

    535

    0

    Posted August 7th, 2007 13:00

    You can verify if there's any Open File Manager Service running, or at leasst if the software is installed.

    I've never seem this error without OFM, but you can try to expand the error message running a save of this saveset using verbose or debug options, from the client side.
  • ble1

    6 Operator

    14354 Posts

    56186 Points

    535

    0

    Posted August 8th, 2007 09:00

    ... and if OFM is not in the game go to client and run that backup manually from cmd line and see what happens.
  • 535

    0

    Posted August 9th, 2007 05:00

    Hi,

    First make sure OFM is installed or not. You can check for OFM services. IF yes then pause OFM services and then check system state backup. If still fails, Try to put NIC settings on full duplex mode. And also put server IP address into servcer network interface settings under the client resources.

    Regads
    Narendra Yadav
  • Flavio3

    2 Posts

    535

    0

    Posted July 15th, 2010 07:00

    Hi,

    Take a look in your Networker bit version x O.S bit version.

    They must be equal !

    I had this same problem one time and fixed it checking the bit version of them both.

    I.E: Networker 64bits x Windows Server 64.(OK!)

           Networker 32 bits xWindows Server 64.(Not Ok! System State Backups errors.)

    You can install a N.W 32 bits on 64 O.S, but you can find erros like this one.

    Regards!

    Flávio Novello

  • 535

    0

    Posted July 27th, 2010 08:00

    Additionally you may also check if the system state backup works from the client side.

    you can do so by using NW User.

  • elvinperez

    87 Posts

    66

    0

    Posted July 27th, 2010 11:00

    Hello,

    Verified the files hosts of both servers

    run nslookup backupserver, nslookup client, plus ping backupserver

    Regards,

    Elvin...