Microsoft SQL Server 2005 CTP Setup - Could not open a connection to SQL Server [2]

Hi,
Here is the error that I get during install. Does anyone have an idea how to solve this?
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

TITLE: Microsoft SQL Server 2005 CTP Setup
-

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2]. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&ProdVer=9.00.1116&EvtSrc=setup.rll&EvtID=29545&EvtType=lib%5Codbc_connection.cpp@.Do_sqlScript@.OdbcConnection::connect@.x80070002

-
BUTTONS:

&Retry
Cancel
-

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
In the log file I can see the folowing information at the bottom:

Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Thu Jun 16 08:15:46 2005
Service MSSQLSERVER with parameters '-m -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Thu Jun 16 08:15:46 2005
SQL service MSSQLSERVER started successfully waiting for SQL service to accept client connections
Service MSSQLSERVER started at Thu Jun 16 08:16:10 2005
Loaded DLL:
C:\WINDOWS\system32\Odbc32.dll
Version:
3.525.1117.0

SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=08001, level=-1, state=-1, native_error=2, msg=[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2].
sqlstate=08001, level=-1, state=-1, native_error=2, msg=[Microsoft][SQL Native Client]Client unable to establish connection
sqlstate=HYT00, level=-1, state=-1, native_error=0, msg=[Microsoft][SQL Native Client]Login timeout expired
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: lib\odbc_connection.cpp
Compiler Timestamp: Fri Mar 18 08:21:13 2005
Function Name: OdbcConnection::connect
Source Line Number: 140

- Context --

Connecting to SQL Server
ExecuteSqlCommands
Originial error was 80070002 (2)
lScript
SqlScriptHlpr

Error Code: 2
MSI (s) (DC!54) [08:16:43:920]: Product: Microsoft SQL Server 2005 CTP -- Error 29545. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2]. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
Error 29545. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2]. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Thu Jun 16 08:16:43 2005
Service MSSQLSERVER with parameters '-m -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Thu Jun 16 08:16:43 2005
Attempt to start service when it is already running
SQL service MSSQLSERVER started successfully waiting for SQL service to accept client connections
Service MSSQLSERVER started at Thu Jun 16 08:16:43 2005
Loaded DLL:
C:\WINDOWS\system32\Odbc32.dll
Version:
3.525.1117.0

SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=08001, level=-1, state=-1, native_error=2, msg=[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2].
sqlstate=08001, level=-1, state=-1, native_error=2, msg=[Microsoft][SQL Native Client]Client unable to establish connection
sqlstate=HYT00, level=-1, state=-1, native_error=0, msg=[Microsoft][SQL Native Client]Login timeout expired
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: lib\odbc_connection.cpp
Compiler Timestamp: Fri Mar 18 08:21:13 2005
Function Name: OdbcConnection::connect
Source Line Number: 140

- Context --

Connecting to SQL Server
ExecuteSqlCommands
Originial error was 80070002 (2)
Do_sqlScript
SqlScriptHlpr

Error Code: 2

Probably better to ask this in the Setup/Upgrade group...

However, do you have SQL 2000 installed? If so are named pipes enabled in cli config? If not enable them and re-run setup.

-Euan|||Hey Edwin.

I just had this very same problem.

The way that I got around it was to run the SQL server install, and when it came up with this error I went into my services MMC snapin and restarted the SQL Server (MSSQLSERVER) service.

Then I pressed retry in the install window and it worked.

See if that helps

Cheers
Beric Holt
e-Media Ltd
Dunedin
New Zealand|||Hi Beric

work around suggested by you worked for me as well.thanks.|||

I had the similar issues, and this has been resolved by running command Setup\sqlncli.msi REINSTALL=ALL REINSTALLMODE=omus /qb.
More informations is available on link :http://download.microsoft.com/download/E/1/1/E1196B19-DE92-4AB2-BAFD-5B5AD26E67B4/AprilCTPNotes.mht
Thanks!

Microsoft Reporting Services

Folks --
Does anyone have any idea as to where I would go to find
help on getting the beta of Reporting Services up and
running?
Thanks
Pete HohenhausTry this page first
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sql/next/rsdepgd.asp
And this is a chat link on RS
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itcommunity/chats/trans/sql/sql0625.asp
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"peteh@.180solutions.com" <anonymous@.discussions.microsoft.com> wrote in
message news:022701c3ac94$c4808480$a301280a@.phx.gbl...
> Folks --
> Does anyone have any idea as to where I would go to find
> help on getting the beta of Reporting Services up and
> running?
> Thanks
> Pete Hohenhaus|||Hey, Ray, thanks, man!
>--Original Message--
>Try this page first
>http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/sql/next/rsdepgd.asp
>And this is a chat link on RS
>http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/itcommunity/chats/trans/sql/sql0625.asp
>HTH
>--
>Ray Higdon MCSE, MCDBA, CCNA
>--
>"peteh@.180solutions.com"
<anonymous@.discussions.microsoft.com> wrote in
>message news:022701c3ac94$c4808480$a301280a@.phx.gbl...
>> Folks --
>> Does anyone have any idea as to where I would go to
find
>> help on getting the beta of Reporting Services up and
>> running?
>> Thanks
>> Pete Hohenhaus
>
>.
>

Microsoft OLE DB Provider for SQL Server error '80004005' on Load Balancing

I have posted this also in one forum. Somebody might have idea here.

We have four Windows 2003 advance servers with SP 3 configured on NLB.
Each of them has one NIC.
Recently we started to get frequent time-out error messages from web applications on those servers when they try to establish the connection with the SQL 2005. If you run web pages application to connect to sql server 10 times, 9 times you will get good connection results and 1 time you will get time-out.

Microsoft OLE DB Provider for SQL Server error '80004005'
Timeout expired
/common/mypage.asp, line 20

Connection to sql server is established with the connection string. Any idea how to solve this problem? Is there a connectionproblem? from NLB to Web to SQL?

We have tried doing some suggestions (e.g. LMHOST, IP, domain account for WEb to SQL connection, the Query Wait in SQL advance property.), but seems this timeout expired still exist

Thanks in advance...

We thought it was only in IIS and Firewall pooling connections. There were open connection threads on IIS, where in fact the firewall already disconnect it. When a new request from IIS is set, sometimes it uses the aged out connections. This was one of the cause. What we did is modify the timeout connection from firewall 1 minute more than the IIS timeout expiration. Though we still encounter timeout expired once in a while. Any idea?

|||

Another thing that might help to analyze this issue:

I tried to check the Profiler for the timeout expiration. On the Profiler, SQL grants login (AuditLogin) but kicked it out right away (AuditLogut) for that specific timeout connection. No duration cost.

Microsoft OLE DB Provider for SQL Server error ''80004005'' on Load Balancing

I have posted this also in one forum. Somebody might have idea here.

We have four Windows 2003 advance servers with SP 3 configured on NLB.
Each of them has one NIC.
Recently we started to get frequent time-out error messages from web applications on those servers when they try to establish the connection with the SQL 2005. If you run web pages application to connect to sql server 10 times, 9 times you will get good connection results and 1 time you will get time-out.

Microsoft OLE DB Provider for SQL Server error '80004005'
Timeout expired
/common/mypage.asp, line 20

Connection to sql server is established with the connection string. Any idea how to solve this problem? Is there a connectionproblem? from NLB to Web to SQL?

We have tried doing some suggestions (e.g. LMHOST, IP, domain account for WEb to SQL connection, the Query Wait in SQL advance property.), but seems this timeout expired still exist

Thanks in advance...

We thought it was only in IIS and Firewall pooling connections. There were open connection threads on IIS, where in fact the firewall already disconnect it. When a new request from IIS is set, sometimes it uses the aged out connections. This was one of the cause. What we did is modify the timeout connection from firewall 1 minute more than the IIS timeout expiration. Though we still encounter timeout expired once in a while. Any idea?

|||

Another thing that might help to analyze this issue:

I tried to check the Profiler for the timeout expiration. On the Profiler, SQL grants login (AuditLogin) but kicked it out right away (AuditLogut) for that specific timeout connection. No duration cost.

sql

microflop

idea for sql virus scannerFrom the performance point of view Anti virus programs are liable, but still
you can deploy them and excude the database folders to skip while the scann
er is running.
Ensure you've plenty of machine resources memory in order to perform this ac
tion, AV are resource hungry and if you're running OLTP application then per
formance will be dented at times.
http://vyaskn.tripod.com/sql_server...t_practices.htm for tips and
practices.
HTH
--
--
Satya SKJ
"milli" wrote:

> idea for sql virus scanner
>