Windows 2008 R2 X64 Print Server Problem

Have also tried to import the identical information into Server B from Server A's printer migration export file......

Import Settings - finishes printer drivers

Hangs at same place..... Restoring Print Queues..... about 90% and stops.

Alo, if you have any idea why the printers disappeared in the first place, causing the problem, I would love to hear it....  thanks.

I deleted all the ports but one..... it will not delete, say it is in use.... this might be why it is hanging on the restore..... how do I clear it?

is there some what to edit the print management file and delete this port, and printer so it is not restored??

That is the likely culprit. Try shutting down the print spooler service (start-run-services.msc) and then delete the port. It will probably re-import fine after that.

Found a printer connected to the server that I cannot delete, that is on that port.

UPDATE..... got the rogue printer and port deleted.  Tried the import again from the original printer migration file for this server.....  still hangs on Restoring Print Queues

Should have asked this before....check the System and Application event logs, there should be a corresponding error.

Log Name:      Application
Source:        Microsoft-Windows-PrintBRM
Date:          4/5/2012 3:05:05 PM
Event ID:      31
Task Category: (3)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      1730W6LG5FP1.calvaryspringfield.org
Description:
Printbrm.exe (the Printer Migration Wizard or the command-line tool) restored a driver for a different processor architecture than that of the destination computer. Printbrm.exe will attempt to locate and install a native version of driver SHARP AR-M620N PCL6 on destination Windows x64. Try to print to the print queue, and if necessary, manually install a native version of the driver.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-PrintBRM" Guid="{CF3F502E-B40D-4071-996F-00981EDF938E}" EventSourceName="PrintBrm" />
    <EventID Qualifiers="32770">31</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>3</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-04-05T20:05:05.000000000Z" />
    <EventRecordID>51458</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>1730W6LG5FP1.calvaryspringfield.org</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">SHARP AR-M620N PCL6</Data>
    <Data Name="param2">Windows x64</Data>
  </EventData>
</Event>



Log Name:      Application
Source:        Microsoft-Windows-PrintBRM
Date:          4/5/2012 3:05:05 PM
Event ID:      33
Task Category: (3)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      1730W6LG5FP1.calvaryspringfield.org
Description:
The driver in the backup file is for a different processor architecture than the destination computer, and Printbrm.exe (the Printer Migration Wizard or the command-line tool) could not locate and install a native version of the driver. Driver: SHARP AR-M620N PCL6. Destination architecture: Windows x64. Error: 0x80070057. The parameter is incorrect.
. Install a native version of the driver on the destination computer and then retry importing the print queues.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-PrintBRM" Guid="{CF3F502E-B40D-4071-996F-00981EDF938E}" EventSourceName="PrintBrm" />
    <EventID Qualifiers="49154">33</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>3</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-04-05T20:05:05.000000000Z" />
    <EventRecordID>51459</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>1730W6LG5FP1.calvaryspringfield.org</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">SHARP AR-M620N PCL6</Data>
    <Data Name="param2">Windows x64</Data>
    <Data Name="param3">0x80070057. The parameter is incorrect.
</Data>
  </EventData>
</Event>


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>several of these type msgs >>>>>>>>>>>>>>>>>>
Log Name:      Application
Source:        Microsoft-Windows-PrintBRM
Date:          4/5/2012 3:05:05 PM
Event ID:      24
Task Category: (4)
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      1730W6LG5FP1.calvaryspringfield.org
Description:
Printbrm.exe (the Printer Migration Wizard or the command-line tool) successfully restored ZIMFPrint. No user action is required.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-PrintBRM" Guid="{CF3F502E-B40D-4071-996F-00981EDF938E}" EventSourceName="PrintBrm" />
    <EventID Qualifiers="16386">24</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>4</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-04-05T20:05:05.000000000Z" />
    <EventRecordID>51495</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>1730W6LG5FP1.calvaryspringfield.org</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">ZIMFPrint</Data>
  </EventData>
</Event>


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>last event

Log Name:      Application
Source:        Microsoft-Windows-PrintBRM
Date:          4/5/2012 3:05:05 PM
Event ID:      11
Task Category: (2)
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      1730W6LG5FP1.calvaryspringfield.org
Description:
Printbrm.exe (the Printer Migration Wizard or the command-line tool) is beginning a restore of print queues. No user action is required.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-PrintBRM" Guid="{CF3F502E-B40D-4071-996F-00981EDF938E}" EventSourceName="PrintBrm" />
    <EventID Qualifiers="16386">11</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>2</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-04-05T20:05:05.000000000Z" />
    <EventRecordID>51499</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>1730W6LG5FP1.calvaryspringfield.org</Computer>
    <Security />
  </System>
  <EventData>
  </EventData>
</Event>

Looks like a driver mismatch. Try pre-installing the correct driver for the printer(s) that are failing and rerun the import.

Check these links for more details:

http://technet.microsoft.com/en-us/library/cc734745(v=ws.10).aspx

http://technet.microsoft.com/en-us/library/cc734757(v=WS.10).aspx

Is it possible to import  printers selectively.....  wanting to import all the ones that work.
Command line syntax???

You could probably edit the xml file and comment out or remove entries.

What is the OS/architecture of source server  and the destination server? If you are going from a 32-bit machine to a 64-bit you will need to pre-install the 64-bit drivers.

You may also need to edit the config file to map the drivers if the names are different.

Example from http://blogs.technet.com/b/askperf/archive/2009/02/20/two-minute-drill-printbrm-and-the-configuration-file.aspx

<BrmConfig>

    <PLUGINS>
    </PLUGINS>

    <LanguageMonitors>
    </LanguageMonitors>

    <DriverMap>
        <DRV old="HP LaserJet 5Si" new="HP LaserJet 4Si"/>
    </DriverMap>

</BrmConfig>

Command line syntax:

http://technet.microsoft.com/en-us/library/dd379470(v=ws.10)

Sorry, just saw in your original post that both servers are 2K8R2 (64-bit only).

Have you tried preinstalling the drivers?

Another thing that caught my eye is "-noacl" switch which does not restore ACLs when the print queues are created during the import. Give that a go and see if it finishes since it was hanging on creating the queues.

Update..... cannot get it to work,......  so began process of reinstalling all printers manually.
This failed also....  cannot install any new printers.....  getting this error:
unable to install printer operation could not be completed server 2008 0x000006d9

Ruh-roh

Okay, 3 things to try.

First, log on with a user account that has never logged onto the server (domain admin equivalent). This will eliminate any profile issues. Try to create a printer. If it works, delete the cached profile for the user account you were using before. If it does not work go to next step.

Second, clean up all printer objects, drivers, etc. Pretty good list of steps in the first part of this post: http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/d5d1a4db-551c-4eb8-aff8-feaba8e22bea/ .....reboot after cleanup and try again. If it does not work....next step.

Third, run "sfc /verifyonly > sfc.txt" look through the file this creates for errors. If there are, run "sfc /scannow" after *** making sure you have a good full system backup ***

Lastly, are there other services running on the server (e.g. file services, DHCP, etc)? If not, you might be better served with a re-install. If that is not an option we are nearing the blue telephone support call.

one more thing....you can download and run the MS Product Support Report and see if it sheds any light on where the problem lies

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=24745

I appreciate your willingness to assist me.  While your solution did not fix the problem, it did assist me in working thru the problem to find a solution.  So, I am awarding the points on that basis.  Thanks.

Windows firewall was turned off and would not allow shared printers to be imported.   Turning on the firewall fixed the problem.

That is very interesting. Typically issues with the Windows Firewall are the other way around: turn it off to see if it is related to the problem mand work back from there to add rules as needed. We both learned something on this one.

Glad your issue is resolved.