Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to install Oracle 12c in a Windows 7 x64 computer and after a while I get this error:

SEVERE: [FATAL] [INS-30131] Initial setup required for the execution of installer validations failed.
   CAUSE: Failed to access the temporary location.
   ACTION: Ensure that the current user has required permissions to access the temporary location.
- Framework setup check failed on all the nodes
- Cause: Cause Of Problem Not Available
- Action: User Action Not Available
Summary of the failed nodes
- Version of exectask could not be retrieved from node "XXXXXX"
- Cause: Cause Of Problem Not Available
- Action: User Action Not Available

Does anybody have an idea how to solve this problem?

share|improve this question
Sounds like you're trying to install it without admin privileges. – Phil Nov 1 '13 at 10:42
Nope :) I am dumb but not THAT dumb. – Y. Ecarri Nov 1 '13 at 11:17
In my case there was no C$ share. I shared with admin only permissions and did the trick. – pmesina Mar 12 '14 at 22:02

I found the problem. For reasons I don't understand Oracle needs access to the file system through the administrative network share (i.e. \computer\c$) and I had disabled it.

Things to check to solve this issue:

  1. Remove your computer from workgroups.
  2. Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System DWORD value LocalAccountTokenFilterPolicy to 1
  3. Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters DWORD value AutoShareWks to 1
share|improve this answer
Adding a share helped, thanks a lot! – mruether Sep 24 '14 at 13:29
Please click the 'checkmark' to mark your answer as "the" answer. – Paul White Mar 31 '15 at 9:04

I finally got the answer for this error, this was because of the machine name being big. While setting up a new machine we should ensure that the machine name is not bigger then the bios name. which is 15 chars. This will definitely work.

share|improve this answer
One of my colleagues had this problem. As Incredible as it might seem, his PC name had 16 characters. After changing to less than 15, the installer worked! – XMight Mar 3 at 10:41

Extending the answer from Y.Ecarri above,

  • Ensure the Server service is started. Go to run box and type services.msc. This should bring up the Services console.

  • Type \\<your-computer-name> in the run box and check if you're able to see the shared folders.

share|improve this answer

protected by Community Aug 27 '15 at 16:28

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.