FAQs

From CometWiki

Revision as of 00:50, 19 February 2015

FAQs

Where are all the various log files?
When troubleshooting problems with your Comet installation, a good first place to start is with the appropriate log file. Here is a list of the log files and where you'll find them:

The Comet Log
Normally the easiest way to find the Comet log is to click on the "System Logs" button on the QMONITOR screen. This will open Windows Explorer to the folder containing the log. It will have all of the log information since the last time the log file was either erased or truncated. If you only need to see the log for the current Comet session just click on View->Comet log at the top of your Comet window (full Comet sessions only).

Another way to find the path to the Comet log file is to look at the value assigned to your LOGS alias. Click on Edit->Directory Aliases at the top of your Comet window to view the path.

If you are using the /log command line argument on your Comet shortcut then the Comet log will be in the user's temp folder (%temp%). It'll be called [profile].log, where [profile] is the Comet profile name matching the /PN= command line argument.

The CosP Log
For printing problems this is the first place to look. You'll find it in the same folder as the Comet log (above). In some error situations you will see a message to find additional information in CosPErr.log. Follow the path in the error message to retrieve that file as well.
In order to get the printing logs you must turn on the logging option in your CosW.ini. See info below about where to find CosW.ini and where to find a list of the settings.

The Comet Services Logs
Both the Security Server and the File Server produce logs which may be helpful in troubleshooting problems. You'll find the logs in a folder called LOGS in your Comet Services folder.

The current Security Server log is called CSecSrv.log. Each time you restart the Security Server a new log is started so that seven generations of logs are kept. They are named CSecSrvN.log, where N is a number from 1 to 6.

The current file server log is called CometSrv.log. Each time you restart the File Server a new log is started so that seven generations of logs are kept. They are named CometSrvN.log, where N is a number from 1 to 6. The log is only created if you have logging turned on. You'll need administrative privileges to turn logging on. From the file server console, click on View->Properties. (If the dialog is disabled, you'll need to restart the console using "Run as administrator".) Check the "Log Messages" box under "Diagnostic Logging". Select the "All Messages" radio button. The top half of the properties dialog lets you choose which functions will generate log entries. Unless you are troubleshooting a particular function we recommend you choose the "Show None" button. This will restrict logging to just logins and logouts and any error messages that occur. Adding additional functions to the logging can impact file server performance.

The XAP Log
An XAP log is only generated if you have a LOGFILE statement in your #XAP file. The LOGFILE specifies where to find the log.

Where can I find my CosW.ini file?
If you can find your Comet log file, finding CosW.ini is really easy. Navigate one folder up from the folder containing the Comet.log file. You'll find CosW.ini there. This file contains important settings for how your Comet session and printing will be handled. You can find out about those settings here [[1]]

What ports are used by Signature Systems software?
You can find a list of ports here [[2]]

I'm getting an error message that CometLib couldn't be registered. What should I do?
The CometLib dll should register automatically when you start Comet. If not, there are a couple of things to try.
First, right-click your Comet shortcut and select "Run as administrator". If CometLib registers successfully, you can run Comet normally from now on.
If that was unsuccessful then you can try to register it manually. It needs to be registered for the user's temp folder. To do that, get to the Windows command prompt by running cmd.exe. Change to the temp folder by typing cd %temp%. Now you can register CometLib by typing regsvr32 cometlib.dll

Will the Comet Services run on a virtual server?
Yes as long as the server is running a supported version of Windows. You will probably want to consider using a virtual dongle for your Comet security. Here's a link to info about the virtual dongle: [[3]]