IMPORTANT Vividata technical support announcement

[address@hidden]

IMPORTANT MESSAGE

This email account is NO LONGER BEING MONITORED, due to
excessive unsolicited email advertisements. Please go to the
Vividata web site and submit your support inquiries there

  http://www.vividata.com/cgi-bin/support

We are very sorry to have to implement this extreme measure, but
the junk email we received reduced our ability to reliably track
and respond to new support cases.

Thank you for your understanding.

Before you contact technical support, however, please review the
following list of common problems.

Most commonly, users have trouble with licensing. When you installed
the software, you should have entered the license key and pressed the
"Apply" button. If you have not entered the key, please run the
installer from the Vividata/bin directory and press "Jump to
Licensing".

To check and see if licensing is working correctly:

Run ./lmstat from the Vividata/bin directory and check the output for
the word "UP". If it says up, then it is fine. If not, keep reading.
Check the file /opt/Vividata/config/license.dat (or /usr/vividata) and
make sure it has 644 permissions, and is owned by root.

If lmstat reports that it can not find the license file, or if you plan
to use another location for the file, please set LM_LICENSE_FILE
environment variable for each user. This should point to the correct
file including its full path. You can also set it to address@hidden if
the license resides on another machine.

If this does not help, please run the ./lmutil lmdiag command from
$VV_HOME/bin directory.  This provides a limited diagnostic of
licensing issues. and check the result.

Lastly, if all this does not help - Run ./lmhostid from the
$VV_HOME/bin directory and verify that the output is the same hostid
as in the license.dat file, if it is not, you will need a new license
key.

Device issues:

If your software cannot find the device, please run ./vvshowdevs and
check the output. The output should contain the same information as the
file /tmp/vvdrv.rc. If your device is not listed or found, this means
that our software can not access the device. Most often the reason for
this is the permissions on the /dev entry, cabling or termination.

Log Files:

All Vividata software includes a set of log files useful in
troubleshooting.

vividata.log: All products have the /tmp/vividata.log that logs
licensing and licensing problems.

vvdrv.rc: The /tmp/vvdrv.rc file contains information on SCSI devices
and printers used by PostShop, ScanShop and OCRShop.

 .results: After every print attempt, a print_queue_name.results file is
put in the /tmp directory with information on successful and failed
prints.

gs_errs: If a print fails, often a gs_errs file is created in the /tmp
directory.  Please see our online knowledge base for information about
these errors.