Failed To Restore Print Queue Error
Contents |
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools
Error 0x80070705
Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet printbrm 0x800706ba Library TechNet Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions failed to restore print queue error 0x800706ba Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft
Windows Could Not Read Printer Data From The Import File
SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training Microsoft
Printbrm.exe Download
Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Windows Server 2008 R2 and Windows Server 2008 Migrate Server Roles to Windows Server 2008 R2 Print Services Migration Guide Print Services Migration Guide Print Services Migration: Migrating the Print and Document Servic
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways printer migration tool download to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts
Printbrm.exe (the Printer Migration Wizard Or The Command-line Tool) Failed To Restore Print Queue
Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Failed to restore print queue 0x80070709 printer migration tool server 2012 Want to Advertise Here? Solved Failed to restore print queue 0x80070709 Posted on 2012-08-31 MS Legacy OS MS Server OS Windows Server 2008 1 Verified Solution 5 Comments 1,410 Views Last Modified: 2013-04-06 I https://technet.microsoft.com/en-us/library/dd392278(v=ws.10).aspx am trying to migrate print queue's from one Windows 2008R2 server to another. I have exported the printers using printbrm without failures. When i try to import on the new server I get "Failed to restore print queue
is x64. A few of the printers on the source servers have x64 drivers, most don't. I just did a test run - exported on a source and then imported that file on the destination. http://www.networksteve.com/forum/topic.php/Printer_Migration_Wizard_-_errors/?TopicId=19704&Posts=18 In Event Viewer I got quite a few 31 and 33 events. Looks like the 31's warn that the source driver was x32, that the destination is x64, and it will *attempt* to then find the x64. Some https://community.spiceworks.com/topic/530111-printer-migration-tool are found. If they aren't I get a 33 id, saying it didn't find the x64 driver. But I also get a lot of 92 id's. Which states: Printbrm.exe (the Printer Migration Wizard or the command-line tool) failed to failed to restore print queue PU253-HP M2727. The restore process will continue, skipping this queue. Error: 0x80070705. The printer driver is unknown. But, when all is said and done, it looks like I have most of the drivers, forms and ports on the destination server. But NO printers. None. I don't understand the results. Seems like I should have had, at least, the printers from the source server that had x64 drivers. How did failed to restore I end up with none? March 25th, 2011 5:58pm As I see you have got driver problems. Have a look to this thread about a similar problem: http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/54cf609c-ba21-47be-9718-172685c80133 This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Free Windows Admin Tool Kit Click here and download it now March 25th, 2011 6:39pm As I see you have got driver problems. Have a look to this thread about a similar problem: http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/54cf609c-ba21-47be-9718-172685c80133 It appears that Alan Morris is the man when it comes to printer migration! I was reading this thread when I checked on my post and saw your link to a similar situation: http://int.social.technet.microsoft.com/Forums/en-CA/winserverprint/thread/ae509a31-5f1a-4933-8945-b9277779f33c Thanks! I'll have a read. March 25th, 2011 6:49pm Regardless of the errors I received, the printers with x64 drivers from the source should be showing up on the destination server after the import/export. Everything I read about this is pointing to the problem being: 1.) the x64 driver should be on the source server before performing the export 2.) if the x64 is on the source, it should match the x64 driver name o
BY MICROSOFT See more RELATED PROJECTS Windows Deployment Services Replacing Norton Ghost with WDS. Virtual Test environment Needed to set up a test/sandbox environment so that I could learn VMWare and how to setup a domain. Secure Endpoints Needing to secure all endpoints on the LAN. No managed AV solution or patch management. TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now I have two window 2003 servers, I need a tool to migrate the printers from one server to the other. Thanks, Chad Reply Subscribe View Best Answer RELATED TOPICS: Quest migration tool File migration tool recommendation? GroupWise 6.5 to Exchange 2007 migration tool   10 Replies Cayenne OP Best Answer Chris5280 Jun 30, 2014 at 4:24 UTC Try the built in one. http://technet.microsoft.com/en-us/library/cc722360.aspx 1 Anaheim OP PauloXS Jun 30, 2014 at 4:27 UTC Chris5280 is right that should work 0 Sonora OP user59511 Jul 1, 2014 at 6:21 UTC It keep failing ... Do I have to remove all the printers from the old server first before I import the list into the new server? 0 Sonora OP user59511 Jul 1, 2014 at 8:12 UTC All of the drivers and the ports will import but the printers wont. keep getting an error 0 Cayenne OP Chris5280 Jul 2, 2014 at 7:17 UTC What error are you getting? 0 Cayenne OP Helpful Post Chris5280 Jul 2, 2014 at 7:18 UTC Also you might look at upgrading your print server to at least 2008 R2. It works a whole lot better than 2003. And if you can go to 2012 its even better. 0 Sonora OP user59511 Jul 2, 2014 at 7:37 UTC Printbrm.exe (the Printer Migration Wizard or the command-line tool) failed to restore print queue HP LaserJet 4250 (MStimler). The restore process will continue, skipping this queue. Error: 0x800705AA. This is the error message. 0 Cayenne OP Chris5280 Jul 2, 2014 at 8:54 UTC Have you checked the printer Queue's? is there any stuck jobs? 0 Sonora OP user59511 Jul 2, 2014 at 8:56 UTC Yup, nothing is being printed 0 Cayenne OP Chris5280 Jul 2, 2014 at 9:05 UTC That printer you may have to delete from the old server and add it to the new server. Most of the time when i do migrations the windows tool sticks on one printer for some reason. 0 This discussion