GENERAL ERROR: The NetBackup Java administration console for Windows cannot connect to a UNIX master where NetBackup is installed with a language pack.
| Article:TECH75745 | | | Created: 2009-01-19 | | | Updated: 2013-01-02 | | | Article URL http://www.symantec.com/docs/TECH75745 |
Problem
GENERAL ERROR: The NetBackup Java administration console for Windows cannot connect to a UNIX master where NetBackup is installed with a language pack.
Solution
Overview:
When trying to log in to a UNIX master using the Java console on Windows, the GUI hangs at the step where it displays the status message Checking if NBAC is configured...
This is a configuration issue caused due to a character encoding mismatch between the NetBackup server and the remote Java GUI console - for example, where NetBackup with the Japanese language pack has been installed on the master and the Java GUI is running on a Windows machine in English. NetBackup does not support mixed encoding.
Log Files: n/a
Resolution:
Determine the encoding on the master and define it in the configuration of the Java console so that there is no mixed encoding.
Output of a locale command executed on the master can be compared with the table provided in the following link to determine the correct canonical name for the encoding set to be used:
http://java.sun.com/javase/6/docs/technotes/guides/intl/encoding.doc.html
For NetBackup 7.0:
Edit the setconf.bat file on the machine where the console is invoked. Edit the following line:
When trying to log in to a UNIX master using the Java console on Windows, the GUI hangs at the step where it displays the status message Checking if NBAC is configured...
This is a configuration issue caused due to a character encoding mismatch between the NetBackup server and the remote Java GUI console - for example, where NetBackup with the Japanese language pack has been installed on the master and the Java GUI is running on a Windows machine in English. NetBackup does not support mixed encoding.
Log Files: n/a
Resolution:
Determine the encoding on the master and define it in the configuration of the Java console so that there is no mixed encoding.
Output of a locale command executed on the master can be compared with the table provided in the following link to determine the correct canonical name for the encoding set to be used:
http://java.sun.com/javase/6/docs/technotes/guides/intl/encoding.doc.html
For NetBackup 7.0:
Edit the setconf.bat file on the machine where the console is invoked. Edit the following line:
@REM Change this if there's trouble browsing files with non-ASCII names
REM SET NBJAVA_FILE_ENCODING=
REM SET NBJAVA_FILE_ENCODING=
to
SET NBJAVA_FILE_ENCODING=<encoding_set>
The setconf.bat file can be found in <install_path>\VERITAS\Java (for instance, C:\Program Files\VERITAS\Java\setconf.bat).
Example:
The encoding used on a master using the Japanese language pack is EUC_JP.
In this example, the following change would be made in setconf.bat:
SET NBJAVA_FILE_ENCODING=EUC_JP
For NetBackup 6.5:
Edit the nbjava.bat file on the machine where the console is invoked and add the command line switch -Dfile.encoding=<encoding_set> to both invocations of the java.exe command found in that file.
The nbjava.bat file can be found in <install_path>\VERITAS\Java (for instance, C:\Program Files\VERITAS\Java\nbjava.bat).
Example:
The encoding used on a master using the Japanese language pack is EUC_JP.
In this example, the following would be added:
-Dfile.encoding=EUC_JP
leading to a command looking similar to the following in the nbjava.bat file:
"%NBJDIR%\jre\bin\java.exe" -showversion -Xms%INITIAL_MEMORY% -Xmx%MAX_MEMORY% -Djava.library.path="%JAVALIBPATH%" -Dvrts.NBJAVA_CONF="%NBJDIR%"\\nbjconf -Dvrts.common.utilities.DEBUG_PROPERTIES=Debug.properties -Dvrts.nbe.INST_REL=%INSTALLED_RELEASE% -Dvrts.nbe.BUILDNO=%BUILDNUMBER% -Djava.util.prefs.PreferencesFactory=vrts.common.launch.PropertiesPreferencesFactory -Dfile.encoding=EUC_JP -classpath "%NBUCLASSPATH%;%THIRDPARTYCLASSPATH1%;%THIRDPARTYCLASSPATH2%;%CORBACLASSPATH%" vrts.nbe.AdminConsole
|
|
Related Articles
Legacy ID
335933
Article URL http://www.symantec.com/docs/TECH75745
Terms of use for this information are found in Legal Notices
Thank you.