Sorry, it didn't work. The Shared Memory protocol was enabled.
I found out that the installation seems to be confused about where to find stuff by starting the service from the command prompt before clicking cancel on the install where it wants to start the installation rollback.
The error message from sqlservr.exe contains:
2005-04-20 21:02:00.73 spid4s Error: 17207, Severity: 16, State: 1. 2005-04-20 21:02:00.73 spid4s FCB:pen: Operating system error 2(Det gar i nte att hitta filen.) occurred while creating or opening file 'D:\Program Files\ Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf'. Diagnose and c orrect the operating system error, and retry the operation. 2005-04-20 21:02:00.76 spid4s Error: 17204, Severity: 16, State: 1. 2005-04-20 21:02:00.76 spid4s FCB:pen failed: Could not open file D:\Prog ram Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf for fi le number 1. OS error: 2(Det gar inte att hitta filen.).
My system doesn't have and folder named D:\Program Files, the D: unit is the DVD...
I have searched the folder structure of the unpacked installation files in SQLExpress temporary directory for any reference to this D: thing without success...
That sounds quite reasonable. When running the installation on it's own from the WCU\SSE folder on the DVD it seemed to stop and rolled back when trying to connect to the instance.
I had the same problem installing VS Beta 2 on a new machine, where only Windows XP and Office was installed.
Finally, I managed to install SSE by starting the setup in vs\wcu\SSE. The standard setup fails with the same error. However, after I checked the "advanced options" in the page where you enter your name and company and changed the account for SSE to local machine and the login mode to mixed mode, SSE installed without any problems. I do not know if both changes are necessary.
I am also having this problem. I tried starting the service manually but I receive the following error:
2005-05-03 10:59:53.71 spid4s FCB:pen: Operating system error 21(The device is not ready.) occurred while creating or opening file 'D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf'. Diagnose and correct the operating system error, and retry the operation.
My D: drive is a cd drive that had nothing to do with the installation or setup. I cannot find a registry setting to fix this path error.
I am also getting error 1603. I do not have Yukon installed, but do have SQL 2000 and a named instance of SQL 2000 DE from MS Small Biz Acctg Beta. I can no longer connect to DDBs fromwithin SQL 2000 EM. I can however connect to my DBs from within the VS2003 Server Explorer.
We've seen several different SQL Server Express failures.
1. Do you have an existing CTP or Beta 1 drop on your machine If you do, please remove those first before installing SQL or VS. 2. Try to install SQL Express by itself from the \wcu\SSE folder using the following command line parameters:
I'm not sure if it's the same bug you had, but I ran into a problem installing SSE with an error saying that the setup could not connect to the instance. I was able to find a solution though:
Make sure you install the Client Tools only first, and then in the Configuration Manager, under SQL Native Client Configuration -> Client Protocols, make sure that the Shared Memory protocol is enabled. On my system, it seemed to be disabled by default and the SSE Setup could not connect to the instance to do its configuration. Enabling Shared Memory on the client config and then running the full setup again made things work for me.
SQL Server 2005 Express April CTP Fails from VSTS DVD
Ian Price
I found out that the installation seems to be confused about where to find stuff by starting the service from the command prompt before clicking cancel on the install where it wants to start the installation rollback.
The error message from sqlservr.exe contains:
2005-04-20 21:02:00.73 spid4s Error: 17207, Severity: 16, State: 1.
2005-04-20 21:02:00.73 spid4s FCB:
nte att hitta filen.) occurred while creating or opening file 'D:\Program Files\
Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf'. Diagnose and c
orrect the operating system error, and retry the operation.
2005-04-20 21:02:00.76 spid4s Error: 17204, Severity: 16, State: 1.
2005-04-20 21:02:00.76 spid4s FCB:
ram Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf for fi
le number 1. OS error: 2(Det gar inte att hitta filen.).
My system doesn't have and folder named D:\Program Files, the D: unit is the DVD...
I have searched the folder structure of the unpacked installation files in SQLExpress temporary directory for any reference to this D: thing without success...
/Per
xpy1999
/Per Salmi
Ean L. Towne
Risotto
I had the same problem installing VS Beta 2 on a new machine, where only Windows XP and Office was installed.
Finally, I managed to install SSE by starting the setup in vs\wcu\SSE. The standard setup fails with the same error. However, after I checked the "advanced options" in the page where you enter your name and company and changed the account for SSE to local machine and the login mode to mixed mode, SSE installed without any problems. I do not know if both changes are necessary.
Gerd
Michael Entin
2005-05-03 10:59:53.71 spid4s FCB:
My D: drive is a cd drive that had nothing to do with the installation or setup. I cannot find a registry setting to fix this path error.
Scott Simms
Richard Willis
Installation steps:
1. SQL 2005 (YUKON) CTP April 2005 WITHOUT Client Tools.
2. VS 2005 (April CTP - any Version) with SQL Express & Client Tools (default install)
3. From Settings => Add & Remove Programms - Remove the SQL Express Tools
4. Install the SQL 2005 (YUKON) CTP April 2005 Client Tools from the DVD.
It worked super here. No problems with either VS or SQL Server.
The smoothest install yet.
HTH
Alle
kail7
Any solutions so far Would be great...
markus
Michael Vu
I can't find the installer or the folder you mentioned to do a manual install.
dDude
If you change the permissions from "network .." to "local service" the install works. Mixed mode authentification is not neccessary.
Gerd
timbailey
Any ideas
Brian
Christopher Hansen
1. Do you have an existing CTP or Beta 1 drop on your machine If you do, please remove those first before installing SQL or VS.
2. Try to install SQL Express by itself from the \wcu\SSE folder using the following command line parameters:
-q /norebootchk /qn reboot=ReallySuppress addlocal=all instancename=MSSQLSERVER DISABLENETWORKPROTOCOLS=0 SCCCHECKLEVEL=IncompatibleComponents:1 SQLAUTOSTART=1 ERRORREPORTING=2 /watsongenman=SQL .mft
(this is what VS passes in when it installs SSE).
Kenshiro
Make sure you install the Client Tools only first, and then in
the Configuration Manager, under SQL Native Client Configuration -> Client
Protocols, make sure that the Shared Memory protocol is enabled. On my
system, it seemed to be disabled by default and the SSE Setup could not
connect to the instance to do its configuration. Enabling Shared Memory on
the client config and then running the full setup again made things work for
me.
--Oren
ademar
See this blog-link, there is a "removol tool", that did it for me. :-)
https://blogs.msdn.com/astebner/archive/2005/04/19/409905.aspx