No Versions Of QuickBooks Will Install On Server 2012 R2

CLC

Well-Known Member
Reaction score
320
Location
Central Minnesota USA
No matter what version/year of QuickBooks I try to install on this server I get the message that there isnt enough memory so I followed the followed the instructions below and all I get is a flash on the screen when running the setup.exe and nothing happens. Antivirus is not blocking it. I also ran the QuickBooks Install Diagnostic Tool with no luck. I'm going to try disabling all unneeded startup items and see what happens but if anyone has a solution to this it would be greatly appreciated. This server is not on a domain either, work group mode.

  1. On your keyboard, press Windows+R to open the Run window.
  2. Type %temp% in the search field, then select OK.
  3. Locate the folder created by the setup. Create a copy of the QuickBooks folder on your Desktop. Note: The name of the folder will depend on the version of QuickBooks that you are trying to install (Pro, Premier, or Enterprise).
  4. Inside the QuickBooks folder, open QBooks.
  5. Right-click the Framework.xml file, then select Edit. The file should open in Notepad. Note: If the file is not available in the %temp% folder, run the QuickBooks installer again. When you reach the Welcome to QuickBooks screen, select Cancel. The extracted version of the installer should now appear in the temp directory.
  6. Look for MinRequirements.
    7230_05.png
  7. Change 1000MB to 0MB.
  8. From the File menu, select Save.
  9. Go back to the main installation folder and run Setup.exe.
 
Microsoft updates current?
Latest .NET Frame installed and updated (slap on full install of 4.8)
I've also seen wonky temp variables cause the extraction of the initial download file to fail..so it's failing as it tries to crack open the .EXE just to get to files such as setup.exe. Try opening with your favorite full archiver program to find setup.exe inside.
 
If I were in your shoes I’d fire up a clean Hyper-V VM copy of Server 2012 R2 and watch it install there, just to see it happen and know there’s nothing inherently wrong with that combination.
 
I've read in the past where QB sometimes misread the amount of available memory in 64 bit systems, throwing a "not enough memory" error.

It's inconceivable that such a problem would still exist today, but....
 
It's inconceivable that such a problem would still exist today, but....
Really? Microsoft only recently fixed the 255 character problem. You still can't name files things like con because of old legacy MS-DOS stuff that still exists in Windows 10. I could go on. The point is, old software can carry bugs from 25 versions ago because the companies just don't think it's worth the cost to fix them.
 
Sorry I didn't reply for a while. It doesn't matter anymore because we're putting in a new server this month, it was a long time coming. Thanks for the input!
 
Back
Top