I have just had to reinstall edbsrvr on a new DELL Windows 64 bit server for a client as their old XP 32 bit PC had died. Unfortunately I have since  had reports of severe LAN slowdowns and other associated program issues.

I like to have all my programs in the same place so  I had installed the 64 bit version of the server into the C:\Program Files (x 86) folder rather than  C:\Program Files but I did think that the  server folder location should make no difference to its running Am I correct?  

I plan to reinstall the 32 bit server version iof the server as this has been working flawlessly but I have another question  Can I use the same Config Files that were created when I installed the 64 bit server.

Finally please confirm that the following is the correct procedure for installing either version of the server and if there is anything else I should do or check

1. Ensure a blank edbsrvr.ini file is present  in either C:\Program FIles or C:\Program FIles (x86) and ensure  write permissions are enabled

2 Run edbsrvr from either C:\Program FIles or C:\Program FIles (x86) and point the Configuration Path to the correct folder  Set up the Session timeout etc parameters  I have increased Session Timout to 600 and left the rest as default

2 Ensure that Port 12010 is allowed through the firewall

3.Install edbsrvr as a Service from the CMD window  ie "C:\Program Files (x86)\FolleyTech\BoozeBarnEDB\edbsrvr.exe" /install  /nointeract   then start it ie net start edbsrvr

If Ihave done nothing wrong then what do oI need to do next to try and resolve this

Many thanks

I would not be installing into Program Files.

Since Vista - Program Files is a  virtualized folder.

I would install into ProgramData

or make my own folder under  C:\Users\Public

Walter

Walter Matte wrote:

I would not be installing into Program Files.

Since Vista - Program Files is a  virtualized folder.

I would install into ProgramData

or make my own folder under  C:\Users\Public

Walter

Thanks for that    As I general rule you may be right but I as I understand it should not matter where the server program is located especially if is run as  service

I have been examining the server log and it may be that there is another reason for the LAN slowdown It appears that 2 computers were left on overnight  because the message

"The session ID 7 is no longer present on the server"

is logged at regular 1 minute intervals "  from each machine for many overnight  hours even though the sessions on the server were obviously destroyed  

I wonder could this be caused by the workstaion powering down  even though the pings were getting through

In any case it appears that when one computer is  then started up in the morning the same message is logged for 25 times in just 1 second  And it occurs again later on  with multiple messages in just a couple of seconds  Thsi doesn't look right to me Any ideas perhaps hardware issues ?  I need more log info but if this is happening regularly it would certainly slow things down

Thanks

Michael,

<< I like to have all my programs in the same place so  I had installed the 64 bit version of the server into the C:\Program Files (x 86) folder rather than  C:\Program Files but I did think that the  server folder location should make no difference to its running Am I correct? >>

The *executable* location makes no difference, but the EDB Server (by default) looks for the edbsrvr.ini file in the current directory, and then in the:

c:\programdata\Elevate Software\ElevateDB Server

directory for 32-bit servers and the:

c:\programdata\Elevate Software\ElevateDB Server (Win64)

directory for 64-bit servers.

<< I plan to reinstall the 32 bit server version iof the server as this has been working flawlessly but I have another question  Can I use the same Config Files that were created when I installed the 64 bit server. >>

Do you mean EDB configuration files (edbconfig.edbcfg), or the edbsrvr.ini server settings file ?

<< 1. Ensure a blank edbsrvr.ini file is present  in either C:\Program FIles or C:\Program FIles (x86) and ensure  write permissions are enabled >>

I wouldn't store the edbsrvr.ini file in the \Program Files tree.  As I say above, you *can* put the edbsrvr.ini file in the same directory as the edbsrvr.exe, but that is normally only for situations where the edbsrvr.exe is stored somewhere *outside* of the \Program Files tree.

<< 2 Run edbsrvr from either C:\Program FIles or C:\Program FIles (x86) and point the Configuration Path to the correct folder  Set up the Session timeout etc parameters  I have increased Session Timout to 600 and left the rest as default >>

If you're using pinging with the client's remote sessions (the default - TEDBSession.RemotePing=True), then you should keep the session timeout as the default.

Tim Young
Elevate Software
www.elevatesoft.com

Michael,

<< I wonder could this be caused by the workstaion powering down  even though the pings were getting through >>

<< In any case it appears that when one computer is  then started up in the morning the same message is logged
for 25 times in just 1 second  >>

Yes, this is what will occur if:

1) Your application attempts several operations

2) They fail because the remote session is no longer present on the EDB Server

3) Your application is not handling the OnRemoteReconnect event for the remote TEDBSession.  In such a case, the remote session will simply try to reconnect when a call fails because there is no active connection.

The reasons for 2) can be numerous, but it is usually caused by the remote session not pinging the EDB Server at a regular interval (TEDBSession.RemotePing=False). However, it could be caused by restarting the EDB Server, a session being manually removed, etc.

Tim Young
Elevate Software
www.elevatesoft.com

<< I plan to reinstall the 32 bit server version iof the server as this has been working flawlessly but I have another question  Can I use the same Config Files that were created when I installed the 64 bit server. >>

Do you mean EDB configuration files (edbconfig.edbcfg), or the edbsrvr.ini server settings file ?
 

I mean the EDB configuration files (edbconfig.edbcfg)  Can these be shared between 32 and 64 bit server editions

Thanks

Michael,

<< I mean the EDB configuration files (edbconfig.edbcfg)  Can these be shared between 32 and 64 bit server editions >>

Yes, absolutely.  None of the configuration, database, or table files are specific to a certain type of client, which is why they can be updated using 32-bit, 64-bit, Windows, Linux, managed .NET, etc.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

Michael,

<< I mean the EDB configuration files (edbconfig.edbcfg)  Can these be shared between 32 and 64 bit server editions >>

Yes, absolutely.  None of the configuration, database, or table files are specific to a certain type of client, which is why they can be updated using 32-bit, 64-bit, Windows, Linux, managed .NET, etc.

Tim Young
Elevate Software
www.elevatesoft.com

Just for the record the all the issues i have been having would appear to be hardware related,

However although this is not presenting a problem as far as I am aware I would still like to know what may be the cause of the message  'The session ID X is no longer present on the server'  in particular because client pinging is enabled.  Every now and then there will be a lot of these messages all logged  at 1 minute intervals (I assume coinciding with a ping interval of 1 minute as set on the client)

Many thanks

On 9/10/2015 1:28 PM, Michael Saunders wrote:
> However although this is not presenting a problem as far as I am aware I would still like to know what may be the cause of the message  'The session ID X is no longer present on the server'  in particular because client pinging is enabled.  Every now and then there will be a lot of these messages all logged  at 1 minute intervals (I assume coinciding with a ping interval of 1 minute as set on the client)

It essentially means the server has removed the disconnected/dead
sessions so when client attempts to reconnect the session is gone from
server. Normally this is due to not enabling the session remoteping but
since you said it is enabled it would require some additional
investigation (i'd start by checking the server timeout settings but the
hardware issues you are mentioning sound suspect also - is it possible
you lose server connection due to HW issues and remoteping keeps failing
also?).

This is a great article for understanding these types of situations
better in general and how to handle them on both sides:

http://www.elevatesoft.com/articles?action=view&category=edb&article=connections_disconnections_reconnections

Raul

Raul wrote:

On 9/10/2015 1:28 PM, Michael Saunders wrote:
> However although this is not presenting a problem as far as I am aware I would still like to know what may be the cause of the message  'The session ID X is no longer present on the server'  in particular because client pinging is enabled.  Every now and then there will be a lot of these messages all logged  at 1 minute intervals (I assume coinciding with a ping interval of 1 minute as set on the client)

It essentially means the server has removed the disconnected/dead
sessions so when client attempts to reconnect the session is gone from
server. Normally this is due to not enabling the session remoteping but
since you said it is enabled it would require some additional
investigation (i'd start by checking the server timeout settings but the
hardware issues you are mentioning sound suspect also - is it possible
you lose server connection due to HW issues and remoteping keeps failing
also?).

This is a great article for understanding these types of situations
better in general and how to handle them on both sides:

http://www.elevatesoft.com/articles?action=view&category=edb&article=connections_disconnections_reconnections

Raul

All the settings are as the default apart from the server session timeout  which is set to 360   These timeouts have in fact been occuring for quite sometime and I overcame this by picking them up the OnRemoteReconnect event  as described elsewhere on this forum.   This then allowis the user to reinitialise the session without having to restart the program  Fortunatey the nature of the program allows me to do this without causing any problems  It does mean that I have to set the session timeout value to more than the default

Mike