I am having issues with DBISAM server running as a service on Windows 2003 Server.

I cannot get the service to allow the GUI to interact with the desktop.  I have tried running the
service under Local System and an Admin account on the box.  Also, the "Interact with the Desktop"
option is checked.

It works fine on Windows XP and 2000 Pro/Server.  Just not on 2003 correctly.  The service is running,
but my clients really want to log on the box and open the service GUI and kill locked sessions, etc - not
just stop and restart when an issue occurs.

Any ideas?

Thanks,
Mike Valverde
ACS Technologies.

Michael,

<< I am having issues with DBISAM server running as a service on Windows
2003 Server.

I cannot get the service to allow the GUI to interact with the desktop.  I
have tried running the service under Local System and an Admin account on
the box.  Also, the "Interact with the Desktop" option is checked.

It works fine on Windows XP and 2000 Pro/Server.  Just not on 2003
correctly.  The service is running, but my clients really want to log on the
box and open the service GUI and kill locked sessions, etc - not just stop
and restart when an issue occurs. >>

Per my email response, is this a stock 2003 installation, or has it been
heavily configured ?   Our stock 2003 installation here works fine with the
service running and interacting with the desktop, which indicates to me that
something has to have changed in terms of the access rights for the Local
System account.  We don't use IIS here on our 2003 server, however, so this
might have something to do with it if you also run IIS on that machine:

http://support.microsoft.com/kb/886695

--
Tim Young
Elevate Software
www.elevatesoft.com

Michael Valverde wrote:

> I am having issues with DBISAM server running as a service on Windows
> 2003 Server.

It works fine on our Windows 2003 server but at one of my clients, it
behaves exactly as you report. Interact with GUI is checked, but no GUI
is availble.  I am thinking that there must be some policy setting that
must override the applications.  Not sure.. just guessing.

I actually prefer to administer the server remotely but would like to
know why this happens so that I can advise clients.

--
David Farrell-Garcia
Whidbey Island Software, LLC

<< It works fine on our Windows 2003 server but at one of my clients, it
behaves exactly as you report. Interact with GUI is checked, but no GUI
is availble.  I am thinking that there must be some policy setting that
must override the applications.  Not sure.. just guessing.  >>

I can't find a policy and give the .exe all permissions possible.  Also, the Win 2003 server we have
is on SP1.  The sever is configured Vanilla w/ nothing else installed.  (No IIS, SQL, etc.).

Thanks,
Mike

Mike,

<< I can't find a policy and give the .exe all permissions possible.  Also,
the Win 2003 server we have is on SP1.  The sever is configured Vanilla w/
nothing else installed.  (No IIS, SQL, etc.). >>

Wow, this is really weird.  I've been searching everywhere and I can't find
any particular information that is helpful besides what I posted yesterday.
I'll keep looking.

--
Tim Young
Elevate Software
www.elevatesoft.com