Hi Everyone,
I'm really in a desperate situation. I've tried installing Visual Web Developer including SQL Express 2005. I kept getting the error:
[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe.
I tried tinkering with the registry and that made things worse.
I even re-installed Windows! I completely nuked my hard disk, formatting it totally. After re-installing Win XP Pro and the rest of my applications, I tried again. I got the SAME ERROR as before:
[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe.
Am I the only person who's getting this error when installing SQL Express 2005?
I really need to use this software. I have projects to write and it's getting desperate. Is there someone out there who can give me a solution to this? All the Microsoft info on this error relates to connecting to an existing instance, not installing a new one.
I already have SQL 2000 installed. (MSDE + Evaluation version of SQL 2000) Could that be causing the problem? I really don't know what to do.
Ken, Please confirm that the SQL Server service is running. There are a few ways to determine this:
1) Open Task Manager, go to the Processes tab, click on Image Name to sort by name. If SQL Server is running you'll see an entery called sqlservr.exe.
2) Launch the Services manager from Control Panel -> Administrative Tools -> Services. Scroll down to find "SQL Server (<INSTANCE_NAME>)" Where <INSTANCE_NAME> will be displayed as the name of the instance you installed. If you didn't specify an instance name it will show as MSSQLSERVER or SQLEXPRESS, if you installed the Express edition.
3) From the Command Prompt type "Net Start" - this will list the currently running services. Look for "SQL Server (<INSTANCE_NAME>)"
Dan
|||Hi Dan,
Thanks for replying to my message!
Here's what I got:
1) In Task Manager I found sqlservr.exe and sqlmangr.exe.
2) In Services, I don't have anything starting with "SQL Server..." but I do have MSSQLSERVER. The only thing starting with SQL is SQLSERVERAGENT which is not running.
3) Running "net start" shows the same as option 2 - I have MSSQLSERVER running.
I don't have SQL Express running just now. I know that much. Whenever I try to install, I get the error and it rolls back, deleting the files.
What I do have is MSDE and an evaluation version of SQL 2000. They are working fine. I'm using them for my existing SQL stuff just now.
It's almost as if the SQL Expressinstaller expects something to be there that isn't. It tries to use a named pipe to connect to an instance that isn't there.|||
Ken,
Take a look at the file %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\SQLSetup*_*_SQL.log for the failed installation - you can open this up in notepad. Search for "Value 3" (this is the generic error code for Windows Installer). Surrounding this should be all of the error text for the problem. Copy and paste that into a reply. My initial guess is that the server isn't starting up - you can also look in the event log for failures associated with SQL Server. I believe the MSSQLSERVER services you see are for your SQL 2K instances and not SQL2K5 so this tells me the SQL2K5 engine is failing to start.
Dan
|||Hi Dan,
I was pretty sure there wasn't an instance of SQL 2005 running. Whenever I tried to install it I got an error message saying it failed. Then I looked through the logs and found the error messages about named pipes.
Since I had deleted the logs, I decided to be brave and try installing it again, so I could see the log files and give you the "value 3" information you asked for.
I was surprised to find that this time it installed perfectly! It asked me to reboot which I did and all seems to be well.
I've had a few teething problems with my database in VWD and DotNetNuke, though. It seemed when I added a database file in VWD, the program couldn't connect to it. I got the following error:
An attempt to attach an auto-named database for file C:\inetpub\wwwroot\DotNetNuke\App_Data\database.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.
I deleted the database and tried again, stopping and starting the service since there was an error deleting the file. (or creating the new one, I forget which)
Anyway, I've only got one hurdle now - I need to give the ASPNET account permission on the database in question and I don't know how to do it. I've seen a sqlcmd.exe command that I could maybe use from the command line.
I wondered about downloadingMicrosoft SQL Server Management Studio Express but I was hesitant because it had the dubous words "Community Technology Preview" at the end which sounds a bit like b-e-t-a to me. I just had to re-install windows because of a beta (Visual Studio 2005 Beta 2) so I don't relish the prospect of something similar again.
Is SSMSE CTP safe to use? Is that what I should use to give permission to the ASPNET account?
Thanks for the help, by the way. It's really great when someone takes the time to respond!|||I can answer a couple of my own questions here...
The two errors I had seemed to be due to the fact that I had a connection active to the database through Visual Web Developer while I was running the web application that was attempting to connect. When I chose "Detach Database" in VWD, I was able to refresh the browser and everything was rosy.
I'm still curious about SSMSE CTP and whether it's worth a shot or not, though!|||
Ken, I'm glad to hear that you're up and running! As for SSMS-EE it is a CTP which means it's pre-release software. If you read through the General Tools forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=84&SiteID=1) you'll see that some folks have experienced a few issues with it. I'll say this: SSMS-EE is largely based on the same code base as SSMS so it's pretty solid. However, there were a few modifications made which may have destabilized it in certain areas. We're fixing bugs but I don't know when the next update will come out. So I suggest you read through the forum and ask other people who've installed it what they think - that will be the best way to make an informed decision.
Don't take my hesitation as a lack of confidence in the product. I haven't installed SSMS-EE so I can't speak first hand about it and I don't want to steer you wrong.
Your three other options are: 1) use the command line tool (sqlcmd.exe) or 2) buy developer for $50 (http://www.microsoft.com/sql/howtobuy/default.mspx) or 3) Download the evaluation edition and use it for 180-days until SSMS-EE releases (http://www.microsoft.com/sql/downloads/trial-software.mspx). While I can't say for sure, I expect SSMS-EE to release some time in the next 180-days.
Cheers,
Dan
|||Ok, good stuff. I appreciate your unbiased view of the product. That's sound advice.
I think that I'll stick with sqlcmd.exe for now since I don't plan on using SQL 2005 for much yet. Once SSMS-EE releases I'll get it, though.
I would just request one final clarification, if you don't mind. What would you say is the difference between "community technology preview" and beta? I should say that I don't want a huge answer but I'm wondering if they're synonymous or if CTP is one iteration on from beta. Does it go alpha -> beta -> ctp -> release? I just want to be able to have a realistic expectation of the reliability of things I'm going to install in the future based on the suffix :) Just a rough idea would be great.
Have a relaxing Christmas and happy New Year, by the way!
next time if you have this kind of a issue please refer setup bootstrap|||