UNSOLVED

Hemant-I97jT

updated

17 years ago

HI

Hemant-I97jT

1 Rookie

•

117 Posts

0

1451

March 5th, 2010 23:00

SYSTEM error: There is already a machine using the name:

Hello,

       We are using Networker 7.4.4 in Windows 2008 32 bit environment.

I am getting the following error consistently.

==================================================================================

SYSTEM error: There is already a machine using the name: "15barmfs.f1sml.nsn.com". Either choose a different name for your machine, or delete the "NSR peer information" entry for "15barmfs.f1sml.nsn.com" on host: "barserver.barserver"

SYSTEM error: There is already a machine using the name: "15barmfs.f1sml.nsn.com". Either choose a different name for your machine, or delete the "NSR peer information" entry for "15barmfs.f1sml.nsn.com" on host: "barserver.barserver"

=================================================================================

Can you please clarify the following.

1) In which scenario this error will come. I had observed this error after disaster recovery.

2) How to rectify it.

Best Regards,

Hemant Joshi

  • masonb

    445 Posts

    312

    0

    Posted March 8th, 2010 00:00

    Hemant,

    This error is caused by the Networker Authentication certificates getting out of sync between the client and NetWorker server. You can correct this be deleting the certificate and a new one will be calculated and stored next time the backup is attempted.

    Support Solution esg73971 gives you the details on how to do this.

    Regards,

    Bill Mason

  • DarkPanda

    12 Posts

    312

    0

    Posted June 22nd, 2010 19:00

    Hi Hemant,

    Have you manage to resolve this issue?

    I have also encounter the same thing.

    Regards,

    TS

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    312

    0

    Posted June 23rd, 2010 02:00

    See what William has said.  Also, by disabling nsrauth you will get rid of this.  I believe 7.5SP3 will be the first version with improved nsrauth mechanism.

  • PetersonPS

    1 Rookie

    •

    39 Posts

    312

    0

    Posted June 23rd, 2010 18:00

    Heman,

    try disabling the nsrauth following the example below and see if it solves.

    After disabling the nsrauth you need to restart the services of the Networker Server.

    C:\>nsradmin -p nsrexec
    NetWorker administration program.
    Use the "help" command for help.
    nsradmin> . type: NSRLA
    Current query set
    nsradmin> show auth methods
    nsradmin> p
                    auth methods: "0.0.0.0/0,nsrauth/oldauth";
    nsradmin> update auth methods: "0.0.0.0/0,oldauth"
                    auth methods: "0.0.0.0/0,oldauth";
    Update? y
    updated resource id 2.0.40.9.0.0.0.0.249.182.31.76.0.0.0.0.10.10.10.15(24)
    nsradmin> p
                    auth methods: "0.0.0.0/0,oldauth";
    nsradmin> q