There may be two reasons, and the most possible cause is privileges control.

1. Maybe the Antivirus soft prevents access. Please check all Antivirus soft to confirm.
2. The current user may have not ACCESS privilege: Check all related directory and files privilege, such as in directories and subdirectories in DBMaker installation directory to confirm whether the current user has “read and write” privilege. If the current user has not these privileges, the problem will occur.

For DBMaker 4.1.2, most of files and sub folders under JRE folder do not have "read and write" for "Everyone". Changing them to "read and write" for "Everyone", the problem is solved.

The problem exists on DBMaker 4.1.2, but not exists after 4.1.2 version.

Two versions used different install tool and different install tool（install shield and inno setup）has different action which cause the problem. So user should grant privilege first, or install high version DBMaker client (after 4.1.2).