|
|
|
Troubleshooting
 |
I
don't get any entries in my Enterprise Edition
|
 |
If the service can be started, but no entries
appear, please ensure that a system DSN has been configured, rather
than a user DSN.
Also make sure SyslogView points at the correct
file or database (options button during login).
|
Back to top
|
The service can
not be installed!
|
|
Verify that you are an
Administrator on the server. Otherwise reboot and try again. Check the
Event log for more information.
|
Back to top
|
The
service will not start when I press Start Service!
|
|
Syslog Server performs
several checks at startup. The program will inform you if it fails to
contact the database, fail to authenticate, or if the tables seem to be
non-existant or of the wrong format. Also ensure you have proper user
rights to start services.
|
Back to top
|
SyslogServer
sends syslog messages that my license has been exceeded.
|
|
Datagram SyslogServer bases
the license on the number of different IP addressess that has been
received since service start. If the service has been active for a long
time some changes in IP presence might have occured, causing
SyslogServer to have received a total of more IP addresses than is
currently connected on the network. The solution is to simply restart
the service in order to reset the counter. Please note that the IP
address of the SyslogServer is excluded from the license
count. |
Back to top
|
Some
of my units are not displayed with names, just IP address
|
|
SyslogView normally displays
the received host information in the host field,
and the sending IP address in the Syslog Host field.
However, SyslogServer also
has an optional name lookup support, which can be set in the
configuration program. The Syslogserver will then try to resolve the
'Host' column information, thereby translating IP addresses into names.
Please note that name lookup does have a performance penalty.
|
Back to top
|
I
cannot connect to my SQL server
|
|
Please review your ODBC
settings. Compare the settings with the pictures in the manual.
Generally, the settings are default.
Another issue is Microsoft
SQLs trused connection settings. In the enterprise manager, choose
properties for your server. Choose tab security. Ensure you have the
correct setting regarding 'Windows only' or 'SQL Server and Windows'
authentication.
|
Back to top
|
I
cannot remove the service
|
|
Depending on which
installation procedure you used when installing Syslogserver, uninstall
can fail to stop the service. This results in that the service will not
be removed from the service list. Best method is to manually stop the
service before running the uninstall program.
If needed, the service can also be removed from the command prompt:
sc stop Syslogserver
sc delete Syslogserver
|
Back to top
|
I
cannot login with SyslogView
|
|
For Windows XP and Windows
2003, if you don't even get the login window, you lack the .NET
framework:
If you get an error message
when trying to login about missing ODBC components, you are missing
the ODBC Data provider support:
Also ensure that correct ODBC
is choosen, if using Enterprise Edition, and that the ODBC connection
itself works. Make sure that using table Syslog is specified.
|
Back to top
|
I'm experiencing some other problems with
SyslogAgent...
|
|
First, inspect the database for any entries
originating from the SyslogAgents themselves, for possible error
messages. The process name is SyslogAgent.
For debugging purposes, a log file can be created
in the SyslogAgent directory. Start the service with debug flags to
activate the file logging. Use Windows service interface
to enter these parameters (Start->control
panel->Administrative
tools->services->Syslogagent. Enter the parameters, and
then start the service from the same interface.
Always use -DLOGGER as parameter when debugging.
Possibly also add -DSERVICE for service start/stop problems, and
-DPARSE for parsing problems, and -DAPPLPARSE for application parsing
problems.
For updated SyslogAgents, dump files are created in
the same directory if the program crashes. These files are called
SyslogAgentCrashInfo.dmp and the previous one
SyslogAgentCrashInfo_old.dmp. If these files exist, please mail them to
info@syslogserver.com
Check the manual for possible differences from your
setup. Feel free to ask us as info@syslogserver.com.
|
Back to top
|
I'm experiencing some other problems with
SyslogServer...
|
|
Most problems result from database settings. Most
db related error messages are also displayed in a popup window when
starting the service from SyslogConf. Also check or confirm db user/pwd
settings work.
For debugging
purposes, a log file called service.log is used. You find it in the
same directory SyslogServer was installed in. Any error message,
including all database errors, can be found here.
Syslogserver can
also be started with debug flags, for increased logging to the
service.log file. Specify -DALARM and/or -DBACKUP and/or -DSERVICE as
an argument to the service. Use Windows service interface to enter
these parameters (Start->control panel->Administrative
tools->services->Syslogserver. Enter the parameters, and
then start the service from the same interface.
Check the manual
for possible differences from your setup. Feel free to ask us as info@syslogserver.com.
|
Back to top
|
|
