HowTo - Resolve DeviceConfig login error

The DeviceConfig (DC) login is not successful using default credentials in FW 2.xx.

Solution

Please check the following solution options.

1. Default login credentials have changed from 1.xx FW, please raise a ticket to get new default credentials.

2. Credentials have been modified using DeviceConfig during field installation. If this is the case, please reset using device admin interface under Maintenance - Security - Reset DeviceConfig Access. If no user is available with admin role, try to write a new user to the reader by it within TBS BIOMANAGER; this will then be synchronized to the reader (create user with PIN and ADMIN role). If this is not possible, please raise a ticket.

3. TBS root CA Certificate has not been installed in the PC that is used to access DC. Some browsers (especially Mozilla) are enforcing it. Please use the Certificates attached below, and refer to documentation 'TN Securing Device Channels' on how to install the certificate.

NOTE: In case of firmware 2.xx, Port 18883 (MQTT) is required for DC connection. It may be blocked at site between device and PC. Please refer to the document 'TBS System Requirements' for further details.  This port is not used in firmware 3.xx

• Related Articles

• HowTo download logs from TBS System

  This article explains how to download the logs from TBS system to share while creating the ticket in the Help Center or share it with the TBS Support team during the troubleshooting since it contains the detailed information related to version, ...

• HowTo - Resolve 3D sensor errors

  The sensor in 3D AIR (Model 2012, former 3D TERMINAL) is not working stably and sensor runtime issues are reported regularly Solution If firmware is not able to load sensor at startup or report sensor run-time issues (error codes 42/412/414), it may ...

• HowTo - Resolve enrollment errors

  Symptom: Enrollments on device are not reflected on server and device reports 'Enrollment error occurred' (error 702) on info page. Solution Enrollment errors on device happen if data consistency got violated with new enrollment, e.g. because of ...

• HowTo - Handle 'Processing...' error

  BioManager may report 'Processing...' error endlessly after installation/upgrade. This is a generic error indicating an internal component was not installed or configured properly. No standard solution can be given, hence more information is required ...

• HowTo - Handle 'SOAP-ERROR: Parsing WSDL' error in BioManager

  BioManager reports error “SOAP-ERROR: Parsing WSDL” which means connection to RemoteAdmin WSDL resource failed. Solution This error is most of the times caused by: missing ‘WCF Services - HTTP activation’ component (under Windows Features - .Net 4.5 ...