Hi,

on an Windows Server 2012R2 RDS the spoolsv.exe is crashing randomlay.

Here is a crashdump:

FAULTING_IP:
KERNELBASE!RaiseException+68
00007fff`0b858a5c 488b8c24c0000000 mov     rcx,qword ptr [rsp+0C0h]

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007fff0b858a5c (KERNELBASE!RaiseException+0x0000000000000068)
   ExceptionCode: c0000002
  ExceptionFlags: 00000001
NumberParameters: 0

DEFAULT_BUCKET_ID:  STATUS_NOT_IMPLEMENTED

PROCESS_NAME:  spoolsv.exe

ERROR_CODE: (NTSTATUS) 0xc0000002 - {Nicht implementiert}  Der Vorgang ist nicht implementiert.

EXCEPTION_CODE: (NTSTATUS) 0xc0000002 - {Nicht implementiert}  Der Vorgang ist nicht implementiert.

EXCEPTION_CODE_STR:  c0000002

WATSON_BKT_PROCSTAMP:  54503ab3

WATSON_BKT_PROCVER:  6.3.9600.17415

PROCESS_VER_PRODUCT:  Microsoft® Windows® Operating System

WATSON_BKT_MODULE:  KERNELBASE.dll

WATSON_BKT_MODSTAMP:  57366075

WATSON_BKT_MODOFFSET:  8a5c

WATSON_BKT_MODVER:  6.3.9600.18340

MODULE_VER_PRODUCT:  Microsoft® Windows® Operating System

BUILD_VERSION_STRING:  6.3.9600.17415 (winblue_r4.141028-1500)

MODLIST_WITH_TSCHKSUM_HASH:  0c04458e9b82b37bf1472dfed3614a132c51736b

MODLIST_SHA1_HASH:  6b54b7e88e6922f58844e8953c82585173197b90

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

DUMP_FLAGS:  94

DUMP_TYPE:  1

ANALYSIS_SESSION_HOST:  T13800

ANALYSIS_SESSION_TIME:  01-27-2017 17:27:36.0288

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

THREAD_ATTRIBUTES:
OS_LOCALE:  DEU

PROBLEM_CLASSES:

    Tid    [0x0]
    Frame  [0x00]
    String [STATUS_NOT_IMPLEMENTED]
    Data Bucketing

BUGCHECK_STR:  STATUS_NOT_IMPLEMENTED

LAST_CONTROL_TRANSFER:  from 00007ffeebb4877f to 00007fff0b858a5c

STACK_TEXT: 
000000ff`410cde70 00007ffe`ebb4877f : 000000ff`41753a98 00007ffe`ebb2d214 000000ff`410ce060 00000000`00000000 : KERNELBASE!RaiseException+0x68
000000ff`410cdf50 00007ffe`ebb4811f : 000000ff`419ceed0 00000000`00000000 00000000`00000000 000000ff`40766fc0 : win32spl!NCSRCommon::VariantGetEncapsulatedType<NCSRCommon::TIniSpooler>+0x73
000000ff`410cdf90 00007ffe`ebbb2f99 : 000000ff`41a344b0 000000ff`41a344b0 00000000`00000000 00000000`00000000 : win32spl!NCSRCommon::GetAttribute<NCSRCommon::TIniSpooler * __ptr64>+0x67
000000ff`410ce010 00007ffe`ebb7c5e9 : 00000000`80070057 000000ff`417f0110 000000ff`410ce160 00000000`00000000 : win32spl!NCSRMonitor::TPortMonitor::NewIniSpooler+0xc9
000000ff`410ce0e0 00007ffe`ebb7cb50 : 000000ff`41838388 000000ff`41891970 00000000`00000002 00007ffe`f1c65760 : win32spl!NCSRMonitor::TPortMonitorTable::InitializePortMonitorTable+0xa1
000000ff`410ce150 00007ffe`f1c56b0a : 000000ff`417f0100 000000ff`41891970 00000000`00000000 000000ff`41891970 : win32spl!InitializePrintMonitor2+0x30
000000ff`410ce180 00007ffe`f1c57c78 : 00000000`000011cc 00000000`00000000 00000000`0000001a 00000000`00000000 : localspl!CreateMonitorEntry+0x29f
000000ff`410ce670 00007ffe`f1c57a27 : 000000ff`00000000 00000000`00000001 000000ff`410cf000 000000ff`41891970 : localspl!BuildAllPorts+0x150
000000ff`410ceb20 00007ffe`ebb86092 : 00000000`00000001 00007ffe`ebbe0efc 00000000`00000001 00000000`00000000 : localspl!SplCreateSpooler+0x577
000000ff`410cefe0 00007ffe`ebb4c5e3 : 00000000`00000001 00000000`00000001 000000ff`40767920 000000ff`406fdd08 : win32spl!NCSRCommon::TIniSpooler::CreateSpooler+0x1e2
000000ff`410cf120 00007ffe`ebb4e4a6 : 00000000`00000000 000000ff`4078aba0 000000ff`406fdd08 000000ff`40767420 : win32spl!TPrintOpen::FillInCacheAtAPC+0x9f
000000ff`410cf160 00007ffe`ebb4ec10 : 00000000`00000000 00000000`00000000 000000ff`419bc300 000000ff`41a18e20 : win32spl!TPrintOpen::ReEstablishCacheConnection+0xe2
000000ff`410cf1f0 00007ffe`ebb4e950 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : win32spl!TPrintOpen::ReEstablishPrinterConnection+0x20c
000000ff`410cf2c0 00007ffe`ebb3c194 : 00000000`00000036 00007ffe`ebb25c30 00000000`00000000 00007ffe`00000000 : win32spl!TPrintOpen::ReEstablishConnectionFromKey+0x1b0
000000ff`410cf3c0 00007ffe`ebb21286 : 000000ff`00000000 00000000`00000000 000000ff`406fdcf0 00000000`00000000 : win32spl!TPrintOpen::RediscoverPrinterConnections+0x19244
000000ff`410cf4e0 00007ff6`b4b1fccd : 00000000`00000088 00000000`00000000 00007ffe`f1c192b0 00000000`00000088 : win32spl!TPrintProviderTable::forwardEnumPrinters+0x50e
000000ff`410cf6b0 00007ff6`b4b20b1c : 00000000`00000006 00000000`00000000 000000ff`00000002 000000ff`41868b00 : spoolsv!EnumPrintersW+0xed
000000ff`410cf750 00007ff6`b4b209ca : 000000ff`00000006 00000000`00000000 00000000`00000002 000000ff`4070d5f0 : spoolsv!YEnumPrinters+0xec
000000ff`410cf7d0 00007ff6`b4b20336 : 000000ff`00000000 00007fff`00000002 00007fff`00000006 00000000`00000000 : spoolsv!TFunction8<unsigned long,unsigned short * __ptr64,unsigned long,unsigned char * __ptr64,unsigned long,unsigned long * __ptr64,unsigned long * __ptr64,enum Call_Route>::Run+0xca
000000ff`410cf860 00007fff`0e30678e : 00007ff6`b4b202d0 000000ff`416ffcc0 000000ff`410cfa48 000000ff`416ffd70 : spoolsv!NThreadingLibrary::TWorkCrew::tpSimpleCallback+0x62
000000ff`410cf890 00007fff`0e328e2d : 000000ff`416ffd70 000000ff`42021650 00000000`00000000 000000ff`4019a208 : ntdll!TppSimplepExecuteCallback+0x7e
000000ff`410cf8d0 00007fff`0e1b13d2 : 00000000`00000000 00007fff`0e3289b0 000000ff`401a4b20 00000000`00000000 : ntdll!TppWorkerThread+0x47d
000000ff`410cfcb0 00007fff`0e3054e4 : 00007fff`0e1b13b0 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x22
000000ff`410cfce0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34

THREAD_SHA1_HASH_MOD_FUNC:  3ffb06851e5d1577bb7a832702456151524547ee

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  4f17eb346ee9b4fe0522ddaed0fb8c9903f83d69

THREAD_SHA1_HASH_MOD:  682b6604ce70a3e2d769d192b70f848f40b90dd5

FOLLOWUP_IP:
win32spl!NCSRCommon::VariantGetEncapsulatedType<NCSRCommon::TIniSpooler>+73
00007ffe`ebb4877f 8bf8            mov     edi,eax

FAULT_INSTR_CODE:  c085f88b

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  win32spl!NCSRCommon::VariantGetEncapsulatedType<NCSRCommon::TIniSpooler>+73

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32spl

IMAGE_NAME:  win32spl.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  57d2c162

STACK_COMMAND:  .ecxr ; kb

BUCKET_ID:  STATUS_NOT_IMPLEMENTED_win32spl!NCSRCommon::VariantGetEncapsulatedType_NCSRCommon::TIniSpooler_+73

PRIMARY_PROBLEM_CLASS:  STATUS_NOT_IMPLEMENTED_win32spl!NCSRCommon::VariantGetEncapsulatedType_NCSRCommon::TIniSpooler_+73

FAILURE_EXCEPTION_CODE:  c0000002

FAILURE_IMAGE_NAME:  win32spl.dll

BUCKET_ID_IMAGE_STR:  win32spl.dll

FAILURE_MODULE_NAME:  win32spl

BUCKET_ID_MODULE_STR:  win32spl

FAILURE_FUNCTION_NAME:  NCSRCommon::VariantGetEncapsulatedType_NCSRCommon::TIniSpooler_

BUCKET_ID_FUNCTION_STR:  NCSRCommon::VariantGetEncapsulatedType_NCSRCommon::TIniSpooler_

BUCKET_ID_OFFSET:  73

BUCKET_ID_MODTIMEDATESTAMP:  57d2c162

BUCKET_ID_MODCHECKSUM:  dd346

BUCKET_ID_MODVER_STR:  6.3.9600.18470

BUCKET_ID_PREFIX_STR:  STATUS_NOT_IMPLEMENTED_

FAILURE_PROBLEM_CLASS:  STATUS_NOT_IMPLEMENTED

FAILURE_SYMBOL_NAME:  win32spl.dll!NCSRCommon::VariantGetEncapsulatedType_NCSRCommon::TIniSpooler_

FAILURE_BUCKET_ID:  STATUS_NOT_IMPLEMENTED_c0000002_win32spl.dll!NCSRCommon::VariantGetEncapsulatedType_NCSRCommon::TIniSpooler_

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/spoolsv.exe/6.3.9600.17415/54503ab3/KERNELBASE.dll/6.3.9600.18340/57366075/c0000002/00008a5c.htm?Retriage=1

TARGET_TIME:  2017-01-27T12:03:46.000Z

OSBUILD:  9600

OSSERVICEPACK:  17415

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  16

PRODUCT_TYPE:  3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

OSEDITION:  Windows 8.1 Server TerminalServer

USER_LCID:  0

OSBUILD_TIMESTAMP:  2014-10-29 03:45:30

BUILDDATESTAMP_STR:  141028-1500

BUILDLAB_STR:  winblue_r4

BUILDOSVER_STR:  6.3.9600.17415

ANALYSIS_SESSION_ELAPSED_TIME: 2a1d

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:status_not_implemented_c0000002_win32spl.dll!ncsrcommon::variantgetencapsulatedtype_ncsrcommon::tinispooler_

FAILURE_ID_HASH:  {95d9f5a4-50c1-9c0e-7448-501172d643fa}

Followup:     MachineOwner

I do not know, how to debug this forther. It seems, that is it not a Driver related Problem. Anyonce can help ?

WinServer2012R2 - Print server role - LPD service active

I can apply changes to the configured printport tcp/ip settings (default 515) to 516 (regedit or script).

I can open the port after changes have been applied but after 10-15 seconds this Raw Setting Port Number is reset to 515.

This behavior is not consitent because on some printports the changes are kept in the system.

What do I overlook?



After installing Windows 10, I found another something that doesn't work. It's my HP Desktop 3050A J611g All in One Printer.  I am getting an error message 0x0000007e

Can someone please help me with this one?

Thanks!

Manuel Robles

Hello!

I got a really delicate problem that I'm unable to figure out. And I would like some input from Reddit before I take the big step of opening a case at Microsoft.

I'm working as a consultant in the SMB-segment of IT. With that I have daily fights with regular PCs, virtual enviorments, networking and of course: Printers.

A couple of months ago we deployed a new printserver (Windows Server 2012), dedicated to a printing software for labels (Nicelabel). This printserver takes care of about 30 labelprinters, all from the same brand (Datamax-O'Neil MP Nova4). In the beginning of the deployment everything went stunning! Printing a label would'nt take less than 2-3 seconds and everybody was happy!

But since a couple of weeks back, we've seen horrible performance of the printing. Printing a label takes 10 seconds now days (exactly 10 seconds) on all the printers on that server. The label that's about to get printed (weather it's generated from the printing software, or simply a test page in Windows) gets stuck in the Printspool, and let's go after 10 seconds.

I've tried to disable bidirectional support, disabled "Advanced Printing Features" and changing the VLAN (so the printserver is on the same VLAN as the printers). Still the same problem. We are using the recommended driver from DATAMAX themself (according to them, there is no problem with the driver at all).

The printers has been deployed on the server with two simple Powershell-commands (see below):

add-printerport -name "$portname" -printerhostaddress "$portip"​
add-printer -name "$printername" -drivername "$driver" -port "$portname".

If I add another printer, let's say a HP 2055dn with Universal Print Driver, the printing process is working like a charm.

So, printer gurus at TechNet. What would you do?

Best regards, sad-consultant-who-deals-with-printers

Printers rolled out using GPP run in User Security Context

I am testing using an Administrator account

I get 2 types of errors in the log

1. 0x8007000a

Here's the Trace

2020-06-02 09:03:11.748 [pid=0x674,tid=0x1ba0] Adding child elements to RSOP.
2020-06-02 09:03:11.763 [pid=0x674,tid=0x1ba0] FindSharedPrinterEx: \\FS\Lexmark MS410-01 [SUCCEEDED(S_FALSE)]
2020-06-02 09:03:11.779 [pid=0x674,tid=0x1ba0] Failed to find shared printer with restricted token. [SUCCEEDED(S_FALSE)]
2020-06-02 09:03:11.841 [pid=0x674,tid=0x1ba0] InstallDriversEx: \\FS\Lexmark MS410-01
2020-06-02 09:03:11.904 [pid=0x674,tid=0x1ba0] AddSharedPrinterEx: \\FS\Lexmark MS410-01 [ hr = 0x8007000a "The environment is incorrect." ]
2020-06-02 09:03:11.904 [pid=0x674,tid=0x1ba0] Properties handled. [ hr = 0x8007000a "The environment is incorrect." ]
2020-06-02 09:03:11.904 [pid=0x674,tid=0x1ba0] Set system security context.
2020-06-02 09:03:11.904 [pid=0x674,tid=0x1ba0] EVENT : The user 'Lexmark MS410-01' preference item in the 'NEW - Printer Policy - Vaughan {1406C2FE-073A-4D5B-B64B-23CF4EF32AAF}' Group Policy Object did not apply because it failed with error code '0x8007000a The environment is incorrect.'%100790273
2020-06-02 09:03:11.904 [pid=0x674,tid=0x1ba0] There was a failure so the run once filter was rolled back. [ hr = 0x8007000a "The environment is incorrect." ]
2020-06-02 09:03:11.904 [pid=0x674,tid=0x1ba0] Error suppressed. [ hr = 0x8007000a "The environment is incorrect." ]
2020-06-02 09:03:11.904 [pid=0x674,tid=0x1ba0] Completed class <SharedPrinter> - Lexmark MS410-01.

2. 0x80070bc4

2020-06-02 09:03:12.107 [pid=0x674,tid=0x1ba0] Starting class <SharedPrinter> - KONICA MINOLTA C368.
2020-06-02 09:03:12.107 [pid=0x674,tid=0x1ba0] Preliminary filter processing (status may be adjusted).
2020-06-02 09:03:12.107 [pid=0x674,tid=0x1ba0] Set user security context.
2020-06-02 09:03:12.107 [pid=0x674,tid=0x1ba0] Post Filter processing.
2020-06-02 09:03:12.107 [pid=0x674,tid=0x1ba0] Adding child elements to RSOP.
2020-06-02 09:03:12.154 [pid=0x674,tid=0x1ba0] FindSharedPrinterEx: \\FS\KONICA MINOLTA C368 [SUCCEEDED(S_FALSE)]
2020-06-02 09:03:12.154 [pid=0x674,tid=0x1ba0] Failed to find shared printer with restricted token. [SUCCEEDED(S_FALSE)]
2020-06-02 09:03:12.216 [pid=0x674,tid=0x1ba0] InstallDriversEx: \\FS\KONICA MINOLTA C368 [ hr = 0x80070bc4 "No printers were found." ]
2020-06-02 09:03:12.216 [pid=0x674,tid=0x1ba0] Properties handled. [ hr = 0x80070bc4 "No printers were found." ]
2020-06-02 09:03:12.216 [pid=0x674,tid=0x1ba0] Set system security context.
2020-06-02 09:03:12.216 [pid=0x674,tid=0x1ba0] EVENT : The user 'KONICA MINOLTA C368' preference item in the 'NEW - Printer Policy - Vaughan {1406C2FE-073A-4D5B-B64B-23CF4EF32AAF}' Group Policy Object did not apply because it failed with error code '0x80070bc4 No printers were found.'%100790273
2020-06-02 09:03:12.216 [pid=0x674,tid=0x1ba0] There was a failure so the run once filter was rolled back. [ hr = 0x80070bc4 "No printers were found." ]
2020-06-02 09:03:12.216 [pid=0x674,tid=0x1ba0] Error suppressed. [ hr = 0x80070bc4 "No printers were found." ]
2020-06-02 09:03:12.216 [pid=0x674,tid=0x1ba0] Completed class <SharedPrinter> - KONICA MINOLTA C368.

Hi

We see some Printers have two DHCP options: DHCP and DHCP Auto.

https://support.brother.com/g/s/id/htmldoc/printer/cv_hl3040cn/eng/html/nug/chapter8_2_1.html

I don't really quite understand the difference between the two (the seem, as regarding DHCP at least, the same). Does anyone know if it matters which one we choose?

About 2 weeks ago it started that the printer settings were not propagated anymore to our Terminal Servers (Windows 2016, Version 1607). They are being propagated to our Windows 10 clients though.

I am talking about printer settings like "Print in black", Choices of paper tray, etc. 

What I tried so far:
- Delete and reconnect printer queues
- Delete printer queues and all registry setting before reconnecting
- Logged in and tried with a new user profile

The settings of the printer queue are the absolute standards of the printer driver, as if it was just installed and nothing was configured. So it even shows "Letter" as paper format and not "A4", even though the locale of our Terminals Servers is swiss-german.

Any ideas or suggestions on what to try?

Hi,

I have two printer servers. Each have their own unique printers and some duplicate printers from the other server.  My goal is to make each service identical for redundancy.

If I use the printer migration wizard to migrate printers from server A to server B will it only install printers which are not installed on Server B or will it overwrite everything including printers with the same name.

Thank you.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

I have a Windows 10 computer with a couple of shared printers.  I can access these printers fine from other Windows 10 computers.  However, when I try to connect to these printers from a Windows Server 2003, I get Access Denied errors.  I can see the printers on the Windows 10 computer, but I can't access them.  All the printers have full permissions set for Everyone.  I also have shared folders on the same Windows 10 computer.  I don't have any problems accessing these folders from the 2003 server.

Any suggestions on what the problem is?

Mike Schumann

I wrote about 9 pages on word document (2007), but when I try to print one or more of the pages.... it says NOT RESPONDING and the print queue is stuck in a spooling mode or it says print job time out !

however this particular document states that it has been REPAIRED and when opened last it caused a serious event or something but now it wont let me print any of the contents

nothing like this has happened before in the last 3 years or since i have had this computer

PS. I do not know anything about computers

ARIF

This “Print/Fax” Forum will be migrating to a new home on Microsoft Q&A!

We’ve listened to your feedback on how we can enhance the forum experience. Microsoft Q&A allows us to add new functionality and enables easier access to all the technical resources most useful to you, like Microsoft Docs and Microsoft Learn. 

Now until July 26, 2020:

• You can post any new questions onMicrosoft Q&A or here.

From July 27, 2019 until August 10, 2020:

• New posts– We invite you to post new questions in the “Print/Fax” forum’s new home on Microsoft Q&A. The current forum will not allow any new questions.
• Existing posts– Interact here with existing content, answer questions, provide comments, etc.

August 10, 2020 onward:

• This forum will be closed to all new and existing posts and all interactions will be inMicrosoft Q&A.

We are excited about moving to Microsoft Q&A and seeing you there.        

Learn More

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Hi Folks,

I have Windows Fax Server installed on both my Windows Server 2008R2 and my Windows Server 2012R2. Both work perfectly well sending and receiving faxes when I run Window Fax and Scan (wfs.exe) locally, either connected directly to the modem or connected to themselves as fax servers, but neither can connect to the other as a fax server, and the same is true of any of my desktops:

I'm the Fax Administrator and, trust me, I have consulted myself almost to the point of mayhem. Neither threats nor inducements have worked so far.

Since "permissions" is a huge, opaque area, and the list of things I have tried is long, I need a new approach, which is less focused on the specific problem of the fax server and more on permissions problems in general. Is there a way to discover the source of this security violation? What is protected? What are the existing permissions? What is trying to access it? What permissions are necessary?

For example, after many hours of analysis, I still don't know if the problem is on the client or the server. I see no log entries anywhere explaining the security violation. If I stop the Fax Service, then clients complain that there is no Fax Server, so I am getting as far as trying to connect, but after I re-start the Fax Service, I am right back to my permissions problem, meaning I have learned nothing. Is the client deciding that it can't connect or is the server rejecting the connection? Is there a log anywhere that can tell me?

So, my question is less about the specifics of the Windows Fax Server, and more about the general question, "How do I debug security violations in a GPO Managed Windows Domain?". This is a problem of opacity that Microsoft has not handled well, but I am not the first person to encounter this and I hope that smarter people than I have prevailed over this and have some worthwhile advice.

Thanks for the help,

Chris.

A network printer was moved from one location to another recently, and it got a new IP address since it is now in a different subnet.

I confirmed that the IP address in the printer was changed and, on the print server.  But it still shows up in Print Management as "offline", so it is also showing up as offline on the workstations it's deployed to.  The users can print to it.  I can ping it's IP.

Any ideas why it would be showing as offline?

Hello together,

Microsoft Print To PDF problem!

We have system issues with “Microsoft Print to PDF” printer / drivers.
We have this problem on one of our Windows 2016 Standard servers, which is in production environment. We already tried a lot of solutions and workarounds, regrettably with no success. The server also runs Print Server Role.

SYMPTOMS:
- Printer Microsoft Print to PDF is missing.
- Can`t be installed (it is not matter of user rights or incompatible drivers or software).
- Manual / GP install etc., (change & try all local ports etc.), did not solve the problem.
- Export / Import printers from other server in same pool (almost identical) not works (explicitly) for Microsoft Print To PDF.
- Driver Microsoft Print to PDF is missing (not presented at existing drivers). Microsoft updates did not help (system or search for print drivers).
- Driver can`t be added / installed (it is not matter of user rights or incompatible drivers or software).
- Replacing / Copy / Install etc., for *prnms009.inf (*03.inf,0*.inf, related) did not work. Same with full packages (printer files).
- Update of the server OS to 1607 / 14393.3808 - no result.
- After weeks with searches and solutions and lot of best practices from the major related vendors (OSs etc.), still no solution.

LOG (event viewer)
GENERAL – Unable to install Microsoft Print to PDF, Type 4- User Mode, x64driver ELEMENT NOT FOUND
ERROR 215 - Installing printer driver - failed, error code 0x490, HRESULT 0x80070490. See the event user data for context information.
ERROR 215 - Installing printer driver Microsoft Print To PDF failed, error code 0x0, HRESULT 0x80070490. See the event user data for context information.
ERROR 215 - Installing printer driver Microsoft Print To PDF failed, error code 0x0, HRESULT 0x80070490. See the event user data for context information.

LOG SYSTEM (event viewer)
- System - Provider [ Name]  Microsoft-Windows-PrintService [ Guid]  {747EF6FD-E535-4D16-B510-42C90F6873A1} EventID 215 Version 0 Level 2 Task 19 Opcode 12 Keywords 0x8000000000000220 - TimeCreated [ SystemTime]  2020-07-21T17:35:03.279174400Z EventRecordID 39262 Correlation - Execution [ ProcessID]  68640 [ ThreadID]  54096 Channel Microsoft-Windows-PrintService/Admin Computer xxxxxxxxx.xxxxxxxxxxxx.xxxxxx - Security [ UserID]  S-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx00 - UserData Label InstallPrinterDriverFromInfPackage Message InstallPrinterDriverFromPackage failed AdditionalInfo - InfPath C:\Windows\System32\DriverStore\FileRepository\prnms009.inf_amd64_bd3f6a64dee1535d\prnms009.inf DriverName Microsoft Print To PDF InstallSection - ProcessorArchitecture Windows x64 PackageAware Not package aware CoreDriverDependencies - LastError 0x0 HResult 0x80070490

Please for assistance.

Best Regards.
With respects:

Hi. Can anyone help me with this issue I have been battling with for a few days now. 

Setup 

Site 1 and 2 on the same domain. All server are running Windows Server 2016 Standard 

Site 1 =

Server 1 (DC / 192.168.15.220) - New build

Server 2 (Backup / 192.168.15.221) - New build 

HP LaserJet Pro (192.168.15.222) 

Printer is connected to DC and shared. As a test I can confirm that connecting the Shared HP Printer on Server 2 is successful. 

Printer is deployed via GP to users on site 1 - Successfully. 

Site 2 = connected via Site-to-Site VPN 

Server 3 (DC / 192.168.16.220) 

Server 4 (Remote Desktop / 192.168.16.225) - New Build 

When connecting Server 3 to the shared printer - 

When connecting Server 

4to the shared printer - Prompts "No Driver Found" click OK prompts "Connect to Printer, Windows cannot connect tothe printer. Access is denied"

If I then try to create a new printer using the printers IP address on Server 4 - It takes sometime connecting to the printer, followed by a request to install the printer driver (I have downloaded the driver only from HP), once selected the printer drive shows the correct model. This still looks good as it now asks for me to provide a printer name. Once I click next an error appears saying "Printer driver was not installed, Element not found - Frustrating. 

I can now go back and just as a test I select any driver which Microsoft has listed as available and I still get the "Element not found" error. It did evenually allow me to selecta generic driver which I then tried to change after install but again his and "Element not found" warning. 

Finally anyone from Site 1 who has the HP Shared Printer mapped and connects to the RDP server at Site 2 the printer will appear as a redirected printer without any isses. The GPO for the deployed printer must fail in the background as it hits the errors mentioned above. 

I cannot seem to figure it out and I am unable to explain why the printer will successfully connect to Server 3 when I try. 

Does anyone have any ideas? Any help or guidence would be greatly appreciated. 

Many thanks, Dan