Can't restart service
RPM had stop printing out job so we restarted the RPM service but are getting the following.
Error starting - 2017-06-28 11:04:30.830
[ *** RPM Service failed to start *** ]
[ Note: module name and message follow ]
Module: MsgQMgr
Message: boost::interprocess_exception::library_error
We have intermittent problems of job getting stuck in Active or RCVD and nothing printing out, the solution has been to restart the service, this is the first time we get stuck here.
Requires the computer to be restarted (in the version reported)
In your version, the RPM service communicates with the database manager using the Boost interprocess library. In our experience, once you encounter this error, a computer restart is required for it to be functional again. We have recently eliminated the boost interprocess library and now use named pipes, something Windows uses internally, which seem to work very well and eliminates this error and the subsequent required computer reboot.
I would recommend an upgrade to the latest version.
It may also help with your issue where a job is getting stuck, though I cannot be certain.
Update
Editor’s note, 2026-08-20. This exchange is from June 2017 and the answer was correct for the version the customer was running. The cause has since been engineered out of the product entirely, so nothing above should be read as current advice.
RPM’s service reaches its database through a separate interface program, and that program has been replaced three times since this post:
- Through 6.1.0.451 (2017-06-22) it used shared-memory message queues by way of the Boost interprocess library. That is the
MsgQMgrfailure in the error above, and it is the case where a full system restart genuinely was the only recovery. - 6.1.0.451 replaced it with dbpipe, using Windows named pipes. That is the change the answer above describes as recent — this post is dated six days after that release.
- 6.2.0.511 (2019-11-19) added dbshm, a shared-memory alternative, because named pipes conflicted with some endpoint security products.
- RPM now uses direct database access, and both dbpipe and dbshm have been removed from the product. Direct became the default for new installations in 6.2.0.599 and is part of the move to Firebird 5.0.
On a current release there is no MsgQMgr and no Boost interprocess library, so this error cannot occur and no reboot is required for it. If jobs are sitting in Active or RCVD on a current version, that is a different problem: start with the message log rather than restarting the service.