Link to home
Start Free TrialLog in
Avatar of hypercube
hypercubeFlag for United States of America

asked on

Where is dcomcnfg?

We have an important 3rd party ASP application that requires particular settings of DCOMCNFG.
In some computers (e.g. Windows 8.1) we aren't able to use the familiar:
Start \ Search programs and Files \ [ type in dcomcnfg or dcomcnfg.exe]

However, I was able on one computer to Search the C: drive for dcomcnfg and did find dcomcnfg.exe in a strange place.
I ran it and it worked (it seems).  i.e. it took the settings.

But I'm wondering:
- Why did I have to "find" it this way?
or, similarly, why wasn't it found in the normal way?
It appears that it was deleted from a "regular" place or moved.
- Is it OK to run?

As far as I know, dcomcnfg.exe is normally in C:\Windows\system32
But I also find it in places like:
C:\Windows\WinSxS\x86_microsoft-windows-com-complus-ui_31bf3856ad364e35_6.3.9600.17415_none_4594231863989324
Avatar of McKnife
McKnife
Flag of Germany image

Here it works perfectly normal through search. Maybe a type mismatch?
Avatar of hypercube

ASKER

McKnife:  Yes, it normally works normally  :-)
Yet, we have a few computers where it doesn't.  Thus the question.

Doing a search over C: on a Windows 8 64-bit machine results in this:
User generated imageIt's a bit concerning to see 11KB versions and 10KB versions .. I wonder what that's about?
Stop worrying, everything is ok. Simply press winkey+r, enter dcomcnfg and there you go.
I find the "same" file with two different sizes:
User generated image
ASKER CERTIFIED SOLUTION
Avatar of McKnife
McKnife
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
So, the same file version appears in two versions: one 32-bit and one 64-bit.  
Not my idea of a "version" at all!!  One might humbly suggest that they be different.

Thanks McKnife for helping me understand.

I think that part of the problem was operator error / a typo in the file name.
I discovered that when providing support this morning.
So, it appears to be resolved now!
Thanks again!
Thanks