UNSOLVED

KruthiMahadevap

updated

10 years ago

0

2475

March 15th, 2017 04:00

i have client with Networker 7.4.5 version, getting RPC error by generating WMIC.exe faulting application on windows 2008 R2 machine COuld anyone help here

i have client with Networker 7.4.5 version, getting RPC error by generating WMIC.exe faulting application on windows 2008 R2 machine COuld anyone help here

  • wlee

    263 Posts

    922

    0

    Posted March 15th, 2017 07:00

    Please look at the system and application event logs for complete details regarding this error.

    That being said, find out the following:

    When did this problem start?  What event(s) occur on the system preceding this event?

    Any networking changes on the client and server? Any changes to the network itself?  Can you verify connectivity from NetWorker server to client, and from client to server, using tools such as: ping, nslookup, tracert, rpcinfo, nsradmin?

    How long has this client been backed up via NetWorker before the error occurred?

    How is this problem affecting NetWorker?  On this client, can you perform a manual backup using the save command?  Can you test recovery using the recover command?  Can you use the NetWorker user GUI for Windows to connect, perform the backup, and browse for recoveries?

  • 922

    0

    Posted March 15th, 2017 08:00

    Thank you Lee...

    I have tried all the above actions... Stil no use

    But found new error as "nsrexed:there was an error creating the file:"\nsr\tmp\sec\authdata_gsslgtov1_x000042" errno: 2"

  • wlee

    263 Posts

    922

    0

    Posted March 15th, 2017 09:00

    > "nsrexed:there was an error creating the file:"\nsr\tmp\sec\authdata_gsslgtov1_x000042" errno: 2"

    Where are you seeing this error?  When did it occur?  This could indicate some Windows permissions issue.  What account is used to start NetWorker on this client? Had this changed before you started seeing problems?

    Use for following to determine the start up account, and nsr path:   sc qc nsrexecd

    Try stopping the n/w servince, rename nsr\tmp, and restarting.

    If that does not help, then please look at my earlier questions, and supply the answers...

  • R_Friberg

    34 Posts

    922

    0

    Posted March 15th, 2017 09:00

    Hi,

    NetWorker 7.4.5 was never supporting Windows 2008 R2, that support came in 7.5. So a more modern client version would be a good start (preferably a supported one too).

    Regards

    Rickard

  • bingo.1

    1 Rookie

    •

    2430 Posts

    922

    1

    Posted March 15th, 2017 10:00

    error 2 usually indicates "file not found".

    What me surprises even more is the location. Usually, for a NW client, ..\nsr\tmp\sec is empty. (at least today)

    However, as you mentioned a NW linux server earlier, this can only be the client.

    I guess the easiest way is to download your software (see the other post) and quickly reinstall the NW client.

  • 922

    0

    Posted March 15th, 2017 10:00

    Yes, \nsr\tmp\sec is empty ... now i'm trying to download package and reinstall:)

  • wlee

    263 Posts

    922

    0

    Posted March 15th, 2017 18:00

    @R.Friberg

    >NetWorker 7.4.5 was never supporting Windows 2008 R2, that support came in 7.5. So a more modern client version would be a good start (preferably a supported one too).

    Just FYI, I have a copy of the NetWorker software compatibility guide from October 2010, and it says that Windows 2008 (all editions) 32 and 64 bit, client was supported starting with NetWorker 7.4.2.

  • R_Friberg

    34 Posts

    922

    0

    Posted March 16th, 2017 00:00

    Wallace, if you check a later version of the SCG you see that 7.4 supports all editions of Windows 2008, but 7.5 support Windows 2008 all editions, and Windows 2008 R2 all editions.

  • 922

    0

    Posted March 16th, 2017 01:00

    i have reinstalled the agent, but still iam getting RPC error:(

    Anything else need to be checked from OS and network end.

    As the backup server and client IP segment is same 10.1.255.xxx there is no network policy defined for allowing port right!!

    Need help urgently

  • 658

    0

    Posted March 16th, 2017 04:00

    Anyone has answer... please let me know if any recommendation can be added to it