Kbase 17796: 1720 shared memory error on Win95/98/NT
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/09/1999 |
|
1720 shared memory error on Win95/98/NT
Some possible causes of a 1720 "Unable to attach shared memory" error
on Win95/98/NT PCs running version 8.2+ of Progress are:
1. You are trying to connect to a database in single user mode, but
but forgot to specify a -1 parameter.
2. You are attempting to connect to a database that has a local
server running on this PC (started with _mprosrv.exe) and have
not indicated the path for finding the db when starting the
client. You can specify the path in one of two ways:
- give the full path on the command line
(for example: prowin32 c:\data\info.db)
- make sure the Start in directory for the client icon is the
directory where the database file is
3. You are attempting to connect to a database in self service mode
(With no -1, or -S -H -N parameters) and have forgotten to add the
environment variable "ACCESS=all" in ProControl. NT ONLY.
4. You forgot to put a dash in front of a startup parameter on your
command line. For example, if you want to use the -basekey
parameter, but your command line says: prowin32.exe basekey "INI"
Progress will interpret 'basekey' as the name of your database
and try to connect to it in shared memory. This will give the
1720 error.
5. You are 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 from the ODBC driver. You have
specified a path to the database incorrectly in the ODBC
Data Source Administrator. Be sure the entry for the database
path (under the Database Options tab) does not include the
database name, and ends in a \ Example: c:\progress\database
Progress Software Technical Support Note # 17796