This is what i found within the forum for users who have NetSupport Remote Software installed and are having issues with the Print Spooler Terminating Unexpectedly ID Event#7034.
Re: Print Spooler service terminated unexpectedly. after XPsp2
Refers to a problem with Remote Manager software and Print Spooling. Seem that stopping the Client32.exe service fixes the Spooling problem, though it leaves you with no remote management.
Stuff happens, that is why IT matters.
-------------------------------------
I spoke to NetSupport Thursday 26th Jan, they told me that the fix they were using for the Print Spooler Termination was, First when deploying a NSM Master down to the client this will create a .dll file called injib.dll, so rename this injib.old Then go to Program Files\ NetSupport Manager and double-click the PCICFGUI.EXE, then d/Click the Master Profile, then navigate to the Security Tree, then Access Privileges, look at the right hand side check boxes and "Disable Print Capture".
This is the fix they are advising customers as a work around. I have tried the "Dirty Fix" which is the one in Administrative Tools\ Services\ Print Spooler and navigate to the Recovery tab and change the settings from 1 to 0 in both boxes, this forces the print spooler to start immediately after a fraction of a second.
The latter fix works perfectly well, so it's up to you which one works better for you. I aslo added a registry value to keep the print spooler either at normal or high priority which did increase te speed of the spooler coming back on line, but we are talking in just a fraction of a second.
Good idea with the NetSupport follow-up. We checked with their support and where advised to go into Services and stop Client32. Then to rename injiblib.dll and pciminhook.dll, then reboot.
JohnK324
317 Posts
0
February 22nd, 2006 01:00
kjc218
5 Posts
0
February 22nd, 2006 01:00
Re: Print Spooler service terminated unexpectedly. after XPsp2
Refers to a problem with Remote Manager software and Print Spooling. Seem that stopping the Client32.exe service fixes the Spooling problem, though it leaves you with no remote management.
Stuff happens, that is why IT matters.
-------------------------------------
I spoke to NetSupport Thursday 26th Jan, they told me that the fix they were using for the Print Spooler Termination was, First when deploying a NSM Master down to the client this will create a .dll file called injib.dll, so rename this injib.old Then go to Program Files\ NetSupport Manager and double-click the PCICFGUI.EXE, then d/Click the Master Profile, then navigate to the Security Tree, then Access Privileges, look at the right hand side check boxes and "Disable Print Capture".
This is the fix they are advising customers as a work around. I have tried the "Dirty Fix" which is the one in Administrative Tools\ Services\ Print Spooler and navigate to the Recovery tab and change the settings from 1 to 0 in both boxes, this forces the print spooler to start immediately after a fraction of a second.
The latter fix works perfectly well, so it's up to you which one works better for you. I aslo added a registry value to keep the print spooler either at normal or high priority which did increase te speed of the spooler coming back on line, but we are talking in just a fraction of a second.
Good idea with the NetSupport follow-up. We checked with their support and where advised to go into Services and stop Client32. Then to rename injiblib.dll and pciminhook.dll, then reboot.
This also appears to work.
Stuff happens, that is why IT matters.