Problems installing SQL 2005 Express after trying VS.NET 2005 Beta 2

Hi Everyone,
I recently installed Visual Studio .NET 2005 Beta 2 which included SQL 2005 Community Technology Preview. After installing it all, I was no longer able to connect to my SQL 2000 instance in Enterprise Manager. The application opened ok but whenever I tried to browse the server or register it again, it was giving me an error relating to named pipes which really confused me since I was trying to connect to a SQL 2000 database through the SQL 2000 application. I was able to use the 2005 equivalent application (the name eludes me right now) to connect to the \SQLEXPRESS instance. All this time I could still connect to the default instance through Query Analyser and my .NET Web Applications that used SQL databases.
I later had to uninstall the betas because I needed a newer version of the .NET Framework to work with DotNetNuke 4.0. (A whole other story there...)
After uninstalling everything relating to the betas (which I had to do carefully in a prescribed order) I found that I couldn't even open Enterprise Manager properly. It had a big error message in the main display window. I discovered from a forum somewhere that I had to re-register a dll file to fix it. I did this and everything was back to normal.
(pause for breath)
OK, so then I downloaded Visual Web Developer 2005 Express Edition and installed it. Everything was great until the end of the SQL Server 2005 Express Edition setup when I was told it had failed to install. I haven't looked through ALL the log files but in the summary log file, the following message is reported for all three errors:
"[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe."
I am running Windows XP, SP2 with everything up to date in Windows Update. The Beta 2 of VS.NET was the only beta software I've installed. I'm not trying to connect to a different machine or anything either. VS and SQL are both on the same machine. The only other thing that may be relevant is that the SQL 2000 I have is an evaulation version. I don't think that affects it but you never know. It's often the most overlooked variable that trips you.
Does anyone have any suggestions about how to remedy this?
Thanks for taking the time to read about my problem :)

i had the last ctp installed cleaned up the instalation and now when i try to install i get an error message:

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe

walt

|||Sounds like an existing instance is there, but the service is not running.|||Walt,

Can you reply with the error code you're getting. Also, go to Add/Remove Programs and remove SQL Server Native Client and rerun setup and see if that works.

Dan|||

walt wrote:

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe

walt

That's exactly what's happening to me. I'm afraid I don't have a solution but you're the first person I've found who's got the same experience as me. I had Visual Studio 2005 Beta 2 including the SQL CTP and after I uninstalled it all I downloaded Visual Web Developer which included the SQL 2005 Express. I got the same error about no process on the other end of the pipe. (My post on the subject.)
Hopefully one of us will get a reply!|||

error code 29515 i did the add remove

thanks

|||Update:

I solved the problem by backing up my data and re-installing windows. I now have Visual Web Developer and SQL 2005 Express running alongside Visual Studio 2003 Enterprise Developer, MSDE and SQL 2000.

I don't know if there was a simpler solution but I had spent too much time on it already. Hurrah for my new Maxtor OneTouch II external 300GB beast that carried the burden of my data during these difficult hours!|||

Well, I can add myself to your group of installation problems with the same error mesage!!!

From my SQL Server Log:

Machine : <our machine name>
Product : SQL Server Database Services
Error : SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe.
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.
--
Machine : <our machine name>

Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_MITTEN52_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}Shared Memory Provider: No process is on the other end of the pipe.
Error Number : 29515

Here's hoping someone comes up with a solution.

Problems installing SQL 2005 Express after trying VS.NET 2005 Beta 2

Hi Everyone,
I recently installed Visual Studio .NET 2005 Beta 2 which included SQL 2005 Community Technology Preview. After installing it all, I was no longer able to connect to my SQL 2000 instance in Enterprise Manager. The application opened ok but whenever I tried to browse the server or register it again, it was giving me an error relating to named pipes which really confused me since I was trying to connect to a SQL 2000 database through the SQL 2000 application. I was able to use the 2005 equivalent application (the name eludes me right now) to connect to the \SQLEXPRESS instance. All this time I could still connect to the default instance through Query Analyser and my .NET Web Applications that used SQL databases.
I later had to uninstall the betas because I needed a newer version of the .NET Framework to work with DotNetNuke 4.0. (A whole other story there...)
After uninstalling everything relating to the betas (which I had to do carefully in a prescribed order) I found that I couldn't even open Enterprise Manager properly. It had a big error message in the main display window. I discovered from a forum somewhere that I had to re-register a dll file to fix it. I did this and everything was back to normal.
(pause for breath)
OK, so then I downloaded Visual Web Developer 2005 Express Edition and installed it. Everything was great until the end of the SQL Server 2005 Express Edition setup when I was told it had failed to install. I haven't looked through ALL the log files but in the summary log file, the following message is reported for all three errors:
"[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe."
I am running Windows XP, SP2 with everything up to date in Windows Update. The Beta 2 of VS.NET was the only beta software I've installed. I'm not trying to connect to a different machine or anything either. VS and SQL are both on the same machine. The only other thing that may be relevant is that the SQL 2000 I have is an evaulation version. I don't think that affects it but you never know. It's often the most overlooked variable that trips you.
Does anyone have any suggestions about how to remedy this?
Thanks for taking the time to read about my problem :)

i had the last ctp installed cleaned up the instalation and now when i try to install i get an error message:

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe

walt

|||Sounds like an existing instance is there, but the service is not running.|||Walt,

Can you reply with the error code you're getting. Also, go to Add/Remove Programs and remove SQL Server Native Client and rerun setup and see if that works.

Dan|||

walt wrote:

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe

walt

That's exactly what's happening to me. I'm afraid I don't have a solution but you're the first person I've found who's got the same experience as me. I had Visual Studio 2005 Beta 2 including the SQL CTP and after I uninstalled it all I downloaded Visual Web Developer which included the SQL 2005 Express. I got the same error about no process on the other end of the pipe. (My post on the subject.)
Hopefully one of us will get a reply!|||

error code 29515 i did the add remove

thanks

|||Update:

I solved the problem by backing up my data and re-installing windows. I now have Visual Web Developer and SQL 2005 Express running alongside Visual Studio 2003 Enterprise Developer, MSDE and SQL 2000.

I don't know if there was a simpler solution but I had spent too much time on it already. Hurrah for my new Maxtor OneTouch II external 300GB beast that carried the burden of my data during these difficult hours!|||

Well, I can add myself to your group of installation problems with the same error mesage!!!

From my SQL Server Log:

Machine : <our machine name>
Product : SQL Server Database Services
Error : SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe.
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.
--
Machine : <our machine name>

Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_MITTEN52_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}Shared Memory Provider: No process is on the other end of the pipe.
Error Number : 29515

Here's hoping someone comes up with a solution.

Problems connecting with VS.NET Server Explorer

I have SQL Server SPK3 and Visual Studio.NET running on the same machine.
When I try to connect to my SQL Server from the VS.NET Server Explorer I can
expand the server and look at the SQL Server instance on my computer but when
I try to expand the instance, I get a login dialog entitled "SQL Server
Login" which asks for Login and Password. When I put in what I think the
Login and Password should be, it tells me, "The specified procedure could not
be found". If I check the option that says, "Use Windows NT Integrated
Security" it tells me "The specified procedure could not be found". I need
some assistance from some gurus. What's going on here?!!
I cannot help you but have a similar problem. I can add servers, but never
connect and see details. Worse yet, I cannot create a connection. I go
through the dialog and click test connection and get connection "test
connection succeeded" message. When I try to finish the task I get a message
twice saying "Unable to connect to database. The connection failed. Check
your username and password, and try again." Using either Enterprise Manager
or Query Analyzer, I can connect to the server and databases and see whatever
I need to.
I have Visual Studio 2003, I am trying to connect to both a MSDE SP3 (same
machine) and SQL Enterprise SP3 (different machine).
I am not sure when exactly this occurred as in the past I had created some
connections. I noticed it within the last couple weeks as I have gotten back
into .Net for my current project. I cannot use the old connections and once
deleted cannot recreate them as above.
"DBase_Tron" wrote:

> I have SQL Server SPK3 and Visual Studio.NET running on the same machine.
> When I try to connect to my SQL Server from the VS.NET Server Explorer I can
> expand the server and look at the SQL Server instance on my computer but when
> I try to expand the instance, I get a login dialog entitled "SQL Server
> Login" which asks for Login and Password. When I put in what I think the
> Login and Password should be, it tells me, "The specified procedure could not
> be found". If I check the option that says, "Use Windows NT Integrated
> Security" it tells me "The specified procedure could not be found". I need
> some assistance from some gurus. What's going on here?!!
|||

Quote:

Originally posted by DBase_Tron
I have SQL Server SPK3 and Visual Studio.NET running on the same machine.
When I try to connect to my SQL Server from the VS.NET Server Explorer I can
expand the server and look at the SQL Server instance on my computer but when
I try to expand the instance, I get a login dialog entitled "SQL Server
Login" which asks for Login and Password. When I put in what I think the
Login and Password should be, it tells me, "The specified procedure could not
be found". If I check the option that says, "Use Windows NT Integrated
Security" it tells me "The specified procedure could not be found". I need
some assistance from some gurus. What's going on here?!!

|||I have been searching news groups and Microsoft support sites for two days now and finally found a solution to our problem. You should download MDAC 2.8 and install. Apparently a new procedure has been included in this release. Good Luck.|||I had the same problem and what did to solve it was removing the Alias in
the SQL Server Client Network Utility, done.
Hope it helps
Javier.
"Matt Wyncoop" <Matt Wyncoop@.discussions.microsoft.com> wrote in message
news:E55058DA-AA95-48BA-930C-0726BDCAEA28@.microsoft.com...[vbcol=seagreen]
>I cannot help you but have a similar problem. I can add servers, but never
> connect and see details. Worse yet, I cannot create a connection. I go
> through the dialog and click test connection and get connection "test
> connection succeeded" message. When I try to finish the task I get a
> message
> twice saying "Unable to connect to database. The connection failed. Check
> your username and password, and try again." Using either Enterprise
> Manager
> or Query Analyzer, I can connect to the server and databases and see
> whatever
> I need to.
> I have Visual Studio 2003, I am trying to connect to both a MSDE SP3 (same
> machine) and SQL Enterprise SP3 (different machine).
> I am not sure when exactly this occurred as in the past I had created some
> connections. I noticed it within the last couple weeks as I have gotten
> back
> into .Net for my current project. I cannot use the old connections and
> once
> deleted cannot recreate them as above.
>
> "DBase_Tron" wrote:
|||I looked there and I have no aliases.
"Javier Troconis" wrote:

> I had the same problem and what did to solve it was removing the Alias in
> the SQL Server Client Network Utility, done.
> Hope it helps
> Javier.
> "Matt Wyncoop" <Matt Wyncoop@.discussions.microsoft.com> wrote in message
> news:E55058DA-AA95-48BA-930C-0726BDCAEA28@.microsoft.com...
>
>

Problem with VS.Net when using SQL Reporting Services

I'm experiencing an odd problem with Visual Studio 1.1 when
using/developing reports, etc with the SQL Reporting Services.
After I build/deploy SRS reports to my Reporting Service Visual Studio
seems to lose its ability to display intellisense and format
new/modified VB.NET code per the original tools/option settings. I
have to shut-down Visual Studio (not just the session) and start it up
again if I want to have the editting options and intellisense work (at
all). I've looked at the tools/options settings and everything appears
to be as it should be (VS simply is ignoring the edit/intellisense)
So... I'm wondering if anyone else has experienced this and/or is
there something that I can do about keeping the settings?
TIA
GlennGlenn,
I was suffer from same problem but workaround like following:
1)Remove your MS Report project from the solution1. Leave web/business logic
etc project as they are.
2)Create solution2 and put the MS Report project in. Open one more instance
of VStudio so that you can access all projects same time. (I like the
multi-instance feature of VStudio)
Anyway, I hope someone in MS can look into the issue.
Cheers.
Joe
"Glenn Owens" wrote:
> I'm experiencing an odd problem with Visual Studio 1.1 when
> using/developing reports, etc with the SQL Reporting Services.
> After I build/deploy SRS reports to my Reporting Service Visual Studio
> seems to lose its ability to display intellisense and format
> new/modified VB.NET code per the original tools/option settings. I
> have to shut-down Visual Studio (not just the session) and start it up
> again if I want to have the editting options and intellisense work (at
> all). I've looked at the tools/options settings and everything appears
> to be as it should be (VS simply is ignoring the edit/intellisense)
> So... I'm wondering if anyone else has experienced this and/or is
> there something that I can do about keeping the settings?
> TIA
> Glenn
>|||Joe, thanks for the suggestion. It confirmed my suspicion that I
needed to separate the logic projects from the report projects.
Once done everything is working again!
There are definitely some gottchas in the SRS 1.0.
Regards,
Glenn
Joe <Joe@.discussions.microsoft.com> wrote in message news:<9CFA1EEE-51A3-4A1E-9ECD-DA33664ABC0E@.microsoft.com>...
> Glenn,
> I was suffer from same problem but workaround like following:
> 1)Remove your MS Report project from the solution1. Leave web/business logic
> etc project as they are.
> 2)Create solution2 and put the MS Report project in. Open one more instance
> of VStudio so that you can access all projects same time. (I like the
> multi-instance feature of VStudio)
> Anyway, I hope someone in MS can look into the issue.
> Cheers.
> Joe
> "Glenn Owens" wrote:
> > I'm experiencing an odd problem with Visual Studio 1.1 when
> > using/developing reports, etc with the SQL Reporting Services.
> >
> > After I build/deploy SRS reports to my Reporting Service Visual Studio
> > seems to lose its ability to display intellisense and format
> > new/modified VB.NET code per the original tools/option settings. I
> > have to shut-down Visual Studio (not just the session) and start it up
> > again if I want to have the editting options and intellisense work (at
> > all). I've looked at the tools/options settings and everything appears
> > to be as it should be (VS simply is ignoring the edit/intellisense)
> >
> > So... I'm wondering if anyone else has experienced this and/or is
> > there something that I can do about keeping the settings?
> >
> > TIA
> > Glenn
> >