Kbase P92479: Troubleshooting error 1720 "Unable to attach shared memory" on Windows
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/11/2008 |
|
Status: Verified
GOAL:
Troubleshooting error 1720 "Unable to attach shared memory" on Windows
GOAL:
Unable to attach shared memory <shmname>, error <n>. (1720)
FACT(s) (Environment):
Windows 32 Intel
Windows NT 32 Intel/Windows 2000
Progress/OpenEdge Product Family
FIX:
This Solution has been created to assist in the troubleshooting of possible causes of a 1720 "Unable to attach shared memory" error on Windows platforms running Progress 8.2x and above, when a client session tries to establish a connection to the database:
1. Trying to connect to a database in single user mode, but forgot to specify a -1 parameter:
$ prowin32 dbname -1 [parameters]
$ CONNECT dbname -1 [parameters]
2. Attempting to connect to a database that has a local server running on this PC (started with _mprosrv.exe) and have made the connection from a directory that is not this database's working directory. In this case, the full path needs to be specified when starting the client. You can specify the path in one of two ways:
a.) give the full path on the command line:
$ prowin32 <full path to database>\dbname [parameters]
b.) put the directory where the database file is, in the "Start in" directory of the client's icon.
3. On a database managed by ProControl, connecting to a database in Client Server mode works, but connecting to Connect to a database in self service mode (in other words, with no -1, or -S -H -N parameters) fails with this 1720 error. The environment variable "ACCESS=all" needs to be added to ProControl and restarted.
4. There is a typo in the command line. For example, there is a missing dash in front of a startup parameter, if you want to use the -BASEKEY parameter, but your command line reads: prowin32.exe basekey "INI" , Progress will interpret 'basekey' as the name of your database and try to connect to it in shared memory. Strip as many parameters out of the command line until you can establish a connection and then add these back incrementally.
5. Attempting to connect to a database that has a local server running on this PC (started with _mprosrv.exe) and are trying to access the data through the ODBC driver. One of the entries in the Driver Setup are incorrect. Ensure that these connection parameters mirror a command line Client Server connection from the same machine to the same database.