Hi.
We run adobe 7 on windows xp workstations. Everything is fully patched. I have one workstation which sometimes hangs on doing pdf conversions, although most of the time it does convert successfully it is always slow - like a number of minutes slower than other equivalent workstations.
In the event viewer i always see error 6004 in the system log: "A driver packet received from the I/O subsystem was invalid." This made me suspect the network and I have updated the network card drivers, swapped network cards, checked cables etc but the error remains the same and everything else except pdf conversion are fine on that workstation.
Since this happens every time the Adobe LM Service stops and starts (many times a day), i am now wondering if the two are connected. I have searched on this topic but not found anything on the net so far. I am wondering if anyone else has seen this? I have spent a day messing about with the network to become convinced its an adobe problem. But since there are no specific adobe errors I don't know what to try except a complete rebuild. If anyone has some less radical ideas i'd love to hear them....
We run adobe 7 on windows xp workstations. Everything is fully patched. I have one workstation which sometimes hangs on doing pdf conversions, although most of the time it does convert successfully it is always slow - like a number of minutes slower than other equivalent workstations.
In the event viewer i always see error 6004 in the system log: "A driver packet received from the I/O subsystem was invalid." This made me suspect the network and I have updated the network card drivers, swapped network cards, checked cables etc but the error remains the same and everything else except pdf conversion are fine on that workstation.
Since this happens every time the Adobe LM Service stops and starts (many times a day), i am now wondering if the two are connected. I have searched on this topic but not found anything on the net so far. I am wondering if anyone else has seen this? I have spent a day messing about with the network to become convinced its an adobe problem. But since there are no specific adobe errors I don't know what to try except a complete rebuild. If anyone has some less radical ideas i'd love to hear them....