Problem mapping network printer after upgrade to 1.5.9.60


  • Hi,

    It’s maybe a coincidence but I had no problem with 1.5.9.58 (so why did have made an upgrade isn’t it ?) and since upgrade to 1.5.9.60 several users called me (some of them every day) because their printer is no longer connected, while fog.log seems ok :

    ------------------------------------------------------------------------------
    --------------------------------PrinterManager--------------------------------
    ------------------------------------------------------------------------------
     18/02/2021 06:55:47 Client-Info Client Version: 0.12.0
     18/02/2021 06:55:47 Client-Info Client OS:      Windows
     18/02/2021 06:55:47 Client-Info Server Version: 1.5.9.60
     18/02/2021 06:55:47 Middleware::Response Success
     18/02/2021 06:55:47 PrinterManager Adding printers
     18/02/2021 06:55:47 PrinterManager \\impression\Photocop_RGI already exists
    ------------------------------------------------------------------------------
    

    Is it a bug of 1.5.9.60 or something else ?
    Can you refresh my memory and tell me how to revert to 1.5.9.58 ?

    Thanks,
    Matthieu


  • @sebastian-roth A fourth colleague had the same problem today so I restarted fog service, it takes a while but photocop_rgi printer has been connected after that :

    ------------------------------------------------------------------------------
    --------------------------------PrinterManager--------------------------------
    ------------------------------------------------------------------------------
     18/02/2021 15:37:55 Client-Info Client Version: 0.12.0
     18/02/2021 15:37:55 Client-Info Client OS:      Windows
     18/02/2021 15:37:55 Client-Info Server Version: 1.5.9.60
     18/02/2021 15:37:55 Middleware::Response Success
     18/02/2021 15:37:55 PrinterManager Adding printers
     18/02/2021 15:37:55 PrinterManager \\impression\Compta already exists
     18/02/2021 15:37:55 Printer Adding: \\impression\Photocop_RGI
     18/02/2021 15:37:55 PrinterManager PrintUI return code = 0
     18/02/2021 15:37:56 PrinterManager Invoking add \\impression\Compta for all users
     18/02/2021 15:37:56 PrinterManager PrintUI return code = 0
     18/02/2021 15:37:56 PrinterManager Invoking add \\impression\Photocop_RGI for all users
     18/02/2021 15:38:26 PrinterManager PrintUI has not finished in a timely fashion, abandoning process
     18/02/2021 15:38:26 PrinterManager Restarting spooler
    ------------------------------------------------------------------------------
    

    I’m just unable to explain this problem…

  • Senior Developer

    @matthieu-jacquart said in Problem mapping network printer after upgrade to 1.5.9.60:

    Is there a way to force it to re-add printer ?

    Restart fog-client service or the computer.


  • @sebastian-roth I can’t tell you, it only happen on dedicated computers.
    I’ve juste been called by a colleague which has 2 configured printers by fog, one is ok (“compta”) but not the other one (“Photocop_RGI”, as you mentionned “already exists”)

    ------------------------------------------------------------------------------
    --------------------------------PrinterManager--------------------------------
    ------------------------------------------------------------------------------
     18/02/2021 10:14:13 Client-Info Client Version: 0.12.0
     18/02/2021 10:14:13 Client-Info Client OS:      Windows
     18/02/2021 10:14:13 Client-Info Server Version: 1.5.9.60
     18/02/2021 10:14:13 Middleware::Response Success
     18/02/2021 10:14:14 PrinterManager Adding printers
     18/02/2021 10:14:14 PrinterManager \\impression\Compta already exists
     18/02/2021 10:14:14 PrinterManager \\impression\Photocop_RGI has already been configured
    ------------------------------------------------------------------------------
    

    Is there a way to force it to re-add printer ?

  • Senior Developer

    @matthieu-jacquart said in Problem mapping network printer after upgrade to 1.5.9.60:

    PrinterManager \impression\Photocop_RGI already exists

    Looking at this again I see it saying “already exists”. In such a case the fog-client does not re-add it and also does not restart the printer spooler.

    Does this happen, when several users login to the same computer one after the other?


  • @sebastian-roth Hi Seb, It’s maybe related to a windows bug but it began before last tuesday patch, and I made no change on GPO.
    Very strange, according to fog.log printer is mapped but didn’t appear on printer control panel or office documents, I have to map it manually to work.

  • Senior Developer

    @Matthieu-Jacquart The code changed between 1.5.9.58 and 1.5.9.60 are minimal. You can take a look on github. Minor change in the installer script and HTTP header on snapin delivery to the client. Nothing that could cause an issue with printers I am sure!

    Possibly Windows updates causing this? Change in GPO or other settings?

282
Online

8.0k
Users

14.9k
Topics

140.5k
Posts