UNSOLVED

peterdwood

updated

20 years ago

0

879

June 8th, 2006 06:00

Intermittent errors

Hello, I just started working with the Networker product at a new job site. Intermittently the backups fail with the below information. I'm not having much luck finding a resolution. Has anyone seen this before and have any insights.

The servers are mostly Dell. Mostly Win2k Server (stnd/adv) the backend is a AIX box. I don't touch this box so I don't know much about the config.

Drives are configured like this

Dell Util part
Os Drive
Emergency partition (incase for a need to parrallel install.)
Data drives : mostly SAN storage



* server:SYSTEM FILES:\ 1 retry attempted

* server:SYSTEM FILES:\ System Files - Unable to determine system boot file location. No system boot files saved

* server:SYSTEM FILES:\ System Files - Error saving

* server:SYSTEM FILES:\ save: RPC error: RPC cannot encode arguments

* server:SYSTEM FILES:\ save: save of SYSTEM FILES:\ to server.domain.org failed
  • mg115301

    2 Intern

    100 Posts

    411

    0

    Posted June 9th, 2006 00:00

    You paste not many information here in this thread.

    Is the Win2k Server the Backup Server or client?

    We need the deamon.log to the same time, where you see this error.

    Which EBS version you have installed on clients/server?

    Which Win2k version with SP version.
  • 411

    0

    Posted June 9th, 2006 11:00

    Win2k server SP4 is the client.

    daemon.log from where, the BU Server?

    error occurs on servers with 7.3 jumbo 8 or jumbo 9.
  • 411

    0

    Posted June 9th, 2006 12:00

    System Files - Starting save
    save: SYSTEM FILES: WPFOW - sfcow_save: Saving boot and system protected files.
    save: SYSTEM FILES: WPFOW - GetVN4VMP returned 0x00000002
    System Files - Unable to determine system boot file location. No system boot files saved
    save: SYSTEM FILES: WPFOW - Error saving component
    System Files - Error saving
    save: SYSTEM FILES: WPFOW - ow_free called
    save: RPC error: RPC cannot encode arguments (severity 5, number 1)
  • ble1

    6 Operator

    14354 Posts

    56186 Points

    411

    0

    Posted June 11th, 2006 04:00

    error occurs on servers with 7.3 jumbo 8 or jumbo 9.

    Do you see that error only with that client? If you have 7.2.2 client installed on Windows box do you see it then too? (or initial 7.3 version)

    If this is 7.3 (or 7.3 jumbo patch) problem only then it looks like old friend might be back. It was an issue under win2k (we could not see it under win 2003) when something would be mapped to B: drive (or that drive letter would be assigned). It might not be your case, but it sounds like the same problem according to error print. I would suggest to check it out, confirm if you see this with other NW client releases (7.2.2 or 7.2.1) and if you confirm this as an issue with 7.3 code to open up this with your support.
  • 411

    0

    Posted June 14th, 2006 05:00

    It occurs with 7.2.2 and 7.2.1, Sometimes rolling back to 6.1 fixes it but not all the time
  • ble1

    6 Operator

    14354 Posts

    56186 Points

    411

    0

    Posted June 14th, 2006 06:00

    As I said, issue like this has been known under circumstances I explained before. It may be triggered in your environment for some other reason and might be fault not on NW side - I would suggest to open this with support first.