Hi, What printer drivers are you using? What O.S. version 2000 Server or Server 2003? You've got a number of ways of dealing with rogue drivers. If it's HP, the native driver coverage in Windows server 2003 is quite good, otherwise you've got the HP Universal printer drivers (PCL and HP). Lexmark have "thin" drivers for many of their top end printers, Fuji Xerox (the Fuji end anyway) have TS friendly drivers etc. As far as low end printer support, in the long run it's far cheaper to get a more expensive printer than to have to cope with the "cost" of crap drivers and extortionate media costs. Anyway, back to your problem. It actually is possible to get an environment where the cpsvc is stable. You just have to know what to avoid ;-) Replacing drivers is easy enough that it's worth doing. regards, Rick Ulrich Mack Volante Systems ________________________________ From: thin-bounce@xxxxxxxxxxxxx on behalf of IT Support Sent: Wed 30/08/2006 20:41 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Anyone with printing problems install R02 yet? We're in a bit of a catch 22 situation here. We've got network printers with features that require the original drivers. The drivers crash cpsvc.... Apart from replacing the printers, there's not much else we can do apart from use this workaround! ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Pitsch Sent: Monday, August 28, 2006 8:58 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Anyone with printing problems install R02 yet? Sounds like a 'fix the symptom but not the problem' scenario here. Clean out your print drivers.... Jeff Pitsch Microsoft MVP - Terminal Server Forums not enough? Get support from the experts at your business http://jeffpitschconsulting.com <http://jeffpitschconsulting.com/> On 8/27/06, IT Support <it@xxxxxxxxxxxx> wrote: We get this too - to save you manually killing and restarting the service, put this script as a scheduled task on system startup. It monitors the event log and automatically restarts cpsvc whenever it runs into problems. Works a treat for us... ' Monitors the eventlog for event id 26 regarding cpsvc.exe, if found it kills the process and after 10 sec. restarts the process. ' 290805: Michael Pultz-Hansen / Martin Larsen, Compu-Game A/S, Denmark strComputer = "." Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate,(Security)}!\\" _ & strComputer & "\root\cimv2") ' send any instance creation events where the instance being created is of the Win32_NTLogEvent class Set colMonitoredEvents = objWMIService.ExecNotificationQuery _ ("Select * from __instancecreationevent where TargetInstance ISA " _ & "'Win32_NTLogEvent' and TargetInstance.EventCode = '26'") intContinue = 0 Do Until intContinue > 0 Set objLatestEvent = colMonitoredEvents.NextEvent strDisplayMessage = objLatestEvent.TargetInstance.Message If Instr(1, strDisplayMessage, "cpsvc.exe", 1) > 0 Then strComputer = "." arrTargetProcs = Array("cpsvc.exe") Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colProcesses = objWMIService.ExecQuery("SELECT * FROM Win32_Process") ' Checking for target processes ... For Each objProcess in colProcesses For Each strTargetProc In arrTargetProcs If LCase(objProcess.Name) = LCase(strTargetProc) Then Set WshShell = wscript.createobject("wscript.shell") WshShell.Exec("taskkill /im CpSvc.exe /f") End If Next Next ' Restart the CpSvc service after 10 sec. Dim WshShell WScript.Sleep 10000 Set WshShell = wscript.createobject("wscript.shell") WshShell.Exec("Net Start CpSvc") End If Loop ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto: thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> ] On Behalf Of thinlist@xxxxxxxxx Sent: 24 August 2006 13:50 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Anyone with printing problems install R02 yet? If the cpsvc is hanging then it *may* be related to printer drivers and not any fix in R02. If you are can handle the manually killing of the cpsvc for the moment I'd wait until citrix release a post R02 hotfix with a fix for the deleting printers after 5min issue. On 8/23/06, Evan Mann < emann@xxxxxxxxxxxxxxxxxxxxx <mailto:emann@xxxxxxxxxxxxxxxxxxxxx> > wrote: Have any of you that have been experience printing problems lately because of recent R01 hotfixes, updated to R02 and seen any relief? I've been reluctant to move to R02 because of the known issues with mapped printers being deleted 5 minutes post print system being restarted. That would be worse then just dealing with having to manually kill cpsvc.exe and restart the services like I do now. However, if R02 may solve the crashing issues in general, the 5 minute thing doesn't matter Click here <https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg==> to report this email as spam. ##################################################################################### This e-mail, including all attachments, may be confidential or privileged. Confidentiality or privilege is not waived or lost because this e-mail has been sent to you in error. If you are not the intended recipient any use, disclosure or copying of this e-mail is prohibited. If you have received it in error please notify the sender immediately by reply e-mail and destroy all copies of this e-mail and any attachments. All liability for direct and indirect loss arising from this e-mail and any attachments is hereby disclaimed to the extent permitted by law. ##################################################################################### ##################################################################################### This e-mail, including all attachments, may be confidential or privileged. Confidentiality or privilege is not waived or lost because this e-mail has been sent to you in error. If you are not the intended recipient any use, disclosure or copying of this e-mail is prohibited. If you have received it in error please notify the sender immediately by reply e-mail and destroy all copies of this e-mail and any attachments. All liability for direct and indirect loss arising from this e-mail and any attachments is hereby disclaimed to the extent permitted by law. #####################################################################################