Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 595
  • Last Modified:

Citrix Print Management Service on Xendesktop 7

Morning Experts,

I am running a xendesktop 7 experience in my infrastructure. The Citrix Print Management Service intermittently crashes during the day. I can start the service back up but it will crash again after a few hours. Here's the error:


Faulting application name: CpSvc.exe, version: 7.1.0.4057, time stamp: 0x524ef6c8
Faulting module name: MSVCR80.dll, version: 8.0.50727.8428, time stamp: 0x520b0ac2
Exception code: 0x40000015
Fault offset: 0x0000000000006a68
Faulting process id: 0xb70
Faulting application start time: 0x01cfa5ba3ce5f121
Faulting application path: C:\Program Files (x86)\Citrix\system32\CpSvc.exe
Faulting module path: C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_88dcdb0b2fb19957\MSVCR80.dll
Report Id: a55711af-11af-11e4-80fd-005056bd5296
Faulting package full name:
Faulting package-relative application ID:


I have made sure to install the native drivers for our client printers onto the Delivery controller as well as the actual presentation server. I also have the citrix UPD disabled via the unfiltered policy on the delivery controller. Please give me some insight on this, as I'm still green to this citrix platform.
0
sonjayshepherd
Asked:
sonjayshepherd
1 Solution
 
Stephen EvansTech Support EngineerCommented:
Typically, cpsvc crashes are driver related. Even some native drivers can cause issues.
To rule out driver issues (or to confirm), set your policy to use Citrix UPD for all printers. If cpsvc stops crashing, we can assume its a driver related issue.

The only way to really know what is going on is to get a dump of the process when it crashes either using WER (http://support.citrix.com/article/CTX118614) or setting up ProcDump (http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx)

Once you have a dump file, open it up with WinDBG (http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx) and run the command "!analyze -v". This will give you the dll that it crashed on. If you are unsure who owns the dll, you can run the command "lmvm <dllName>" and it will give you the details on that dll file.

Typically, the dll will correlate to a driver that is in use.

Hope this helps,

Stephen
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now