0x00000006 error on adding server 2022 fax server

mahyar palay 11 Reputation points

I have a windows server 2022 standard (ver:10.0.20348.1194) with fax server role configured and fax printer shared too
in "windows fax and scan" program on clients (windows 7sp1 and 10) > tools menu>fax account>add>connect to fax server...>
when i type \servername >next>done it finished unsuccessfully without error (account list remain empty!!)
when i want to add shared fax server printer in client, add printer windows displayed:
windows cannot connect to the printer ,operation failed error 0x00000006.

i searched for this error on internet and try this solutions without any success:

  1. Delete "Client Side Rendering Print Providers" key from HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers
  2. remove Microsoft shared fax driver form Print Management
  3. sfc /scannow
  4. dism /online /cleanup-image /restorehealth

i think the problem is in "windows server 2022 shared fax driver"
please help me solve this problem

best regards.

Windows Server Printing
Windows Server Printing
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Printing: Printer centralized deployment and management, scan and fax resources management, and document services
651 questions
0 comments No comments
{count} votes

11 answers

Sort by: Most helpful
  1. Alan Morris 1,161 Reputation points


    Error 6 is an invalid handle error. I do not know why you are experiencing this error.

    I actually don't expect Windows 7 to be supported anymore with the new RPC protocol defaults for connecting to print shares since Windows 7 does not support the protocol.

    Have you attepted to disable the RPC authentication on the Fax server?

    That might be worth a try.

  2. mahyar palay 11 Reputation points

    anyone please help me
    is there any way to update (or change) windows fax printer driver or install it on client directly (whit .inf file i mean)

    0 comments No comments

  3. Bill Klicker 21 Reputation points

    I'm getting the same error and have not yet found a solution.

  4. Fernando Ruiz 1 Reputation point

    Same error here on Win Server 2022, spawning a new 2019 test server to check if i encounter the same issue.

    0 comments No comments

  5. Fernando Ruiz 1 Reputation point

    Same with 2019, i don't believe it's just 2022

    0 comments No comments