Troubleshooting with clock error log messages
This table lists potential error messages that can be displayed in the Log tab of the Admin Console:
Error message | Details and resolution |
---|---|
[exportswipes] - ReaderException while exporting Swipes: com.infor.wfm.clock.server.wbsynch.CommunicationException: Protocol not
found: /wb:wsclocks-inbound
|
Ensure that the value for the
wbsynch.webservice.url setting in
settings.conf is a valid URL. The URL needs
to be the same address as the system server with
/axis/services appended. For example,
http://192.168.22.22:8005/axis/services.
|
[exportswipes] - Exception during sendSwipe() - connection not available.
|
Ensure that the value for the
wbsynch.webservice.url setting in settings.conf
is a valid URL. The URL needs to be the same address as the system server with
/axis/services appended. For example,
http://192.168.22.22:8005/axis/services.
|
[exportswipes] - Exception during sendSwipe() - connection not available.
|
Ensure that the value for the wbsynch.webservice.username and wbsynch.webservice.password found in the settings.conf file are valid credentials to log into the system.
The clock's username and password can be viewed and set with the Admin Console.
Valid credentials are defined in the system by accessing:
|
[dbupdate] -
Could not insert group: reader 10002 does not exist in
the database!.Groups: [10001]
|
This error indicates that the reader type was not
specified in the Reader table in the system. Ensure that wbsynch.mapping.READER.type is commented out, by
typing # before the first character, in
settings.conf. In addition, ensure that
the Reader Type
field on the Readers
Detail page of the system, has a value of WB9000 . |