Common error log messages

This table lists potential error messages displayed in the Log tab of the Admin Console:

Error Message Details and Resolution
ERROR 022307003049 [exportswipes ] - ReaderException while exporting Swipes:

com.workbrain.clocks.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 must be the same address as the application server with /axis/services appended. For example, http://192.168.22.22:8005/axis/services.
ERROR 022307004502 [exportswipes ] - Exception during sendSwipe() - connection not available.

com.workbrain.clocks.server.wbsynch .CommunicationException: Could not login into web service. Reason: (404)Not Found

Ensure that the value for the wbsynch.webservice.url setting in settings.conf is a valid URL. The URL needs to be the same as the application with /axis/services appended. For example, http://192.168.22.22:8005/axis/services.
ERROR 022307004727 [exportswipes ] - Exception during sendSwipe() - connection not available.

com.workbrain.clocks.server.wbsynch .CommunicationException: Could not login into web service. Reason: java.rmi.RemoteException: Unable to login user [], [1], [DEFAULT]. null; nested exception is:com.workbrain.webservices.excepti on.WSApplicationException

Ensure that the value for the wbsynch.webservice.username and wbsynch.webservice.password settings found in settings.conf are valid credentials to log into the application. The clock’s username and password can be viewed and set with the Admin Console.

Valid credentials are defined in the application in the Users page, accessed with this menu path:

Maintenance > Security > Users

ERROR 022307005042 [exportswipes ] - Exception during sendSwipe() - connection not available.

com.workbrain.clocks.server.wbsynch .CommunicationException: Could not login into web service. Reason: java.rmi.RemoteException: Error during login. Unable to resolve identifier [6A:C9:03:56:1B:D1] to a reader id.; nested exception is:java.rmi.RemoteException: Unable to resolve identifier [6A:C9:03:56:1B:D1] to a reader id.

This error indicates that Web Services is looking for the MAC address of the clock in the Reader Name field of the Readers Detail page but cannot find the address. Either the MAC address was incorrectly specified in the application or you did not intend on using the MAC address to identify the clock. If you did not intend to identify clocks by their MAC address, modify the wbsynch.webservice.useMacAddrAsName setting in settings.conf. A value of N indicates that the serverName value, also specified in the settings.conf file, will be used to identify the clock. If the useMacAddrAsName setting is set to N, then check to ensure that the wbsynch.webservice.serverName value is identical to the Reader Name field that was specified in the application.
ERROR 120706082927 [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 application. Ensure that wbsynch.mapping.READER.type is commented out (by specifying # before the first character) in settings.conf and that the Rdr Type field on the Readers Detail page of the application has a value of EDC.