I just had what looks to be my first successful attempt at creating a SP build with patches slipstreamed in. One of the cluster servers is now at NW6SP5 and that's where printing is located. My hope is that this will minimize one of the annoyances we've been experiencing of late.
Specifcally, one of the print-agents will throw a message of the sort:
"Life sucks. I'm stopping this agent for no reason"
Which works just like a circuit-breaker. The status still shows on, but it doesn't do anything. To get the printer-agent working again, you need to stop the agent then restart it. At which point things start processing again. This behavior could be the result of using post-SP5 NDPS modules (needed for PCounter to work right) with an SP4 machine. Hard to prove, so that's what I'm about to do.
Specifcally, one of the print-agents will throw a message of the sort:
"Life sucks. I'm stopping this agent for no reason"
Which works just like a circuit-breaker. The status still shows on, but it doesn't do anything. To get the printer-agent working again, you need to stop the agent then restart it. At which point things start processing again. This behavior could be the result of using post-SP5 NDPS modules (needed for PCounter to work right) with an SP4 machine. Hard to prove, so that's what I'm about to do.