Hi
We use RDS on Server 2008 R2 and I have recently come across multiple errors being reported on the Terminal Server.
These errors are reported when users print to HP 3015N printers. I have replicated the error reporting by sending a print and then watching the Error log create 4 new erros for every print sent.
Event Log error:
Log Name: Microsoft-Windows-PrintService/Admin
Source: Microsoft-Windows-PrintService
Date: 16/04/2013 09:47:57
Event ID: 808
Task Category: Initializing
Level: Error
Keywords: Print Spooler
User: WREXHAM\ks
Computer: CCLTS.wrexham.local
Description:
The print spooler failed to load a plug-in module C:\Windows\system32\spool\DRIVERS\x64\3\UNIDRVUI.DLL, error code 0xc1. 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>808</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>36</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000020000</Keywords>
<TimeCreated SystemTime="2013-04-16T08:47:57.569724400Z" />
<EventRecordID>221775</EventRecordID>
<Correlation />
<Execution ProcessID="51960" ThreadID="50052" />
<Channel>Microsoft-Windows-PrintService/Admin</Channel>
<Computer>CCLTS.wrexham.local</Computer>
<Security UserID="S-1-5-21-683164905-1790711394-740312968-2029" />
</System>
<UserData>
<LoadPluginFailed xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
<PluginDllName>C:\Windows\system32\spool\DRIVERS\x64\3\UNIDRVUI.DLL</PluginDllName>
<ErrorCode>0xc1</ErrorCode>
<Context>112</Context>
</LoadPluginFailed>
</UserData>
</Event>
The same error is reported throughout the day whenever the users print to this printer.
I have limited knowledge on really how to tackle this issue - can you help?
Perhaps installing a new driver from the HP Site - there appears to be a new one available dated Dec 2012 - but the release notes for this upgrade do not note this issue as being fixed..