MS SQL 2005 Express Edition - SP3

Question

Hi,

I am trying to package MS SQL 2005 Express Edition - SP3.

Before that I was performing some testing as it has various MSI inbuilt.

I first run the setup.exe and installed this with default settings. Looked fine than I uninstalled it.

Now on same machine when I try to run it with following command it fails and crash my machine.

Setup.exe /qb ADDLOCAL=ALL INSTANCENAME=SQLEXPRESS

It runs the setup for few minutes and after that when it tries to start SQL server it suddenly reboots my machine and then I fail to restart my machine.

It restart till login screen and again reboot. [:@]

It is happening again and again.

I also tried many other ways to install with setup.exe but it fails in all way.

Also, I tried to run following 4 msi:

1. SqlSupport.msi --> Installs fine
2. sqlncli.msi --> Installs fine
3. SqlWriter.msi --> Installs fine
4. SqlRun.msi - When I run this msi, it install for 1 minutes and when it tries to start SQL server it suddenly reboots my machine and then again I fail to restart my machine.

What could be missing here [&:]

Could this be due to the fact that MS SQL Server was first installed on this machine and then uninstalled. And then on this machine I am trying to run it again with silent switches and other parameters?

I will really appreciate all the comments.

Thanks

Answer

Could this be due to the fact that MS SQL Server was first installed on this machine and then uninstalledAlmost certainly. My guess is that the instance name isn't being removed. What does the verbose log - which of course you specified on the command line - tell you?

Answer

How can I remove the INSTANCENAME and when I had installed it first I had not specified any INSTANCENAME.

Answer

I used the follwoing command to uninstall :
  
 setup.exe /qb REMOVE=ALL INSTANCENAME=MSSQLSERVER
  
 or probably
  
 setup.exe /qb REMOVE=ALL
  
 What is the default INSTANCENAME? Any idea?

Answer

The INSTANCENAME property will be ignored for uninstallation, I think.
 
 http://www.lmgtfy.com/?q=sql+server+default+instancename
 
 My supposition about the INSTANCENAME property being the culprit was just that - a supposition. Anyway, IIRC, the InstanceNames are stored in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Services\SQL Server. I think the value is 'Name'. Don't quote me, though.
 
 To create a log of an install/uninstall, use the '/L' argument, e.g. /L*V %TEMP%\SQLExpress.LOG

Answer

I am creating a log file. I will look into it in detail.
  
 I would like to inform the further testing.
  
 I tested the installation on a fresh machine with only OS installed. And installation failed with same error.
  
 Really Strange...[8|]

Answer

Application try to run SQL service and then machine crash:
  
 "" Starting SQL Service: MSSQL$SQLEXPRESS""
  
 How can I attach the log file?

Answer

Hum  - is your box set to reboot upon a blue screen...  I installed SQL Express 2005 SP3 on an XP SP2 box and she blue screened...
 It wants XP SP3...
 This may be a red herring... in which case ignore my rant
 Good luck
 AB

Answer

what is red  herring?

Answer

ORIGINAL: djain3
 
 what is red  herring?

a dried and smoked herring having a reddish color [:D]
 AB  are you sure you have no fixed adobe
 so AB all your adobe apps are not working 
 
 we need more of this on appdeploy [:D]

Answer

I did further testing and finally come to the conclusion that there is problem with MS SQL Express 2005 Express edition SP3 (v9.0.4035.0)
  
 as it always crash down my machine.
  
 While MS SQL Express 2005 Express edition SP2(9.0.3042.0) installs fine
  
 Any comments?

Answer

have you found any info on google or microsoft website as to why  sql  SP3 (v9.0.4035.0) crashes

Answer

what is red  herring? http://www.lmgtfy.com/?q=english+idioms

Answer

I did further testing and finally come to the conclusion that there is problem with MS SQL Express 2005 Express edition SP3 (v9.0.4035.0) as it always crash down my machine.A sterling conclusion. A package which MS released almost a year ago is BOUND to be the problem. They'd never have got round to fixing problems between then and now, would they? And they'd leave a package known to be fundamentally broken available for download all that time, too, wouldn't they?
 
 EDIT:
 A few moments spent with the Internet's best-kept secret, a search engine called Google, highlighted a known issue where XP SP3 and SQL Server Express SP3 were installed with different languages. Search the MSDN SQL Server Express forum http://social.msdn.microsoft.com/Search/en-US/?query=SP3&rq=meta:Search.MSForums.ForumID%284dfc1132-ed0e-4490-865b-89dcc2402af9%29&rn=SQL+Server+Express+Forum

Answer

My machine is Windows XP SP2

Answer

So, not an avenue even worth exploring. Fair enough.

Answer

I am not getting the silent installation cmd for installing service pack 3 (KB955706-X86-ENU.EXE) for SQL SERVER 2005 EXPRESS EDITION.
 Please suggest, I have tried all the silent switches.

Answer

As i remember there was some problem with SP3
  
 Try SP2 with below command
  
 setup.exe /qb INSTANCENAME=SQLEXPRESS ADDLOCAL=ALL ADDUSERASADMIN=1 SQLBROWSERAUTOSTART=1 SQLAUTOSTART=1 AGTAUTOSTART=1

Answer

Extract KB955706-X86-ENU.EXE. The main exe which needs to run is hotfix.exe, which you can find after extarcting the files. 
 
 Then check for the possible command lines by using hotfix.exe /?
 
 Thanks.

Answer

We have extracted the hotfix.exe and tried all the switches which we got after clicking hotfix.exe /?
 But it the exe is not installing silently..
 
 Please suggest how to silently install this exe???

Answer

[:(]

Answer

Hello All,
  
 Does anybody already try to install MS SQL Express Edition SP3 on Windows7 ??
 There are 4 MSI files in the "SQLEXPR.EXE":
 1-sqlsupport.msi (installs fine)
 2-sqlncli_x64.msi (installs fine)
 3-sqlwriter_x64.msi (installs fine)
 4-sqlrun.msi (I have a strange message: directory can not be found)
  
 By using the setup.exe, it works fine. But I need to deploye it with a MSI format
  
 thank you for your help