A customer has a version 3 server running as a service on Windows 2000
server.  They just added 2-3 users on Terminal Server.  Now the service just
quits working every once in a while.  They have not previously had any users
on terminal server.

Thanks,
Bill

Bill,

<< A customer has a version 3 server running as a service on Windows 2000
server.  They just added 2-3 users on Terminal Server.  Now the service just
quits working every once in a while.  They have not previously had any users
on terminal server. >>

Is anyone logging in as the administrator and then logging off ?  This
shouldn't affect the service itself, but I'm wondering if it's a desktop
interaction issue.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:E4A06638-5250-4662-A4CF-CC7ABFD1330E@news.elevatesoft.com...
>
> Is anyone logging in as the administrator and then logging off ?  This
> shouldn't affect the service itself, but I'm wondering if it's a desktop
> interaction issue.
>

I dont think its what you suggest in 3 or 4 running as a service its
bullet proof in what your thinking, even from admin logging on and
off on a client machine the same time the client user is logged on.
Plus multiple logging on/off via various clients.

Version 3 tested with 10 users all savvy logging onto my remote server
on both Win 2003 and Linux SuSE 8 from clients as diverse as RH 7
to SuSE 10.3 and even WinME (cough splutter) to Win XPPro 64 Bit
not a Vista box insight tho so I cant say its out the frame ask Bill.

Also 25 users trying to screw up my server at the same time by all pressing
submit booking had some serious testing on a local network.
I was also logged on as Admin plus Rita with admin status logging on and
off, thats a common gotcha in 2 other BDE replacement libs no longer
used or developed as far as I know, but it may have been a DBF file problem.
So if its what you suggest I owe you a beer if not you owe me a scotch.
Rita

Rita,

<< I dont think its what you suggest in 3 or 4 running as a service its
bullet proof in what your thinking, even from admin logging on and off on a
client machine the same time the client user is logged on.  Plus multiple
logging on/off via various clients. >>

Yeah, I don't think it's that either, but I'm just trying to probe and find
out if I can find anything peculiar.

--
Tim Young
Elevate Software
www.elevatesoft.com

> Is anyone logging in as the administrator and then logging off ?  This
> shouldn't affect the service itself, but I'm wondering if it's a desktop
> interaction issue.

They don't have any admin access to the dbisam server.  But at least one
person I know of logs into the Windows 2000 server as an admin user.
Could I try the nointeract parameter?

This is a new problem.  They've been running for a couple years with no
issues until they added users to the terminal server accessing data directly
on the same machine and applied the latest updates to Server 2K.

Bill

Bill,

<< They don't have any admin access to the dbisam server.  But at least one
person I know of logs into the Windows 2000 server as an admin user. Could I
try the nointeract parameter? >>

Sure, it's worth a try.

<< This is a new problem.  They've been running for a couple years with no
issues until they added users to the terminal server accessing data directly
on the same machine and applied the latest updates to Server 2K. >>

It would be interesting to know if the problem started after the first
incident (TS) or second incident (updates).

--
Tim Young
Elevate Software
www.elevatesoft.com

"B Miller" <bmiller@nospam.com> wrote in message
news:122C74DF-4BFC-4439-BA76-226030F4E36A@news.elevatesoft.com...

Bill do they get a 7031 notice next to Dbisam in the Service Control Manager
?
From deep in my memory 2k stopped abruptly when you added users after
SP4.
Rita

"Rita" <no@spam.com> wrote in message
news:F0F51B5C-B641-4DC6-8DA1-8CF40B1EFCBB@news.elevatesoft.com...
>

I forgot to ask is the service set to Automatic ?
if not set it to Automatic.

Rita

> It would be interesting to know if the problem started after the first
> incident (TS) or second incident (updates).

I'll ask but I think they were simultaneous.

Bill