Known Issues with Toshiba MDS Embedded (PaperCut MF)

PaperCut is fully committed to helping customers and partners make the best use of our technology. A key part of that is transparency and full disclosure of issues that may affect how well the solution works for you. Unfortunately, with complex modern technology (often supplied by different organizations) there is no way to address all problems and issues immediately but keep checking back to see if we have fixed something. If something is causing you particular concern please contact PaperCut support.

Issue ID

Description

Reported in

Status

Resolved in

13296

Toshiba MDS can get error status of NullPointerException on newly setup devices. More info…

18.0.4

Fixed

hotfix and soon in 18.0.5

11962

Toshiba devices with the PaperCut MDS app may incorrectly show as Inactive in PaperCut admin UI. More info…

17.2

Fixed

17.3.3

2389

Devices intermittently become disconnected from the PaperCut app server. More info…

13296: Toshiba MDS can get error status of NullPointerException on newly setup devices.

A bug was introduced in PaperCut 18.0.4 whereby if the EWB Home and Login URLs are empty (as seen in TopAccess via the menus: Administration → EWB) then an error of “Error occurred of type: NullPointerException” will be generated. This bug can be worked around by entering anything into the EWB Home and Login URLs and these URLS will then be overridden correctly by PaperCut in a few minutes. Alternatively, a hotfix installer for this issue can be provided by PaperCut support.

This issue will be fixed in 18.0.5.

11962: Toshiba devices with the PaperCut MDS app may incorrectly show as Inactive in PaperCut admin UI.

A change made in PaperCut 17.2 may cause devices with the PaperCut MDS app to show as Inactive when in fact they are operating correctly. There is no impact on end users - the devices will continue to operate correctly, and all PaperCut functionality should work as usual. The only impact is the incorrect status shown in the PaperCut Admin UI.

This issue was fixed in 17.3.3.

2389: Devices intermittently become disconnected from the PaperCut app server

Devices become disconnected from the app server and display a message on the device screen that says “This device is not enabled or not registered successfully”.

PaperCut have identified the cause of this message. A combination of firmware 1050 and v17.2.1 resolved the issue.

Toshiba recently released a new firmware version incorporating a protocol change that breaks compatibility with PaperCut integrated scanning.

On the device screen the user will see the following message: Javax.xml.ws.soap.OAPFaultException. The subscription is not known

PaperCut have worked with Toshiba to understand the change in protocol and to update our app to work with it. A fix for this issue was included in PaperCut MF 17.2.1

2944: Recent Toshiba firmware causes users to be incorrectly logged out from the device.

Changes in recent versions of Toshiba firmware may cause users to be logged out from the device whilst they are still using it. This issue has been resolved for users accessing native functionality by using the Access Device button within the PaperCut App, but it is yet to be addressed for users accessing native functionality by using the device’s hard keys. Users might still be logged out if using the device’s hard keys to access native functionality. PaperCut is working with Toshiba to resolve this issue.