I have Windows 7 running on my machine (I know it's old) and when I try to install SQL Server 2017 using the setup utility, I get this error:
The operating system on this computer does not meet the min requirements for SQL Server 2017. To determine the min required OS supported for this SQL server release, see the hardware and software requirements.
This is the link provided: Hardware and Software Requirements for Installing SQL Server
I don't see anything there that stands out that my machine does not have. I know people have installed SQL Server 2017 on Windows 7 boxes, so that can't be the issue.
I tried changing the compatibility mode by right clicking the setup file and properties too, to Windows 7 but I still can't get passed that error message.
I think at the link you provided Windows 7 is actually not in the list of OS supported? Here it's also mentioned SQl Server 2017 can only be installed on Windows 8 or Windows Server 2012 and later versions.
Related
In our company we have to support a large legacy system built on Microsoft Access 2010 as frontend and SQL Server 2008 R2 as backend. The backend SQL server runs on Windows Server 2008 R2. Currently our users works on Terminal Server sessions on a Windows Server 2008 R2. A couple of days ago we started to test Windows Server 2019 and Notebooks with the latest version of Windows 10. We recognized a big performance difference while executing the same Access databases on the different environments.
For instance the creation of a report takes 27 seconds (new environment) instead of 7 seconds (old environment). The database.accdb is identical, the backend is identical (still Windows 2008 R2 Server with SQL Server 2008 R2 and SP2), only the execution environment (Windows) changed.
Does anyone of you have an idea how to explain this?
In Access 2010 the SQL server tables are linked using System-DSN data sources. On the old environment ODBC is used (Driver: SQL Server, Version: 6.01.7601.17514).
On the new environment I tested the following drivers:
ODBC Driver 11 for SQL Server (2014.120.5543.11)
ODBC Driver 17 for SQL Server (2017.173.01.01)
SQL Server (10.00.17763.01)
SQL Server Native Client 10.0 (2009.100.4000.00)
SQL Server Native Client 11.0 (2011.110.5058.00)
I created a new System-DSN using the different drivers and updated the linked tables in Access. But in any case the performance is still bad. I also tested the latest version of Access which comes with Office 2019, but again it is slow.
Sounds like your terminal sessions are getting throttled. Despite the fact that you have a SQL Server back end, Access is still doing a fair bit of thunking with the result sets, so any resource throttling differences between your Server 2008 and Server 2019 policies could be choking Access in the new server.
I think your answer is going to be found in Windows System Resource Manager. The page says it's not being maintained, but following the "Recommended Version" link leads to a generic Server 2019 page. Here's another article about how WSRM might be throttling sessions: Using WSRM to control RDS Dynamic Fair Share Scheduling.
Compare the Weighted_Remote_Sessions policy in 2008 and 2019 servers. There's either been a change to the default settings or behavior or the 2008 server policy was modified in the past to get to the current performance level.
Ok, a number of things to check.
First thing to check:
Launch the ODBC manager and check if SQL log tracing is on. I don’t know why, but I see sql logging turned on.
You NEED to be 100% sure it is turned off.
You MUST launch the ODBC manager from the command line or start menu, since the one in the control panel is for the x64 bit version, and you are using Access x32 (I assume).
So launch this version:
c:\Windows\SysWOW64\odbcad32.exe
So VERY important to launch the x32. It is assumed you are using a FILE dsn. So check these two settings:
(Make sure they are un-checked).
Next up?
Link access using the IP address of the sql server.
So, place of say:
myServer\SQLEXPRESS
Use:
10.50.10.101\SQLEXPRESS
(Of course use the IP address of sql server, not the above “example” IP).
The above things are quite easy to check.
Still no performance fix?
Then disable the fire wall on your new Terminal server (I seen this REALLY cause havoc).
And, disable windows defender on the new TS server if running.
The above tips should fix your issues.
If above don’t work, then next would be to check the priority settings for the TS server (GUI over server).
However, I am betting the above checks should restore your performance.
I tried Installing Microsoft SQL Server 2008 at first, Its installation was going smoothly until I closed my computer to attend to an occasion. Before I tried installing it for a second time, I compressed my C drive(C:) so as to create more storage space. On Installing it again, It couldn't install as a dialog box displayed showing that my attributes doesn't match.
I uncompressed my C: drive and tried installing it again yet it couldn't install. Finally I tried for the last time just to see the image below.
What do I do? My computer is a 32bit OS. and window 7 Ultimate.
You should take a look at the Hardware and Software Requirements for Installing SQL Server 2008, some conditions are:
SQL Server Setup will block installations on read-only or compressed drives.
For minimum version requirements to install SQL Server 2008 on Windows Server 2012 or Windows 8, see Installing SQL Server on Windows Server 2012 or Windows 8 (http://support.microsoft.com/kb/2681562).
So please read it carefully, you can found it in the MSDN here
In my office there is one machine running Windows 7 32BIT Professional and SQL Server Express 2008 along with others software are installed. But the problem is in certain course of time Windows gets automatically deactivated and SQL server gets uninstalled, while other microsoft products are performing well. I have already reactivated the windows and installed SQL server on that machine atleast 3 - 4 times, but problem still persist. Please help in this regard.
regards,
Snehashis Ghosh
I've developed an application that uses SQL Server (in particular LocalDB), and, I have just pushed it out to the client.
The client runs Windows 8.1 x64, but, when I try to install either x86 or x64 version of SQL LocalDB direct from Microsoft, I keep getting this error:
Microsoft SQL Server 2014 Express LocalDB
Installation of this product failed because it is not supported on this operating system. For information on supported configurations, see the product documentation.
I'm a little bit stuck here, and, quite confused as I am using LocalDB on my Windows 8.1 dev machine.
How can I resolve this?
Please right click the LocalDB setup file and check if it is configured with other compatibility mode. And make sure that you choose “Run as Administrator” to start the installation. There is also a similar thread for your reference, which may require you to reinstall the Windows to resolve the OS error.
SQL Server 2014 Express why not support Windows 8.1 Pro
I wanna install SQL Server 2012 Enterprise edition but I have an issue during the installation.
I'm working on a Win 7 OS, i5, x64, sp1.
I tried to install it on my laptop and it doesn't work. After installing rules this error comes up:
SQL server setup has encoutered the following error: There was a
failure to calculate the default value of setting INSTANCEID. Error
code 0x85640001.
Now, I don't know what I can do? =/
Help me please.
i know nothing about that specific error message but maybe it is related with the fact that win 7 is not a supported operating system for that sql server version.
you can check on ms website: the enterprise edition requires a server operating system.
SQL Server Enterprise does not support Windows 7 -
Hardware and Software Requirements for Installing SQL Server 2012