Known Issues with Toshiba MDS Embedded (PaperCut MF)

KB Home   |   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

780464

Toshiba MDS can get error status of “Connection Refused” when device is booting up. More info…

All versions

Workaround possible and pending firmware fix

Future firmware.

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…

17.x

Fixed

FW 1050 and v17.2.1

11662

Upgrading to Toshiba firmware 1050 causes Integrated Scanning to fail More info…

17.x

Fixed

17.2.1

2944

Recent Toshiba firmware causes users to be incorrectly logged out from the device. More info…

17.0.7 (Build 40233)

Fixed

17.1.2

Other known issues, not specific to the Toshiba SDK2 Embedded solution are covered in:



780464: Toshiba MDS can get error status of “Connection Refused” not long after device has booted up.

During boot up of the Toshiba Device where the ODCA server (the server which communicates with PaperCut for information) is starting up, the lockScreen call used when logging in a user by PaperCut, can crash the ODCA server. This can be verified by trying to connect to port 49629 of the device (e.g. nc -v toshibadevice 49629) and getting a connection refused error from the connection command. As a workaround in order to restart the ODCA server, one needs to disable and enable the ODCA service. This can be done in TopAccess by going to:

  • Administration→Setup→General Setting→MDS mode, disabling and hitting Save
  • Administration→Setup→ODCA→Enable Port, disabling and hitting Save
  • Administration→Setup→ODCA→Enable Port, enabling and hitting Save
  • Administration→Setup→General Setting→MDS mode, enabling and hitting Save (though this last step should happen automatically by PaperCut re-enabling MDS).

This issue has been identified by Toshiba and will be fixed in an upcoming firmware release.

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.

11662: Upgrading to Toshiba firmware 1050 causes Integrated Scanning to fail

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.

A fix for this issue was included in PaperCut MF 17.1.2.



Categories: Troubleshooting, PaperCut MF


Keywords: MDS, V3+

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on March 23, 2018, at 12:36 AM
Printable View   |   Article History   |   Edit Article