Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1106 Source: MetaframeEvents

Level
Description
Client printer auto-creation failed.  The driver could not be installed. Possible reasons for the failure: The driver is not in the list of drivers on the server. The driver cannot be located. The driver has not been mapped. Client name: (<client name>) Printer: (<printer name>) Printer driver: (<printer driver name>)  
Comments
 
This problem can appear after you run DSCHECK 3.5 -> full printers -> purge option. See "Citrix Support Document ID: CTX108791" for a workaround.
When the Citrix server you are connecting to does not have the print driver of the local print queue located on the PC you are connecting from, this message will appear in the event log. However, if the Citrix server has the Universal Print Driver (UPD) installed, and you have enabled the option to use UPD when native drivers are not found, your print queue will still appear in the Citrix session regardless of this message showing up in the event log.
Citrix Document ID: CTX488760, Created on: Jul 3, 2002, Updated: Apr 23, 2003 indicate that this key must be added :
HKEY_LOCAL_MACHINE]SOFTWARE\Citrix\IMAPRINTER
Add the following:
Value Name: DisableError
Type: DWORDValue: 1
This event tells us that auto-creation failed. The reason for this is that a driver could not be found on the Citrix Server to match the driver named at the end of the event information. To resolve this, and ensure that the printer auto-creates correctly, open the Citrix Management Console, expand "Printers" in the left pane, highlight "drivers". In the right-hand pane a list of drivers currently installed will appear. Right-click anywhere on this list and select "Mapping". A new dialogue will open giveing you the oppurtunity to map a print driver. In the "Client Driver" box, type , exactly as it appears, the name of the client driver found in the Error Event message, or copy and paste it directly from the Error Event Message to ensure that no mistakes are made. When your user logs on again their printer will be auto-created and that message will not appear.
We solved this issue by clearing the c:\winnt\system32\spool\printers folder on the Citrix server.  On the server that had the error, that folder was pretty full with older files.


This is a very accurate message. It literally does mean that the client side driver is either named differently than the server side driver or that the driver does not exist on the server. If the correct driver is loaded, but the client uses a different name, map the driver in the CMC. This usually occurs when the client is 9x based. If the driver is not loaded, load it. Then verify the driver name against the client driver name. They must match. If not, map it in the CMC.
From a newsgroup post:
"In the Citrix User Forum I found a userīs hint to solve that problem.
---------------------
Here's cutouts of the four regfiles needed (might easily be made into one file):

1.reg looks like this:
----------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\RDPDR]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\RDPDR\0000]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"
"Class"="System"
"HardwareID"=hex(7):52, 00, 4f, 00, 4f, 00, 54, 00, 5c, 00, 52, 00, 44, 00, 50, 00, 44, 00, 52
, \
00, 00, 00, 00, 00
"Driver"="{4D36E97D-E325-11CE-BFC1-08002BE10318}\\0025"
"Mfg"="(Standard system devices)"
"Service"="rdpdr"
"DeviceDesc"="Terminal Server Device Redirector"
"ConfigFlags"=dword:00000000
"Capabilities"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\RDPDR\0000\LogConf]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\RDPDR\0000\Control]
"DeviceReference"=dword:818bd710
"ActiveService"="rdpdr"
-------------------------------------

Mind you that you have to check if the Driver={LotsOfNumbers}\\0025 -key is not already used under
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97D-E325-11CE-BFC1-08002BE10318}\0025]
If it's used, just enter a higher number in both the above 1.reg-file and the 4.reg-file below

2.reg looks like this:
----------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
root#rdpdr]
"Service"="rdpdr"
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"
----------------------------------------

3.reg looks like this
----------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rdpdr]
"Type"=dword:00000001
"Start"=dword:00000003
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):53, 00, 79, 00, 73, 00, 74, 00, 65, 00, 6d, 00, 33, 00, 32, 00, 5c, 00, 44,
00, \
52, 00, 49, 00, 56, 00, 45, 00, 52, 00, 53, 00, 5c, 00, 72, 00, 64, 00, 70, 00, 64, 00, 72, 00, 2e, \
00, 73, 00, 79, 00, 73, 00, 00, 00
"DisplayName"="Terminal Server Device Redirector Driver"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rdpdr\Security]
"Security"=hex:01, 00, 14, 80, a0, 00, 00, 00, ac, 00, 00, 00, 14, 00, 00, 00, 30, 00, 00, 00, 0
2, \
00, 1c, 00, 01, 00, 00, 00, 02, 80, 14, 00, ff, 01, 0f, 00, 01, 01, 00, 00, 00, 00, 00, 01, 00, 00, \
00, 00, 02, 00, 70, 00, 04, 00, 00, 00, 00, 00, 18, 00, fd, 01, 02, 00, 01, 01, 00, 00, 00, 00, 00, \
05, 12, 00, 00, 00, 20, 02, 00, 00, 00, 00, 1c, 00, ff, 01, 0f, 00, 01, 02, 00, 00, 00, 00, 00, 05, \
20, 00, 00, 00, 20, 02, 00, 00, 00, 00, 00, 00, 00, 00, 18, 00, 8d, 01, 02, 00, 01, 01, 00, 00, 00, \
00, 00, 05, 0b, 00, 00, 00, 20, 02, 00, 00, 00, 00, 1c, 00, fd, 01, 02, 00, 01, 02, 00, 00, 00, 00, \
00, 05, 20, 00, 00, 00, 23, 02, 00, 00, 00, 00, 00, 00, 01, 01, 00, 00, 00, 00, 00, 05, 12, 00, 00, \
00, 01, 01, 00, 00, 00, 00, 00, 05, 12, 00, 00, 00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rdpdr\Enum]
"0"="Root\\RDPDR\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001
----------------------------------

4.reg looks like this:
----------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97D-E325-11
CE-BFC1-08002BE10318}\0025]
"InfPath"="machine.inf"
"InfSection"="RDPDR"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00, 40, 99, 31, 33, 2e, bf, 01
"DriverDate"="11-14-1999"
"DriverVersion"="5.0.2183.1"
"MatchingDeviceId"="root\\rdpdr"
"DriverDesc"="Terminal Server Device Redirector"
----------------------------------

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...