Client process failing with error 1720 in 10.1B+ attempting to attach to database in shared memory on Windows.

« Go Back


EnvironmentProduct : OpenEdge
Version: 10.1B, 10.2x, 11.x
OS: Windows
Other: 32-bit
Question/Problem Description
Client process getting error 1720 in 10.1B and later when attempting to attach to database shared memory on Windows.
Getting error 1176 when starting database server with large value for -B on Windows under 10.1B.
Steps to Reproduce
Clarifying Information
Error MessageUnable to attach shared memory Global\<shmname>, error 0. (1720)
The data space of the process is not enough for the shm segment (1176)
Defect/Enhancement Number
Changes to internal architecture of the OpenEdge 10.1B client code and 10.1B database internals have changed the memory requirements and some functional limits for many executables.

In 10.1B the client will most likely only be able to connect in shared memory to a database or multiple databases whose total allocated shared memory is around 1.4 Gig of RAM (or less).

Depending on the database startup parameters, the following are typical values for -B dependent on database blocksize:

DB Blocksize   Approximate limit for -B value which
               will allow shared memory connection
1k             1400000
2k              700000
4k              350000
8k              175000

These numbers are largely approximations. 
Other database startup parameters which affect shared memory sizing such as -B, -L, -Mxs, -shmsegsize, et al. will lower the above limits.
Changes to .dll versions within a system may lower the above suggested values. In prior versions shared pointers were only 64 bits wide on 64-bit versions of Progress / OpenEdge. In 10.1B or later versions shared pointers are 64 bits wide for both 32-bit and 64-bit versions of Progress / OpenEdge. This is one of the factors which has increased the size of client and server memory space in 10.1B and later necessary for the manipulation of 64-bit structures.

Though the database may be able to startup with values higher than those listed above, the client requires a much larger heap size in 10.1B compared to earlier versions and this added memory usage lowers the total memory that the client can attach to and still be within the addressable 32-bit memory limit for a client executable on Windows.
1. Reduce the shared memory on one or more database servers startup parameters.  

A good starting point is to reduce the prior value of Database Buffers (-B) by 10%. Since OpenEdge 10.1B the -shmsegsize database startup parameter can be adjusted down so enough contiguous Memory are available for the Virtual Memory Manager to provide to the server. Refer to Article P133127, What is the default -shmsegsize value used when allocating shared memory segments?   

The database must be restarted for these new settings to take effect and the client connection in shared memory should be attempted immediately after the database is started to see if the reduction in shared memory and the segments used to satisfy the requirement is sufficient to avoid the 1720 error. This also increases the chances of their being enough contiguous Memory available for the Virtual Memory Manager to provide to the client.  For example several clients may be able to connect, before the nth fails due to the fact that the memory pages have fragmented such that contiguous memory are not longer available when the shared memory requirements are approaching the 32-bit executable limit.

2.  Connect Client-Server (-S -H) instead of shared-memory

3.  Use Windows OpenEdge 64-bit license instead of 32-bit which is available since OpenEdge 10.2B.  
  • 32-bit clients will need to connect to the 64-bit Database Client Server
  • 64-bit client processes will be able to attach to more shared memory
Last Modified Date11/11/2016 11:36 AM

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Was this article helpful?


Your feedback is appreciated.

Please tell us how we can make this article more useful.

Characters Remaining: 255