Latest News – May 2018

Latest Windows 10 update (1803)

In recent weeks, we have received a couple of reports of customers having issues connecting to the server, using a shared client after the latest Windows 10 update (1803) is installed.

Before the update, a client workstation using a shared client on the server can connect to the application server without error.  After the update is installed and with no other changes to the setup, that same client machine then sees the standard network connection error shown below:

capture4

We are investigating the Windows update in order to try and resolve this issue, however the workaround in the meantime is to copy the client to the local machine.  This will then allow the connection successfully.

Obsolete Ini Keys

If you are having issues with your server appearing to freeze during very large processing, we recommend you check your application ini file for the following two ini keys:

  • RecordAutomaticClose=
  • DirectoryUpdateInterval=

If you find either of these keys, then we recommend you remove it from the ini file and restart the Equinox service.  After some recent investigations we have discovered that these ini keys have been the cause of some speed issues in the server.

These ini keys were originally created back as far as version 3, system environments have moved on quite a lot since then and therefore these ini keys are no longer required. As of build 4210 of V6 these ini keys have been made obsolete so even if they exist in your ini file, they will be ignored.

Advertisements

Equinox 7 Interim Beta

Compsoft has today released an Interim Beta version of Equinox 7. The Interim Beta contains a sub-set of the final version 7 features and has been created to enable developers to test these features well in advance of release, currently scheduled for Q4 2018. A feature-complete Beta version will be produced closer to the release date.

If you would like to become a Beta Tester or to find out more about the features in the Interim Beta, please contact support@compsoft.com.

Latest Equinox News

Latest Equinox 5 Build Released (3915)

We are pleased to announce the release of the latest build of Equinox 5 (3915).  The only change in this build is an upgrade of the build environment to Visual Studio 2008, which allows the continued maintenance and creation of new builds as necessary.  This new build also comes with EqlSLib.dll in the executable folder.

As you know, the number of Equinox 5 builds is now becoming less frequent and we only produce a V5 build for major issues affecting systems.  Any reported bugs will only be fixed in V6 from now on so this is likely to be the last build of V5.

Knowledgebase

We have made a change in the list view of the Equinox Knowledgebase to provide a new column showing which versions of Equinox an article is written for – this is to enable you to determine whether an article is valid for your current version(s).  We are gradually working through the articles and adding a version value to them. Please note that several of the articles have not been not marked as applicable to version 6.x solely because the external declarations have not yet been updated – please contact support if you’d like more information on this.

There are also 2 new articles since the last newsletter:

  • Improved Unique ID Creation Code
  • Generate Random Strong Password

Latest Equinox 6 Build Released (4203)

We are pleased to announce the release of the latest build of Equinox 6 (4203).  We know a lot of you have been eagerly awaiting this build as we have been working on several fixes for issues reported by you.

One of the main reasons for the delay in the release of this build is that we found an issue with the automated backup process.  You could setup a schedule and commands as normal and they would work perfectly fine for an undetermined amount of time, then all of a sudden for no reason the backup process would stop taking a copy of the application.  Equinox was going through the process, it was triggering the command at the scheduled time, but the command would take zero seconds and when you looked at the backup itself, it was not updated with a new copy.

So instead of the output log showing:

04-09-2017 12:30:01 TM40: TransactionGlobalStart
04-09-2017 12:30:02 TM110: TransactionGlobalStart complete
04-09-2017 12:30:02 Scheduler: Executing command d:\Equinox\eq600\4203\v6atozBackups\Scripts\backupMon30.bat
04-09-2017 12:30:20 Scheduler: Command d:\Equinox\eq600\4203\v6atozBackups\Scripts\backupMon30.bat complete
04-09-2017 12:30:20 Scheduler: ‘Bu’ command completed
04-09-2017 12:30:21 TM80: TransactionGlobalCommit
04-09-2017 12:30:21 TM120: TransactionGlobalCommit complete

 

Instead the backup log showed this:

04-09-2017 12:30:01 TM40: TransactionGlobalStart
04-09-2017 12:30:02 TM110: TransactionGlobalStart complete
04-09-2017 12:30:02 Scheduler: Executing command d:\Equinox\eq600\4203\v6atozBackups\Scripts\backupMon30.bat
04-09-2017 12:30:02 Scheduler: Command d:\Equinox\eq600\4203\v6atozBackups\Scripts\backupMon30.bat complete
04-09-2017 12:30:20 Scheduler: ‘Bu’ command completed
04-09-2017 12:30:21 TM80: TransactionGlobalCommit
04-09-2017 12:30:21 TM120: TransactionGlobalCommit complete

 

After much investigation, we believe this is down to a Windows change.  Having made the following change to the Windows registry, we have been unable to replicate the above issue and the backups have been working every 15 minutes between 09:00 and 20:00 hrs for the past 2 weeks.

Increase the maximum number of child processes that can be spawned by a Windows service.

  • Backup your registry before making any changes
  • Run Regedt.exe as the administrator
  • Edit the registry value:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows

 

  • You will see a string like:
%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=1

 

The critical part is:

SharedSection=1024,20480,768

 

We increased the third number in this section from 768 to 2048 and we have not seen the issue with the backups since this change was made.

SharedSection=1024,20480,2048

 

 

More details on the change we have made in our testing can be found here:

https://stackoverflow.com/questions/17472389/how-to-increase-the-maximum-number-of-child-processes-that-can-be-spawned-by-a-w

 

Full details of the other fixes contained in this build can be found on the Equinox6 website.  If you would like a copy of this new build, please complete the usual software request form and send it to support@compsoft.com (please remember only one item of software per request form, thank you).