MS SQL Server 2005 Express Edition installation problem - Help!

During installation, I get a warning message that the hardware doesn't meet minimum requirement. But I'm running it on a laptop with 30 gigs of free space and running Windows XP home edition.

When I click on install anyway, I end up getting an error message that I need a "sqlncli.msi" file that can't be found.

Could it be because I have both 2.0 NET and 3.0 NET installed?

Thanks in advance for your help.

System Configuration Check

- WMI Service Requirement (Success)

Messages

WMI Service Requirement

Check Passed

- MSXML Requirement (Success)

Messages

MSXML Requirement

Check Passed

- Operating System Minimum Level Requirement (Success)

Messages

Operating System Minimum Level Requirement

Check Passed

- Operating System Service Pack Level Requirement. (Success)

Messages

Operating System Service Pack Level Requirement.

Check Passed

- SQL Server Edition Operating System Compatibility (Success)

Messages

SQL Server Edition Operating System Compatibility

Check Passed

- Minimum Hardware Requirement (Warning)

Messages

Minimum Hardware Requirement

The current system does not meet the recommended hardware requirements for this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.

- Pending Reboot Requirement (Success)

Messages

Pending Reboot Requirement

Check Passed

- Default Installation Path Permission Requirement (Success)

Messages

Default Installation Path Permission Requirement

Check Passed

- Internet Explorer Requirement (Success)

Messages

Internet Explorer Requirement

Check Passed

- COM Plus Catalog Requirement (Success)

Messages

COM Plus Catalog Requirement

Check Passed

- ASP.Net Version Registration Requirement (Success)

Messages

ASP.Net Version Registration Requirement

Check Passed

- Minimum MDAC Version Requirement (Success)

Messages

Minimum MDAC Version Requirement

Check Passed

- Edition Change Check (Success)

Messages

Edition Change Check

Check Passed

What Edition of SQL Server 2005 are you attempting to install?

As you can see from the chart at this reference, only Developers' Edition and SQL Server Express will install on XP Home -and only if XP Home is Service Pack 2 (SP2).

|||

Thanks for your reply.

Express, and my laptop already has SP2.

Anything else I should check for?

If not, where exactly do I find "sqlncli.msi" and how do I run that? Would that solve the issue?

Thanks again.

|||

hi,

ExpressionWeb wrote:

Thanks for your reply.

Express, and my laptop already has SP2.

already checked http://msdn2.microsoft.com/en-us/library/ms143506.aspx ?

Anything else I should check for?

If not, where exactly do I find "sqlncli.msi" and how do I run that? Would that solve the issue?

Thanks again.

http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&DisplayLang=en

regards

|||

I tried to download the sqlncli.msi file (second link), but got an error message saying that it can't be read?!?

Not really sure what to look for in the first link. In your opinion, what tends to be the usual culprit? I have a Toshiba Tecra from late 2005 and I'm running IE7.

Thanks. I've been up all night on this and am fried. I'll catch some shut eye and be back. Any additional insights/best guesses/advices would be greatly appreciated.

Thanks

|||

Please 'walk' through this checklist to gather information that may better assist us in helping you.

Configuration - Guideline for Connectivity Question Posting
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1

MS SQL 2000 Client connectivity

Hi,
We have a requirement to test connectivity of clients to
the SQL 2000 database. I am very new to this :-( ... well,
what I need to accomplish is when the database is running
all the clients should be able to connect to it also when
the SQL system goes down for some maintenance the clients
should not abort the connection but should keep on trying
to reestablish the connection. Once the SQL server comes
back online the clients must be able to reconnect to the
database with out any intervention.
My questions are,
1.) What is the client software required to accomplish
this' I also need to know if it is possible to set a
timeout period for the reconnection to the database.
2.) Does the default Client tools that come with SQL2000
support this kind of re-connection?
3.) What happens to the transaction that might be
happening when the server goes down? Can we recall/recover
these transactions?
Please help.
Thanks,
Karthik S SLoaded question....Let me see if I can answer the best I can.
Normally clients use MDAC (affectionately know as ODBC to most people) to co
nnect to SQL Server. A connection to SQL Server should not be persistent.
When an application runs and needs data from the database, it connects, gets
data, disconnects. So, if
you need to do maintenance, most people do it in the off hours, night time,
etc. This way it does not impact users during the day. If the server goes
down and there is a transaction in progress, that transaction will be rolled
back if it is not in a co
mplete state, and the application should trap the error for this. If it is
in a complete state, Begin Trans and End Trans are present for the whole tra
nsaction, when the server recovers, it will roll forward, meaning commit the
changes to the database.
MDAC is part of the client tool of SQL 2000.|||Answers inline:
1.) What is the client software required to accomplish
this' I also need to know if it is possible to set a
timeout period for the reconnection to the database.
A: You would need to write you code to trap connection failed and query
cancelled type messages and to retry after X seconds for Y number of times.
2.) Does the default Client tools that come with SQL2000
support this kind of re-connection?
A: Sort of. If you have a query up and running in Query Analyzer and the
SQL Server is shutdown, then the results window in Query Analyzer will
report an error. If you leave the window up and wait for SQL Server to
start again, you can just execute the query again and it will start over
without needing to go through the connection dialog. But it will not
automatically retry the query for you, you have to execute it again.
3.) What happens to the transaction that might be
happening when the server goes down? Can we recall/recover
these transactions?
A: If the transaction was not complete then it will be rolled back. Your
application has to be written to recognize that the transaction did not
complete and take whatever action is appropriate for your application.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.