Как установить sql 2000 на windows 10

I know of no hacks to get SQL Server 2000 to install on an existing Windows 10 installation. There are probably forces against you from both within the setup program (which looks for certain things on the host system) and within the operating system (which prevents many flavors of older software from getting installed, mostly for security reasons but also compatibility, stability, etc). I have tried in the past and even with compatibility override options I came across the same failures every time.

A couple of ideas:

Use a virtual machine. This really is the simplest and most obvious solution. Most (if not all) editions of Windows 10 now support Hyper-V natively; if not, there is always VMWare Workstation (not free) and Oracle VirtualBox (free).
Install 2000 then upgrade. Not really practical, especially if you want to use the Windows 10 installation you already have, but if you were doing this from scratch, you could install XP/Vista/Win7, all of which should allow you to install 2000, and then upgrade. Take care, though, because some methods of upgrading to Windows 10 will relegate all of your programs and services to Windows.old, and they won’t run any more.

In either case, firewall the crap out of that thing, because the most recent security patches for 2000 are hard to find, and the ones that I found wouldn’t install anyway…

Источник

I need to install MSDE 2000 Release A on Windows 10.

The installation window pops up and then immediately closes without an error message.

This answer to this SO question seemed to solve a very similar problem and indicates that it is in fact possible to install and run MS SQL Server 2000 on Windows 10. I know that that question is about SQL Server 2000 and not MSDE, but I hope that if it works for SQL Server 2000, it will also apply to the Desktop Engine variant.

Any ideas about what could be killing the installer and/or how I could try to figure this out?

I have already tried setting the compatibility mode of the installer to WinXP SP2 and running with admin priviledges
I have not yet tried to first install Win 7, then MSDE, then upgrade to Win 10, and would very much prefer to directly install on Win 10

asked Jan 10, 2016 at 19:22

Reto HöhenerReto Höhener

5,4524 gold badges40 silver badges81 bronze badges

I have found a workaround…

I found that it was extracting several dlls to the temp folder during install and the MSI log was complaining about loading one of them. No dependency loading issues found with any of them so I tried copying them all to C:\Windows\SysWow64, but one of them (sqlunirl.dll) got access denied as it is a part of the OS. If I change the owner and permissions of that dll, I can then replace it with the extracted one, install MSDE, and afterwards replace it with the original Win10 one. However the SQL Service Manager app then refuses to start, but since exes always look for dlls in their own folder first, put that same dll in C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn. Just in case, I’ve also copied it to other folders that have executables in too. I’ve not tested this out yet but have knocked up a quick batch file to install (put it next to Setup.exe along with the sqlunirl.dll grabbed from the temp folder from a previous install attempt):

takeown /f C:\Windows\SysWOW64\sqlunirl.dll /a
icacls C:\Windows\SysWOW64\sqlunirl.dll /grant *S-1-5-32-544:f
IF NOT EXIST C:\Windows\SysWOW64\sqlunirl.bak move C:\Windows\SysWOW64\sqlunirl.dll C:\Windows\SysWOW64\sqlunirl.bak
copy /y "%~dp0sqlunirl.dll" C:\Windows\SysWOW64

"%~dp0Setup.exe" (plus your extra parameters such as SAPWD=PASSWORD)

move /y C:\Windows\SysWOW64\sqlunirl.dll "C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn"
copy /y C:\Windows\SysWOW64\sqlunirl.dll "C:\Program Files (x86)\Microsoft SQL Server\80\COM"
copy /y C:\Windows\SysWOW64\sqlunirl.dll "C:\Program Files (x86)\Microsoft SQL Server\Mssql$InstanceName\BinnMSSQL$InstanceName\Binn"
move /y C:\Windows\SysWOW64\sqlunirl.bak C:\Windows\SysWOW64\sqlunirl.dll
icacls C:\Windows\SysWOW64\sqlunirl.dll /remove *S-1-5-32-544
icacls C:\Windows\SysWOW64\sqlunirl.dll /grant *S-1-5-32-544:(GR,GE,WO)
icacls C:\Windows\SysWOW64\sqlunirl.dll /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464

(NB: SIDs are used for Administrators group and TrustedInstaller so that it works on any language. Generic Read and Generic Execute rights are the default on the administrators group, but I am also applying Write Owner so that I can set it back to TrustedInstaller as I couldn’t find a way to use TakeOwn.exe to set it back!)

answered Jan 26, 2018 at 16:18

This is sort of a reverse-answer to the question, hope it’s OK! I couldn’t find anyone else mentioning it so hopefully it’s alright. Just wanted to say that Dan’s solution also works for uninstalling MSDE 2000 from Windows 10.

I had a Win7 computer that had MSDE 2000 installed, which I upgraded to Windows 10. Everything worked fine till I needed to upgrade the software which involved uninstalling MSDE 2000. It simply wouldn’t uninstall — the msi would run then just exit.

All I had to do was rename sqlunirl.dll, run the uninstaller from add/remove programs, then rename it and change the permissions back:

takeown /f %SystemRoot%\SysWOW64\sqlunirl.dll /a
icacls %SystemRoot%\SysWOW64\sqlunirl.dll /grant *S-1-5-32-544:f
IF NOT EXIST %SystemRoot%\SysWOW64\sqlunirl.bak move %SystemRoot%\SysWOW64\sqlunirl.dll %SystemRoot%\SysWOW64\sqlunirl.bak

< RUN UNINSTALLER HERE >

move /y C:\Windows\SysWOW64\sqlunirl.bak C:\Windows\SysWOW64\sqlunirl.dll
icacls %SystemRoot%\SysWOW64\sqlunirl.dll /remove *S-1-5-32-544
icacls %SystemRoot%\SysWOW64\sqlunirl.dll /grant *S-1-5-32-544:(GR,GE,WO)
icacls %SystemRoot%\SysWOW64\sqlunirl.dll /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464

Hope that helps someone!

answered Jul 21, 2019 at 11:52

It has worked for me doing what it says @Eugene Kang, but with the following setting I add the sqlunirl.dll dll in Windows\system32 before installation.

I have used sql server 2000 sp4.

So i add one line to your script:

takeown /f %SystemRoot%\SysWOW64\sqlunirl.dll /a
icacls %SystemRoot%\SysWOW64\sqlunirl.dll /grant *S-1-5-32-544:f
copy %SystemRoot%\SysWOW64\sqlunirl.dll %SystemRoot%\system32\sqlunirl.dll
IF NOT EXIST %SystemRoot%\SysWOW64\sqlunirl.bak move %SystemRoot%\SysWOW64\sqlunirl.dll %SystemRoot%\SysWOW64\sqlunirl.bak

< RUN UNINSTALLER HERE >

move /y C:\Windows\SysWOW64\sqlunirl.bak C:\Windows\SysWOW64\sqlunirl.dll
icacls %SystemRoot%\SysWOW64\sqlunirl.dll /remove *S-1-5-32-544
icacls %SystemRoot%\SysWOW64\sqlunirl.dll /grant *S-1-5-32-544:(GR,GE,WO)
icacls %SystemRoot%\SysWOW64\sqlunirl.dll /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464

Thanks in advance,

answered Aug 28, 2020 at 8:25

Источник

Solution 1

I have found a workaround…

takeown /f C:\Windows\SysWOW64\sqlunirl.dll /a
icacls C:\Windows\SysWOW64\sqlunirl.dll /grant *S-1-5-32-544:f
IF NOT EXIST C:\Windows\SysWOW64\sqlunirl.bak move C:\Windows\SysWOW64\sqlunirl.dll C:\Windows\SysWOW64\sqlunirl.bak
copy /y "%~dp0sqlunirl.dll" C:\Windows\SysWOW64

"%~dp0Setup.exe" (plus your extra parameters such as SAPWD=PASSWORD)

move /y C:\Windows\SysWOW64\sqlunirl.dll "C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn"
copy /y C:\Windows\SysWOW64\sqlunirl.dll "C:\Program Files (x86)\Microsoft SQL Server\80\COM"
copy /y C:\Windows\SysWOW64\sqlunirl.dll "C:\Program Files (x86)\Microsoft SQL Server\Mssql$InstanceName\BinnMSSQL$InstanceName\Binn"
move /y C:\Windows\SysWOW64\sqlunirl.bak C:\Windows\SysWOW64\sqlunirl.dll
icacls C:\Windows\SysWOW64\sqlunirl.dll /remove *S-1-5-32-544
icacls C:\Windows\SysWOW64\sqlunirl.dll /grant *S-1-5-32-544:(GR,GE,WO)
icacls C:\Windows\SysWOW64\sqlunirl.dll /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464

Solution 2

All I had to do was rename sqlunirl.dll, run the uninstaller from add/remove programs, then rename it and change the permissions back:

takeown /f %SystemRoot%\SysWOW64\sqlunirl.dll /a
icacls %SystemRoot%\SysWOW64\sqlunirl.dll /grant *S-1-5-32-544:f
IF NOT EXIST %SystemRoot%\SysWOW64\sqlunirl.bak move %SystemRoot%\SysWOW64\sqlunirl.dll %SystemRoot%\SysWOW64\sqlunirl.bak

< RUN UNINSTALLER HERE >

move /y C:\Windows\SysWOW64\sqlunirl.bak C:\Windows\SysWOW64\sqlunirl.dll
icacls %SystemRoot%\SysWOW64\sqlunirl.dll /remove *S-1-5-32-544
icacls %SystemRoot%\SysWOW64\sqlunirl.dll /grant *S-1-5-32-544:(GR,GE,WO)
icacls %SystemRoot%\SysWOW64\sqlunirl.dll /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464

Hope that helps someone!

Comments

I need to install MSDE 2000 Release A on Windows 10.

The installation window pops up and then immediately closes without an error message.

This answer to this SO question seemed to solve a very similar problem and indicates that it is in fact possible to install and run MS SQL Server 2000 on Windows 10. I know that that question is about SQL Server 2000 and not MSDE, but I hope that if it works for SQL Server 2000, it will also apply to the Desktop Engine variant.

Any ideas about what could be killing the installer and/or how I could try to figure this out?
- I have already tried setting the compatibility mode of the installer to WinXP SP2 and running with admin priviledges
- I have not yet tried to first install Win 7, then MSDE, then upgrade to Win 10, and would very much prefer to directly install on Win 10
- Have you considered a virtual machine with an OS that does support that version?
Wow, thanks. Didn’t know/think about the MSI log. I don’t need MSDE anymore, but that debug avenue might be useful in the future.
I’m just going to accept your answer, even though I didn’t try it out myself.

Recents

Источник

I have to admit it, that when I first heard about this I was HIGHLY skeptical, but sure enough it actually works.

Enterprise Manager looking at the infamous PUBS database

Although I have gotten SQL Server 4.21a & 6.5 running on Windows 10 (The core from 6.0 works, but it’s pre-release COM objects for the Enterprise manager don’t like Windows 10) There were two stumbling blocks I never could get around.Â The first one turned out to be something trivial, which is SQL 4.21 would never listen on TCPIP.

Fixing SQL 4.21

It turns out that this actually was a simple fix.

17/09/21 19:40:24.00 server server name is ‘JADERABBIT’
17/09/21 19:40:24.00 server Recovering database ‘model’
17/09/21 19:40:24.00 server Recovery dbid 3 ckpt (45,26)
17/09/21 19:40:24.00 server Clearing temp db
17/09/21 19:40:24.03 kernel Using ‘SQLEVENT.DLL’ version ‘4.21.00’.
17/09/21 19:40:24.83 kernel Using ‘OPENDSNT.DLL’ version ‘4.21.09.02’.
17/09/21 19:40:24.83 kernel Using ‘NTWDBLIB.DLL’ version ‘4.21.00’.
17/09/21 19:40:24.83 ods Using ‘SSNMPNTW.DLL’ version ‘4.21.0.0’ to listen on ‘\\.\pipe\sql\query’.
17/09/21 19:40:24.83 ods Using ‘SSMSSOCN.DLL’ version ‘4.21.0.0’ to listen on ‘1433’.
17/09/21 19:40:26.04 server Recovering database ‘pubs’
17/09/21 19:40:26.06 server Recovery dbid 4 ckpt (469,25)
17/09/21 19:40:26.06 server Recovering database ‘ultimate’
17/09/21 19:40:26.06 server Recovery dbid 5 ckpt (524295,12)
17/09/21 19:40:26.06 server Recovery complete.
17/09/21 19:40:26.12 server SQL Server’s default sort order is:
17/09/21 19:40:26.12 server ‘bin_cp850’ (ID = 40)
17/09/21 19:40:26.12 server on top of default character set:
17/09/21 19:40:26.12 server ‘cp850’ (ID = 2)

The DLL for TCP/IP isÂ SSMSSOCN.DLL, and it turns out it really wants to be located in theÂ C:\Windows\SysWOW64 directory (aka the system path for libraries).Â Well that’s all great now, isn’t it?

Not really.

ODBC Hell

The ODBC drivers in Windows 10 finally made a magical cut off point that they will not talk to any old and ‘vulnerable’ SQL Servers.Â This means that the oldest version you can connect to is SQL Server 2000.Â Even SQL 7 didn’t make the cut.Â Trying to connect to a SQL 7 server, you just get:

Attempting connection
[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context

And then I saw this post, about using FreeTDS to connect to MSSQL.Â So I followed their instructions, and got nowhere fast just lots of crashing.Â Turns out theÂ bloodshed environment’s included G++ just fails 100% of the time for me, with a nice crash.Â So I pointed it to the TDM GCC install, and then had to link the DLL manually and… nothing.Â No configuration point.Â In a fit of rage, I took the exist msvc project, opened it in Visual Studio 2015, and built it, except for one issue…

odbccp32.lib(dllload.obj) : error LNK2019: unresolved external symbolÂ __vsnwprintf_sÂ referenced in function _StringCchPrintfW

Seriously, it turns out that 2015 can’t just link to ODBC, that the libc thing that gave me SDL grief is deeply entrenched all over the place.Â So in this case you need to link againstÂ legacy_stdio_definitions.lib. Fantastic.

I get my DLL, and yes, it’s a Windows 32bit ODBC driver!

FreeTDS Access failure

And yeah, lots of failure.

A red-herring was seeing this in the trace:

So I was thinking that SQL 4.21 & 6.5 are just too old to have this weird table, and as mentioned over hereÂ people would just create it, to get Access to shut up, and get on with their lives.

So, I put in some SQL

CREATE TABLE MSysConf(CREATE TABLE MSysConf(ConfigÂ Â int NOT NULL,chValueÂ char(255) NULL,nValueÂ Â int NULL,Comments char(255) NULL)
GO
INSERT INTO MSysConf(Config,nValue,Comments)VALUES(101,1,’Prevent storage of the logon ID and password in linked tables.’)
GO

And yes, it creates the table, Access get’s it’s result then obviously doesn’t like it and up and dies.Â Maybe I can burn more cycles on it later, or break down and ask.

***UPDATE As a follow up, check outÂ Loading the MS SQL 6.5 drivers on Windows 10, for enabling ODBC access on newer versions of Windows.

SQL Server 2000 (Dev) on Windows 10

And then I saw this epic thread,Â Windows 10 & My SQL Server 2000 Personal.

I managed to install following these steps:

Extract SP4
Copy ..SP4\x86\other\sqlredis.exe to ..\originalinstallpath\x86\other
(this avoid mdac insall freezing)
Create this folder structure (any place):
Microsoft SQL Server\80\Tools\Binn
Microsoft SQL Server\MSSQL\Binn
Find out sqlunirl.dll on SP4 path and copy to Binn folder above
Copy dll files on ..SP4\x86\setup to Microsoft SQL Server\MSSQL\Binn (folder above)
Copy folder structure (created on step 3) to C:\Program Files (x86)
Give full access to user logged to **Microsoft SQL Server** folder
Change install compatiblity ..\originalinstallpath\x86\setup\setupsql.exe
XP SP2
Run as administrator

**UPDATE

Newer versions of Windows 10 don’t include the old Visual C++ runtime, and the install will fail.Â Just copy the DLL’s into the syswow64 directory.

copy SP4\x86\system\msvc?71.dll \Windows\SysWOW64

This is tested on 17134.112 Version 1803 of Windows 10.

Could that really be it?Â For some reason I had a file held in theÂ Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\PendingFileRenameOperations registry key, preventing me from installing, but zapping the key & stub program, and I was able to follow the steps (I’m still not sure if you copy the dlls into the MSSQL\Binn or Tools\BInn directories, so I copied them to both!) and yes, it worked.Â I even could run the SP4 update.

And now I can use Access 2016 with this fine ancient database.

Access 2016 with SQL 2000 via ODBC

And here we are.Â As always there is no larger over reaching point to this.Â I did have to create a linked SQL login for myself to get ODBC to login properly but it’s somewhat simple, and honestly if that sounds bizarre to you, why are you even thinking about something like this?

For me, I’m interested in the DTS of all things.Â Sure the new ones are fancier, and all that jazz, but I paid good money back in the day for old MS dev tools, and being able to use them without any virtualization, aka running on bare iron is all the more appealing.

Источник

Сначала установите SQL Server 2000, как решить

1, работает Regedit

2. Проживайте каталог в последовательности в реестре:

HKEY_LOCAL_MACHINE \ System \ CurrentControlset \ Control \ Manager Session, затем найдите PendingFileerNameoperation в правильном поле

3, выберите правую кнопку -> Удалить этот элемент для переустановки SQL Server 2000

Во-вторых, обновление SQL2000 до Win10 Подскажите не находить номер 1 в динамической библиотеке ссылок SQLUNIRL.DLL.

1. Получить доверительные разрешения доверия (копировать ниже с блокнотом, сохранить, запустить, запустить)

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\*\shell\runas]

@ = «Получить доверительные разрешения»

[HKEY_CLASSES_ROOT\*\shell\runas\command]

@=»cmd.exe /c takeown /f \»%1\» && icacls \»%1\» /grant administrators:F»

«IsolatedCommand»=»cmd.exe /c takeown /f \»%1\» && icacls \»%1\» /grant administrators:F»

[HKEY_CLASSES_ROOT\Directory\shell\runas]

@ = «Получить доверительные разрешения»

«NoWorkingDirectory»=»»

[HKEY_CLASSES_ROOT\Directory\shell\runas\command]

@=»cmd.exe /c takeown /f \»%1\» /r /d y && icacls \»%1\» /grant administrators:F /t»

«IsolatedCommand»=»cmd.exe /c takeown /f \»%1\» /r /d y && icacls \»%1\» /grant administrators:F /t»

2, Щелкните правой кнопкой мыши «Доверяются разрешения» в C: \ Windows \ Syswow64, C: \ Windows \ System32, получите разрешения «Получить довериерсталлер», нажмите «Подтвердить».

3. Найдите файл SQLUNIRL.DLL в системе \ x86 \ Система в установочном диске SQL, затем щелкните правой кнопкой мыши «Получите довериемые разрешения», нажмите «Подтвердить». Затем скопируйте файл в C: \ Windows \ Sysswow64, C: \ Windows \ System32, вы можете открыть MSSQL2000. все нормально.

В-третьих, Windows позволяет пользователям гостей через графический интерфейс или командную строку CMD:

1. В каталоге WindWOS найдите файл работает CMD, запустите как администратор, введите: Net User Guest / Activ: Да, чтобы включить гостевую учетную запись

В-четвертых, SQL Server MOSIC MODE Вход:

Подключитесь к SQL Server с действительным входом в Windows. Если вы должны продолжать использовать логин SQL Server, вы можете изменить режим аутентификации безопасности на SQL Server 2000 на «SQL Server и Windows». Для этого выполните следующие действия:

Начальный менеджер предприятий.
Разверните «Microsoft SQL Servers» и расширите «SQL Server Group».
Щелкните правой кнопкой мыши сервер, который вы хотите изменить на «SQL Server и Windows» аутентификацию, а затем нажмите Свойства.
В диалоговом окне «Свойства SQL Server» щелкните вкладку «Безопасность», нажмите SQL Server и Windows, а затем нажмите ОК.
При предложении перезапустить службу SQL Server, нажмите Да.

Пять, как Win10 Home Edition открывает групповую стратегию

1. Откройте текстовый файл, скопируйте следующий код,

@echo off

pushd «%~dp0»

dir /b C:\Windows\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~3*.mum >List.txt

dir /b C:\Windows\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~3*.mum >>List.txt

for /f %%i in (‘findstr /i . List.txt 2^>nul’) do dism /online /norestart /add-package:»C:\Windows\servicing\Packages\%%i»

pause

2. Измените расширение файла из TXT в CMD, как показано ниже

win10

3, система предлагает изменять риск расширения, нажмите Да, как показано ниже

win10

4. Щелкните правой кнопкой мыши файл CMD, выберите администратор в качестве администратора, а затем перезагрузите компьютер после запуска, как показано ниже

win10