Issue selecting network printer as default (error 0x00000709)
Hi,
I have had an issue recently where a user had a problem selecting a default printer.
The environment is the following:
Windows 2008R2 domain
Windows 2008R2 SP1 Connection Broker/Terminal server.
vWorkspace 7.2 MR1
Office 2010 SP1 32 bit
Windows 7 clients with 7.2 MR1 connector
Most of the printers in the environment are Print-It printers set up on a remote print relay. However, there was one MFD that is used to print envelopes. I could not get the device to recoginse the correct paper size with the universal driver. The printer support company refused to help unless I used the native driver. In the end I had to admit defeat and install the driver on the terminal server, and map the envelope print queue as a standard network printer using Manage Network Printers under the Resources\Printers node.
It maps fine, but when the user tries to select this printer as default, they get error 0x00000709. After looking at the user registry I found that there was no entry for this printer under HKCU\Software\Microsoft\Windows NT\CurrentVersion\Devices, although there were entries for all the Print-It printers (which can be selected as defaults with no issues). After manually adding a value for this print queue, the user could then select it as default.
I am not sure if this is an issue with the way vWorkspace is mapping the printer or a Windows problem. I am going to look at mapping the printer with GP preferences to see if this makes any difference.
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
9086
0
Posted 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