Vista - SQL installation:"Login failed for user 'sa'"

I want to install SQL express edition on a laptop with vista home basic, but
I faced a lot of problems.I have this error:

SQL Setup could not connect to the database service for server
configuration. The error was:[Microsoft][SQL Native client][SQL Server] Login
failed for user 'sa'.refer to server error logs ans setup logs for more
information.

I went to Microsoft 'help and support center'. I found a page that describes
my problem. it is available at 'bug#431174'. It said that I must delete some
specific temporary files and goto SQL configuration Manager and start the SQL
Server services. I delete those files, but I couldn't start the "MSSQLSERVER"
in SQL configuration Manager. I tried to do that. It was going to be started,
but in the middle of the progress, it stopped. I do it several times, but it
did not start. I think the main problem that I can't install SQL Server is: I
can't make the MSSQLSERVER start.what can I do?Please help me!

When you run the sql icon, do you right click on it and say "Run as
Administrator" ?


"F.N.Z" <FNZ@xxxxxx> wrote in message
news:705750BC-74BF-4326-9309-BB3783420BEF@xxxxxx

I am not too familiar with SQL 2005 and Vista but if you are
logged in as an administrator you can use the OSQL utility from the
command prompt to access the database. From there you can reset the
'sa' password.

i.e.
1) Select: Start > Run and type in the word COMMAND and click on OK.
2) At the prompt type osql -E and press Enter.
3) Type sp_password 'oldpassword','newpassword',sa and press Enter at
the "1>" prompt.
4) Type go and press Enter at the "2>" prompt.
5) You should receive the message Password changed.
6) The "1>" prompt should return. Type in exit and press Enter.
7) Type in exit and press Enter again.

If you don't know the 'oldpassword' you can try the line: sp_password
NULL, NULL, sa ...BUT, I am not sure if SQL 2005 will let you set the
'sa' password to NULL.

On Apr 30, 4:40*pm, Blue Streak <rdlebre...@xxxxxx> wrote:Oh, crap! Please disregard this post. It *assumes* the SQL server is
running.