Should JIT be invoked by NETWORK SERVICE account?

[Guest]

This is about ASP.NET 1.0, but it may still applies to 1.1 and 2.0.

We have a very large web application, some part of the code calls EXE files
to do jobs. It all worked fine on Windows 2000 Server until we migrated the
app to a completely new Windows Server 2003.

In a long running Terminial session, we occasionally (often) see a popup
that says 'JIT Debugger was initiated by the user account NT
AUTHORITY\NETWORK SERVICE'.

According to my lilmited knowledge about security, I think NETWORK SERVICE
account is a non-user account - it's built-in. JIT should never be invoked
for this account.

Am I right?

 

[Cowboy \(Gregory A. Beamer\)]

NETWORK SERVICE is a non-user account, but it is the account some of the
services associated with .NET run under, so it is not surprising to see .NET
classes firing under this service or the JIT debugger come up due to errors
in the .NET classes fired up by this account.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*************************************************
Think outside of the box!
*************************************************

 

[Guest]

But this account has not a user interface (non-interactive accoutn) - what is
the use if JIT coming up under this accont if it cannot display UI?