Newly in place Server 2012 R2 Standard server.
Brand new install of SQL Express 2012.

When trying to start SSMS, I get the following error:

TITLE: Connect to Server

Cannot connect to servername.


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) (Microsoft SQL Server, Error: 2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476


The system cannot find the file specified

I have checked and SQL Server service is started.
TCP/IP and Named Pipes are enabled.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Éric MoreauSenior .Net ConsultantCommented:
but the error states that you are trying to connect using Named Pipes

I would check again to ensure that TCP IP is enabled everywhere you see it (Native or not, 32bits or 64)
SBSWIZARDAuthor Commented:
Verified TCP/IP is enabled everywhere.

Getting this error in event logs now:

FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1.  OS error: 3(The system cannot find the path specified.).

FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.

E:\ doesnt exist.
Éric MoreauSenior .Net ConsultantCommented:
was any databases restored/attached to that server?
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Éric MoreauSenior .Net ConsultantCommented:
and when SQL was installed, was the server attached to a E: drive?
SBSWIZARDAuthor Commented:
There was no E:\ drive ever setup on the server.

I ended up completely uninstalling, rebooting and reinstalling SQL.
Changed the login for the services to a service account and everything is working normally.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Vitor MontalvãoMSSQL Senior EngineerCommented:
Looks like you had a corrupted installation or something was changed after you got the first MSSQL instance installed.
I think you did the best thing since a clean install solved the issue.
SBSWIZARDAuthor Commented:
While other comments did help in troubleshooting, it was actions taken on our own that resolved the issue.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.