If the OnBase Client and Configuration modules are communicating with DDS Server, but are having difficulty accessing Disk Group files, the problem may be with the assigned Windows rights to the Disk Group files and directories. The DDS Server is running in a process under security rights to an assigned user. For more information, see Windows Directory Security Configuration.
Here are some tips for diagnosing security problems:
-
Use the -verbose command line switch. If an error occurs accessing files, it should be recorded in the error log file. The following error codes are common:
Number
Code
Description
2
ENOENT
No such file or directory. This could be a security problem or an improperly created path in the Configuration module.
12
ENOMEM
Not enough memory.
13
EACCES
Permission denied. This is a problem with assigned Windows permissions.
24
EMFILE
Too many open files.
28
ENOSPC
No space left on device.
-
Log on to the workstation running DDS Server as the user assigned to DDS Server. Verify the problem file/directories can be opened.
-
Verify permissions to Windows shares are set on both the Share Permissions tab and the Security tab. Right-click on the shared directory and select Properties.
-
The Share Permissions tab is found by selecting the Sharing tab and clicking Permissions.
-
The Security tab is found by clicking the Security tab.
-
-
Verify permissions on different directories/files (including the onbase32.ini file) of the problem path(s) are not overriding parent permissions and removing privileges.