Invalid Path Error
Leicester asked 7 years ago
Hi,
I created a scheduled Map in SmartConnect which imports data from a mapped network drive. This map returns the following error:
“Connection could not be validated.
ERROR [HY024] [Microsoft] [ODBC Excel 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.
Error [IM006] [Microsoft] [ODBC Driver Manager] Driver’s SQLSetConnectAttr failed.”
If I copy the file to a local drive, the map runs without an error.
How can I get this map to run without an error with the file on the mapped network drive ?
Thanks
I created a scheduled Map in SmartConnect which imports data from a mapped network drive. This map returns the following error:
“Connection could not be validated.
ERROR [HY024] [Microsoft] [ODBC Excel 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.
Error [IM006] [Microsoft] [ODBC Driver Manager] Driver’s SQLSetConnectAttr failed.”
If I copy the file to a local drive, the map runs without an error.
How can I get this map to run without an error with the file on the mapped network drive ?
Thanks
Answers
Patrick Roth Staff answered 7 years ago
Leicester,
I would guess either you do not have the file and drive letter mapped to the source path (so SC cannot find it) or else you don’t seem to have permissions to the file on that drive.
patrick
I would guess either you do not have the file and drive letter mapped to the source path (so SC cannot find it) or else you don’t seem to have permissions to the file on that drive.
patrick
Leicester replied 7 years ago It works fine when I manually run the map, but it will not work once it is scheduled, and they are both reading from the same file location.
Holly replied 4 years ago For other users (like me) searching for the answer – in order to deal with the drive mapping issue, we copied and pasted the UNC path into the file name field since we could not navigate to it. (Server was not shown in network.) This resolved our issue.