by jasper » 20 December 2012, 21:50
You can run the 64 bits or the 32 bits version. The 64 bits version is a bit faster on x64 windows, but not much, and GOOOP32 is the glue between the 64 bits version and 32 bits clients, which is only required to load 32-bits CAPE-OPEN objects. So if you are just using COFE components, they are all available in both 64 bits and 32 bits, hence GOOOP32 is not required in this scenario. If you do load items via GOOOP32 they are no longer in-process, and as a result you will get some slower performance from these components. In this particular case it is probably faster just to use the 32 bits version of COFE.
If you run GOOOP32 /RegServer, it will redo its own COM registration. If you do that as administrator, e.g. from a DOS box that was started with administrative rights, it will be registered for all users; it will attempt to register just for the current user only if you installed COCO for the current user. Hence, running GOOOP32 /RegServer will likely fail to register if you are not running it with administrative rights, and if you installed COCO for all users.
Still, COFE simply exiting is not normal behaviour, but from what you report it does not sound to me like it is related to the message about the missing registration of GOOOP32. The update of COFE64 that will follow soon will not start GOOOP32 at the start of COFE anymore, so that message will be postponed until COFE64 tries to load some 32 bit component via GOOOP32.
Did the Windows Event Viewer not show any report on the reason for COFE64 to exit?