QlikView cannot connect to Access Database via ODBC driver with "is not a valid path" error when mapped drives are used.

QlikView Distribution Services cannot connect to Access Database via ODBC driver with "is not a valid path" error when mapped drives are used. Using the mapped driver later while connecting to data with QlikView Desktop works fine when logged in with the user that created the mapped drive.

The following is registered in the document logs:
...
2019-06-17 12:17:11 Error: Connector connect error: SQL##f - SqlState: S1009, ErrorCode: 4294966273, ErrorMsg: [Microsoft][ODBC Microsoft Access Driver] '(unknown)' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.
2019-06-17 12:17:11 Connector connect error: SQL##f - SqlState: S1009, ErrorCode: 4294966273, ErrorMsg: [Microsoft][ODBC Microsoft Access Driver] '(unknown)' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.
2019-06-17 12:17:11 Execution Failed
2019-06-17 12:17:11 Execution finished.
...

Environment:

• QlikView Distribution Service, all versions.

The QlikView Distribution Service, runs as a Windows Service which does not support use of mapped drives letters. More information on this is documented under Services and Redirected Drives

This issue has also been discussed under the community post below:
MS Access ODBC connection prevents reload in management console
 

Use the UNC share path in the ODBC System DSN configuration. The value can also be changed directly under the following registry string:

Note: Please make sure to backup your registry information prior making any changes:

64-bit:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\<DSN_name>\DBQ

32-bit
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBC.INI\<DSN_name>\DBQ