In Windows, the access to the network drives by the component software listed in the following table is restricted. The following table describes the constraints for the component software.

Also, note that the access to the network drives is restricted for a program started from a service depending on the Windows specifications.

Table 3-2 Constraints on accessing the network drives

Component software	Constraints
Component Container (in 32-bit Windows)	The server communication agent is started from a service. Therefore, the server communication agent cannot access the network drives. Do not specify a network drive in the log output destination, storage location of the processing data, and work directory of the server communication agent.
Component Transaction Monitor	When you use a Windows service to start Component Transaction Monitor, do not specify a network drive path in the CTMSPOOL environment variable.
HTTP Server	The network drives cannot be accessed from the HTTP server.
Performance Tracer	When you use a Windows service to start Performance Tracer, do not specify a network drive path in the PRFSPOOL environment variable.
Reliable Messaging	Do not specify the files and directories on a network drive in the following Reliable Messaging configuration properties: QueueConfigFileName QueueMakeFileName RMTRTransferControlDir
TPBroker	Do not specify a network drive or the files on a network drive in the environment variables and properties used with the ORB functionality.
HiRDB Embedded Server Version 8	The network drives are not connected when the power is input, so HiRDB Embedded Server Version 8 cannot be started by using a Windows service. Therefore, do not install this software on a network drive and do not set up the database environment.
DABroker Library (in 32-bit Windows)	A directory on a network drive cannot be specified in the DABTMP (work directory). For details on the DABTMP, see 4.23 Items set up in common in the uCosminexus Application Server Maintenance and Migration Guide.