Home Dashboard Directory Help
Search

Mr by henritzo


Status: 

Closed
 as Fixed Help for as Fixed


1
0
Sign in
to vote
Type: Bug
ID: 682474
Opened: 8/1/2011 12:11:44 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

This is the log file on installation.
Could not install SQL server 2006 Express edition service park 1 (X86)

Details
Sign in to post a comment.
Posted by Microsoft on 8/10/2011 at 10:33 AM
NOTE - the SQL Express 32bit (x86) version is available at:
http://go.microsoft.com/fwlink/?LinkId=153228

thanks
Posted by Microsoft on 8/10/2011 at 10:30 AM
Hello
It is not clear if you already have SQL installed on this machine.
If you do not have SQL already installed on the machine, you can try one (or both) of the following:

1. Just retry the Lightswitch setup and see if it can successfully install it on the second attempt

or
2. Try installing SQLExpress manually. First you need to bring down the appropriate version of SQLExpress for you machine. if you are a 64bit machine, please download and save locally the SQLExpress setup sources from http://go.microsoft.com/fwlink/?LinkId=153229. Then install it SQL Express by running the sql setup and following these settings:
Once the SQL Setup wizard is up...The top link that will show up in the right panel is "New installation or add features...". Click this link. Start pushing through the sql setup wizard. When you get to the wizard page called "Instance Configuration" , be sure to select "Named Instance" and in the text box enter "SQLEXPRESS" if it is not already there. Continue with wizard until you get to the "Server Configuration" page- Here make sure you enter "NT AUTHORITY\Network Service" for the "Account Name" for both services that need to be filled in. Now continue to “Database Engine Configuration” and in the “Specify SQL Server Administrator”please select “Add Current User”. I think at this point you can continue pushing through the SQL setup wizard and install. Hopefully now you can install Lightswitch and it should by-pass the SQL part.

thanks
Robert Schoen


Sign in to post a workaround.