+ Post New Thread
Page 1 of 3 123 LastLast
Results 1 to 15 of 32
Windows 7 Thread, Win7 64bit and Server 2003 printers in Technical; Bit of a noob question here but I'm trying to get our new Win7 64bit PCs to connect to the ...
  1. #1
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,321
    Thank Post
    115
    Thanked 91 Times in 61 Posts
    Rep Power
    29

    Win7 64bit and Server 2003 printers

    Bit of a noob question here but I'm trying to get our new Win7 64bit PCs to connect to the printers shared on our Server 2003 32 bit box.

    Bascially we use the PrintUiEntry command to add printers to a machine:

    rundll32 printui.dll,PrintUIEntry /ga /n\\server\printername

    This works great on XP but the Win7 machines come up with an error: ('Operation could not be completed error 0x00000709) and no printer is added.

    I guess this is something to do with 64bit drivers? Do I need the 64bit drivers on the 2003 server, or do I install them on the 64 client? Or can I somehow make the client use the existing 32bit drivers that are already on the server?

    The printers I'm trying to add are all HP - HP only seem to offer a 'universal' driver for Win7 64 bit

  2. #2

    mac_shinobi's Avatar
    Join Date
    Aug 2005
    Posts
    9,762
    Thank Post
    3,271
    Thanked 1,053 Times in 974 Posts
    Rep Power
    365

  3. #3

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,172
    Thank Post
    868
    Thanked 2,698 Times in 2,288 Posts
    Blog Entries
    11
    Rep Power
    772
    The 32bit UPD is avalible HP Universal Print Driver Series for Windows*-* Download drivers and software - HP Business Support Center

    HP Universal Print Driver Series for Windows*-* Download drivers and software - HP Business Support Center

    and you just need to make sure that your 32bit server is using the same version as you want to add a 64 bit driver for, download both, install the UPD on the server and then under the shareing tab there is an additional drivers button, click that, x64 and point it to the location of the extracted UPD driver.

    You can swap out the drivers on your existing printers and as long as you have added the x64 one once it will be avalible to all printers using the UPD. Your clients will then just pull down the correct driver for its platform when the script is run.
    Last edited by SYNACK; 31st May 2011 at 12:24 PM.

  4. 2 Thanks to SYNACK:

    mac_shinobi (31st May 2011), Sheridan (31st May 2011)

  5. #4
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,321
    Thank Post
    115
    Thanked 91 Times in 61 Posts
    Rep Power
    29
    Hmm when I try to add the 64bit UPD driver to the server (in Additional Drivers \ x64) it just tells me there is no driver 'for the requested processor architecture'?

  6. #5

    mac_shinobi's Avatar
    Join Date
    Aug 2005
    Posts
    9,762
    Thank Post
    3,271
    Thanked 1,053 Times in 974 Posts
    Rep Power
    365
    Quote Originally Posted by Sheridan View Post
    Hmm when I try to add the 64bit UPD driver to the server (in Additional Drivers \ x64) it just tells me there is no driver 'for the requested processor architecture'?
    As per my first link - there is a comment on or near the bottom of the tutorial :

    1. GeronimoDubois posted the comment on June 23rd, 2010

    2. A lot of older model HP printers, for which i can’t use the universal PCL6 driver (because i need printer specific features). The Win7 drivers are only available from Win7, not from HP site anymore. I guess installing the drivers once on the win7 client, and then using RSAT from that client to install it on the Windows 2003 server does the trick.

  7. Thanks to mac_shinobi from:

    Sheridan (31st May 2011)

  8. #6
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,321
    Thank Post
    115
    Thanked 91 Times in 61 Posts
    Rep Power
    29
    Ahh I see - I just need to try and get the correct driver on the client first. Which I haven't managed to do yet as it just sits at the 'checking windows update' stage for ages when I try to add the printer.

    Edit:

    Nope still struggling with this. Downloaded the 64 bit UPD which won't install on the server. Managed to get the Windows 7 64 bit driver on the client and copied it over with Print management to the server. Still get the error adding the printer (error 0x00000709) which seems to be as if it can't see the server/printer. It definitely can because if I use the GUI to add the printer it is listed!
    Last edited by Sheridan; 31st May 2011 at 01:05 PM.

  9. #7

    mac_shinobi's Avatar
    Join Date
    Aug 2005
    Posts
    9,762
    Thank Post
    3,271
    Thanked 1,053 Times in 974 Posts
    Rep Power
    365
    Quote Originally Posted by Sheridan View Post
    Ahh I see - I just need to try and get the correct driver on the client first. Which I haven't managed to do yet as it just sits at the 'checking windows update' stage for ages when I try to add the printer
    Think before you get to that stage if i remember correctly its either to do with :

    1. A checkbox that needs un checking regarding automatically finding or updating drivers

    2. Selecting the correct option with regards to manually setting up the printer

    Also with regards to manually setting up the printer on a win 7 client I think I used LPR and to enable LPR you can do the following on the client - see attached pdf.

    I was using the method described in the pdf for single clients but not sure how it would work with regards to what you are trying to do
    Attached Files Attached Files

  10. #8
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,321
    Thank Post
    115
    Thanked 91 Times in 61 Posts
    Rep Power
    29
    If I skip the windows update section I've now got the 64bit driver loaded on both client and server.

    I get an error whether I run the script or when I manually add using the gui! When I leave the windows update to complete it simply comes back with a message saying it couldn't find a .inf file for '(Unknown)' - odd as it knows the printer driver name!

  11. #9

    mac_shinobi's Avatar
    Join Date
    Aug 2005
    Posts
    9,762
    Thank Post
    3,271
    Thanked 1,053 Times in 974 Posts
    Rep Power
    365
    Quote Originally Posted by Sheridan View Post
    If I skip the windows update section I've now got the 64bit driver loaded on both client and server.

    I get an error whether I run the script or when I manually add using the gui! When I leave the windows update to complete it simply comes back with a message saying it couldn't find a .inf file for '(Unknown)' - odd as it knows the printer driver name!
    Any info on the error - any screen grab of said error and also copy of the script ?

  12. #10
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,321
    Thank Post
    115
    Thanked 91 Times in 61 Posts
    Rep Power
    29
    I'm not in front of the server now - I'll get some screen shots when I'm back in the office!

  13. #11
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,321
    Thank Post
    115
    Thanked 91 Times in 61 Posts
    Rep Power
    29
    Right, this is the error I get when I run the command: (attachment error1)
    Code:
    rundll32 printui.dll,PrintUIEntry /ga /n\\server\printer
    And if I let it search Windows Update for a driver I get the error shown in error2

    This is with the 64bit driver on both the client and the server - checked by looking at Print management on the client, and also on the server itself

    Even more bizarre - if I add the printer manually by specifying its IP address, the client installs the printer (using the x64 driver) and works OK!

    Does the PrintUIEntry command just no longer work on Windows 7?
    Attached Images Attached Images
    Last edited by Sheridan; 1st June 2011 at 11:25 AM.

  14. #12

    mac_shinobi's Avatar
    Join Date
    Aug 2005
    Posts
    9,762
    Thank Post
    3,271
    Thanked 1,053 Times in 974 Posts
    Rep Power
    365
    Quote Originally Posted by Sheridan View Post
    Right, this is the error I get when I run the command: (attachment error1)
    Code:
    rundll32 printui.dll,PrintUIEntry /ga /n\\server\printer
    And if I let it search Windows Update for a driver I get the error shown in error2

    This is with the 64bit driver on both the client and the server - checked by looking at Print management on the client, and also on the server itself

    Even more bizarre - if I add the printer manually by specifying its IP address, the client installs the printer (using the x64 driver) and works OK!

    Does the PrintUIEntry command just no longer work on Windows 7?
    Any chance you can try with the PCL 5 driver if there is one available ?

    For both print server and client - not sure if its related but found something on google stating that if a profile is deleted then the memory / cache in the print spooler is not deleted and to work around it to restart the print spooler service, just curious if that helps or makes any difference on a windows 7 client ?
    Last edited by mac_shinobi; 1st June 2011 at 11:50 AM.

  15. #13

    mac_shinobi's Avatar
    Join Date
    Aug 2005
    Posts
    9,762
    Thank Post
    3,271
    Thanked 1,053 Times in 974 Posts
    Rep Power
    365

  16. #14
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,321
    Thank Post
    115
    Thanked 91 Times in 61 Posts
    Rep Power
    29
    The spooler at client and server end has been restarted many times now.

    When I run the PrintUIEntry manually (through command line) I get no errors, and if I run it with the /ge option it shows the printer in the list!

    So its adding the printer,but not showing it for the users. I'm guessing it can't find/load the drivers to finish the process in some way?

    I've also tried this on a 32 bit version of Windows 7 - same error!

  17. #15
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,321
    Thank Post
    115
    Thanked 91 Times in 61 Posts
    Rep Power
    29
    Removing the line from my script that sets the printer as default has got rid of that error now - but still the printer doesn't appear to install. I've also tried enabling Network Discovery and still no luck.

    The error in the PrintService log shows this:

    Code:
    Log Name:      Microsoft-Windows-PrintService/Admin
    Source:        Microsoft-Windows-PrintService
    Date:          01/06/2011 12:37:32
    Event ID:      215
    Task Category: Installing a printer driver
    Level:         Error
    Keywords:      Printer Setup,Printer
    User:          SYSTEM
    Computer:      computer.domain
    Description:
    Installing printer driver HP LaserJet P2050 Series PCL 6 failed, error code 0x0, HRESULT 0x80070705. See the event user data for context information.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" />
        <EventID>215</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>19</Task>
        <Opcode>12</Opcode>
        <Keywords>0x8000000000000220</Keywords>
        <TimeCreated SystemTime="2011-06-01T11:37:32.985737100Z" />
        <EventRecordID>86</EventRecordID>
        <Correlation />
        <Execution ProcessID="1068" ThreadID="2280" />
        <Channel>Microsoft-Windows-PrintService/Admin</Channel>
        <Computer>computername</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <UserData>
        <SetupInstallPrinterDriver xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
          <Label>InternalInstallPrinterDriverFromPackage</Label>
          <Message>pfnPSetupParseInfAndCommitFileQueue failed</Message>
          <AdditionalInfo>-</AdditionalInfo>
          <InfPath>-</InfPath>
          <DriverName>HP LaserJet P2050 Series PCL 6</DriverName>
          <InstallSection>-</InstallSection>
          <ProcessorArchitecture>Windows x64</ProcessorArchitecture>
          <PackageAware>Not package aware</PackageAware>
          <CoreDriverDependencies>-</CoreDriverDependencies>
          <LastError>0x0</LastError>
          <HResult>0x80070705</HResult>
        </SetupInstallPrinterDriver>
      </UserData>
    </Event>
    That doesn't really give me any more info.
    Last edited by Sheridan; 1st June 2011 at 12:43 PM.

SHARE:
+ Post New Thread
Page 1 of 3 123 LastLast

Similar Threads

  1. How do I add 64bit printer drivers to Server 2003
    By edutech4schools in forum Windows Server 2000/2003
    Replies: 3
    Last Post: 20th May 2011, 08:40 PM
  2. Sharing option missing - Server 2003 64bit
    By greengate in forum Windows Server 2000/2003
    Replies: 1
    Last Post: 7th September 2010, 04:41 PM
  3. Upgrading print drivers for Win7 (server 2003)
    By RTFM in forum Windows Server 2000/2003
    Replies: 2
    Last Post: 3rd September 2010, 12:17 PM
  4. PHP to work with IIS 6 in 64bit Windows Server 2003
    By MattGibson in forum Windows Server 2000/2003
    Replies: 8
    Last Post: 31st July 2009, 11:50 AM
  5. Replies: 11
    Last Post: 24th May 2006, 07:45 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •