04-27-2018 11:29 AM
I tested a recent VersaLink device sw fix on the VL C405 and VL C70xx that fixed issues opening the @PrintbyXerox app after logging into a CA session using XPMMService with a userid > 32 characters. The @PrintbyXerox app fails to open and the user is prompted again for their login credendials.
VersaLink development fixed this problem in new sw I tested. However, when I attempt to release a job, it fails to print. See attachment (IMG_2752.JPG) for device LUI details of the job in Job Status.
In addition, when I login with a userid < 32 characters, the job prints, but I still get an error in Job Status. See IMG_2755.JPG.
Is this an XPMMService issue, an @PrintbyXerox issue or possibly another VersaLink sw bug?
04-27-2018 01:21 PM
Update on this one...
I was using a lab VL C70xx device with no PS kit installed. So that’s why I got the errors 016-749.
When I switched to a VL C405 that has a PS kit installed, print jobs still failed to print when logged into a CA session with a userid > 32 characters. However, the symptoms were different.
- No job appears on the MFD LUI Jobs pathway for the failed job.
- If I select the failed job in the @PrintbyXerox app on the MFD LUI, I see the reason for the failure (document failed to convert). See new screen shot.
Will someone please let me know if this is an XPMMS issue or possibly a VersaLink sw issue?
04-30-2018 10:03 PM
I have shared this post with the @PrintByXerox team. I will post additional information as soon as I hear back.
05-01-2018 10:17 AM
We are currently looking into this issue with the device team. We will post an update once we identify a fix to this issue.