unable to connect with default instance

Question

Post reply

unable to connect with default instance

teertha

SSC Veteran

Points: 287
More actions
August 1, 2013 at 11:10 am

#276538

Hi,
I have installed sql server 2008r2 enterprise edition on my system.i have got the following errors such as
1) unable to connect with an instance name ..some network failure.when I repaired that software master database was not existing and database engine connection problems.
so, i uninstall and installed it properly.still iam unable to connect with default instance but i can connect through named instance and local.
Could anyone explain me the reason.when i searched on Google,someone mentioned that we don't connect through default instance.As of my knowledge i did connect through that instance before on my frnd's system.please explain me the problem.
thank you..!!!

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

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

durai nagarajan SSCoach Points: 15778 More actions · Answer 1

can you post the error which you recieved last, check in services sql default service is started or not .

Regards
Durai Nagarajan

raadee SSC Eights! Points: 881 More actions · Answer 2

Check out this connectivity troubleshooter:

http://blogs.msdn.com/b/sql_protocols/archive/2008/04/30/steps-to-troubleshoot-connectivity-issues.aspx

vultar Hall of Fame Points: 3271 More actions · Answer 3

Is the SQL service running ? Is there anything in the SQL / windows logs ?

Cheers

Vultar

teertha SSC Veteran Points: 287 More actions · Answer 4

TITLE: Connect to Server

------------------------------

Hi, the following error has occured.....!!!!! server is running and protocols are also enabled.

Named instance is working but default instance is not.

Cannot connect to SINDU-PC\MSSQLSERVER.

------------------------------

ADDITIONAL INFORMATION:

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: SQL Network Interfaces, error: 25 - Connection string is not valid) (Microsoft SQL Server, Error: 87)

Superdoc SSCommitted Points: 1654 More actions · Answer 5

teertha (8/4/2013)
TITLE: Connect to Server
------------------------------
Hi, the following error has occured.....!!!!! server is running and protocols are also enabled.
Named instance is working but default instance is not.
Cannot connect to SINDU-PC\MSSQLSERVER.
------------------------------
ADDITIONAL INFORMATION:
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: SQL Network Interfaces, error: 25 - Connection string is not valid) (Microsoft SQL Server, Error: 87)

Hi,

Default instance need not be specified as MSSQLSERVER, you just put the hostname "SINDU-PC" then connect and it should work, also ensure your firewall is enabled for defaults ports and dns properly working.

Regards,

UmaShankar Patel Ten Centuries Points: 1142 More actions · Answer 6

First Check weather SQL Server Instance is running and exists.

to see list of intances use

Go to command prompt and type in “osql -L” or “sqlcmd -L”.

or

use

http://www.queryingsql.com/2013/02/search-all-running-sql-server-instances.html

If instance is showing in list then check your credentials.

Thanks.......
-----------------------------------
My Blog[/url] | Articles

Jason Wolfkill SSCrazy Eights Points: 9832 More actions · Answer 7

Perhaps a silly question, but did you install a default instance? IIRC, you can install a named instance without first installing a default instance. If you only ran the install once and specified a named instance at the time, you don't have a default instance.

Jason Wolfkill