Printer Management Issue - Data Conversion...failed - RC10

  • OS: Ubuntu 16.04
    Fog Running Version 1.3.0-RC-10
    SVN Revision: 5955
    Fog Client Version: 0.11.5

    I do not seem to be able to deploy printers from the FOG server. Here is the relevant message from fog.log on the client machine.

     9/15/2016 7:42 AM Client-Info Client Version: 0.11.5
     9/15/2016 7:42 AM Client-Info Client OS:      Windows
     9/15/2016 7:42 AM Client-Info Server Version: 1.3.0-RC-10
     9/15/2016 7:42 AM Middleware::Response Success
     9/15/2016 7:42 AM PrinterManager ERROR: Data conversion using the DataContract FOG.Modules.DataContracts.PrinterManager failed
     9/15/2016 7:42 AM PrinterManager ERROR: Error converting value "" to type 'FOG.Modules.PrinterManager.Printer+PrinterType'. Path 'printers[0].type'.

    The .fog_user.log has the following:

     9/15/2016 7:43 AM Client-Info Client Version: 0.11.5
     9/15/2016 7:43 AM Client-Info Client OS:      Windows
     9/15/2016 7:43 AM Client-Info Server Version: 1.3.0-RC-10
     9/15/2016 7:43 AM Middleware::Response Success
     9/15/2016 7:43 AM DefaultPrinterManager Checking defaults
     9/15/2016 7:43 AM Printer Setting BiSci-LSE202-Xerox660DN as default
     9/15/2016 7:43 AM PrinterManager PrintUI return code = 0

    I have been able to install from the server previous and have several printers (Brother, Canon, and HP) configured. Deployment did work from the server up until recently (not sure when it stopped working correctly).

    The apache error log does not have any error messages.

    I configured the Xerox printer using the instruction posted here (very useful – thanks for the helper utility):

    I also ran a git pull and this morning to make sure the server was up to date.

    Any ideas on what I should check next?


  • @Tom-Elliott Gotcha. I appreciate the help.

  • Senior Developer

    @jburleson RC 11 hasn’t been released quite yet, I was just informing that the fix does exist and will be available relatively soon.

  • @Tom-Elliott Thanks Tom. I will update the server in the morning.

  • Senior Developer

    There wouldn’t have been an error because nothing was failing. The reason the add post wasn’t passing the config properly was because of case though, so it was setting the config to a value that was never set to begin with.

    I have fixed that issue on RC-11 as well, thanks for the replicatable information and reporting it. (Just the type being set to blank that is and how to reproduce.)

  • There is nothing logged to the apache2 error log either.

  • @Tom-Elliott Interesting. The printer detail page shows the type set to TCP/IP Port Printer.
    However, when I looked at the list of all printers, it did not show a printer type for that printer. When I clicked on update printer from the Printer Management screen (not changing anything just clicking update), it filled in the type on the list of all printers.

    I think I may have found what caused this issue. When creating a new printer, when you click add printer it is not saving the Printer Type to the database. If you then select the printer and just click update printer, it adds the printer type.

    To reproduce:

    1. Select create printer

    2. Filling in printer detail

    3. Save the printer and then go the list all printers. I just snipped the listing for the test printer. The second field which should be Printer Type is blank.

    4. Select printer to edit it.

    5. Do not change anything just click Update Printer and then check the list of all printers. The Printer Type is now set correctly.

  • Senior Developer

    So I believe this issue is corrected for RC 11. The error was because the type was blank. I’ve added better checking and going basically I’m not going to display printers that have no type defined. I’ll likely fix this with some failsafe setting, but for now I hope this issue is somewhat resolvable.

  • Senior Developer

    @Joe-Schmitt Not exactly server issue, though I’m suspecting it’s more a bad entry in the database of an old associated printer. Checking theory now.

  • Senior Developer

    @Tom-Elliott server issue.