All, my apologies for the delayed response. This issue has not been ignored, and is being addressed with the next roll of the Universal Print Driver (UPD), slated for late Aug 2014. While we haven't been able to repro this issue, we have been able to root-cause
from dump files provided by a few customers. As you have all found out, disabling status notifications (SNP) is the work-around, which doesn't get enabled if the driver is being installed in a 100+user domain (USERDNSDOMAIN environment variable set, then
LDAP query for # of users).
I hope this helps, and again, apologies for the delay in response.
Feel free to contact me directly with any questions/comments.
Best regards,
Dan
Daniel.eccher@hp.com
First of all, thanks for the update Dan; it's been an awfully long time in coming. And now a few questions if I (and many others, I'm sure) may (& I'm not trying to be rude or ungrateful here, just direct):
1. I'm incredulous that HP couldn't reproduce this problem when countless other people have experienced it each time they installed the printer driver; seems like at some point you said you were trying to reproduce it on virtual machines, which apparently
still are not like a regular "hardware install" on a standalone computer. Did you guys in fact try it with individual standalone computers by doing clean installs on them? As mentioned elsewhere, this occurs exclusively with Office 13, regardless
of whether it's on Windows 7, Windows 8 or Windows 8.1. In my broad experience it never happened with Office 2010.
2. What on Earth took so long after the original problem was identified and reported over a year ago? That's a really long response time, much more so than HP usually takes to address such a vexing bug. Remember this was not just a minor
annoyance; you could only print one job at a time and then the computer would be useless to print again (often locking up completely) until it was rebooted. This caused my clients untold agony, not to mention me, because I was expected to explain what the
problem was and magically fix it. (Fortunately after the work-around became known I could sort of head it off at the pass on future installations.)
3. Finally just exactly what, technically, was causing the problem? After all the turmoil and brain-damage we went through confronting this nightmare, I (and countless others, I'm sure) would like to know exactly what caused it to blow up
after printing only one time; I've never seen a bug like that before or after this time.
Thanks and standing by...
-
Edited by
Travis_Lloyd
Friday, May 23, 2014 7:28 AM
typo