Showing results for 
Search instead for 
Did you mean: 

"Could not connect to Netbackup Service Layer, You will be rre-directed to Backup , Archive and Restore User interface"

Level 3

We are getting the below error while loggin into the java console( NBU)  and directing to the  BAR window alone

"Could not connect to  Netbackup Service Layer,  You will be rre-directed to  Backup , Archive  and Restore User interface"

Details of Master server

RELEASEDATE Fri Oct 24 23:07:58 CDT 2014

I checked whether nbsl is running ( restrted it ) nbatd (running),still the issue persist. We are able to login to the rest  of the masters which are in the same patch level.


Appreciate the quicker Response





Level 6
Employee Accredited

I have to go out, so I'll only be able to give a little advice.

Firstly, what changed - reecently upgraded ??? 

Max out all logging - specifically  the following need to be at VERBOSE = 5 in bp.conf

pbx - this will be set already, well it is by default

This is a bit different, should be set to 10

/opt/VRTSpbx/bin/pbxcfg -p (see

Also - make sure that we set 6 and 6 for nbsvcmon (163), nbevtmgr (231),  libraries (137) and ACE/TAO (156) nbsl (132)

vxlogcfg -a -p 51216 -o 163 -s DebugLevel=6 -s DiagnosticLevel=6

vxlogcfg -a -p 51216 -o 231 -s DebugLevel=6 -s DiagnosticLevel=6

then -o 135 and -o 156 -o 132

I'd restart NBU at this point

Recreate the issue, leave the system 5 mins

Immediately run:

vxlogview -p 51216 -i 132 -t 00:15:00 >nbsl_132.txt  (This gives the last 15 mins of logs, hence why to run immediately)

vxlogview -p 51216 -i 163 -t 00:15:00 >nvscmon_163.txt

vxlogview -p 51216 -i 231 -t 00:15:00 >nbevtmgr_231.txt

vxlogview -p 50936 -o 103 -t 00:15:00 >103.txt

The other logs are just in hte netbackup/logs/<process data>

There is no seperate log for 156 and 137, these log into the others

If -i <xxx> fails use -o <xxx>

If more than 15 mins passes after you recreated the issue, increase the time (it's relative to when the command is run).

Turn the logging down (same vxlogcfg commands as above, just use -s DebugLevel=1 )  Debug 1 and Diag 6 are the defaults, turn Diag down if you wish.

These logs are probably overkill. with lucj something will be seen in pbx, nbsl or one of the bpjava logs - If you wish you could just set these first and try, it's easy to turn on the others and retry.

HINT.  The vxlogview commands with -i <xxx> mean that the command will display the <xxx> log (eg 132 = nbsl) but also any other processes that log into it (in the case 156 and 132 - TAO and libraries (network stuff basically).  If you run -o <xxx> you only get the process that is the log file (eg -o 132  = only nbsl, no TAO or library stuff).

I usually get both -i and then -o (adjust the output files to determine which is which) as -i  output will be larger and harder to look through.


vxlogview -p 51216 -i 132 -t 00:15:00 >nbsl_132i.txt  

vxlogview -p 51216 -i 163 -t 00:15:00 >nvscmon_163i.txt

vxlogview -p 51216 -i 231 -t 00:15:00 >nbevtmgr_231i.txt

vxlogview -p 50936 -o 103 -t 00:15:00 >103.txt

vxlogview -p 51216 -o 132 -t 00:15:00 >nbsl_132o.txt  (This gives the last 15 mins of logs, hence why to run immediately)

vxlogview -p 51216 -o163 -t 00:15:00 >nvscmon_163o.txt

vxlogview -p 51216 -o 231 -t 00:15:00 >nbevtmgr_231o.txt


... then you have a choice.

Also, just before you start the GUI, make a note of the exact system time on the master

Level 6


try updating this file on you laptop or machine where java gui is installed, we had the same issue and this solution for 7.7.2 but give a try


change NBJAVA_CORBA_DEFAULT_TIMEOUT  from 60 to 120.

Level 3
Partner Accredited

Having this very same issues after updating a RedHat 7.2 Master Server from NB 7.6.1 to NB 7.7.2.


Chaning the default timeout value in the nbj.conf file did not do the trick. :(


Any other idea/solution?


Thanks in advance.



Level 6


there are 2 to 3 technote for your issue and for some reason i not able to find those technote..i had the same issue and updating nbjconf file resovled the issue..

try this below technote, if not then please open support case.


Level 3
Partner Accredited

We could not fix this and had to upgrade to 7.7.3.


After upgrading everything went fine.