Konica Minolta - Session for user [username] is still active

Summary

Users may encounter an issue where the Konica Minolta Embedded Terminal displays: Session for user [username] is still active

This prevents the user from logging in on a specific MFD. However:

  • Other users can still authenticate on the same MFD.

  • The affected user can authenticate on other MFDs without issue.

  • Occasionally, the user may log in but:

    • Their credit balance appears as zero, and

    • A reservation for their full credit is visible in Payment System > Subjects > User details > Last 5 reservations.

terminalserver.log
2024-10-03 11:22:22.4533 WARN 83| SpecificPaymentChecksStep | Step | [10.12.5.99][21] User [sampleuser] has still active transaction.

Root cause

This issue typically occurs when the MFD has an unfinished job in its internal job list. The credit rental by MFD (GetCounterTicket) is not completed (missing ReturnCounterTicket), leaving session active in YSoft SafeQ. As a result:

  • The user cannot start a new session until the job is completed or cancelled.

  • In the YSoft Payment System an active transaction remains open.

Common causes for unfinished jobs include:

  • Missing paper or toner

  • Paper jam

  • Insufficient credit

Users are usually warned about issue with job execution on the MFD display. Ignoring these warnings and logging out without resolving the issue leads to stuck sessions and possible security concerns (e.g., jobs being released later by another user after filling up paper tray).

Another possible trigger may be MFD firmware related.

Resolution

  • Either cancel the job via:

    • MFD panel (requires configuration allowing job deletion by any user)

    • MFD web interface

  • Or reboot the MFD to clear stuck jobs

Preventing recurrence

  • Use Konica Minolta firmware GG2-RF or equivalent to address possible Firmware issues with missing ReturnCounterTicket.

    • Konica Minolta reference IDs: INC000000072346, INC0431657, INC0427868

    • After applying the firmware do: [Service Mode] > [System 1] > [Initialization] > [Server Cache Data] > START

  • Try enabling SSDP on the MFD - there were reports of ReturnCounterTicket missing with SSDP turned off

  • Educate users on the risks of ignoring error prompts

  • Ensure users finish or cancel jobs before logging off, or enable MFD dip switch that cancels all jobs on logout (consult Konica Minolta)

  • Consider enabling system settings in YSoft SafeQ:

    • kmReservationStep - Set to 500 to reserve full credit amount per session to reduce stuck partial reservations

    • autoDeleteOverflowJobs - Deletes jobs with insufficient credit (consult Konica Minolta to confirm support of CounterLimitSetting.JobDelete during terminal installation)

    • Use IPP backend with Monitor Ready State enabled for automatic deletion of failed jobs

    • Use V3 client and IPP backend with IppPrintMonitoringEnabled to prevent delivery of job to printer in error state

  • Monitor the credit reservations that are stuck for too long, review them and take a necessary action (e.g. cancel job from MFD joblist or restart MFD) - reservation should disappear then). Such reservations can be listed by the SQL query on the Payment System database:

    select o.created_date, c.name, c.lookup_key, o.provided_id as reservation, o.created_date from open_transaction o left join customer c on c.id = o.customer_id order by o.created_date asc

Avoid modifying the "Expiration of reservations" setting in the YSoft Payment System or attempting to resolve the issue by manually cancelling reservations. Doing so may lead to negative credit balances and session inconsistencies.

Reservations are automatically cleared once the MFD session ends properly. The correct approach is to prevent jobs from getting stuck on the MFD, rather than trying to work around the consequences afterward.

Example Scenarios:

  • After receiving initial credit from YSoft SafeQ, the MFD consumes it through printing . Some devices display an “Insufficient balance” warning and require the user to press Retry to request more credit. If the user ignores the prompt and logs off, the session remains active, and they won’t be able to log in again.

  • A user with $100 credit receives an initial $10 allocation. They start printing jobs totaling $30. The first few print successfully, but the user is logged off due to inactivity . The MFD continues printing until the initial $10 is used up. It then needs to request more credit, but depending on firmware behavior, the process may get stuck - either because no prompt is shown to the logged-off user, or the MFD does not proceed despite receiving additional credit. As a result, the user is locked out due to the still-active session.