PrintMig Error: Can't get printer driver direcotry

[Christine]

Hello,

I'm using the printmig.exe tool to migrate print queues
from a Windows2000 server to a Windows 2003 server. It
can backup OK. If I try and do any kind of restore, even
a restore to itself I get the following error message:

FAILURE - Can't get printer driver directory: 1722

Anyone got any ideas how to fix this?

Christine.

 

[Sean]

Sounds like there is a registry problem. Here are some details. The
printer directories are in:

%SYSTEMROOT \ system32 \ spool \ drivers \ <platform> \ <printername>

PLATFORM = W32X86 (2000 and XP), X64 (XP x64, Server 2003 x64), IA64 (XP
Itanium) and others
PRINTERNAME = duh

Also:

%SYSTEMROOT \ system32 \ spool \ drivers \ <platform> \ <version-#>

VERSION-# = the number from the registry entry below, as in "Version-3"

The printers the system knows about are defined in the Registry:

HKLM / System / CurrentControlSet / Control / Print / Printers

There should be an entry for each printer.

Also in the registry:

HKLM / System / CurrentControlSet / Control / Print / Environments /
<platform> / Drivers / Version-3 / <printername>

Maybe (probably) there is a printer listed in the registry that does not
have a printer-driver-directory -- an install or uninstall that failed.

Either delete the registry entries that refer to non-existent printers, or,
to be safer, create the missing directory manually.

 

[Alan Morris\(MSFT\)]

the RPC listening endpoint is not set on Server 2003 until one adds a shared
printer or turns on the RPC endpoint in gpedit.msc. Printmig should work
locally but will always fail remotely on a fresh install

launch gpedit.msc / Administrative Templates / Printers
Allow Print Spooler to accept client connections

enable this.



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.