Interbase Server Data Execution Prevention on Server 2003 R2

Today when I logged in as a domain admin, I received a couple of notices that
Windows Server 2003 R2 was locking down the Interbase Server threads due to Data
Execution Prevention.

Is there something I need to set for Interbase 7.5 to prevent windows from
blocking the threads with DEP?

Has anyone else experienced this behaviour as well?

	Are you running IB as an application? Because if it's running as a
service then it should always be under the same account; it shouldn't
matter which account *you* are logged in as.

-- 
Craig Stuntz [TeamB] · Vertex Systems Corp. · Columbus, OH
  Delphi/InterBase Weblog : http://blogs.teamb.com/craigstuntz
All the great TeamB service you've come to expect plus (New!) 

It is running as a service, but Windows reserves certain messages for certain
users.

I have just done a fresh install to verify, and I am still getting DEP messages
from Windows in regards to the Interbase Server Service.

Is there any information about what can be causing these error messages and what
I should do as a work around?

Well, one workaround is to exclude InterBase from DEP.  I'm a little
confused by what you mean about "certain users", but excluding IB
should fix the problem.

-- 
Craig Stuntz [TeamB] · Vertex Systems Corp. · Columbus, OH
  Delphi/InterBase Weblog : http://blogs.teamb.com/craigstuntz
All the great TeamB service you've come to expect plus (New!)