FAQ: What issues does RPM 3.0/NT fix from RPM 2.3/NT?

Question: What 'bugs' are fixed in RPM Remote Print Manager™ version 3.0/NT to that are not working correctly in RPM version 2.3/NT?

Answer: There are 2 major bugs that the newest version of RPM/NT fixes. The first one is many times after rebooting Windows NT, then if you tried to access the RPM user-interface, you would receive a message stating:

	RPM Fatal Error!  Cannot connect to service.

The fix for this problem was actually a combination of a few different programming items. It was not caused by one simple thing, but by many. We believe that the only way to get this message now is to have a major problem in the installation. If you get this error with version 3.0, please contact us at support to resolve the problem.

The other problem was really not a problem at all, but it was a headache for a number of users. When a print job was sent to the Windows spooler, SYSTEM was the user name that issued the command. Many times, users would not have the ability to delete these jobs if there was a problem, but more importantly, you would not know which user sent the job. That is now fixed.

Note: The RPM user now must have full control to the printer that you are trying to print to or the queue will be automatically suspended.