How to Reset WebClientPrint Protocol Handler on Chrome

Each time that WCPP client utility must be launched at the client machine, Chrome displays to the user a dialog asking for confirmation. The user is allowed to “Remember my choice”. If user check the “Remember my choice” option and click on “Do Nothing” or “Deny” or “Don’t open” button, then WCPP will not be launched making printing process impossible to be accomplished, nor WCPP detected or being able to send list of installed printers as well.

To revert back this Chrome setting, user must do the following:

  1. Open Chrome and go to the target website. Then click on “More” icon, then select “More tools > Clear browsing data…”. The option “Cookies and other site data” should be sufficient. Click “Clear Browsing Data” and Refresh the page. Chrome should display the URL Handler dialog again.
    If this process did not work, then try the next approach.
  2. If #1 option failed, they try the following.

    For Windows Clients
    – It’s mandatory to Quit Chrome (all instances).
    – Open Windows Explorer and go to your C: drive, then Users -> (your user profile name) -> AppData -> Local -> Google -> Chrome -> User Data

    NOTE: AppData is often a hidden folder, so be sure you can view “Hidden Items” if you will be looking for the file through your directory. (Click on the “View” tab and make sure the box next to “Hidden Items” is checked.)

    – Open the Local State  file by using Notepad.
    – Within the file, hit the keys Control and F to search for “webclientprint” (you could found “webclientprint3“, “webclientprint4“, etc depending on the version installed on that machine). You should see a line that says “webclientprint”: true
    – Delete true and replace it with false.
    – Save the file.
    – Re-open the file, and verify that the “webclientprint” line has been changed.
    – Now re-start Chrome

    For Mac Clients
    – It’s mandatory to Quit Chrome (all instances).
    – You will need to find and open the Local State file. Open a Finder window, and go to Library -> Application Support -> Google -> Chrome, and find the Local State file.

    NOTE: the Library folder may be hidden. To find it, right click on the Finder icon and select Go to Folder… enter “~/Library”

    – Once you’ve found the Local State file, double-click to open it using TextEdit.
    – Within the file, hit the keys Command and F to search for “webclientprint” (you could found “webclientprint3“, “webclientprint4“, etc depending on the version installed on that machine). You should see a line that says “webclientprint”: true
    – Delete true and replace it with false.
    – Save the file.
    – Re-open the file, and verify that the “webclientprint” line has been changed.
    – Now re-start Chrome

    For Linux Clients
    – It’s mandatory to Quit Chrome (all instances).
    – You will need to find and open the Local State file. Open File Explorer, and go to ~/.config/google-chrome/, and find the Local State file.
    – Once you’ve found the Local State file, open it using your favorite Text Editor.
    – Within the file, hit the keys Control and F to search for “webclientprint” (you could found “webclientprint3“, “webclientprint4“, etc depending on the version installed on that machine). You should see a line that says “webclientprint”: true
    – Delete true and replace it with false.
    – Save the file.
    – Re-open the file, and verify that the “webclientprint” line has been changed.
    – Now re-start Chrome

 

In case of needing further assistance, please contact our tech support team.

Advertisements

How to configure the HttpHandler method or Codeless Barcode Generation feature of Barcode Professional for ASP.NET in IIS 7.x

If you are using the rendering method “HttpHandler” or the “Codeless Barcode Generation” feature of our Barcode Professional for ASP.NET product, and you are hosting your website in IIS 7.x (v7.0 available in Windows Server 2008 or v7.5 in Windows Server 2008 R2), then the barcode settings in web.config file need to be moved to another section of such configuration file.

See the following points to learn how to configure Barcode Professional for ASP.NET handler depending on your server settings:

  • For Windows Server 2003 with IIS 6.0 the barcode settings in the web.config of your website should look like the following:

    <system.web>      
         ...
       <httpHandlers>
           <add verb="*" path="BarcodeGen.axd" type="Neodynamic.WebControls.BarcodeProfessional.BarcodeProfessional, Neodynamic.WebControls.BarcodeProfessional"/>
       </httpHandlers>
         ...
    </system.web>
    

  • For Windows Server 2008 and Windows Server 2008 R2 with IIS 7.x the barcode settings in the web.config of your website should look like the following:

    <system.webServer>
       ...
       <handlers>
         <add name="BarcodeGen" verb="*" path="BarcodeGen.axd" type="Neodynamic.WebControls.BarcodeProfessional.BarcodeProfessional, Neodynamic.WebControls.BarcodeProfessional"/>
       </handlers>
       ...
    </system.webServer>
    

Notice that in IIS 7.x the handler section ( node) is under node NOT under node as in IIS 6. HTH,