Problem installing SQL Server Express 2008 Advanced

Question

Every time I try to install this I get a Restart computer failed.  I have restarted multiple times, including cold boots, and the same thing happens.  It happens when I try to upgrade from 2005 or a new stand-alone installation.

 

I'm running Vista Ultimate, up to date, and I have installed PowerShell, Framework, and Installer as per the website instructions.  I also have VS.NET 2005 installed.

 

Any help?

Answer 1

 

Hi!

Tell us the exact error message you get.

Answer 2

Its not a "message" as such.  As the setup starts, a screen is displayed with the title "Setup Support Rules", and shows a list of 6 items:

 

Minimun operating system version,

Setup administrator,

Restart computer,

Windows Management Instrumentation (WMI) Service,

Consistency validation for SQL Server registry keys, and

Long path names to files on SQL Server installation media. 

 

All indicate "Passed" except Restart computer, which indicates "Failed."  The only button that is enabled is Cancel.  And as I said, I have rebooted several times, including a cold boot.

Answer 3

 

Can't you unintall and then reinstall the software?

Answer 4

The install was never successful, so what am I going to uninstall??

Answer 5

Then try to reintall

Answer 6

Lucian, you're not paying attention.  I cannot "reinstall" because I cannot install in the first place.  The same thing happens every time I try to install.

 

Answer 7

MWulfe1 wrote:

I cannot "reinstall" because I cannot install in the first place.  The same thing happens every time I try to install.

Oh, now I understand. Can't you try to copy the intalation package another time? I know there are two versions: one for web install and one for offline install. Try both of them.

Answer 8

Lucian, I don't think you can help me.  The "internet" install is just downloading the file to a temporary folder then running it.  The file is the same if it is "downloaded" before running.  There is something else going on.

 

Answer 9

MWulfe1 wrote:

Lucian, I don't think you can help me.

Ok, I've tried.

Answer 10

The solution has come from another forum.  I had to revise a registry name to fool the computer into believing that no file deletions were pending after a reboot.

 

I must admit disappointment in this forum for not knowing about the source of this problem, especially since I was not the first one to experience it.  The problem demonstrates a bug in Windows, Windows Installer, SQL Server, or some combination of these, and has been around since at least SQL Server 2005.

 

I realize that the problem may be rare and subtle enough for MS to want to avoid a fix that might break something else, but someone here should have know about it.

 

Answer 11

MWulfe1 wrote:

The solution has come from another forum.  I had to revise a registry name to fool the computer into believing that no file deletions were pending after a reboot.   I must admit disappointment in this forum for not knowing about the source of this problem, especially since I was not the first one to experience it.  The problem demonstrates a bug in Windows, Windows Installer, SQL Server, or some combination of these, and has been around since at least SQL Server 2005.   I realize that the problem may be rare and subtle enough for MS to want to avoid a fix that might break something else, but someone here should have know about it.

If you found an answer, can't you share it with us, so we can learn and help others with this?

Answer 12

Sure -

 

I found a solution by Geoff N. Hiten, Principal SQL Infrastructure Consultant,  Microsoft SQL Server MVP, on a phwinfo.com forum.  His suggestion was to open Regedit, find the key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager", and rename the “PendingFileRenameOperations" value to "PendingFileRenameOperations2", then restart the computer and try again.

 

Every time I rebooted, the name and value of the registry key returned to its original value, which was

 

\??\C:\Windows\TEMP\logishrd\LVPrcInj03.dll

 

\??\C:\Windows\TEMP\logishrd\

 

This is apparently an illegal value since it has embedded spaces.  Eventually I successfully installed SQL Server after making the suggested registry change but without rebooting.  The only remaining problem is that this registry key is retaining its original value, and may give me problems in the future.

 

I hope this is useful to others, although I still do not know why the registry data reverts to its original value after a reboot.

Answer 13

MWulfe1 wrote:

Sure -   I found a solution by Geoff N. Hiten, Principal SQL Infrastructure Consultant,  Microsoft SQL Server MVP, on a phwinfo.com forum.  His suggestion was to open Regedit, find the key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager", and rename the “PendingFileRenameOperations" value to "PendingFileRenameOperations2", then restart the computer and try again.   Every time I rebooted, the name and value of the registry key returned to its original value, which was   \??\C:\Windows\TEMP\logishrd\LVPrcInj03.dll   \??\C:\Windows\TEMP\logishrd\   This is apparently an illegal value since it has embedded spaces.  Eventually I successfully installed SQL Server after making the suggested registry change but without rebooting.  The only remaining problem is that this registry key is retaining its original value, and may give me problems in the future.   I hope this is useful to others, although I still do not know why the registry data reverts to its original value after a reboot.

Thank you, MWulfe1!

 

Lingzhi, you should mark MWulfe1's post (the last one) as answer, to be easier for others to find it.

Answer 14

naicul said:

 

Can't you unintall and then reinstall the software?

Pardon me for griping: Why oh why do people who don't know the answer insist on making up some quick, rash, useless answer? If they don't know the answer, don't answer.

Answer 15

 

MWulfe1, are you having any problems with the registry?  I am also having problems installing SQL 2008 Express Advanced X64.   I am installing and it gets to the point where it is installing the setup support files and it flashes an error dialog box that passes too fast to read, and exits the install.   My error log is:

2009-02-21 22:35:24 Slp: Running Action: Close
2009-02-21 22:35:24 Slp: Stop Action
2009-02-21 22:35:24 Slp: Completed Action: Close, returned True
2009-02-21 22:35:24 Slp: ----------------------------------------------------------------------
2009-02-21 22:35:24 Slp: Running Action: PassPidBackFromComponentUpdate
2009-02-21 22:35:24 Slp: Pass the flag CuPidDisplayed to the main setup
2009-02-21 22:35:24 Slp: PID value specified, trying to pass the value to main setup
2009-02-21 22:35:24 Slp: Completed Action: PassPidBackFromComponentUpdate, returned True
2009-02-21 22:35:24 Slp:
2009-02-21 22:35:24 Slp:
2009-02-21 22:35:24 Slp: ----------------------------------------------------------------------
2009-02-21 22:35:24 Slp:
2009-02-21 22:35:24 Slp: Error result: -2068643839
2009-02-21 22:35:24 Slp: Result facility code: 1203
2009-02-21 22:35:24 Slp: Result error code: 1
2009-02-21 22:35:24 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2009-02-21 22:35:24 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed

Does anyone have any suggestions?

---

Max Johnson

Answer 16

Tech support just solved MWulfe1's problem for me. I deleted the pendingfilerenameoperations value and then ran the installer WITHOUT REBOOTING. As long as you don't reboot after deleting the key, and as long as it will actually LET you delete the key, the installation should work just fine. Same thing as renaming the key, in theory. Don't know anything about Max587's issue, though, sorry.

Answer 17

You are trying to install program from folder that has WAY TOO LONG a file name.

example:

C:\documen......probably 25 characters or more\....\more name\etc.

 it cannot load from such a long name (don't know why) but it needs to install from DVD 

or

put the program in a simple folder on the c:\ drive.