'UnauthorizedAccessException' - 'Global\.net clr networking'

  • Thread starter Thread starter NickP
  • Start date Start date
N

NickP

Hi there,

I've been experiencing a strange issue for a short while now and have
managed to make a tiny replication of the bug.

The uploaded a VB.NET 2005 project which implements a single instance
application, it's very basic.

http://nickpateman.m6.net/Files/xpbug.zip

Previously I had been using my own implementation but have
recently decided to port to the built in .net 2005 method. Both methods
experience the same problem...

"An unhandled exception of type 'System.UnauthorizedAccessException'
occurred in mscorlib.dll
Additional information: Access to the path 'Global\.net clr networking' is
denied."

If you try running this code on a limited account in XP Pro you will
experience an unhandled 'UnauthorizedAccessException'. My understanding is
that the string literal 'Global\.net clr networking' refers to the name of a
performance counter. But quite why a performance coutner would need to be
created in order to initialise a simple TCP connection I have no idea.

This basically renders the "Make Single Instance Application" feature of
VS 2005 useless on limited accounts. Unless of course I am missing
something. I have enabled click-once security and set the application to
full-trust.

Hasa anyone got any work arounds for this? I can get the application
working by disabling the single instance feature in the project properties,
but of course I then have no interprocess communication, which is 100%
essential for what I am doing.

Thanks loads in advance!

BTW. I have found references to this problem through Google which
suggest that it's a bug with XP Pro, as apparently it does not exist on XP
Home. But unfortunately have not found a resolve for the issue.

Nick.
 
Hi there,

I've finally got the application tested on XP Home and it appears that
the bug is not down to a limited account but the "Guest" account.

If you log on as a restricted account merely a member of "Users" the
application works fine. Although I still consider this to be a problem as
interprocess communication like this shouldn't require any special
priviledges and the .NET application framework has no way of specifying a
condition upon launching as to allow "Single instance" mode or not.

Anyway, I hope this info helps other people.

Nick.
 
Back
Top