


Then the X component under DCOM Config -> properties -> location tab. the solution to bad DcomCnfg behavior under 64 - bit Windows OS's is to use the 32 bit version of DcomCnfg. (VS.85).aspx) saying that DCOMCNFG does work properly in Windows Server 2008 and Windows 7, but it doesn't.Īnyway. Actually the funny part is that there is article from microsoft ( Then after reading some more, I learned that Windows 2008r2 and in Windows 7 the DCOMCNFG does not work. In addition, I found a service called AX32 I wanted to test with and I right clicked and went to the Security tab and everything was grayed out. Went I got to the window (Start > Administrative tools >Ĭomponent Services> Double click in Component Services > M圜omputer> DCOM Config) I did not find the service I was looking for. After reading a few articles about the topic, I eneded up going to the Component Services to edit the Outlook Message Attachment Service component. I was having a problem sending an email through outlook in one of the dev machines at work this morning.
