Forum Discussion

sv_jioo86's avatar
sv_jioo86
Level 3
6 years ago

NSS: Failed to contact master server

Hi team, I have a NSS 8.1.2 installed in Win 2016 Std. I am trying to connect with a master server 8.1.2 with Windows 2008 R2. But I get this message: Exception calling "Start" with "0" argument(s)...
  • sv_jioo86's avatar
    sv_jioo86
    6 years ago

    Hi JonHunt updating this post.

    We work with Veritas / Biomni support until they fix the problem. In the admincmd directory we found this files:

    E:\Program Files\Veritas\NetBackup\bin\admincmd>dir *. /p
    Volume in drive E has no label.
    Volume Serial Number is A83C-7AF6

    Directory of E:\Program Files\Veritas\NetBackup\bin\admincmd

    07/11/2019 09:08 AM <DIR> .
    07/11/2019 09:08 AM <DIR> ..
    10/08/2015 11:45 AM 0 -dv
    08/30/2014 01:07 PM 0 bpgetconfig
    11/28/2017 09:56 AM 0 bptestbpcd
    07/08/2014 09:19 AM 0 nbemmcmd
    02/14/2018 10:15 AM 0 nbstl

    This is the support summary:

    This was due to a 0 byte file called bpgetconfig which was in the admincmd directory.  Instead of running bpgetconfig.exe, it was trying to run the 0 byte file, which obviously wouldn't work (and rightly gave us an exception that it was not a valid application):

    "The specified executable is not a valid Win32 application."

    Logged here in our support db for future reference.

    Biomni Technical Support

     

JonHunt's avatar
JonHunt
Level 5

We are aware of this and it is being handled by Support

sv_jioo86's avatar
sv_jioo86
Level 3
6 years ago

Hi JonHunt updating this post.

We work with Veritas / Biomni support until they fix the problem. In the admincmd directory we found this files:

E:\Program Files\Veritas\NetBackup\bin\admincmd>dir *. /p
Volume in drive E has no label.
Volume Serial Number is A83C-7AF6

Directory of E:\Program Files\Veritas\NetBackup\bin\admincmd

07/11/2019 09:08 AM <DIR> .
07/11/2019 09:08 AM <DIR> ..
10/08/2015 11:45 AM 0 -dv
08/30/2014 01:07 PM 0 bpgetconfig
11/28/2017 09:56 AM 0 bptestbpcd
07/08/2014 09:19 AM 0 nbemmcmd
02/14/2018 10:15 AM 0 nbstl

This is the support summary:

This was due to a 0 byte file called bpgetconfig which was in the admincmd directory.  Instead of running bpgetconfig.exe, it was trying to run the 0 byte file, which obviously wouldn't work (and rightly gave us an exception that it was not a valid application):

"The specified executable is not a valid Win32 application."

Logged here in our support db for future reference.

Biomni Technical Support