id summary reporter owner description type status milestone component version severity resolution keywords cc 12232 boost::interprocess::intermodule_singleton initialization failed in Windows 2012 Server rafael.bronzeri@… Ion Gaztañaga "Hi, I've got the following exception from Boost Interprocess using Windows 2012 Server: ""boost::interprocess::intermodule_singleton initialization"". I've tried to fix it removing SharedMemory and Shared variables previously created, but it doesn't work. The only solution for it is restarting the server. The expcetion happens using this code: //Removing previously created boost::interprocess::named_mutex::remove(""TEST.SHARED.MEMORY0000002.MTX1.0.000000000000000000000000009""); if (mtx1 != nullptr) { delete mtx1; mtx1 = nullptr; } boost::interprocess::named_condition::remove(""TEST.SHARED.MEMORY0000004.NMC1.0.000000000000000000000000050"")); if (condition1 != nullptr) { delete condition1; condition1 = nullptr; } boost::interprocess::shared_memory_object::remove(""TEST.SHARED.MEMORY0000001.XXX.0.000000000000000000000000021""); if (shmObj1 != nullptr) { delete shmObj1; shmObj1 = nullptr; } //Creating SharedMemory boost::interprocess::permissions shared_memory_Perm; shared_memory_Perm.set_unrestricted(); boost::interprocess::managed_shared_memory shmObj1 = new boost::interprocess::managed_shared_memory (boost::interprocess::create_only_t(), ""TEST.SHARED.MEMORY0000001.XXX.0.000000000000000000000000021"", 42768, static_cast(NULL), shared_memory_Perm ); boost::interprocess::named_mutex* mtx1 = new boost::interprocess::named_mutex(boost::interprocess::create_only_t(), ""TEST.SHARED.MEMORY0000002.MTX1.0.000000000000000000000000009""); boost::interprocess::named_condition* condition1 = new boost::interprocess::named_condition(boost::interprocess::create_only_t(), ""TEST.SHARED.MEMORY0000004.NMC1.0.000000000000000000000000050""); Please, I need some help to fix this problem. Is there any solution without restaring the server for it? Thanks! " Bugs new To Be Determined interprocess Boost 1.59.0 Problem