EA is a 32bit Software, that allows automation (like office does), which is not recommended for server use (because sometimes some dialogs might come up if you don’t take care) – but if you want to use it in a 64bit environment you have to trick around a little bit.


Here we go for the hardcore way

  • 1.) Identify your COM object’s GUID with REGEDIT HKEY_CLASSES_ROOT\Wow6432Node\CLSID\[GUID]
  • in our case: you can search for EA.App and you will find: {3A9E4F92-8D27-495B-8B22-1D702B3F0C83}
  • 2.) There you add a REG_SZ (string) Value. Name it AppID and data has to be the same COM object GUID
    • in our case: {3A9E4F92-8D27-495B-8B22-1D702B3F0C83}
  • 3.) Add a new key HKEY_CLASSES_ROOT\Wow6432Node\AppID\ and name it GUID
    • in our case again: {3A9E4F92-8D27-495B-8B22-1D702B3F0C83}
  • 4.) There you add a REG_SZ (string) Key called: DllSurrogate. Value is empty.
  • 5.) Create a new Key under HKEY_LOCAL_MACHINE\Software\Classes\AppID\ and name it GUID
    • in our case again: {3A9E4F92-8D27-495B-8B22-1D702B3F0C83}

Now you can find EA.App in the DCOM Configuration and configure the access, security and whatever.


Here we go for the easier way

The hardcore way works – but do we really want to cheat like this – a more comfortable way is to use a command line (with administrative rights):

c:\windows\syswow64\comexp.exe /32

And now all 32bit COM/OLE/COM+/DCOM stuff is visible and can be configured.

See also: http://blog.lieberlieber.com/2009/09/16/running-enterprise-architect-on-a-server/