August 31, 2013 at 11:25 am
Hi I encounter the following problem when I upgrade sqlexpress 2008 to sqlexpress 2012.
service pack 1 setup a network-related or instance-related error occurred while establishing a connection to sql server
I found a suggested solution from http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/
I've ensured that sqlexpress instance in sql server configuration manager is turned on.
I still could not resolve the issue.
any assistance is really appreciated
my os is windows 7 and rdbms is sqlexpress2012 sqlexpress
here's my upgrade log
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: The upgrade process for SQL Server failed. Use the following information to resolve the error, and then repair your installation by using this command line: setup /action=repair /instancename=SQLEXPRESS
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: The upgrade process for SQL Server failed. Use the following information to resolve the error, and then repair your installation by using this command line: setup /action=repair /instancename=SQLEXPRESS
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
thanks
August 31, 2013 at 4:27 pm
So this is a difficult situations when the server becomes unavailable during the upgrade. I would go the LOG directory for the instance and look at the ERRORLOG file to see if there is a message that indicates that SQL Server dies directly. I would also check the previous log files (ERRORLOG.1 etc) for clues.
[font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy