Windows 2003 to 2008 Print Migration Errors

Discussion in 'Server Setup' started by Tyler McLaughlin, Apr 10, 2009.

  1. Migrating from W2K3-R2 Ent SP2 X32
    Migrating to W2K8 Standard SP1 X64


    When attempting the migration of our "non-inbox print driver" W2K3R2 print
    cluster to W2K8 STD SP1, I'm receiving the following errors. (LPR Printing
    Role has been installed)

    There are quite a few like this for different drivers:

    Log Name: Application
    Source: Microsoft-Windows-PrintBRM
    Date: 4/10/2009 7:06:53 AM
    Event ID: 33
    Task Category: (3)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: MCPRINTDEV02.mclane.mclaneco.com
    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: SAVIN 9050 PCL 5e. 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="2009-04-10T12:06:53.000Z" />
    <EventRecordID>2997</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>MCPRINTDEV02.mclane.mclaneco.com</Computer>
    <Security />
    </System>
    <EventData>
    <Data Name="param1">SAVIN 9050 PCL 5e</Data>
    <Data Name="param2">Windows x64</Data>
    <Data Name="param3">0x80070057. The parameter is incorrect.
    </Data>
    </EventData>
    </Event>


    There are quite a few like this for different LPR Ports:

    Log Name: Application
    Source: Microsoft-Windows-PrintBRM
    Date: 4/10/2009 7:07:07 AM
    Event ID: 73
    Task Category: (8)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: MCPRINTDEV02.mclane.mclaneco.com
    Description:
    Printbrm.exe (the Printer Migration Wizard or the command-line tool) failed
    to restore the Line Printer Remote (LPR) port 172.31.114.250:mymnt because
    the LPR port monitor is not installed on the destination computer. Install
    the LPR port monitor on the destination computer.
    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">73</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>8</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-04-10T12:07:07.000Z" />
    <EventRecordID>3044</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>MCPRINTDEV02.mclane.mclaneco.com</Computer>
    <Security />
    </System>
    <EventData>
    <Data Name="param1">172.31.114.250:mymnt</Data>
    </EventData>
    </Event>


    There are quite a few like this for different print queues:

    Log Name: Application
    Source: Microsoft-Windows-PrintBRM
    Date: 4/10/2009 7:11:12 AM
    Event ID: 21
    Task Category: (2)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: MCPRINTDEV02.mclane.mclaneco.com
    Description:
    Printbrm.exe (the Printer Migration Wizard or the command-line tool) failed
    to restore print queue MGDMY_128 because port 172.31.114.250:mymnt is
    unknown. Printbrm.exe will attempt to restore the print queue on port FILE:
    instead. This can occur if the backup file contains incomplete data about the
    port, or if the port or port settings are incompatible with the version of
    Windows installed on the destination computer. Recreate the affected port on
    the destination computer and then change the print queue to use the new port.
    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">21</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>2</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-04-10T12:11:12.000Z" />
    <EventRecordID>3189</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>MCPRINTDEV02.mclane.mclaneco.com</Computer>
    <Security />
    </System>
    <EventData>
    <Data Name="param1">MGDMY_128</Data>
    <Data Name="param2">172.31.114.250:mymnt</Data>
    </EventData>
    </Event>

    There are quite a few like this for printer drivers:

    Log Name: Application
    Source: Microsoft-Windows-PrintBRM
    Date: 4/10/2009 7:14:36 AM
    Event ID: 76
    Task Category: (2)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: MCPRINTDEV02.mclane.mclaneco.com
    Description:
    Printbrm.exe (the Printer Migration Wizard or the command-line tool) failed
    to restore printer driver settings (PrinterDriverData, HPTRAYINFOREGDATA).
    Error 0x800706f4. A null reference pointer was passed to the stub.
    .. This can occur if the driver on the destination server is newer than the
    driver in the migration file. Open the printer Properties dialog box on the
    destination computer and manually specify the appropriate printer settings.
    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">76</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>2</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-04-10T12:14:36.000Z" />
    <EventRecordID>3294</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>MCPRINTDEV02.mclane.mclaneco.com</Computer>
    <Security />
    </System>
    <EventData>
    <Data Name="param1">PrinterDriverData</Data>
    <Data Name="param2">HPTRAYINFOREGDATA</Data>
    <Data Name="param3">0x800706f4. A null reference pointer was passed to
    the stub.
    </Data>
    </EventData>
    </Event>

    Warnings which occured (serveral like this for different drivers)

    Log Name: Application
    Source: Microsoft-Windows-PrintBRM
    Date: 4/10/2009 7:06:52 AM
    Event ID: 31
    Task Category: (3)
    Level: Warning
    Keywords: Classic
    User: N/A
    Computer: MCPRINTDEV02.mclane.mclaneco.com
    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 SAVIN 9050 PCL 5e 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="2009-04-10T12:06:52.000Z" />
    <EventRecordID>2996</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>MCPRINTDEV02.mclane.mclaneco.com</Computer>
    <Security />
    </System>
    <EventData>
    <Data Name="param1">SAVIN 9050 PCL 5e</Data>
    <Data Name="param2">Windows x64</Data>
    </EventData>
    </Event>
     
    Tyler McLaughlin, Apr 10, 2009
    #1
    1. Advertisements

  2. When attempting to download and install the W2K8 X64 driver from Savin for
    the above referenced failed install of SAVIN 9050 PCL 5e; the following error
    is being reported to the GUI (but not logged anywhere in the event logs)

    Add Printer Driver Wizard (Window Title)
    "Unable to install SAVIN 9050 PCL 5e, Type 3 - User Mode, x64 driver.
    Operation could not be completed (error 0x00000003)."

    Clicking OK is the only option. Upon clicking "OK" the following error is
    reported to the GUI and again not logged in event logs:

    Print Managment (Window Title)
    "Failed to add driver. Operation could not be completed (error 0x00000578)."
     
    Tyler McLaughlin, Apr 10, 2009
    #2
    1. Advertisements

  3. Meinolf Weber [MVP-DS], Apr 11, 2009
    #3
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.