Toad Data Point Windows 10 Issue

Hello All,

My team has recently migrated from Windows 7 to Windows 10. We all all Toad Data Point running fine on our Windows 7 machines, but on Windows 10 we cannot get an automation script to run. Each time we execute even a simple ‘Select to File’ activity, TDP attempts to create a randomly named folder in the local/temp/1 folder and open a cmd line file.

Below are the errors for 3 consecutive run attempts on a ‘Select to File’ activity:

Error opening response file ‘c:\Users\macross\AppData\Local\Temp\1\l4bvfjnt\l4bvfjnt.cmdline’ – 'Access is denied. ’

Error opening response file ‘c:\Users\macross\AppData\Local\Temp\1\15eojm41\15eojm41.cmdline’ – 'Access is denied. ’

Error opening response file ‘c:\Users\macross\AppData\Local\Temp\1\3zcwzqud\3zcwzqud.cmdline’ – 'Access is denied. ’

And below is the log in it’s entirety for a 4th attempt:

Timestamp Message
11/26/2018 11:55:53 AM Starting Automation Script
11/26/2018 11:55:53 AM Setting up environment
11/26/2018 11:55:53 AM Script run by Toad Data Point as macross on CNCVDA1426
11/26/2018 11:55:53 AM Build started
11/26/2018 11:55:53 AM Compiling script
11/26/2018 11:55:53 AM Start CompileWorkflow
11/26/2018 11:55:53 AM Before Compile
11/26/2018 11:55:54 AM Return from CompileWorkflow
11/26/2018 11:55:54 AM Script has Compiler Errors
11/26/2018 11:55:54 AM Error opening response file ‘c:\Users\macross\AppData\Local\Temp\1\14datrvd\14datrvd.cmdline’ – 'Access is denied. ’
11/26/2018 11:55:54 AM Build failed

This is a team wide issue. We’ve reimaged our VDIs well, but this hasn’t resolved the issue. Any ideas as to why it runs on Win 7 but errors out on Win 10 & attempts to create a random folder?

The automation window uses Microsoft Windows Workflow technology. The first thing it does is to compile the automation script. It makes a folder in the user profile temp area. This is where you are getting your error. I don’t think the issue is a Windows 10 issue. Rather it is how your IT has set up your security. Please go over this with your IT and explain that your profile needs to create a folder in the profile Temp dir. They should be able to find out what is causing the restriction.


Thank you for the reply. I’ll reach out to our IT team and follow-up if this resolves the issue. Is this a change between TDP 4.0 & 4.3? I ask because we should have the same persmissions on Win 10 as we did on 7 (I’ll confirm), and this wasn’t an issue on 4.0.

Also, I am able to create folders in the location TDP 4.3 references, though of course a subsequent run of the script tries for a newly named temp file which fails. That said, the fact that I can manually create a folder & file in the path that the TDP log references would imply that I have the necessary permissions, which I assume TDP would inherit. As such, I’m not sure it’s a security issue.

I’ll touch base with our IT team with your recommendation and follow up. Aside from that, did you have any other suggestions?

Thanks, Debbie. I really appreciate your help here.

There hasn’t been a change between TDP 4.0 & 4.3. Let me know what your IT says