Quantcast
Channel: Print/Fax forum
Viewing all articles
Browse latest Browse all 1188

Printbrm.exe event ID 46

$
0
0

Hello together,

I have a problem, using the Printbrm.exe, for migrating 300 printers from a print server with the system "Windows Server 2008 R2", to a new print server with the system "Windows Server 2019".

To export the list with the important data, I used the command "printbrm –B –S Servername –f C:\file –nobin" on the server, that runs the system “Windows Server 2019”. 

Yesterday, this worked perfectly.

But unfortunately, I realized, after exporting the list, that I have to delete some printers and update one driver, before I can migrate everything on the new server. 

Today I wanted to export the file once again, because of the changes. 

The export seems to run normal, until the last port was saved.

After that, an error occurred. 

I am really sorry, but I don't have the error code at the moment. 

There is one thread, answered from “Alan Morris” to the error code, but I cannot find it right now.

I just have the event ID "46" and the text of the error, that said "Printbrm.exe (the Printer Migration Wizard or the command-line tool) failed to place a file in cabinet (CAB) file C:\file while backing up print queues. Error reported: -----. This can occur if the user does not have permission to create a file in the destination location, or if there is insufficient disk space or system resources.”

I couldn’t find a solution, so I tested the export with a second print server, that also runs on the system “Windows Server 2019”.

The same error occurred.

I also changed the destination server to another print server with the system “Windows Server 2008 R2".

After I have done that, the export runs without any problem.

That means, that the problem has to be on that one old print server with the “Windows Server 2008 R2”-system.

To test this, I tried to export the data directly on this source server.

This should also be possible, as long, as I don’t import them.

To export the data, I entered the same command as the one above.

But then another error, with the code “0x80004005” occurred. 

I don’t know how I should go on.

Maybe somebody can help me to fix the problem.

Yours sincerely,

 

SAM_NI


Viewing all articles
Browse latest Browse all 1188

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>