Error migrating printers using PrintBRM

[Tim Crosby]

I am using Vista's print management console to connect to a Windows Server
2003 print server to try and export the printers to a file. When I
right-click the server and select "Export printers to a file", it starts the
wizard and I tell it to save the file on the C: drive of the Vista machine.
It starts exporting printers and printer drivers. It gets about 95% of the
way through and says "Export complete: Windows encountered errors during the
migration process. Open Event Viewer for more information". If I open event
viewer, I see nothing but informational events showing the drivers being
exported, no warnings or errors. But my backup file never gets created.

If I try using printbrm.exe from a command prompt, it gets through all the
print drivers and then says "The following error occurred: 0x800700a1. The
specified path is invalid." Again, nothing in the event logs except
informational events.

If I look at the list of all the things it is going to export, it appears
that it is crashing when it starts backing up the print processors. There
are about 25 of them to be exported, but it doesn't appear to do any of them.
And I don't see any way to exclude the print processors from being exported
or even to remove some of them to see if they are the problem.

Any ideas on how to get around this? I have not tried print migrator yet
but I think it is replaced by PrintBRM?

Thanks,

Tim

 

[Alan Morris [MSFT]]

Re: Error migrating printers using PrintBRM

the error equates to

G:\>winerror 161
161 ERROR_BAD_PATHNAME <--> 0xc0000039 STATUS_OBJECT_PATH_INVALID
161 ERROR_BAD_PATHNAME <--> 0xc000003b STATUS_OBJECT_PATH_SYNTAX_BAD
161 ERROR_BAD_PATHNAME <--> 0xc0000281
STATUS_DIRECTORY_IS_A_REPARSE_POINT



Is this a standalone machine or a cluster?

If it's a cluster you will need Vista SP1.

Do you use separator pages on the printers?



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

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

"Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
news:A347C1D8-A4E6-41EC-AE32-DFD2E8CBB0FD@microsoft.com...
>I am using Vista's print management console to connect to a Windows Server
> 2003 print server to try and export the printers to a file. When I
> right-click the server and select "Export printers to a file", it starts
> the
> wizard and I tell it to save the file on the C: drive of the Vista
> machine.
> It starts exporting printers and printer drivers. It gets about 95% of
> the
> way through and says "Export complete: Windows encountered errors during
> the
> migration process. Open Event Viewer for more information". If I open
> event
> viewer, I see nothing but informational events showing the drivers being
> exported, no warnings or errors. But my backup file never gets created.
>
> If I try using printbrm.exe from a command prompt, it gets through all the
> print drivers and then says "The following error occurred: 0x800700a1. The
> specified path is invalid." Again, nothing in the event logs except
> informational events.
>
> If I look at the list of all the things it is going to export, it appears
> that it is crashing when it starts backing up the print processors. There
> are about 25 of them to be exported, but it doesn't appear to do any of
> them.
> And I don't see any way to exclude the print processors from being
> exported
> or even to remove some of them to see if they are the problem.
>
> Any ideas on how to get around this? I have not tried print migrator yet
> but I think it is replaced by PrintBRM?
>
> Thanks,
>
> Tim

 

[Tim Crosby]

Re: Error migrating printers using PrintBRM

I am using Vista SP1, but the server is standalone.

I do not use separator pages. This server is not really production. I set
it up to start testing the ability to migrate printers around should this
server fail once it becomes production. There's really nothing special about
it. The only thing I've installed besides the printers is the HP Web
JetAdmin tools.

I downloaded print migrator 3.1 and was able to use that to dump everything
to a cab file. It did not report any errors when it ran. But I was hoping
to get the print management console to do this as we want our print server to
be 2008. Can I use print migrator 3.1 to import into a 2008 server? Or do I
have to use the print management console?

Tim

"Alan Morris [MSFT]" wrote:

> the error equates to
>
> G:\>winerror 161
> 161 ERROR_BAD_PATHNAME <--> 0xc0000039 STATUS_OBJECT_PATH_INVALID
> 161 ERROR_BAD_PATHNAME <--> 0xc000003b STATUS_OBJECT_PATH_SYNTAX_BAD
> 161 ERROR_BAD_PATHNAME <--> 0xc0000281
> STATUS_DIRECTORY_IS_A_REPARSE_POINT
>
>
>
> Is this a standalone machine or a cluster?
>
> If it's a cluster you will need Vista SP1.
>
> Do you use separator pages on the printers?
>
>
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
> news:A347C1D8-A4E6-41EC-AE32-DFD2E8CBB0FD@microsoft.com...
> >I am using Vista's print management console to connect to a Windows Server
> > 2003 print server to try and export the printers to a file. When I
> > right-click the server and select "Export printers to a file", it starts
> > the
> > wizard and I tell it to save the file on the C: drive of the Vista
> > machine.
> > It starts exporting printers and printer drivers. It gets about 95% of
> > the
> > way through and says "Export complete: Windows encountered errors during
> > the
> > migration process. Open Event Viewer for more information". If I open
> > event
> > viewer, I see nothing but informational events showing the drivers being
> > exported, no warnings or errors. But my backup file never gets created.
> >
> > If I try using printbrm.exe from a command prompt, it gets through all the
> > print drivers and then says "The following error occurred: 0x800700a1. The
> > specified path is invalid." Again, nothing in the event logs except
> > informational events.
> >
> > If I look at the list of all the things it is going to export, it appears
> > that it is crashing when it starts backing up the print processors. There
> > are about 25 of them to be exported, but it doesn't appear to do any of
> > them.
> > And I don't see any way to exclude the print processors from being
> > exported
> > or even to remove some of them to see if they are the problem.
> >
> > Any ideas on how to get around this? I have not tried print migrator yet
> > but I think it is replaced by PrintBRM?
> >
> > Thanks,
> >
> > Tim
>
>
>

 

[Alan Morris [MSFT]]

Re: Error migrating printers using PrintBRM

Print Management just launches printbrmui.exe, then it's completely out of
the picture.

printbrm.exe will give the best indication of the failure.

look through the print processor registry and confirm print procs and the
files. under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows
NT x86\Print Processors (if you have x64 look there too)

I hit an issue one time where a print proc was listed as
\3\printprocname.dll. I don't recall that I was getting any error, I think
it just never migrated.

I did not need the print processor any longer so I removed it. I have tools
for this but the spooler UI for the field is regedit, sorry.



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

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

"Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
news840BBC8-6CEE-4944-93B6-C730525CD976@microsoft.com...
>I am using Vista SP1, but the server is standalone.
>
> I do not use separator pages. This server is not really production. I set
> it up to start testing the ability to migrate printers around should this
> server fail once it becomes production. There's really nothing special
> about
> it. The only thing I've installed besides the printers is the HP Web
> JetAdmin tools.
>
> I downloaded print migrator 3.1 and was able to use that to dump
> everything
> to a cab file. It did not report any errors when it ran. But I was
> hoping
> to get the print management console to do this as we want our print server
> to
> be 2008. Can I use print migrator 3.1 to import into a 2008 server? Or do
> I
> have to use the print management console?
>
> Tim
>
> "Alan Morris [MSFT]" wrote:
>
>> the error equates to
>>
>> G:\>winerror 161
>> 161 ERROR_BAD_PATHNAME <--> 0xc0000039 STATUS_OBJECT_PATH_INVALID
>> 161 ERROR_BAD_PATHNAME <--> 0xc000003b STATUS_OBJECT_PATH_SYNTAX_BAD
>> 161 ERROR_BAD_PATHNAME <--> 0xc0000281
>> STATUS_DIRECTORY_IS_A_REPARSE_POINT
>>
>>
>>
>> Is this a standalone machine or a cluster?
>>
>> If it's a cluster you will need Vista SP1.
>>
>> Do you use separator pages on the printers?
>>
>>
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/search/?adv=1
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
>> news:A347C1D8-A4E6-41EC-AE32-DFD2E8CBB0FD@microsoft.com...
>> >I am using Vista's print management console to connect to a Windows
>> >Server
>> > 2003 print server to try and export the printers to a file. When I
>> > right-click the server and select "Export printers to a file", it
>> > starts
>> > the
>> > wizard and I tell it to save the file on the C: drive of the Vista
>> > machine.
>> > It starts exporting printers and printer drivers. It gets about 95% of
>> > the
>> > way through and says "Export complete: Windows encountered errors
>> > during
>> > the
>> > migration process. Open Event Viewer for more information". If I open
>> > event
>> > viewer, I see nothing but informational events showing the drivers
>> > being
>> > exported, no warnings or errors. But my backup file never gets
>> > created.
>> >
>> > If I try using printbrm.exe from a command prompt, it gets through all
>> > the
>> > print drivers and then says "The following error occurred: 0x800700a1.
>> > The
>> > specified path is invalid." Again, nothing in the event logs except
>> > informational events.
>> >
>> > If I look at the list of all the things it is going to export, it
>> > appears
>> > that it is crashing when it starts backing up the print processors.
>> > There
>> > are about 25 of them to be exported, but it doesn't appear to do any of
>> > them.
>> > And I don't see any way to exclude the print processors from being
>> > exported
>> > or even to remove some of them to see if they are the problem.
>> >
>> > Any ideas on how to get around this? I have not tried print migrator
>> > yet
>> > but I think it is replaced by PrintBRM?
>> >
>> > Thanks,
>> >
>> > Tim
>>
>>
>>

 

[Tim Crosby]

Re: Error migrating printers using PrintBRM

Thanks for your help Alan.

I ran printbrm from my Vista machine again and I see now that it is in fact
exporting the print processors. When it runs, it starts by listing the print
queues, print drivers, print processors, and then the printer ports (in that
order). Then I see it "Saving Print Queues", "Saving Print Processors",
"Saving Print Drivers", and then it crashes. It appears to save all the
drivers. I'm assuming that the next step should be "Saving Printer Ports"?

I only have 8 printer ports on this server, and they are all pretty much the
same, tcpip ports with a name like IP_172.16.100.2.

Tim

"Alan Morris [MSFT]" wrote:

> Print Management just launches printbrmui.exe, then it's completely out of
> the picture.
>
> printbrm.exe will give the best indication of the failure.
>
> look through the print processor registry and confirm print procs and the
> files. under
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows
> NT x86\Print Processors (if you have x64 look there too)
>
> I hit an issue one time where a print proc was listed as
> \3\printprocname.dll. I don't recall that I was getting any error, I think
> it just never migrated.
>
> I did not need the print processor any longer so I removed it. I have tools
> for this but the spooler UI for the field is regedit, sorry.
>
>
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
> news840BBC8-6CEE-4944-93B6-C730525CD976@microsoft.com...
> >I am using Vista SP1, but the server is standalone.
> >
> > I do not use separator pages. This server is not really production. I set
> > it up to start testing the ability to migrate printers around should this
> > server fail once it becomes production. There's really nothing special
> > about
> > it. The only thing I've installed besides the printers is the HP Web
> > JetAdmin tools.
> >
> > I downloaded print migrator 3.1 and was able to use that to dump
> > everything
> > to a cab file. It did not report any errors when it ran. But I was
> > hoping
> > to get the print management console to do this as we want our print server
> > to
> > be 2008. Can I use print migrator 3.1 to import into a 2008 server? Or do
> > I
> > have to use the print management console?
> >
> > Tim
> >
> > "Alan Morris [MSFT]" wrote:
> >
> >> the error equates to
> >>
> >> G:\>winerror 161
> >> 161 ERROR_BAD_PATHNAME <--> 0xc0000039 STATUS_OBJECT_PATH_INVALID
> >> 161 ERROR_BAD_PATHNAME <--> 0xc000003b STATUS_OBJECT_PATH_SYNTAX_BAD
> >> 161 ERROR_BAD_PATHNAME <--> 0xc0000281
> >> STATUS_DIRECTORY_IS_A_REPARSE_POINT
> >>
> >>
> >>
> >> Is this a standalone machine or a cluster?
> >>
> >> If it's a cluster you will need Vista SP1.
> >>
> >> Do you use separator pages on the printers?
> >>
> >>
> >>
> >> --
> >> Alan Morris
> >> Windows Printing Team
> >> Search the Microsoft Knowledge Base here:
> >> http://support.microsoft.com/search/?adv=1
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
> >> news:A347C1D8-A4E6-41EC-AE32-DFD2E8CBB0FD@microsoft.com...
> >> >I am using Vista's print management console to connect to a Windows
> >> >Server
> >> > 2003 print server to try and export the printers to a file. When I
> >> > right-click the server and select "Export printers to a file", it
> >> > starts
> >> > the
> >> > wizard and I tell it to save the file on the C: drive of the Vista
> >> > machine.
> >> > It starts exporting printers and printer drivers. It gets about 95% of
> >> > the
> >> > way through and says "Export complete: Windows encountered errors
> >> > during
> >> > the
> >> > migration process. Open Event Viewer for more information". If I open
> >> > event
> >> > viewer, I see nothing but informational events showing the drivers
> >> > being
> >> > exported, no warnings or errors. But my backup file never gets
> >> > created.
> >> >
> >> > If I try using printbrm.exe from a command prompt, it gets through all
> >> > the
> >> > print drivers and then says "The following error occurred: 0x800700a1.
> >> > The
> >> > specified path is invalid." Again, nothing in the event logs except
> >> > informational events.
> >> >
> >> > If I look at the list of all the things it is going to export, it
> >> > appears
> >> > that it is crashing when it starts backing up the print processors.
> >> > There
> >> > are about 25 of them to be exported, but it doesn't appear to do any of
> >> > them.
> >> > And I don't see any way to exclude the print processors from being
> >> > exported
> >> > or even to remove some of them to see if they are the problem.
> >> >
> >> > Any ideas on how to get around this? I have not tried print migrator
> >> > yet
> >> > but I think it is replaced by PrintBRM?
> >> >
> >> > Thanks,
> >> >
> >> > Tim
> >>
> >>
> >>
>
>
>

 

[Tim Crosby]

Re: Error migrating printers using PrintBRM

Alan,

So I reread your previous post.... The last informational event I see in the
event log just prior to the error is:

Printbrm.exe (the Printer Migration Wizard or the command-line tool) copied
print processor file \\print01\prnproc$\x64\filterpipelineprintproc.dll to
C:\Users\ADMINI~1\AppData\Local\Temp\2\B701B267-5E9D-4AFC-A6AE-18976AD4EF21\PRTPROCS\Windows x64\filterpipelineprintproc.dll. No user action is required.

This is not a 64-bit server. Should it even have the x64 print processor
there? I tried removing that entry from the registry
(HKLM\System\CurrentControlSet\Control\Print\Environments\Windows x64\Print
Processors\MS_XPS) and reran printbrm but I get the same error.

Tim

"Alan Morris [MSFT]" wrote:

> Print Management just launches printbrmui.exe, then it's completely out of
> the picture.
>
> printbrm.exe will give the best indication of the failure.
>
> look through the print processor registry and confirm print procs and the
> files. under
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows
> NT x86\Print Processors (if you have x64 look there too)
>
> I hit an issue one time where a print proc was listed as
> \3\printprocname.dll. I don't recall that I was getting any error, I think
> it just never migrated.
>
> I did not need the print processor any longer so I removed it. I have tools
> for this but the spooler UI for the field is regedit, sorry.
>
>
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
> news840BBC8-6CEE-4944-93B6-C730525CD976@microsoft.com...
> >I am using Vista SP1, but the server is standalone.
> >
> > I do not use separator pages. This server is not really production. I set
> > it up to start testing the ability to migrate printers around should this
> > server fail once it becomes production. There's really nothing special
> > about
> > it. The only thing I've installed besides the printers is the HP Web
> > JetAdmin tools.
> >
> > I downloaded print migrator 3.1 and was able to use that to dump
> > everything
> > to a cab file. It did not report any errors when it ran. But I was
> > hoping
> > to get the print management console to do this as we want our print server
> > to
> > be 2008. Can I use print migrator 3.1 to import into a 2008 server? Or do
> > I
> > have to use the print management console?
> >
> > Tim
> >
> > "Alan Morris [MSFT]" wrote:
> >
> >> the error equates to
> >>
> >> G:\>winerror 161
> >> 161 ERROR_BAD_PATHNAME <--> 0xc0000039 STATUS_OBJECT_PATH_INVALID
> >> 161 ERROR_BAD_PATHNAME <--> 0xc000003b STATUS_OBJECT_PATH_SYNTAX_BAD
> >> 161 ERROR_BAD_PATHNAME <--> 0xc0000281
> >> STATUS_DIRECTORY_IS_A_REPARSE_POINT
> >>
> >>
> >>
> >> Is this a standalone machine or a cluster?
> >>
> >> If it's a cluster you will need Vista SP1.
> >>
> >> Do you use separator pages on the printers?
> >>
> >>
> >>
> >> --
> >> Alan Morris
> >> Windows Printing Team
> >> Search the Microsoft Knowledge Base here:
> >> http://support.microsoft.com/search/?adv=1
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
> >> news:A347C1D8-A4E6-41EC-AE32-DFD2E8CBB0FD@microsoft.com...
> >> >I am using Vista's print management console to connect to a Windows
> >> >Server
> >> > 2003 print server to try and export the printers to a file. When I
> >> > right-click the server and select "Export printers to a file", it
> >> > starts
> >> > the
> >> > wizard and I tell it to save the file on the C: drive of the Vista
> >> > machine.
> >> > It starts exporting printers and printer drivers. It gets about 95% of
> >> > the
> >> > way through and says "Export complete: Windows encountered errors
> >> > during
> >> > the
> >> > migration process. Open Event Viewer for more information". If I open
> >> > event
> >> > viewer, I see nothing but informational events showing the drivers
> >> > being
> >> > exported, no warnings or errors. But my backup file never gets
> >> > created.
> >> >
> >> > If I try using printbrm.exe from a command prompt, it gets through all
> >> > the
> >> > print drivers and then says "The following error occurred: 0x800700a1.
> >> > The
> >> > specified path is invalid." Again, nothing in the event logs except
> >> > informational events.
> >> >
> >> > If I look at the list of all the things it is going to export, it
> >> > appears
> >> > that it is crashing when it starts backing up the print processors.
> >> > There
> >> > are about 25 of them to be exported, but it doesn't appear to do any of
> >> > them.
> >> > And I don't see any way to exclude the print processors from being
> >> > exported
> >> > or even to remove some of them to see if they are the problem.
> >> >
> >> > Any ideas on how to get around this? I have not tried print migrator
> >> > yet
> >> > but I think it is replaced by PrintBRM?
> >> >
> >> > Thanks,
> >> >
> >> > Tim
> >>
> >>
> >>
>
>
>

 

[Alan Morris [MSFT]]

Re: Error migrating printers using PrintBRM

the filterpipelineprintproc.dll is part on some .NET files.


Anyway we can get the printerexport file?

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

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

"Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
news:B19F35A5-94D0-4796-B119-DF4661666BB7@microsoft.com...
> Alan,
>
> So I reread your previous post.... The last informational event I see in
> the
> event log just prior to the error is:
>
> Printbrm.exe (the Printer Migration Wizard or the command-line tool)
> copied
> print processor file \\print01\prnproc$\x64\filterpipelineprintproc.dll to
> C:\Users\ADMINI~1\AppData\Local\Temp\2\B701B267-5E9D-4AFC-A6AE-18976AD4EF21\PRTPROCS\Windows
> x64\filterpipelineprintproc.dll. No user action is required.
>
> This is not a 64-bit server. Should it even have the x64 print processor
> there? I tried removing that entry from the registry
> (HKLM\System\CurrentControlSet\Control\Print\Environments\Windows
> x64\Print
> Processors\MS_XPS) and reran printbrm but I get the same error.
>
> Tim
>
> "Alan Morris [MSFT]" wrote:
>
>> Print Management just launches printbrmui.exe, then it's completely out
>> of
>> the picture.
>>
>> printbrm.exe will give the best indication of the failure.
>>
>> look through the print processor registry and confirm print procs and the
>> files. under
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows
>> NT x86\Print Processors (if you have x64 look there too)
>>
>> I hit an issue one time where a print proc was listed as
>> \3\printprocname.dll. I don't recall that I was getting any error, I
>> think
>> it just never migrated.
>>
>> I did not need the print processor any longer so I removed it. I have
>> tools
>> for this but the spooler UI for the field is regedit, sorry.
>>
>>
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/search/?adv=1
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
>> news840BBC8-6CEE-4944-93B6-C730525CD976@microsoft.com...
>> >I am using Vista SP1, but the server is standalone.
>> >
>> > I do not use separator pages. This server is not really production. I
>> > set
>> > it up to start testing the ability to migrate printers around should
>> > this
>> > server fail once it becomes production. There's really nothing special
>> > about
>> > it. The only thing I've installed besides the printers is the HP Web
>> > JetAdmin tools.
>> >
>> > I downloaded print migrator 3.1 and was able to use that to dump
>> > everything
>> > to a cab file. It did not report any errors when it ran. But I was
>> > hoping
>> > to get the print management console to do this as we want our print
>> > server
>> > to
>> > be 2008. Can I use print migrator 3.1 to import into a 2008 server? Or
>> > do
>> > I
>> > have to use the print management console?
>> >
>> > Tim
>> >
>> > "Alan Morris [MSFT]" wrote:
>> >
>> >> the error equates to
>> >>
>> >> G:\>winerror 161
>> >> 161 ERROR_BAD_PATHNAME <--> 0xc0000039 STATUS_OBJECT_PATH_INVALID
>> >> 161 ERROR_BAD_PATHNAME <--> 0xc000003b
>> >> STATUS_OBJECT_PATH_SYNTAX_BAD
>> >> 161 ERROR_BAD_PATHNAME <--> 0xc0000281
>> >> STATUS_DIRECTORY_IS_A_REPARSE_POINT
>> >>
>> >>
>> >>
>> >> Is this a standalone machine or a cluster?
>> >>
>> >> If it's a cluster you will need Vista SP1.
>> >>
>> >> Do you use separator pages on the printers?
>> >>
>> >>
>> >>
>> >> --
>> >> Alan Morris
>> >> Windows Printing Team
>> >> Search the Microsoft Knowledge Base here:
>> >> http://support.microsoft.com/search/?adv=1
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >> "Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
>> >> news:A347C1D8-A4E6-41EC-AE32-DFD2E8CBB0FD@microsoft.com...
>> >> >I am using Vista's print management console to connect to a Windows
>> >> >Server
>> >> > 2003 print server to try and export the printers to a file. When I
>> >> > right-click the server and select "Export printers to a file", it
>> >> > starts
>> >> > the
>> >> > wizard and I tell it to save the file on the C: drive of the Vista
>> >> > machine.
>> >> > It starts exporting printers and printer drivers. It gets about 95%
>> >> > of
>> >> > the
>> >> > way through and says "Export complete: Windows encountered errors
>> >> > during
>> >> > the
>> >> > migration process. Open Event Viewer for more information". If I
>> >> > open
>> >> > event
>> >> > viewer, I see nothing but informational events showing the drivers
>> >> > being
>> >> > exported, no warnings or errors. But my backup file never gets
>> >> > created.
>> >> >
>> >> > If I try using printbrm.exe from a command prompt, it gets through
>> >> > all
>> >> > the
>> >> > print drivers and then says "The following error occurred:
>> >> > 0x800700a1.
>> >> > The
>> >> > specified path is invalid." Again, nothing in the event logs except
>> >> > informational events.
>> >> >
>> >> > If I look at the list of all the things it is going to export, it
>> >> > appears
>> >> > that it is crashing when it starts backing up the print processors.
>> >> > There
>> >> > are about 25 of them to be exported, but it doesn't appear to do any
>> >> > of
>> >> > them.
>> >> > And I don't see any way to exclude the print processors from being
>> >> > exported
>> >> > or even to remove some of them to see if they are the problem.
>> >> >
>> >> > Any ideas on how to get around this? I have not tried print
>> >> > migrator
>> >> > yet
>> >> > but I think it is replaced by PrintBRM?
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Tim
>> >>
>> >>
>> >>
>>
>>
>>

 

[Tim Crosby]

Re: Error migrating printers using PrintBRM

I finally worked around this by using Print Migrator 3.1 to export everything
from the 2003 server and imported into a 2008 virtual server. Now I am able
to use the Print Management console on the 2008 server to export printers as
expected.

Still not sure what the problem was unless Vista was too "secure" and
wouldn't let me do the export to my workstation from the 2003 server.

Tim

"Alan Morris [MSFT]" wrote:

> the filterpipelineprintproc.dll is part on some .NET files.
>
>
> Anyway we can get the printerexport file?
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
> news:B19F35A5-94D0-4796-B119-DF4661666BB7@microsoft.com...
> > Alan,
> >
> > So I reread your previous post.... The last informational event I see in
> > the
> > event log just prior to the error is:
> >
> > Printbrm.exe (the Printer Migration Wizard or the command-line tool)
> > copied
> > print processor file \\print01\prnproc$\x64\filterpipelineprintproc.dll to
> > C:\Users\ADMINI~1\AppData\Local\Temp\2\B701B267-5E9D-4AFC-A6AE-18976AD4EF21\PRTPROCS\Windows
> > x64\filterpipelineprintproc.dll. No user action is required.
> >
> > This is not a 64-bit server. Should it even have the x64 print processor
> > there? I tried removing that entry from the registry
> > (HKLM\System\CurrentControlSet\Control\Print\Environments\Windows
> > x64\Print
> > Processors\MS_XPS) and reran printbrm but I get the same error.
> >
> > Tim
> >
> > "Alan Morris [MSFT]" wrote:
> >
> >> Print Management just launches printbrmui.exe, then it's completely out
> >> of
> >> the picture.
> >>
> >> printbrm.exe will give the best indication of the failure.
> >>
> >> look through the print processor registry and confirm print procs and the
> >> files. under
> >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows
> >> NT x86\Print Processors (if you have x64 look there too)
> >>
> >> I hit an issue one time where a print proc was listed as
> >> \3\printprocname.dll. I don't recall that I was getting any error, I
> >> think
> >> it just never migrated.
> >>
> >> I did not need the print processor any longer so I removed it. I have
> >> tools
> >> for this but the spooler UI for the field is regedit, sorry.
> >>
> >>
> >>
> >> --
> >> Alan Morris
> >> Windows Printing Team
> >> Search the Microsoft Knowledge Base here:
> >> http://support.microsoft.com/search/?adv=1
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
> >> news840BBC8-6CEE-4944-93B6-C730525CD976@microsoft.com...
> >> >I am using Vista SP1, but the server is standalone.
> >> >
> >> > I do not use separator pages. This server is not really production. I
> >> > set
> >> > it up to start testing the ability to migrate printers around should
> >> > this
> >> > server fail once it becomes production. There's really nothing special
> >> > about
> >> > it. The only thing I've installed besides the printers is the HP Web
> >> > JetAdmin tools.
> >> >
> >> > I downloaded print migrator 3.1 and was able to use that to dump
> >> > everything
> >> > to a cab file. It did not report any errors when it ran. But I was
> >> > hoping
> >> > to get the print management console to do this as we want our print
> >> > server
> >> > to
> >> > be 2008. Can I use print migrator 3.1 to import into a 2008 server? Or
> >> > do
> >> > I
> >> > have to use the print management console?
> >> >
> >> > Tim
> >> >
> >> > "Alan Morris [MSFT]" wrote:
> >> >
> >> >> the error equates to
> >> >>
> >> >> G:\>winerror 161
> >> >> 161 ERROR_BAD_PATHNAME <--> 0xc0000039 STATUS_OBJECT_PATH_INVALID
> >> >> 161 ERROR_BAD_PATHNAME <--> 0xc000003b
> >> >> STATUS_OBJECT_PATH_SYNTAX_BAD
> >> >> 161 ERROR_BAD_PATHNAME <--> 0xc0000281
> >> >> STATUS_DIRECTORY_IS_A_REPARSE_POINT
> >> >>
> >> >>
> >> >>
> >> >> Is this a standalone machine or a cluster?
> >> >>
> >> >> If it's a cluster you will need Vista SP1.
> >> >>
> >> >> Do you use separator pages on the printers?
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Alan Morris
> >> >> Windows Printing Team
> >> >> Search the Microsoft Knowledge Base here:
> >> >> http://support.microsoft.com/search/?adv=1
> >> >>
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> >> rights.
> >> >>
> >> >> "Tim Crosby" <TimCrosby@discussions.microsoft.com> wrote in message
> >> >> news:A347C1D8-A4E6-41EC-AE32-DFD2E8CBB0FD@microsoft.com...
> >> >> >I am using Vista's print management console to connect to a Windows
> >> >> >Server
> >> >> > 2003 print server to try and export the printers to a file. When I
> >> >> > right-click the server and select "Export printers to a file", it
> >> >> > starts
> >> >> > the
> >> >> > wizard and I tell it to save the file on the C: drive of the Vista
> >> >> > machine.
> >> >> > It starts exporting printers and printer drivers. It gets about 95%
> >> >> > of
> >> >> > the
> >> >> > way through and says "Export complete: Windows encountered errors
> >> >> > during
> >> >> > the
> >> >> > migration process. Open Event Viewer for more information". If I
> >> >> > open
> >> >> > event
> >> >> > viewer, I see nothing but informational events showing the drivers
> >> >> > being
> >> >> > exported, no warnings or errors. But my backup file never gets
> >> >> > created.
> >> >> >
> >> >> > If I try using printbrm.exe from a command prompt, it gets through
> >> >> > all
> >> >> > the
> >> >> > print drivers and then says "The following error occurred:
> >> >> > 0x800700a1.
> >> >> > The
> >> >> > specified path is invalid." Again, nothing in the event logs except
> >> >> > informational events.
> >> >> >
> >> >> > If I look at the list of all the things it is going to export, it
> >> >> > appears
> >> >> > that it is crashing when it starts backing up the print processors.
> >> >> > There
> >> >> > are about 25 of them to be exported, but it doesn't appear to do any
> >> >> > of
> >> >> > them.
> >> >> > And I don't see any way to exclude the print processors from being
> >> >> > exported
> >> >> > or even to remove some of them to see if they are the problem.
> >> >> >
> >> >> > Any ideas on how to get around this? I have not tried print
> >> >> > migrator
> >> >> > yet
> >> >> > but I think it is replaced by PrintBRM?
> >> >> >
> >> >> > Thanks,
> >> >> >
> >> >> > Tim
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>