I had looked at that KB article, but it didn’t seem to be the problem I was seeing. The user was able to print to the printer and see its properties, they just couldn’t select it as their default.
...and checking the various registry locations mentioned, I found that the connection value for the printer was missing from the users’s HKU\Software\Microsoft\Windows NT\CurrentVersion\Devices key.
Manually creating a value for the printer connection under this key appears to have “fixed” the issue for the user for now. I am unable to replicate the problem with a different test user account.
The printer is shared off the same print server as the Print-It printers. Connection is using the server short name \\ServerName\PrinterShareName, not the FQDN or IP address.
Like you I think this is probably a Windows issue.
When you saw the error 0x00000709 trying to set the printer as default, was the user able to print to it?
Did you try to access the printer properties, if so did you see the same error?
I have been looking at this further and can see this problem may be fairly common when using Windows 7 clients and printers shared from a Windows 2008 server. I have read a number of articles claiming different resolutions to this issue. It seems it can be related to the way in which Windows 7 makes the printer connections.
When you see the error there should be an event recorded in the Windows event log, this may contain more details, such as further error codes. Have you seen if this is the case?
I would believe this is a printer mapping problem that is associated to Windows rather than anything vWorkspace is doing. Please take a look at this link http://support.microsoft.com/kb/2546625 which offers a potential solution.
If this does not resolve the problem can you supply further information such as, the connection specifics, did you use NetBIOS, FQDN or IP to locate the print server?
I am having the same issue. I have spent hours on the phone this morning with tech support from printer and Microsoft. Is there any way you can help me? I am able to print test page, print from Word, and the internet. In a program I downloaded to print cd labels (Memorex) I am unable to print. Computer will not allow me to change my default printer (even though I have uninstalled old printer's driver). Any help would be GREATLY appreciated as Microsoft wants to charge me to log in to my computer to attempt to solve my problem.
The problem that Scott reported was related to the use of Quest vWorkspace and our Print-IT feature, using our universal printer driver. Unfortunately I was not able to identify the root cause, as Scott implied, it was probably a local Windows install issue rather than a fault of vWorkspace.
I am sorry I can't help any further,
David
P.S. you suggest the printer works fine for test pages, Word and Internet so is the application you downloaded at fault? Are you able to try another application that provides the option to print CD labels?
2. Right click on the name of your printer and select “see what’s printing”
3. In the que view, select “Open As Administrator”
4. Then select “Set As Default Printer” on the main menu, note if it is already opened up as administrator, then you may not see the option to open it as administrator.
scott.knights-a
9 Posts
0
August 9th, 2011 01:00
Hi David,
I had looked at that KB article, but it didn’t seem to be the problem I was seeing. The user was able to print to the printer and see its properties, they just couldn’t select it as their default.
After looking at this blog posting:
http://blogs.technet.com/b/askperf/archive/2009/10/10/windows-7-windows-server-2008-r2-location-aware-printing.aspx
...and checking the various registry locations mentioned, I found that the connection value for the printer was missing from the users’s HKU\Software\Microsoft\Windows NT\CurrentVersion\Devices key.
Manually creating a value for the printer connection under this key appears to have “fixed” the issue for the user for now. I am unable to replicate the problem with a different test user account.
The printer is shared off the same print server as the Print-It printers. Connection is using the server short name \\ServerName\PrinterShareName, not the FQDN or IP address.
Like you I think this is probably a Windows issue.
Scott
DELL-David Y
228 Posts
1
August 8th, 2011 07:00
Hi Scott,
When you saw the error 0x00000709 trying to set the printer as default, was the user able to print to it?
Did you try to access the printer properties, if so did you see the same error?
I have been looking at this further and can see this problem may be fairly common when using Windows 7 clients and printers shared from a Windows 2008 server. I have read a number of articles claiming different resolutions to this issue. It seems it can be related to the way in which Windows 7 makes the printer connections.
When you see the error there should be an event recorded in the Windows event log, this may contain more details, such as further error codes. Have you seen if this is the case?
I would believe this is a printer mapping problem that is associated to Windows rather than anything vWorkspace is doing. Please take a look at this link http://support.microsoft.com/kb/2546625 which offers a potential solution.
If this does not resolve the problem can you supply further information such as, the connection specifics, did you use NetBIOS, FQDN or IP to locate the print server?
Regards
David
crob2
2 Posts
0
November 26th, 2012 14:00
David, I am hoping you and or Scott can give me some advice. I replied to his last comment in this thread with some details. Thank you in advance!!
crob2
2 Posts
0
November 26th, 2012 14:00
Scott and David,
I am having the same issue. I have spent hours on the phone this morning with tech support from printer and Microsoft. Is there any way you can help me? I am able to print test page, print from Word, and the internet. In a program I downloaded to print cd labels (Memorex) I am unable to print. Computer will not allow me to change my default printer (even though I have uninstalled old printer's driver). Any help would be GREATLY appreciated as Microsoft wants to charge me to log in to my computer to attempt to solve my problem.
Thanks in advance for any guidance.
DELL-David Y
228 Posts
0
November 26th, 2012 15:00
Hi Chrisi,
The problem that Scott reported was related to the use of Quest vWorkspace and our Print-IT feature, using our universal printer driver. Unfortunately I was not able to identify the root cause, as Scott implied, it was probably a local Windows install issue rather than a fault of vWorkspace.
I am sorry I can't help any further,
David
P.S. you suggest the printer works fine for test pages, Word and Internet so is the application you downloaded at fault? Are you able to try another application that provides the option to print CD labels?
scott.knights
29 Posts
0
November 26th, 2012 22:00
Hi Chrisi,
I have found that this error is usually related to invalid or missing values in the following registry keys:
HKCU\Software\Microsoft\Windows NT\CurrentVersion\Devices
HKCU\Software\Microsoft\Windows NT\CurrentVersion\Printerports
If you are using a RDSH (terminal server) make sure you have this hotfix installed to prevent these keys getting polluted with junk values:
http://support.microsoft.com/kb/2620656
You should also check the default printer value in this key:
HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows
REG_SZ Device
sader82
43 Posts
0
March 11th, 2013 11:00
Hi Scott,
I hope you find an solution already! But I want to share this with you :-)
your printer are not listed in: HKCU\Software\Microsoft\Windows NT\CurrentVersion\Devices
So follow the next steps to fix the issue: http://www.van-gelderen.eu/?p=67
johnnymccormack
9 Posts
0
November 29th, 2014 04:00
1. Click Start and select “Devices & Printers”
2. Right click on the name of your printer and select “see what’s printing”
3. In the que view, select “Open As Administrator”
4. Then select “Set As Default Printer” on the main menu, note if it is already opened up as administrator, then you may not see the option to open it as administrator.
Checkout this guide @ Error 0x00000709
DELL-Kevin R
25 Posts
0
December 16th, 2014 03:00
Hi Scott,
Kevin here from support - just following up to see if the issue is resolved?
Thanks