Submitted by Dave Brooks on Wed, 11/14/2018 - 07:28
The biggest change in the 6.2.0.489 release is the device tester. We worked with a customer who had jobs for a number of printers but only jobs for the first three printers ever ran. Restarting the RPM service cleared the problem, but they were able to provide us with a diagnostic log.
Submitted by Dave Brooks on Wed, 10/31/2018 - 04:27
Over the years, a percentage of our incoming questions have to do with help with their RPM license. Typical among these are “how do I” and “what does this mean”.
We have consolidated months of actual questions, along with years of customer support, into a new set of frequently asked questions focused on licensing.
The purpose of this, of course, is to help our customers and if there is any way we can increase our customers' confidence in own skills, then we are happy to do so.
Submitted by Dave Brooks on Mon, 10/22/2018 - 10:12
We do our level best to support LPR print clients with RPM Remote Print Manager® (“RPM”). The fact that we have detailed logging available in RPM has saved our sanity more than once. Back in 1996 when we first encountered the IBM AS/400, our customer was having a problem receiving prints from the AS/400, and the log helped us track down the expectations of the IBM print system. I was able to make adjustments to RPM successfully from that data.
Submitted by Dave Brooks on Fri, 10/19/2018 - 21:22
We receive this question fairly often. I’ll use a sample RPM Remote Print Manager® (“RPM”) version to illustrate how one would research this issue.
Hi. I’m running RPM version x and want to upgrade my Windows to Server 2016. Is this version of RPM certified for Server 2016?
Of course, a few years ago the question was about Server 2012, and before that 2008, 2003, etc.
Submitted by Dave Brooks on Wed, 10/10/2018 - 20:41
We have worked with several customers who report that they receive jobs very slowly using RPM Remote Print Manager® (“RPM”). This is always a surprise to us because when we test RPM features and fixes, we have several folders containing a total of nearly 28,000 files. That is our basic, everyday test base. We use the pylpr program that we ship with RPM
Submitted by Dave Brooks on Fri, 10/05/2018 - 10:32
We posted update 6.2.0.485 for RPM Remote Print Manager® ("RPM") on October 2, 2018. All the details are in the RPM roadmap. Here we have a summary of the top items of interest.
If you have seen ENOUGH of those “boost::filesystem” errors ...
Submitted by Dave Brooks on Thu, 09/20/2018 - 16:57
We had a support email recently with this question:
I get name corruption in RPM. How do I prevent this?
Submitted by Dave Brooks on Thu, 09/20/2018 - 10:51
We recently talked with a customer who reported that RPM Remote Print Manager® ("RPM") was showing an error with MsgQMgr in the event log at startup:
Submitted by Dave Brooks on Wed, 09/19/2018 - 17:33
We have had several emails recently from people having issues with their antivirus programs.
One asked: If I can’t get my sysadmin to set up an exception for our antivirus on the RPM spool folder, can I move the spool folder to a directory which is already excluded?
Yes! Go to the Configure menu and select General Settings:
Submitted by Dave Brooks on Tue, 09/18/2018 - 16:52
We are asked a number of times per week whether someone’s RPM Remote Print Manager® (“RPM”) license support status is active, when support expires, and related questions.
We admit we’re around it all the time and it becomes second nature to know where to look. However, it’s only fair that we make this process as easy as possible.
To that end, we’re pleased to announce that we now display all the license status we know, in the event log each time RPM starts up.
Pages
Newsletter signup
