Hi Dominick
Thanks for taking your time!
The problem is that the application fails to start, when a user without
admin rights trys to launch it, it just throws a sequrity exception.
As said before, this occures only on Metaframe Server with Nt-Server 2003
On a thick workstation the application starts up fine and runs without that
the user has admin rights.
We configured the local internet setting in the dotnet framework
configurator, too fulltrust so we can start our appliucation also from a
network share.
Greetings from Switzerland
Andi
> maybe you should tell us first what problems you get - then we can try to
> figure out what could be wrong :))
[quoted text clipped - 15 lines]
>> All the best from switzerland.
>> Andi
Dominick Baier [DevelopMentor] - 20 Feb 2006 23:21 GMT
hi,
what kind of security exception? stack trace? App installed locally? or from
a share?
sorry - how shall i get an idea from this vague description.
Citrix somehow rings a bell - but can't remember the details at the moment...
---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com
> Hi Dominick
>
[quoted text clipped - 32 lines]
>>> All the best from switzerland.
>>> Andi
Andreas Lutz - 21 Feb 2006 08:07 GMT
Hi Dominick
I talked to our developper.
Actually the applications fails to start at all, no message.
But we will further investigate and try to catch that execpeption and get
the stacktrace.
I come back witht more information.
Thanks allot for allready responding!
Andi
> hi,
> what kind of security exception? stack trace? App installed locally? or
[quoted text clipped - 45 lines]
>>>> All the best from switzerland.
>>>> Andi
Andreas Lutz - 23 Feb 2006 15:20 GMT
Hi Dominick
We actually succeded to solve the problem!
the problem occured in our exception handler itself. That was why we
didn't receive any error messages.
We used the tolken monitor (Tokenmon) from SysInternals and there we
saw that an "adjust rights :DEBUG" occurerd. After some research we
found out that the cause for that, was that our programmer created some
objects from the System.Diagnostics Namespace while handling an
exeception.
this is the code which caused the mess.
Dim oProcess As Process = Process.GetCurrentProcess
dtStartTime = oProcess.StartTime
....
happy programming :-)
Andi
Andreas Lutz schrieb:
> Hi Dominick
>
[quoted text clipped - 58 lines]
> >>>> All the best from switzerland.
> >>>> Andi