GetProcess().ProcessName call hangs in the Enterprise Library

[Eduard Ralph]

Hi,

I've been having a very weird problem in connection with using the
Enterprise Library. I'm programming a Windows Service and utilise the
logging and configuration component. During the initial loading of my
own configuration file I log the status because I also do some checks
to assure that the file is there, etc. In one of these log statements
the software hangs. If I Debug I find that the Enterprise Library is
trying to do something with the PerformanceCounter and in the process
of that calls Process.GetName which in turns calls
PerformanceMonitor.GetData() (an internal method of .NET) and hangs in
there.
I'm using Windows 2003 Server Enterprise Edition with SP1 and .NET 1.1
with all the updates, etc.

What I have done so far:
- I've checked the rights of course and also opened up the perfmon to
check if I have some problems there - it seems ok so far.
- I've roamed the newsgroups and found an article which seems to
describe my problem:
http://groups.google.de/group/micros...46b539755acc4b
though there is no solution unfortunately. There seems to be some kind
of constellation of setup of windows which leads to this issue. I've
2-3 other articles which report of similar problems but also without
Solution.

I would appreciate any help,

Eduard Ralph

[dekel.israeli]

I'm having the same problem - call to ProcessName hanges in a service
on windows XP SP2 framework 1.1

Happens 80% of the time when running as a service, and never when
running as a console application
* it even weirder - another service with the same call - start 95% of
the times (hangs 5% or less)

The call to ProcessName was placed in the first line of the Main.

Any help from Microsoft or MVP will be appreciated

Dekel