Installation troubleshooting guide

The most common reason of trouble with TANGO startup is wrong environment variables for UNIX or, for Windows, installation of the plugin in a wrong directory. These errors make TANGO plugin invisible to Netscape browser. The first thing to check is whether your plugin has been correcly installed. Go to Netscape's Help/About Plug-ins window. You should see something like this:


Tango Plug-in

File name: F:\Program Files\Netscape\Navigator\Program\plugins\NPTangoV10b2.dll
Tango Plug-in
Mime Type Description Suffixes Enabled
hej/hop Tango Plug-in File hej Yes

If you do not see this entry, you haven't installed TANGO according to the instruction. Begin from restarting the browser. If problem persists, please, check envvariables or repeat installation process.

If your plug-in is correctly installed and you still experience problems, please, start Java console (use Netscape's "Options" menu). Then, start TANGO again. The messages appearing in the console should look similar to the following:

.......
Local: Local demon started on port 8000
AcceptThread: thread started
ControlAppletHandle: applet thread number -7 started
Local: Connection accepted by remote host, starting demon threads ......
Local: Connected to kopernik.npac.syr.edu 9500
ThreadOut: Output thread number 1 started
DemonThreadIn: Demon input thread started
Length: 2222 bytes
Read: 2222 bytes
Reading completed
HelpText: Length: 2748 bytes
HelpText: Read: 2748 bytes
HelpText: Reading completed
Warning: Thread.suspend() was called; Navigator deadlock might result
.......

At this point, you should have login window on you screen.

It the "Connected to ...." message is missing, you have networking problem: either your plugin.conf file points to a non-existent TANGO server, or your network connection does not work as it should.

A frequent source of problems is Netscape's use of wrong classes cached in memory or on disk. If you get Java exceptions of any kind, flush you cache. Set cache size to 0 for both memory and disk caches if you experience problems. Once you are comfortable with the system, restore the cache size to useful values.

Yet another set of problems is related to the CLASSPATH variable. Netscape always grabs Java classes from local disk before it gets them from the net. TANGO CA uses Symantec widgets (brrr!..). Please, be aware that shall you have a different version of Symantec classes in any directory specified in your CLASSPATH, Netscape is going to find and load them and TANGO will crash. Get rid of Java junk from locations Netscape can see!

If nothing works, please, accept our apologies, and send us a message.