2

I am trying to install SQL Server Enterprise Core 2012 w SP1 64bit (as downloaded from the Microsoft Partner Program site) on a 64-bit Windows 2008 R2 SP1 server. When simply right-clicking on SETUP.EXE in the root and selecting Run as Administrator, seemingly nothing happens. When I run it from a Command Prompt (Run as Administrator), I get this:

An error occurred during the SQL Server 2012 Setup operation.

Error result: -2067529723 Result facility code: 1220 Result error code: 5

For more information, review SQL Server 2012 Setup logs in your temp folder.

No log files were written anywhere. How can I find out what this error is trying to tell me and what I can do to resolve it?

Improve this question
7
  • 1
    Just for clarification, that error number is 0x84C40005 in hex. Typically, the hex number is mentioned in Microsoft documentation. In fact, there is a document about this problem with SQL 2008 here: social.msdn.microsoft.com/Forums/en-US/sqlexpress/thread/… I don't know if that is the same issue.
    – Hannah Vernon ♦
    Dec 10, 2012 at 21:27
  • I'd suggest you may need to re-download the setup package as a first try.
    – Hannah Vernon ♦
    Dec 10, 2012 at 21:27
  • Max, I did download the the ISO a second time. I doubt that it is corruption in the ISO or I would have had trouble extracting it.
    – Mark Freeman
    Dec 11, 2012 at 14:45
  • The Setup dies before creating and files or folders within either the Program Files or Program Files (x86) folder trees. The machine already has instances of 2005 and 2008 R2 installed on it (it is a development server), so I know that any prerequisites for those versions have already been met and I am unaware of any new ones for 2012.
    – Mark Freeman
    Dec 11, 2012 at 14:54
  • I did find this "The installation of SQL Server 2012 fails if you launch the setup through Terminal Services Client. Launching SQL Server Setup through Terminal Services Client is not supported." The server I am installing on is a VM and I can only access it using Remote Desktop. Could this be an issue?
    – Mark Freeman
    Dec 11, 2012 at 14:56

4 Answers 4

Reset to default
0

I rebooted the VM, and I was then able to get the Setup to work as expected. I am disappointed that the error message did not provide any indication of what was wrong or what needed to be done to correct the situation, but rebooting seems to have resolved whatever the issue was.

Improve this answer
0

I had the same error message as yours. I found out that my environment variable temp was pointing to an existing file, when it should be a directory.

After renaming the original file and creating a directory instead, the installation proceeded.

Improve this answer
0

In my case, I received this error while using a configuration file that was totally unusable.

I inherited it and (wrongly) assumed it was in working order. Instead, it had a bunch of non-valid parameters and instead of using ; for comments, it used #. The logs gave this error without any useful information.

So checking your configuration file's validity with the documentation might be a step worth looking at when seeing this error.

Improve this answer
-2

I was facing exactly same error with error code Error result: -2068643839. It was occurring when I was trying to install SQL Server 2017 Enterprise Edition with mounting ISO file on my Windows 10 machine. I googled and found some other issues getting resolved when installing by extracting ISO file instead of installing it by mounting the ISO. The error went away.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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