fresh install of SQL Server 2008 and 'Cannot connect to (local)'

Question

fresh install of SQL Server 2008 and 'Cannot connect to (local)'

KoldCoffee

SSCoach

Points: 18971
More actions
November 14, 2012 at 2:01 pm

#284836

I believe the root of this problem is that SQL Server Agent isn't running. It is currently stopped. How does one get SQL Server Agent started?
Background:
I've successfully installed a express version of SSMS 2008 Express (trial) and when firing up studio I get 'Cannot connect to (local). the network related or instance specific error occurred while establishing a connection to SQL Server,. The server was not found or was not accessible'.
Troubleshooting so far:
Went to configuration manager and found SQL Server Agent 'Stopped'. Right clicked to start it up but 'Start' was not active/clickable. The user for Agent is the built in account 'Network Service'. We've tried all the other accounts including 'This account' (used administrator name and password) and keep getting 'can't be started either because it is disabled or has no enabled devices associated with it' error.
Please advise.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Dan.Humphries SSChampion Points: 12125 More actions · Answer 1

There are many posts on the internet that go into detail on trouble starting SQL server agent on express addition but I will say that this would in no way cause your connection problem. SQL server agent has no part in the login process and would not prevent a connection to the server. I would look at your autentication mode did you set it up with SQL authentication or mixed mode. did you give the server an SA password and can you connect using that?

Dan

If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.

lptech Hall of Fame Points: 3208 More actions · Answer 2

The agent will never start on Express Edition. Unfortuantely, the status in Configuration Manager is misleading. Look at this link for more details:

http://msdn.microsoft.com/en-us/library/cc645993(v=sql.100).aspx

KoldCoffee SSCoach Points: 18971 More actions · Answer 3

KoldCoffee

SSCoach

Points: 18971

November 14, 2012 at 2:24 pm

#1559125

Thanks Iptech!

KoldCoffee SSCoach Points: 18971 More actions · Answer 4

Hey guys, so I take it that SQL Agent doesn't run in Express and that is not the root cause of the problem. (Thanks for link IpTech). That led me to Pinal Dave's website which advises to check that TCP/IP protocol is enabled and for right port.

BUT

I'm not on a remote computer. I downloaded SQL Server to a standalone and am trying to access from the standalone. Any further direction would really be appreciated.

Can't connect to local.:-(

Lowell SSC Guru Points: 323518 More actions · Answer 5

also, an express edition usually installs a named instance (.\SQLEXPRESS for example) and not a default instance that will answer to (local)

look in Control Panel/Administrative Tools>>Services and see if it's named or not:

also make sure the service is started.

MSSQLSERVER is a default isntance, any otrher name is a named isntance, so you need machienname\InstnaceName, like DEV223\SQLEXPRESS for example.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

KoldCoffee SSCoach Points: 18971 More actions · Answer 6

I didn't select default instance during install. I thought it would default to default during the install, but no, named is the default. I selected default during install.

Phew.problem solved.

THANKS