03-10-2020 02:59 PM
I had a customer instsall NB 8.1.2 on an windows 2016 server about 4-6 weeks ago
To he called and was having issues try to do a restore for the first time
From the Java Console - Backup Archive and Restore he selected the source client, Destination client and proper Policy Type. He was expectiing a list of Drive letters / folders and files to chose to restore. Instead he receive messaged
failed to display lookup VxUL message catalog (status 366)
Receive smae message no matter what client he tried to restore from
Any suggestions to solve this issue.
Thanks
Solved! Go to Solution.
03-11-2020 12:45 AM - edited 03-11-2020 12:46 AM
@RichWeiss and @Marianne - there is an article which I can find internally and it is a public document, but the public facing document doesn't seem to exist anymore. The link to the external article (which doesn't work) is: https://www.veritas.com/docs/100047143
From the copy I can read - the cause and solution are as follows (hope this helps).
The nblog.conf paths for the L10nLib and L10nResouceDir are incorrect
Default.L10nLib=C:\Program Files\Veritas\NetBackup\bin\vxextwincat
Default.L10nResourceDir=C:\Program Files\Veritas\NetBackup\resources
To view the value run below commands
vxlogcfg -l -p 51216 -o Default -s L10nLib
vxlogcfg -l -p 51216 -o Default -s L10nResourceDir
To Correct your Default.L10nLib & L10nResourceDir using below command
vxlogcfg -a -p 51216 -o Default -s L10nLib= "path where the file exist"
vxlogcfg -a -p 51216 -o Default -s L10nResourceDir="path where the file exist"
example:
vxlogcfg -a -p 51216 -o Default -s L10nLib=D:"\Program files\Veritas\NetBackup\bin\vxextwincat"
vxlogcfg -a -p 51216 -o Default -s L10nResourceDir=D:"\Program files\Veritas\NetBackup\resources"
Stop and Restart Services
03-11-2020 12:04 PM
I fouind the use initially tried to install Netbackup on the D:\ drives and his GPO's were preventing it. Si he reinstalled Netbackup on c:|
I did the following to fix issue
C:\Program Files\VERITAS\NetBackup\bin>vxlogcfg -l -p 51216 -o Default -s L10nLib
V-1-8-0 Invalid setting/value is passed
C:\Program Files\VERITAS\NetBackup\bin>vxlogcfg -a -p 51216 -o Default -s L10nLib="C:\Program Files\VERITAS\NetBackup\bin"
The configuration settings were added successfully.
C:\Program Files\VERITAS\NetBackup\bin>vxlogcfg -a -p 51216 -o Default -s L10nResourceDir="C:\Program Files\VERITAS\NetBackup\resources"
The configuration settings were added successfully.
C:\Program Files\VERITAS\NetBackup\bin>vxlogcfg -l -p 51216 -o Default -s L10nLib
Configuration settings for originator 112, of product 51,216...
LogDirectory =
DebugLevel = 0
DiagnosticLevel = 0
DynaReloadInSec = 0
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = None
LogRecycle = False
MaxLogFileSizeKB = 10240
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 4294967295
OIDNames =
AppMsgLogging = ON
L10nLib = C:\Program Files\VERITAS\NetBackup\bin
L10nResourceDir = C:\Program Files\VERITAS\NetBackup\resources
NtEventLogSourceName = Application
NtEventLogCategory = 0
LogFileSDDL = (null)
then I notice the nblog.conf on the D drive was being updated.
To fix my issue I went into the regisrry @ HKLM\Software\Veritas\vrtslog\51216
and changed 'Configuration' Value from D:\Program Files\Veritas\NetBackup\nblog.conf to C:\Program Files\Veritas\NetBackup\nblog.conf
After bpdown -f -v and bpup -f -v I was able tl launch Java and successfully perform a restore without getting error
Thanky for for the help
Problem has been solved
03-11-2020 12:26 AM
I have honestly never seen this error in all my years using NetBackup.
The error is new and undocumented - I have searched NBU Status Code Guide for 8.1.2 and 8.2 and the Veritas web site.
Best to log a Support call with Veritas.
I cannot even suggest which logs to enable in the meantime - wait for the support engineer's guidance.
In the meantime, please ask your customer to open BAR GUI with 'Run as Administrator'.
I have over the years seen how everything in the NBU console was working fine, but BAR GUI was giving 'weird and wonderful' error messages if I did not open it with 'Run as Administrator'.
03-11-2020 12:45 AM - edited 03-11-2020 12:46 AM
@RichWeiss and @Marianne - there is an article which I can find internally and it is a public document, but the public facing document doesn't seem to exist anymore. The link to the external article (which doesn't work) is: https://www.veritas.com/docs/100047143
From the copy I can read - the cause and solution are as follows (hope this helps).
The nblog.conf paths for the L10nLib and L10nResouceDir are incorrect
Default.L10nLib=C:\Program Files\Veritas\NetBackup\bin\vxextwincat
Default.L10nResourceDir=C:\Program Files\Veritas\NetBackup\resources
To view the value run below commands
vxlogcfg -l -p 51216 -o Default -s L10nLib
vxlogcfg -l -p 51216 -o Default -s L10nResourceDir
To Correct your Default.L10nLib & L10nResourceDir using below command
vxlogcfg -a -p 51216 -o Default -s L10nLib= "path where the file exist"
vxlogcfg -a -p 51216 -o Default -s L10nResourceDir="path where the file exist"
example:
vxlogcfg -a -p 51216 -o Default -s L10nLib=D:"\Program files\Veritas\NetBackup\bin\vxextwincat"
vxlogcfg -a -p 51216 -o Default -s L10nResourceDir=D:"\Program files\Veritas\NetBackup\resources"
Stop and Restart Services
03-11-2020 06:36 AM
Internally, I find that error codes 360 to 399 are for audit trail errors. Status 366 is called EC_adtr_vxul_failure.
It's set by nbaudit when it fails to translate a message. Setting the code is accompanied by the log entry "Failed to look up l10n string" in the nbaudit directory.
Disclaimer: I don't know nbaudit.
03-11-2020 12:04 PM
I fouind the use initially tried to install Netbackup on the D:\ drives and his GPO's were preventing it. Si he reinstalled Netbackup on c:|
I did the following to fix issue
C:\Program Files\VERITAS\NetBackup\bin>vxlogcfg -l -p 51216 -o Default -s L10nLib
V-1-8-0 Invalid setting/value is passed
C:\Program Files\VERITAS\NetBackup\bin>vxlogcfg -a -p 51216 -o Default -s L10nLib="C:\Program Files\VERITAS\NetBackup\bin"
The configuration settings were added successfully.
C:\Program Files\VERITAS\NetBackup\bin>vxlogcfg -a -p 51216 -o Default -s L10nResourceDir="C:\Program Files\VERITAS\NetBackup\resources"
The configuration settings were added successfully.
C:\Program Files\VERITAS\NetBackup\bin>vxlogcfg -l -p 51216 -o Default -s L10nLib
Configuration settings for originator 112, of product 51,216...
LogDirectory =
DebugLevel = 0
DiagnosticLevel = 0
DynaReloadInSec = 0
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = None
LogRecycle = False
MaxLogFileSizeKB = 10240
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 4294967295
OIDNames =
AppMsgLogging = ON
L10nLib = C:\Program Files\VERITAS\NetBackup\bin
L10nResourceDir = C:\Program Files\VERITAS\NetBackup\resources
NtEventLogSourceName = Application
NtEventLogCategory = 0
LogFileSDDL = (null)
then I notice the nblog.conf on the D drive was being updated.
To fix my issue I went into the regisrry @ HKLM\Software\Veritas\vrtslog\51216
and changed 'Configuration' Value from D:\Program Files\Veritas\NetBackup\nblog.conf to C:\Program Files\Veritas\NetBackup\nblog.conf
After bpdown -f -v and bpup -f -v I was able tl launch Java and successfully perform a restore without getting error
Thanky for for the help
Problem has been solved