Cannot connect to sql instance after ugrading from 2008 express to 2008 full

Hi,

We have been using a sql 2008 express edition connecting through management studio using webufcw\sqlexpress with windows auth.

This morning I used the upgrade advisor to upgrade from express to enterprise and now i get the following error when trying to connect using management studio
"A network-related or instance-specific error occured 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 connect to sql server)"

I made sure tcp-ip and name pipes were enabled for the instance after the upgrade and i also tried turning off windows firewall and still can't connect

thanks in advance
 
UFCWITAsked:
Who is Participating?
 
UFCWITAuthor Commented:
I think i might have got it, I disabled the via in the protocols after reading a help article about it and i am able to connect now
0
 
UFCWITAuthor Commented:
p.s. - I am running windows server 2008
0
 
jlanderson1Commented:
Did you verify all services are running?  Specifically, the SQL Browser?
Also, did you specify a service account for the SQL Services?
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

 
UFCWITAuthor Commented:
the sql server (sqlexpress) is not running. When i try to start it it comes up with the following error message

"the request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details"
0
 
UFCWITAuthor Commented:
the error it shows in event viewer when trying to start service is
"SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems."
0
 
jlanderson1Commented:
That's good news.  You solved it yourself!
0
 
shalabhsharmaCommented:
Start the MSSQL Service  under the Local service account .
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.