I have a question that may, or may not, be a DBISAM-specific issue. One of my clients claims that their DBISAM client/server engine periodically
does not restart. They've sent me a screen shot of the server that in fact shows something very contradictory: on the list of servics it shows the
DBISAM set to Automatic for startup type, and Started as the Status. When opened for editing, however, the status shows Stopped! This server is
version 3.24 (it might be 3.27, but I don't believe so).

Short of uninstalling the service and restarting it, are there any other suggestions? I see that the executable may be on a remote drive. I'm going
to suggest that the server executable be placed on the server's local drive. That might be one issue.

Phil Frank
MealService Software

Phil,

<< I have a question that may, or may not, be a DBISAM-specific issue. One
of my clients claims that their DBISAM client/server engine periodically
does not restart. They've sent me a screen shot of the server that in fact
shows something very contradictory: on the list of servics it shows the
DBISAM set to Automatic for startup type, and Started as the Status. When
opened for editing, however, the status shows Stopped! This server is
version 3.24 (it might be 3.27, but I don't believe so). >>

It's certainly possible for the dbsrvr *process* (in this case, running as a
service) to be started while the server itself is stopped, meaning that it
is not listening for any incoming connections.  If the server cannot bind
properly to the local IP address for listening, then starting the dbsrvr
process may not actually start the server listening for incoming
connections.  The server log will tell you what, if any, errors are
occurring while trying to bind to the local IP address(es).

--
Tim Young
Elevate Software
www.elevatesoft.com

> It's certainly possible for the dbsrvr *process* (in this case, running as a
service) to be started while the server itself is stopped

I understand this. But you might not have noticed that I attached a screen shot to my original message. The discrepancy is occurring solely at the
Service level, not at the Windows/Server Administration levels.

I will ask the client to check their server log to see what's being logged.

Phil Frank

Phil,

<< I understand this. But you might not have noticed that I attached a
screen shot to my original message. The discrepancy is occurring solely at
the Service level, not at the Windows/Server Administration levels. >>

Sorry about that.  I missed the screen shot.  That is a weird one - I've
never seen a service listed as Started and then showing a different status
in the Properties dialog.  Perhaps a Google search may shed some light on
this.

--
Tim Young
Elevate Software
www.elevatesoft.com