{"id":718,"date":"2009-12-04T12:01:04","date_gmt":"2009-12-04T10:01:04","guid":{"rendered":"https:\/\/www.peppercrew.nl\/?p=718"},"modified":"2011-05-18T20:48:58","modified_gmt":"2011-05-18T19:48:58","slug":"fier-this-printer-driver","status":"publish","type":"post","link":"https:\/\/ingmarverheij.com\/en\/fier-this-printer-driver\/","title":{"rendered":"&#8220;Fier&#8221; this printer driver"},"content":{"rendered":"<p>Recently I wrote a few articles about the problems with printer drivers in a multi-user environment. In the past weeks I&#8217;ve been troubleshooting a problem with Citrix servers who randomly hang, without any clear cause.<br \/>\nThe source of all problems was a classic issue, bad printer drivers.<\/p>\n<p><strong>So what happened?<\/strong><br \/>\nThis can be seen through different eyes, and different perspective. The end-user, administrator and the consultant.<br \/>\n<!--more--><\/p>\n<p>Lets start with the end-user. The end-user is doing what he&#8217;s doing every day, working. Editing some documents, printing reports, browsing on the internet and doing some accounting and then&#8230; everything continues. But opening a new application fails, and internet pages won&#8217;t open anymore. But all other applications respond well.<br \/>\nNew users are unable to connect to the servers, the &#8216;hang&#8217; while waiting for the desktop to show.<br \/>\n<em>User: I can&#8217;t work like this! I&#8217;ll turn of my terminal and try again! (which fails, btw).<\/em><\/p>\n<p>Let&#8217;s assume the adminstrator actively monitors the server. He already has a session opened and he&#8217;s monitoring the server with TSAdmin and performance monitor.<br \/>\nThe most obvious sign is that the server doesn&#8217;t respond \/ refresh anymore in the TSAdmin and the performance values no longer refresh. There are no diagnostics available anymore.<br \/>\nHowever, same as with the users, the session of the administrator still respons well.<br \/>\nBecause launching a new task manager fails (only the tray icons shows) we&#8217;ll assume the administrator already opened the task manager. Just like the performance data collected remotely, the task administrator doesn&#8217;t refresh anymore. It&#8217;s unresponsive.<br \/>\n<em>Administrator : I can&#8217;t administer this server! All I can do is restart the server.<\/em><\/p>\n<p>The consultant (Hi! That&#8217;s me!) looks at the server and sees the same as the administrator. I hangs, but it doesn&#8217;t. All the signals tell me that this is a known error, altough there are more possibilities. Desktop heap exhaustion, black hole effect or print spooler&#8230; As a quick test the print spooler is killed (and the Citrix Print Spooler service). And guess what, the server continues to work!<br \/>\n<em>Consultant : There are issues with printer drivers!<\/em><\/p>\n<p><strong>The culprit<\/strong><br \/>\nAfter a long and thorough search I finnaly found the source of the problems.<br \/>\nThe customer uses a &#8220;Konica Minolta Di5510&#8221; multi functional printer and has recently been added to the network (due to a merge). This printer uses the &#8220;Fiery X3e 7255BW-KM eu&#8221; driver and this driver causes the problem.<br \/>\nAfter replacing the driver with a different, more general, driver the problem was &#8216;solved&#8217;. The environment has been stable for two weeks (and counting).<br \/>\nAltough the driver worked before on a 2003\/PS4 environment, it didn&#8217;t work well on a 2003R2\/XA5 environment.<br \/>\nUnfortunately there&#8217;s just 1 driver available for both PS as PCL, version 1.0. And since this is a MFP, a different driver result in a loss of functionality.<\/p>\n<p>Since the source of the problem is solved, the customer is happy. A real solution is investigated. This can either be a new driver, a new printer or using a silo.<\/p>\n<p>In case you&#8217;re having the same problem with the printer you can find the printer driver (and hopefully a new version) <a href=\"https:\/\/onyxftp.mykonicaminolta.com\/download\/SearchResults.aspx?productid=331&amp;filetypeid=0\">here<\/a>.<\/p>\n<p><strong>Finding the source of the problems<\/strong><br \/>\nIn these situations finding the source of the problem isn&#8217;t easy. There are so many possible places to look, it takes a lot of time. Because of the signs (sort-off) hanging and the quickfix (kill the print spooler) I started by testing the printer drivers.<br \/>\nAfter a stresstest of the printer drivers the most plausible cause was the &#8220;Fiery X3e 7255BW-KM eu&#8221; printer driver.<\/p>\n<p>Ingmar Verheij<\/p>","protected":false},"excerpt":{"rendered":"<p>Recently I wrote a few articles about the problems with printer drivers in a multi-user environment. In the past weeks I&#8217;ve been troubleshooting a problem with Citrix servers who randomly hang, without any clear cause. The source of all problems was a classic issue, bad printer drivers. So what happened? This can be seen through [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-container-style":"default","site-container-layout":"default","site-sidebar-layout":"default","disable-article-header":"default","disable-site-header":"default","disable-site-footer":"default","disable-content-area-spacing":"default","footnotes":""},"categories":[296],"tags":[667,90,119,120,121,93,122,108,23],"class_list":["post-718","post","type-post","status-publish","format-standard","hentry","category-printing","tag-citrix","tag-crash","tag-di5510","tag-fiery","tag-fiery-x3e-7255bw-km","tag-hang","tag-konica-minolta","tag-printer-driver","tag-terminal-server"],"_links":{"self":[{"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/posts\/718","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/comments?post=718"}],"version-history":[{"count":2,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/posts\/718\/revisions"}],"predecessor-version":[{"id":2314,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/posts\/718\/revisions\/2314"}],"wp:attachment":[{"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/media?parent=718"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/categories?post=718"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/tags?post=718"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}