Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Cant connect to server
Wed, Nov 28 2007 7:12 PMPermanent Link

"Al Vas"
Hi,

OK I have misunderstood the client issue a little.  Now as I understand it,
the issue occurs when they try to log in to our product.  They are set up
for client-server access.  When they login it may work fine, but next time
they try and log in they can't as they receive the error:

'DBISAM Engine Error # 11276 The connection to the database server at 'XXX'
has been lost'

When they stop and restart the DBISAM Database engine service they can then
log in.  It seems that the server stops listening on the port or something
similar.  It is spasmodic maybe happening once a day at different times of
the day.  Any ideas?  DBISAM V3.30

Thanks

Alex

Thu, Nov 29 2007 4:13 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Alex,

<< OK I have misunderstood the client issue a little.  Now as I understand
it, the issue occurs when they try to log in to our product.  They are set
up for client-server access.  When they login it may work fine, but next
time they try and log in they can't as they receive the error:

'DBISAM Engine Error # 11276 The connection to the database server at 'XXX'
has been lost'

When they stop and restart the DBISAM Database engine service they can then
log in.  It seems that the server stops listening on the port or something
similar.  It is spasmodic maybe happening once a day at different times of
the day.  Any ideas?  DBISAM V3.30 >>

Are they running any kind of firewall on the server ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Thu, Nov 29 2007 8:06 PMPermanent Link

"Al Vas"
Hi Tim,

They said no when it comes to firewall but they have just indicated there is
a backup that seems to be running overtime.  Maybe that is causing it?

Alex

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:1E2B1F5E-9D03-4C54-856A-33BC63E1D4ED@news.elevatesoft.com...
> Alex,
>
> << OK I have misunderstood the client issue a little.  Now as I understand
> it, the issue occurs when they try to log in to our product.  They are set
> up for client-server access.  When they login it may work fine, but next
> time they try and log in they can't as they receive the error:
>
> 'DBISAM Engine Error # 11276 The connection to the database server at
> 'XXX' has been lost'
>
> When they stop and restart the DBISAM Database engine service they can
> then log in.  It seems that the server stops listening on the port or
> something similar.  It is spasmodic maybe happening once a day at
> different times of the day.  Any ideas?  DBISAM V3.30 >>
>
> Are they running any kind of firewall on the server ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Fri, Nov 30 2007 2:51 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Alex,

<< They said no when it comes to firewall but they have just indicated there
is a backup that seems to be running overtime.  Maybe that is causing it? >>

That still shouldn't cause that particular error.  Something is interfering
with the comms layer, not the database itself.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Dec 3 2007 8:11 PMPermanent Link

"Al Vas"
Hi Tim,

Have just found some extra information from our client in respect to this
issue.

What they have found is that if someone logs onto the server and logs off
again, the DBISAM server engine appears to lockup - or more
correctly -disallows logins from our software.  Stopping and restarting the
service fixes this issue and the user can log in again.

I have checked the service Logon properties and it is set to login on local
system account and allow service to interact with desktop.

Is this the correct standard setup?  Any ideas on what we might be able to
try?

Regards

Alex

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:DBA9D1F0-94AE-4571-8992-9D52D7007F53@news.elevatesoft.com...
> Alex,
>
> << They said no when it comes to firewall but they have just indicated
> there is a backup that seems to be running overtime.  Maybe that is
> causing it? >>
>
> That still shouldn't cause that particular error.  Something is
> interfering with the comms layer, not the database itself.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Tue, Dec 4 2007 4:20 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Alex,

<< What they have found is that if someone logs onto the server and logs off
again, the DBISAM server engine appears to lockup - or more
correctly -disallows logins from our software.  Stopping and restarting the
service fixes this issue and the user can log in again.

I have checked the service Logon properties and it is set to login on local
system account and allow service to interact with desktop.

Is this the correct standard setup?  Any ideas on what we might be able to
try? >>

You'll want to un-check the Interact with Desktop property for the service,
and make sure that you set the DBISAM Database Server dbsrvr.ini file (same
directory as the dbsrvr.exe) so that it doesn't try to display any
interface:

http://www.elevatesoft.com/dbisam4d7_configuring_starting_server.htm

; Sample DBISAM Database Server Parameters INI File

[Server Parameters]
; Default server name is the EXE name
Server Name=Test Server
; Default server description is DBISAM Database Server
; plus the Server Name
Server Description=Test Server Description
; Default server IP address is all addresses on the machine
Server Address=127.0.0.1
; Default server port is 12005
Server Port=10001
; Default server thread cache size is 10
Server Thread Cache Size=20
; Default admin IP address is all addresses on the machine
Administration Address=127.0.0.1
; Default admin port is 12006
Administration Port=10002
; Default admin thread cache size is 1
Administration Thread Cache Size=4
; Default configuration file name is dbsrvr
Configuration File=Test
; Default configuration file password is elevatesoft
Configuration Password=cannotguessme
; 0=main server allows unencrypted connections (default)
; 1=main server allows only encrypted
Encrypted Only=0
; Default encryption password is elevatesoft
Encryption Password=cannotguessme
; 0=show user interface (default) 1=hide user interface  <<<<<<<<<<<<< Set
this to 1
No User Interface=0
; 0=overwrite log file (default) 1=append to log file
Append To Log=0
; 0=no large file support (default) 1=enable large file support
Large File Support=0

--
Tim Young
Elevate Software
www.elevatesoft.com

Image