Skip to main content

Installing SQL Server 2000 Server Components in Windows XP Media Center

Check out my previous experience on installing SQL Server Enterprise and Developer Edition in a Windows XP Media Center box.

The error which i was getting all this while is "Microsoft SQL Server 2000 Enterprise Edition Server Component is not supported on this operating system. Only client components will be available for installation." and "Microsoft SQL Server 2000 Developer Edition Server Component is not supported on this operating system. Only client components will be available for installation."

Later I have downloaded SQL Server 2005 Express edition and after some initial struggle I have installed it.

Today I was again thinking why am I not able to install the DEV version as it is supposed to be installed on Windows XP professional itself. So I reinitiated the installation process and the results were surprising to me.

First I wanted to install MSDE and then try SQL 2000 DEV version.

Installing MSDE:

Step 1: I downloaded MSDE 2000 from Microsoft and ran the installation file (MSDE2000A.exe)

Step 2: Went to command prompt (Start >> cmd)

Step 3: Ran the setup file. Though there are various parameter switches which can be used along with this setup file, I used the bare minimum options only.

Setup.exe InstanceName=db2000MSDE SAPWD=velias SecurityModel=SQL

Here, InstanceName == name of the MSDE instance, SAPWD == password of the SA account and SecurityMode == SQL (Mixed mode).

Check out this to know all available parameters. Btw, MSDE doesn’t have any user interface and it is designed to work as a background service.

Step 4: Navigate to Adminstrative tools >> Services and we could now find MSSQL$YourInstanceName there.

Installing SQL Server 2000:

After installing MSDE now I tried installing SQL Server 2000 Enterprise Editio. But it wasn’t successful (Only client tools were getting installed).

Next I tried my luck with SQL Server 2000 Developer edition and to my surprise this time it got installed. I am really surprised because previously I was also trying the same thing but I didn’t have MSDE then. So is MSDE necessary for installing Developer edition of SQL Server 2000 in Windows XP Media Center? Still I don’t think so!!

Just for my better understanding I uninstalled SQL 2000 DEV edition and MSDE from my box. Then without installing MSDE I directly installed SQL Server 2000 Developer Edition and it installed without any issues at all. I am confused :) Have anyone of you guys come across this issue?

Technorati Tags: , ,

Comments

Anonymous said…
am facing a similar problem.
4:11 AM, October 25, 2006
Anonymous said…
Even I have the same issue. When i installed SQL Server 2K edition on xp - it went fine, but now i get an error saying "set up couldnot configure Server on the machines. Set up would abort!"" Kindly suggest!! Pls reply to sharma.amitkumar@yahoo.com
11:44 AM, January 30, 2007
Post a Comment

Popular posts from this blog

[Non Tech] Want to know the recipe for Omelette :)

Fed up with Bread - Jam and Curd Rice, today i wanted to eat Omelette. Interesting part is I wanted to cook it myself :) So in the first picture you see all the items which are needed for preparing an Omelette. When I had a closer look at the eggs I see that almost all the eggs are broken. But believe me when I bought it couple of days back it was in perfect condition! I was wondering whether the eggs have become rotten or pretty old to consume! I tried taking an egg and break it but couldn't break it at all :) Since I have kept in the freezer all the eggs have frozen and looked like a iron ball :) After trying for few minutes of trying i removed the shell of the egg and then kept that iron ball :) into a bowl and placed it within Oven. I heated it for 1 minute and checked. It melted only to a limit. So i just set it for another 2 minutes and checked it later. It has melted but the part of the egg white has become a Omelette :( I didn't leave it there. I took the bowl out of ...
8 comments
Read more

AWS fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request

While using AWS and trying to copy a file from a S3 bucket to my EC2 instance ended up with this error message. Command Used: aws s3 cp s3://mybucketname/myfilename.html /var/www/html/ Error: fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request The error goes off if we add the region information to the command statement. I am using Asia Pacific (Mumbai) so used ap-south-1 as the region name. Modified Command: aws s3 cp s3://mybucketname/myfilename.html /var/www/html/ --region ap-south-1
Post a Comment
Read more

Script table as - ALTER TO is greyed out - SQL SERVER

One of my office colleague recently asked me why we are not able to generate ALTER Table script from SSMS. If we right click on the table and choose "Script Table As"  ALTER To option would be disabled or Greyed out. Is it a bug? No it isn't a bug. ALTER To is there to be used for generating modified script of Stored Procedure, Functions, Views, Triggers etc., and NOT for Tables. For generating ALTER Table script there is an work around. Right click on the table, choose "Modify" and enter into the design mode. Make what ever changes you want to make and WITHOUT saving it right click anywhere on the top half of the window (above Column properties) and choose "Generate Change Script". Please be advised that SQL Server would drop actually create a new table with modifications, move the data from the old table into it and then drop the old table. Sounds simple but assume you have a very large table for which you want to do this! Then it woul...
2 comments
Read more