Bug 10638

GemStone/S

6.7.2.1, 6.7.2, 6.7.1, 6.7, 6.6.5, 6.6.4, 6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7.5, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.1.5, 6.1.x, 6.0.x, 5.1.5.1, 5.1.5, 5.1.4, 5.1.3, earlier versions

Windows

Service may not start when GemStone resides on network drive

A Stone or NetLDI service created to run as the default account
LocalSystem may fail to start when the GemStone installation
is on another machine accessed by way of a network drive.  The
symptom is an "Access is denied" error at startup.

In general, the account the service is running as must have
"read" access to the GemStone installation directory tree. In
addition, the NetLDI's account by default needs "change" access
to the GEMSTONE\log directory; the stone's account by default
needs "change" access to the GEMSTONE\data directory.

Workaround

Create the NetLDI using the switch ' /u accountName' where
accountName is a user who has network access to the machine
where GemStone is installed.  This user must also have the
Windows NT advanced user right "Log on as a service" on the
machine the service will run on.

Although a Stone can be run from a GemStone installation on
a network drive, it will not be able to use the default database
in GEMSTONE\data.  This is because the database extents need to
be on a disk that is local to the machine the Stone is running on.


                

Last updated: 9/9/03