Printing Now Fixed

  • user warning: Table 'cache' is marked as crashed and should be repaired query: SELECT data, created, headers, expire FROM cache WHERE cid = 'filter:1:ca2840fa083f5d271495e2b8d8773929' in /home/dowdle/public_html/montanalinux/includes/database.mysql.inc on line 121.
  • user warning: Table 'cache' is marked as crashed and should be repaired query: UPDATE cache SET data = '<p>As usual with most tech support I deal with they tend to have you rehash much of what you already have done; assuming you are technically savvy yourself. It infuriates me further to have to jump though their hoops to get any cooperation. The first reply this morning from IT is to \"power down the printer and retry the same documents and report what the error logs say\". Well the only thing that proved was that this issue did not produce those error logs. Those errors were probably legit.</p>\n<p>So on my own I attempt to print to file and use DOS to copy the file to the device. Here I get \"The system cannot write to the specified device.\" This sounds like a write permissions problem. Just before I even got the email off to report this to them, I got a message back stating they changed the spool settings and reboot our server.</p>\n<p>You see, even in Windows I try my best to avoid rebooting servers. Perhaps they didn\'t know you can restart individual services in Windows. Ah well, guess we\'re good to go for another couple weeks before needing to reboot.</p>\n<br class=\"clear\" />', created = 1410931912, expire = 1411018312, headers = '' WHERE cid = 'filter:1:ca2840fa083f5d271495e2b8d8773929' in /home/dowdle/public_html/montanalinux/includes/database.mysql.inc on line 121.
| |

As usual with most tech support I deal with they tend to have you rehash much of what you already have done; assuming you are technically savvy yourself. It infuriates me further to have to jump though their hoops to get any cooperation. The first reply this morning from IT is to "power down the printer and retry the same documents and report what the error logs say". Well the only thing that proved was that this issue did not produce those error logs. Those errors were probably legit.

So on my own I attempt to print to file and use DOS to copy the file to the device. Here I get "The system cannot write to the specified device." This sounds like a write permissions problem. Just before I even got the email off to report this to them, I got a message back stating they changed the spool settings and reboot our server.

You see, even in Windows I try my best to avoid rebooting servers. Perhaps they didn't know you can restart individual services in Windows. Ah well, guess we're good to go for another couple weeks before needing to reboot.