Hi,

I'm having an issue where I'm trying to kill the printisolationhost.exe due to buggy drivers after it has ran for a set amount of time.

I have set the PrintDriverIsolationTimeBeforeRecycle registry key as described in https://blogs.technet.microsoft.com/askperf/2009/10/08/windows-7-windows-server-2008-r2-print-driver-isolation/

Despite setting this DWORD the process still runs longer than the time limit.

Does this key have a maximum time value that can be set? Does this key actually forcefully kill the process after running for the defined time? (in my current case 3 hours).

I am running on Server 2008 R2.

Thanks,

-J

Server 2008 R2 standard SP1

All:

Is there a way to see who is connected to a print share? I don't necessarily need the username, I'll take the IP address at this point.  Anything would help!

Thanks!

Hi, I am trying to set up Branch Office Direct print (BODP) in my test lab, and actually testing offline logs.

Server: Windows Server 2012 R2

Client: Windows 8.1

I was able to set up BODP, as I can see from the logs:

Document 4, Branch Office Direct Print Document owned by test-pc\Administrator on \\TEST-PC was printed on \\WIN-VLQLTIR7V77\Dell 1135n Laser MFP through port Branch Office Direct Printer Port.  Size in bytes: 44890. Pages printed: 1. No user action is required.

When I put Print server offline, I am still able to print on printer. Thats expected.

BUT, I am not able to log print events which sholud be cached on clients until the PrintServer will be online, as is described here:

https://technet.microsoft.com/en-us/library/dn482442(v=ws.11).aspx#Anchor_0

My printer setting from get-printer

Printer server and client are at the same domain.

When I bring PrintServer back online and review Print Logs, the printing which was done during period of print server was done, is not logged.

Can somebody help me, where could be problem ?

Thanks

Pavel

MCTS - Windows 7, Configuration

MCTS - Windows 7, Configuration

I have a Windows Server 2012 R2 server setup to be a print server in my corporate office. Branch Office Direct Printing is enabled for all of the print queues as well as client side rendering. I have a branch office where all of the computers in the office have Windows 10. As far as I can tell using Wireshark, their print jobs are going to the server in the corporate office then out to their printer in the branch office instead of printing directly to their printer. What do I need to do to get Branch Office Direct Printing working for them?

Hi all,

I have a print server set up in an AD domain. Guest account is disabled on the print server. Besides "Administrators", Print queues only have "Authenticated users - Print"  and "CREATOR OWNER - Manage documents" permissions.

The problem is when users with their own laptops hook up a network cable in the wall, find the printer through the ip address and install it on their laptop, they can bypass all that and print freely.

How can this be prevented?

"Installing printer driver DYMO Label Writer 400 Turbo failed, error code 0x490. HRESULT 0x80070940. 

I have literally tried everything to get this driver installed. All other print drivers work except this one. I have tried using a newer driver i have also tried updating all the drivers/firmware on this machine. I have also looked at installing the printer locally, and get the same error code. I also tried looking at hotfixes from microsoft but to no avail. Any insight on this would be helpful. Also looked at DYMO FAQ and nothing really came to light. Please help. 

Hi,

I have a few printers connected over a network through a Window Server. Recently I encountered an issue and would like seek answers from the community.

Lets just say I have 5 printers( P1, P2, P3, P4, P5). My computer is currently connected to P1 but when I print a document and send it to P1, it somehow came out from P2. It happened once and it went back to normal and came out from P1.

But somewhere around my office, someone also encountered this issue (instead of printing from the selected printer, it came out from some other printer and only happened once too.

No permissions were given to other printer.(Like user1 is only allowed to use P1 but not P2)

Can I check if has it got to do with the window server because our window server is quite old and we hardly do patching.

My problem is simple in Print management role (i'm on 2012r2), we can add many printer, drivers and other. We can deploy printers listed in GPO (and printers appear in "Deployed Printers"). But how can i do it when i have 2 printers?

On internet i have seen that we can set as defaut a printer with user config > Strat > Pref > Printers. Okay that's the old method. But if you publish printers with the "Deployed Printers" in Print management, printers are showed inuser config > Strat > Windows Parameters > Deployed Printers And we can't set nothing in this part of the GPO.

What is the solution ?

Thanks a lot !

We just set up a new print server (2008R2) and installed 5 print drivers shared across the network. The names appear correctly when adding them on Windows 7 Pro client laptops. However when clicking "Add a printer" on Windows 10 Pro laptops we're seeing multiple instances of some of the printers. For example on a Win7 machine the printer name appears properly as "Mobile Area 1 BW Copier on <printservername>". On a Win10 machine the same printer name appears + another entry named"Ricoh Aficio MP 5000". 

Thanks

Hank Vare

I've been dealing with an issue getting fax to work on client computers.

I've went through and added permissions to both the local fax and the fax service to Everyone (Just for testing) Disabled the firewall. The service is functional locally on the server but Windows 7 clients don't work over multiple computers. Server is updated to the latest I could get from Microsoft online update. 

I this error -

I tried everything uninstalling the drivers to updating it.. I tried a different usb cables.. I installed the twain, and scanner drivers manually,, I am out ideas and I hope the community will have a solution..

Additional info 

Log Name:      Microsoft-Windows-Kernel-PnP/Configuration
Source:        Microsoft-Windows-Kernel-PnP
Date:          1/23/2017 4:26:04 PM
Event ID:      411
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      AmanaServer.amanaautospares.co.ke
Description:
Device USB\VID_0482&PID_0606&MI_01\6&10467b15&2&0001 had a problem starting.

Driver Name: oem47.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Service: usbscan
Lower Filters: 
Upper Filters: 
Problem: 0x27
Status: 0x0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
    <EventID>411</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2017-01-23T13:26:04.763008700Z" />
    <EventRecordID>398</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="164" />
    <Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
    <Computer>AmanaServer.amanaautospares.co.ke</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="DeviceInstanceId">USB\VID_0482&amp;PID_0606&amp;MI_01\6&amp;10467b15&amp;2&amp;0001</Data>
    <Data Name="DriverName">oem47.inf</Data>
    <Data Name="ClassGuid">{36FC9E60-C465-11CF-8056-444553540000}</Data>
    <Data Name="ServiceName">usbscan</Data>
    <Data Name="LowerFilters">
    </Data>
    <Data Name="UpperFilters">
    </Data>
    <Data Name="Problem">0x27</Data>
    <Data Name="Status">0x0</Data>
  </EventData>
</Event>

Good Afternoon,

         A VIP at my company wants it so that if you have a printer that's already connected it does not show up as a choice when you go to add network printer. The company's pc's used to do this prior to a split and just realized that does not happen any more. I have looked and nothing I have found says that is possible. Another board member's Spouse works for the state and says that's how their network is. Can a GPO/script do this? Is that a function of SCCM (we had but lost because the $$$)?

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 ?

I would like to know how to go about solving the following scenario:

Client requesting Monochrome/Duplex setting as default on server print driver. User should only be able to change settings in document properties when printing and not on the printing defaults and printing preference sections.

Once user has printed the document, any setting user changed should default back to original Duplex/Monochrome settings.

Can this be achieved via Active Directory Print Policies or maybe logon script? And how would logon script look like?

I managed over 50 Windows 2008 and higher servers at several companies.  Every one of these servers has started recording the following error every time the servers are rebooted.  These server are NOT print servers.  They are NOT terminal servers. I have not attempted to install new printers in the past year. Can anyone tell me why I'm getting these errors and how to stop them?

Thanks,
Joe

Log Name:      Microsoft-Windows-PrintService/Admin
Source:        Microsoft-Windows-PrintService
Date:          1/29/2017 8:58:58 AM
Event ID:      215
Task Category: Installing a printer driver
Level:         Error
Keywords:      Printer Setup,Printer
User:          domain\admin
Computer:      server.domain.local
Description:
Installing printer driver {D20EA372-DD35-4950-9ED8-A6335AFE79F5} failed, error code 0x2, HRESULT 0x80070002. See the event user data for context information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" />
    <EventID>215</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>19</Task>
    <Opcode>12</Opcode>
    <Keywords>0x8000000000000220</Keywords>
    <TimeCreated SystemTime="2017-01-29T14:58:58.125841700Z" />
    <EventRecordID>544</EventRecordID>
    <Correlation />
    <Execution ProcessID="11640" ThreadID="14224" />
    <Channel>Microsoft-Windows-PrintService/Admin</Channel>
    <Computer>server.domain.local</Computer>
    <Security UserID="S-1-5-21-583907252-1645522239-682003330-500" />
  </System>
  <UserData>
    <SetupInstallPrinterDriver xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
      <Label>LegacyPrintDriverInstall</Label>
      <Message>-</Message>
      <AdditionalInfo>-</AdditionalInfo>
      <InfPath>C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_neutral_4616c3de1949be6d\ntprint.inf</InfPath>
      <DriverName>{D20EA372-DD35-4950-9ED8-A6335AFE79F5}</DriverName>
      <InstallSection>{D20EA372-DD35-4950-9ED8-A6335AFE79F5}</InstallSection>
      <ProcessorArchitecture>Windows x64</ProcessorArchitecture>
      <PackageAware>Package aware</PackageAware>
      <CoreDriverDependencies>-</CoreDriverDependencies>
      <LastError>0x2</LastError>
      <HResult>0x80070002</HResult>
    </SetupInstallPrinterDriver>
  </UserData>
</Event>