Your problem is most likely caused by the need to reflash the Java VM, or potentially a bad SD card.
1 of 1 people found this helpful
The latest version on FilesAnywhere is 1.4.9. I'm not sure what is new in that version, but it should be listed in the documentation that comes with the download. I have sent you the download link separately.
Have you found a fix for this?
I am having the same issues with Ricoh models MP 4002, MP 301, and MP 6001. We have updated JAVA and are still having the issues. One thing I tried was setting the auto log out timer on the Ricoh to 60 seconds because pharos sets theirs at 58. The new Ricoh models come with it set for 180 seconds. That seemed to help with disconnection, but it still happens. Once the device is rebooted all is well. We are running version 8.3 and web config is 1.4.6 with Java version 10.11.02.
This has to do with a card swipe when an MFP is coming out of sleep. The work-around is to set the "enable second-swipe logout" feature in the release station configuration in Pharos Admin to no/off/disabled.
If you need to use the "second-swipe logout" feature you can set the automatic sleep timer on the MFP to a relatively large value, like an hour or two. This reduces the chance that the MFP is asleep when a student initiates use. Also consider configuring the MFP to forcibly wake at predetermined time, like 7 a.m., so that it's likely to be awake when the first students of the day comes to use it.
Can you explain to me what the difference of having the 2nd swipe and
pushing the log out button and why it would cause the pharos solution to
crash. I appreciate your help.
Do you mean the soft logout button on the Pharos UI or the hard key Login/Logout button on the front panel of the MFP?
The soft log out on the Pharos UI.
From: Nick Bartolotti
To: Logan McDonald <email@example.com>
Date: 10/08/2013 03:21 PM
Subject: Re: -
Restart Problems with Ricoh MP 4002 model
Restart Problems with Ricoh MP 4002 model
reply from Nick Bartolotti in iMFPs & Omegas (Customers and Partners Only)
- View the full discussion
Do you mean the soft logout button on the Pharos UI or the hard key
Login/Logout button on the front panel of the MFP?
Reply to this message by replying to this email, or go to the message on
Start a new discussion in iMFPs & Omegas (Customers and Partners Only) by
email or at Pharos Community
Following Restart Problems with Ricoh MP 4002 model in these streams:
Logging out with the second card swipe is a convenience feature so that a user does not have to switch back to the Pharos Applet to logout. The need to switch back to the Pharos screen to logout is rooted in a limitation of the Ricoh architecture that prevents the hard key logout button press from being recognized when an Applet does not have focus. So the workflow, without the second swipe logout feature is this, assuming the MFP is fully awake:
Fully Awake Use Case (Pharos has focus on the front Panel)
- User authenticates with card
- MFP transitions from Pharos Splash panel to Secure Release panel
- User transitions to Copy, Scan, or another 3rd party Applet
- User presses hard logout button
- Nothing happens
- User transitions back to Pharos Secure Release panel
- User presses hard logout button or soft logout button on Pharos Secure Release panel
- User is logged out from Pharos and the MFP is locked
With the second swipe logout feature enabled the workflow changes to 1, 2, 3, card swipe, 8 allowing the user to logout from the MFP at any time regardless of which Applet or Feature has focus.
If the MFP is not fully awake then the workflow (especially that which happens under the hood) is slightly different:
MFP Asleep Use Case
- MFP is asleep
- User authenticates with a card (a) or presses the Energy Save button to wake the MFP (b)
- If the user waits until the Pharos Applet has focus on the front panel, execution vectors into the the Fully Awake Use Case starting at #1 and does not return here.
- Otherwise, during the time span from (a) or (b) until the Pharos Applet has focus on the front panel, the Pharos Applet is setting up communications to Pharos. This work is done with a worker thread (T1).
- If during (4) a user swipes their card (either for a second time (a) or for the first time (b)) another work thread (T2) is started to either login (a) or logout (b)
- If T1 and T2 are running concurrently they tend to step on each other causing an instability in the system.
So, a way to prevent T1 and T2 from running concurrently is to reduce the probability that a card swipe event happens while the MFP is coming out of sleep mode -- the recommendations I made previously do just this.