Kbase P7693: .p file path was not found in WebSpeed with Shared Network D
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/7/2003 |
|
Status: Verified
FACT(s) (Environment):
WebSpeed 3.x
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
SYMPTOM(s):
.p file path was not found in WebSpeed while compiling the application
The .p file path for the field level triggers is appended in the agent's PROPATH
The database triggers file exists in the shared network drive
Users has access to the network drive
The AdminServer is started as a system user in the control panel > Services
CAUSE:
The AdminServer is started as a System account. The system account in Windows is a valid user for each particular machine. When AdminServer is started using the system account, each of the child processes such as NameServer, broker and ultimately WebSpeed agents inherit the system user privileges. Since the system account or user does not have the privileges to access the network drive, the drive is invisible to the WebSpeed agents.
FIX:
Start the Progress AdminServer by creating a generic user with Administrative privilege with the following Local Security policies and grant the access to the shared mapped drive to that user:
- Act as part of the operating system
- Increase quotas
- Log on as a batch job
- Log on as a service