Frequently Asked Question
job owner issue - terminal server
Last Updated 8 years ago
facing the following issue:
http://support.microsoft.com/kb/958741
This issue is a clear Microsoft issue which they accept as there failure and offer a fix for 2008 and Vista SP1.
However this issue also can occur on Windows 2008R2 which the customer is using.
The solution there is to run the following modifications:
1. In Registry Editor, locate the following subkey:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\
2. Right-click Printers, point to New, and then click DWORD.
3. Type EnabledProtocols.
4. Double click EnabledProtocols.
5. In the Value data box, type 6.
6. Close Registry Editor.
7. Restart the Spooler
We asked the customer to implement this solution but he like first know if Pcounter has experience with this issue. Also he is afraid that this modifications have a negative effect on the print speed.
He found http://social.technet.microsoft.com/Forums/windowsserver/en-US/71b2c4ec-94b1-4302-8f07-349696e9f4d1/windows-server-2008-r2-print-server-job-owner-issue?forum=winserverprint
That shows some discussions about this issue.
http://support.microsoft.com/kb/958741
This issue is a clear Microsoft issue which they accept as there failure and offer a fix for 2008 and Vista SP1.
However this issue also can occur on Windows 2008R2 which the customer is using.
The solution there is to run the following modifications:
1. In Registry Editor, locate the following subkey:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\
2. Right-click Printers, point to New, and then click DWORD.
3. Type EnabledProtocols.
4. Double click EnabledProtocols.
5. In the Value data box, type 6.
6. Close Registry Editor.
7. Restart the Spooler
We asked the customer to implement this solution but he like first know if Pcounter has experience with this issue. Also he is afraid that this modifications have a negative effect on the print speed.
He found http://social.technet.microsoft.com/Forums/windowsserver/en-US/71b2c4ec-94b1-4302-8f07-349696e9f4d1/windows-server-2008-r2-print-server-job-owner-issue?forum=winserverprint
That shows some discussions about this issue.