June 23, 2012 at 3:09 am
I've been trying to install SQLserver 2012 express for a couple of days now - each time I receive the same error: "a network-related or instance-specific error occurred while establishing a connection to SQLServer. The server was not found or was not accessible. Verify that the instance name is correct and that the SQL Server is configured to allow remote connection...".
I am installing on a Windows 7 Ultimate, 64-bit laptop. I had tried upgrading from my SQLserver 2008 installation, but could not install 2008 R2 SP1 so decided to backup the databases and de-install 2008 (deleting all directories as well).
My first suprise is that the default instance name was not SQLEXPRESS but was SQLSERVER (I may have the exact names wrong - but you get the drift).
The install package was downloaded from the Microsoft web-site and is named SQLEXPRADV_x64_ENU.exe.
I chose all the defaults bar where the data went - placing the data root on another partition (my HDD has two partitions C & D) where I had my 2008 data.
Why is the installation looking for an SQLserver? Surely I'm installing it
What have I done wrong?
June 23, 2012 at 11:15 am
It would seem as though this error, whole it is an error, is not preventing me using the server. I've been able to restore databases and use them. Interesting.
July 15, 2012 at 9:19 am
I had a problem when I was testing my upgrade to SQL Server 2012 that cause the upgrade to fail and leave the 2008 R2 instance in an odd state. When I fixed the issue and tried to retry the upgrade it failed saying that some 2012 components were already installed (or something like that).
It's pretty easy to back out those installed components (probably just registry settings or something). While the cause of the problem may not be the same, this blog post has a possible resolution for the failed upgrade: http://www.biadmin.com/2012/05/sql-2012-upgrade-gotcha-network-backup.html
If you couldn't install 2008 R2 SP1 there might be a deeper problem. If didn't do this already, I would uninstall all the SQL Server stuff from your computer and re-install from scratch. I would also try to get Developer Edition so you have all the SQL Server features at your fingertips. You can set all the services to manual and just start what you need when you need it to save resources.
[font="Tahoma"]Bryant E. Byrd, BSSE MCDBA MCAD[/font]
Business Intelligence Administrator
MSBI Administration Blog
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply