Connecting to SQL Server 2005

Hi all,
I have Windows XP SP2 and SQL Server 2005 CTP installed on my machine.
I am trying to connect to the database in a ASP.net application but no matter how much i try i get the following error message : System.Data.SqlClient.SQLException:SQL Server does not exist or Access denied

I have tried to fix the problmm by checking in all the online blogs and trying out whatever is being suggested , still no luck!!!

Would appreciate if anybody could help me

Thanks.
sshettyThe folks on the SQL Server Data Access forum (http://forums.microsoft.com/msdn/ShowForum.aspx?ForumID=87) should be able to help you out with this one.

Raman Iyer
SQL Server Data Mining

Connecting to SQL or MSDE difficulty !

Hey guys,
I am a newbie here, so please bear with me. I have installed SQL Server 2005 CTP on Machine A and MSDE on Machine B. Both these contain the PUBS database beside others. On Machine C, I have installed "ASP.Net Web Matrix" and I want to be able to connect to either Machine A or B to access the PUBS database. It connects to Machine B, when I put in the Servers IP address. But everytime I try to connect to Machine A, it gives me an error saying, "Unable to connect to the database. To connect to this server you must use SQL Server Management Studio or SQL Server Management objects(SMO) ".
I heard that connection strings are needed to access the SQL Server 2005 but I have no idea where to begin. Do I need to create special users to access the Server or will Windows authentication work ? Could anyone help me out in connecting to the SQL Server 2005 CTP?

Management studio is a separate install under management tools, within SQL Server you don't need permissions if you use integrated. When you install the management studio you can register the MSDE. Hope this helps.

|||I had no problems connecting to the MSDE-based server. It's the SQL Server 2005 that's the problem. Could you tell me what I have to do in Management Studio to get the ASP.Net Application that is running on a client machine to connect to it ? Is there some connection string I have to use ? What about this SMO thing ?
|||Try the link below for a walk through tutorial and related link and I would not use SMO (SQL Server Management Object) it is Microsoft property and experience have thought me not to use Microsoft property in my code when using SQL Server. Hope this helps.
http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx|||I tried all that but nothing seems to work. Could the firewall cause a problem ? If yes, then what can I do to rectify it ?|||Yes the firewall usually removes either TCP/IP or Named Pipes from your protocol stack in SQL Server, right click in Management studio and go to properties then Network Configuration and make sure both TCP/IP and Named Pipes is enabled. Hope this helps.|||I get connected to the SQL Server 2000 from a client machine using Web Matrix. I do this by entering the Server name of the SQL Server, say X250-122 and then connecting to a database on that Server. It gives me no problem at all.
When I try the same but in this case trying to connect to an instance of MSDE instead, named NetSDK, i.e. X250-122\NetSDK, on the same Server where SQL Server 2k is installed, then it gives me the following error :

" Unable to connect to the database. SQL Server does not exist or access denied. ConnectionOpen(Connect())".
I tried everything in my capacity that I could but there doesn't seem to be any solution. The protocols ( TCP/IP, Named Pipes) are enabled too. Could you please tell me how to go about this dilemma I am in. Is there a specific way of connecting to an MSDE instance from a client machine ? Please help !!|||The problem was Asp.net account permissions on the MSDE, register it in the full version and go to the security section in Enterprise Manager and configure the server permissions and then to the database and configure the database permissions for Asp.net in the MSDE instance. Another option is to run sp_grantlogin and sp_grantdbaccess in Query Analyzer against the database in the MSDE instance. Hope this helps.
|||I tried doing what you asked and it was already set by default. Ok, let me give you some more details...
I have a local account on each of these machines A, B, C, named say ROOT. SQL Server 2000 and an instance of MSDE named NetSDK is installed on Machine A. All 3 machines have Windows XP Professional with SP 2. Now if I try connecting M/c B or M/c C to the SQL Server on M/c A through the ROOT logins on each of those machines and using ASP.Net Web Matrix, it connects without any problems. But if I do the same trying to connect to NetSDK, it gives me the error I told you about.
I have given ROOT permissions on the SQL Server and the MSDE instance too. But only SQL Server goes through. Thanks for the help, by the way. I appreciate it !!
P.S. By registering the MSDE instance, what did you mean ? I have to register it under Enterprise Manager right ? Because I did that and under Security, there are logins for Machine A\ASPNET, Machine A\ROOT, etc. These are exactly the same as the ones on the SQL Server.
|||Another Problem has just cropped up !! I tried connecting from Machine A to SQL Server 2005 installed on Machine B using the same ROOT login and it didn't work giving me the following error - Unable to connect to the Database. To connect to this Server you must use SQL Server Management Studio or SQL SMO.
But when I tried connecting to Machine B from Query Analyzer i.e. FILE > Connect > Machine B...it works fine. Could you resolve this problem too besides the MSDE one. Thanks !!|||

By registering a server you can access all SQL Server in your network as local access and you do that at the very top of Enterprise Manager. What you do under security is creating a user access to the server not server registration. I have registered 68 SQL Servers in one XP pro box so you will not run into problem with the few instances you have. hope this helps.

|||I did register both the SQL Server and the MSDE instance named NetSDK, but just the SQL Server is granting access to users over the network and it's giving the same error as before. Is my way of accessing correct...i.e. say X250-122\NetSDK ?|||I tried this too... I created a user named ASPNET on the SQL Server machine and I granted the user access under EM for the MSDE instance NetSDK on the same machine. Then I tried logging in from another machine through WebMatrix and it logged in only to the SQL Server and not the NetSDK instance, giving me this error...Unable to connect to the database, Login Failed. Not associated with a trusted SQL Server connection. What could be the reason for that. I am getting access through all the accounts to the SQL Server but not the MSDE instance !!|||Create a new database in the MSDE do an INSERT INTO from the old database then create permissions for the Server under the security section for Asp.net and for the database in the database. Then you may have to delete the old database, I think you have run into orphaned permissions that are created in the Master but not usable in the database. Run a search for orphaned permissions in the BOL (books online). Hope this helps.|||Thanks...it works fine now. I appreciate your help !!

Connecting to SQL 2005 from other machines

The April CTP was working well but both the June and Sept CTP seem to be having problems with connections outside the local machine. It does not seem to matter how the connection is to be established (from code, from SQL managment studio etc) the same error comes up repeatedly.

Cannot connect to SEPTCTP.

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)

Any suggestions besides rolling back to the April CTP (our current solution)?

Is the Named Pipes protocol enabled on server?
On server machine, run SQL Server configuration manager,
open SQL Server Network Configurations and enable Named Pipes.
Or switch client to use TCP/IP protocol rather than Named Pipes.

Thanks,
Michael.

P.S. This seems to be general SQL question, you might
get better response in SQL Server Database Engine group,
rather than in this SSIS-specific group.|||I'm not sure why, but we needed to access remote servers with their IP address AND a specific non-standard port once we upgraded to the newest CTP. This seemed fine for our test applications (we're not releasing anything until the final version is released).

Josh|||

This should be fine, provided that client is also configured

to use TCP/IP protocol and appropriate port. But the error

indicates the connection is using Named Pipes protocol.

It seems like the connection or SQL Client defaults is not

configured properly.

I'm not really a pro in SQL Client configuration, forum
SQL Server Database Engine might have people more
knowlegable in this area.

The answer may depend on whether you are using OLEDB or
ADO.NET connection managed, and in former case - SQL Native
OLEDB provider or Microsoft OLEDB provider for SQL Server.

Connecting to SQL 2005

I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
connect to the server within the same box. When I try to connect to the 2005
SQL server from an other desktop using SQL Server Management studio, I get a
timeout error. Can you please help me to fix this.
This is waht I get when I connect to the SQL server from another computer...
===================================
Cannot connect to CWXPTDVZPT62.
===================================
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding. (.Net SqlClient Data Provider)
For help, click:
http://go.microsoft.com/fwlink?Prod...-2&LinkId=20476
Server Name: CWXPTDVZPT62
Error Number: -2
Severity: 11
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser. ThrowExceptionAndWarning(TdsParserStateO
bjec
t
stateObj)
at
System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
stateObj, UInt32 error, Boolean freePacket)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
enlistOK)
at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
connectionOptions, Object providerInfo, String newPassword, SqlConnection
owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOpti
ons
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbCon
nection owningConnection, DbConnectionPoolGroup poolGroup)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at
Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplore
r.ValidateConnection(UIConnectionInfo ci, IServerType server)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUs
er()Hi Mahesh,
Starting with the June CTP version, remote access to an instance of SQL
Server 2005 is off by default. You can enable remote access by using the
Surface Area Configuration (SAC) tool.
On the local server:
1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
Configuration Tools | SQL Server Surface Area Configuration
2. From the SAC tool, select Surface Area Configuration for Services and
Connections
3. Under Database Engine, select Remote Connections and then select the
Local and Remote Connections and one of the options under that.
4. Click Apply.
5. You'll need to stop and start the MSSQLSERVER service. You can do that
from the SAC as well. Just click Service under Database Engine and
stop/start the service.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
> connect to the server within the same box. When I try to connect to the
> 2005
> SQL server from an other desktop using SQL Server Management studio, I get
> a
> timeout error. Can you please help me to fix this.
> This is waht I get when I connect to the SQL server from another
> computer...
> ===================================
> Cannot connect to CWXPTDVZPT62.
> ===================================
> Timeout expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding. (.Net SqlClient Data Provider)
> --
> For help, click:
> http://go.microsoft.com/fwlink?Prod...-2&LinkId=20476
> --
> Server Name: CWXPTDVZPT62
> Error Number: -2
> Severity: 11
> State: 0
>
> --
> Program Location:
> at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
> exception, Boolean breakConnection)
> at
> System.Data.SqlClient.TdsParser. ThrowExceptionAndWarning(TdsParserStateO
bj
ect
> stateObj)
> at
> System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObje
ct
> stateObj, UInt32 error, Boolean freePacket)
> at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
> asyncResult, TdsParserStateObject stateObj)
> at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
> bytesExpected)
> at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
> at System.Data.SqlClient.TdsParserStateObject.ReadByte()
> at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
> SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
> bulkCopyHandler, TdsParserStateObject stateObj)
> at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
> enlistOK)
> at
> System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnecti
on
> owningObject, SqlConnectionString connectionOptions, String newPassword,
> Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
> connectionOptions, Object providerInfo, String newPassword, SqlConnection
> owningObject, Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOp
tions
> options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbC
onnection
> owningConnection, DbConnectionPoolGroup poolGroup)
> at
> System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
> outerConnection, DbConnectionFactory connectionFactory)
> at System.Data.SqlClient.SqlConnection.Open()
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplo
rer.ValidateConnection(UIConnectionInfo
> ci, IServerType server)
> at
> Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThread
User()
>|||Gail
Thank you for the answer, I checked the Surface area configuration and set
the option to “Local and Remote connections” and select the option to
use
both TCP/IP and named Pipes”.
I tried again to register the 2005 SQL server from Management studio of
another computer. I was able to register/connect only when I selected the
option “Named Pipes” in Connect properties for Network Protocol. When Ne
twork
Protocol option was set to “default” I got Timeout errors.
Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
Native client, I was able to view the Databases, but when I tested the
connection I got a timeout error.
I can connect to the 2005 server using query analyzer or thro creating an
ODBC.
Please advice.
Thanks again for all your help
Mahesh
"Gail Erickson [MS]" wrote:

> Hi Mahesh,
> Starting with the June CTP version, remote access to an instance of SQL
> Server 2005 is off by default. You can enable remote access by using the
> Surface Area Configuration (SAC) tool.
> On the local server:
> 1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
> Configuration Tools | SQL Server Surface Area Configuration
> 2. From the SAC tool, select Surface Area Configuration for Services and
> Connections
> 3. Under Database Engine, select Remote Connections and then select the
> Local and Remote Connections and one of the options under that.
> 4. Click Apply.
> 5. You'll need to stop and start the MSSQLSERVER service. You can do tha
t
> from the SAC as well. Just click Service under Database Engine and
> stop/start the service.
> --
> Gail Erickson [MS]
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
> news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>
>|||Hi Mahesh,
Your follow-up questions are a bit out of area of experience. Please post
your questions to the Setup and DTS newsgroups at this link:
http://communities.microsoft.com/ne...p=sqlserver2005
They should be able to give you some advice.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:8DC49354-F7FC-4979-94A9-3DB20CF6B71E@.microsoft.com...[vbcol=seagreen]
> Gail
> Thank you for the answer, I checked the Surface area configuration and set
> the option to "Local and Remote connections" and select the option to "use
> both TCP/IP and named Pipes".
> I tried again to register the 2005 SQL server from Management studio of
> another computer. I was able to register/connect only when I selected the
> option "Named Pipes" in Connect properties for Network Protocol. When
> Network
> Protocol option was set to "default" I got Timeout errors.
> Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
> Native client, I was able to view the Databases, but when I tested the
> connection I got a timeout error.
> I can connect to the 2005 server using query analyzer or thro creating an
> ODBC.
> Please advice.
> Thanks again for all your help
> Mahesh
> "Gail Erickson [MS]" wrote:
>

Connecting to SQL 2005

I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
connect to the server within the same box. When I try to connect to the 2005
SQL server from an other desktop using SQL Server Management studio, I get a
timeout error. Can you please help me to fix this.
This is waht I get when I connect to the SQL server from another computer...
===================================
Cannot connect to CWXPTDVZPT62.
===================================
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding. (.Net SqlClient Data Provider)
For help, click:
http://go.microsoft.com/fwlink?ProdN...2&LinkId=20476
Server Name: CWXPTDVZPT62
Error Number: -2
Severity: 11
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
stateObj)
at
System.Data.SqlClient.TdsParserStateObject.ReadSni Error(TdsParserStateObject
stateObj, UInt32 error, Boolean freePacket)
at System.Data.SqlClient.TdsParserStateObject.ReadSni (DbAsyncResult
asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPac ket(Int32
bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuf fer()
at System.Data.SqlClient.TdsParserStateObject.ReadByt e()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.Com pleteLogin(Boolean
enlistOK)
at
System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ct or(SqlConnectionString
connectionOptions, Object providerInfo, String newPassword, SqlConnection
owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.Creat eNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.ObjectExplorer.ValidateConnection(UIC onnectionInfo ci, IServerType server)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Co nnector.ConnectionThreadUser()
Hi Mahesh,
Starting with the June CTP version, remote access to an instance of SQL
Server 2005 is off by default. You can enable remote access by using the
Surface Area Configuration (SAC) tool.
On the local server:
1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
Configuration Tools | SQL Server Surface Area Configuration
2. From the SAC tool, select Surface Area Configuration for Services and
Connections
3. Under Database Engine, select Remote Connections and then select the
Local and Remote Connections and one of the options under that.
4. Click Apply.
5. You'll need to stop and start the MSSQLSERVER service. You can do that
from the SAC as well. Just click Service under Database Engine and
stop/start the service.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
> connect to the server within the same box. When I try to connect to the
> 2005
> SQL server from an other desktop using SQL Server Management studio, I get
> a
> timeout error. Can you please help me to fix this.
> This is waht I get when I connect to the SQL server from another
> computer...
> ===================================
> Cannot connect to CWXPTDVZPT62.
> ===================================
> Timeout expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding. (.Net SqlClient Data Provider)
> --
> For help, click:
> http://go.microsoft.com/fwlink?ProdN...2&LinkId=20476
> --
> Server Name: CWXPTDVZPT62
> Error Number: -2
> Severity: 11
> State: 0
>
> --
> Program Location:
> at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
> exception, Boolean breakConnection)
> at
> System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
> stateObj)
> at
> System.Data.SqlClient.TdsParserStateObject.ReadSni Error(TdsParserStateObject
> stateObj, UInt32 error, Boolean freePacket)
> at System.Data.SqlClient.TdsParserStateObject.ReadSni (DbAsyncResult
> asyncResult, TdsParserStateObject stateObj)
> at System.Data.SqlClient.TdsParserStateObject.ReadPac ket(Int32
> bytesExpected)
> at System.Data.SqlClient.TdsParserStateObject.ReadBuf fer()
> at System.Data.SqlClient.TdsParserStateObject.ReadByt e()
> at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
> SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
> bulkCopyHandler, TdsParserStateObject stateObj)
> at System.Data.SqlClient.SqlInternalConnectionTds.Com pleteLogin(Boolean
> enlistOK)
> at
> System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
> owningObject, SqlConnectionString connectionOptions, String newPassword,
> Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlInternalConnectionTds..ct or(SqlConnectionString
> connectionOptions, Object providerInfo, String newPassword, SqlConnection
> owningObject, Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
> options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionFactory.Creat eNonPooledConnection(DbConnection
> owningConnection, DbConnectionPoolGroup poolGroup)
> at
> System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
> outerConnection, DbConnectionFactory connectionFactory)
> at System.Data.SqlClient.SqlConnection.Open()
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.ObjectExplorer.ValidateConnection(UIC onnectionInfo
> ci, IServerType server)
> at
> Microsoft.SqlServer.Management.UI.ConnectionDlg.Co nnector.ConnectionThreadUser()
>
|||Gail
Thank you for the answer, I checked the Surface area configuration and set
the option to “Local and Remote connections” and select the option to “use
both TCP/IP and named Pipes”.
I tried again to register the 2005 SQL server from Management studio of
another computer. I was able to register/connect only when I selected the
option “Named Pipes” in Connect properties for Network Protocol. When Network
Protocol option was set to “default” I got Timeout errors.
Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
Native client, I was able to view the Databases, but when I tested the
connection I got a timeout error.
I can connect to the 2005 server using query analyzer or thro creating an
ODBC.
Please advice.
Thanks again for all your help
Mahesh
"Gail Erickson [MS]" wrote:

> Hi Mahesh,
> Starting with the June CTP version, remote access to an instance of SQL
> Server 2005 is off by default. You can enable remote access by using the
> Surface Area Configuration (SAC) tool.
> On the local server:
> 1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
> Configuration Tools | SQL Server Surface Area Configuration
> 2. From the SAC tool, select Surface Area Configuration for Services and
> Connections
> 3. Under Database Engine, select Remote Connections and then select the
> Local and Remote Connections and one of the options under that.
> 4. Click Apply.
> 5. You'll need to stop and start the MSSQLSERVER service. You can do that
> from the SAC as well. Just click Service under Database Engine and
> stop/start the service.
> --
> Gail Erickson [MS]
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
> news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>
>
|||Hi Mahesh,
Your follow-up questions are a bit out of area of experience. Please post
your questions to the Setup and DTS newsgroups at this link:
http://communities.microsoft.com/new...=sqlserver2005
They should be able to give you some advice.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:8DC49354-F7FC-4979-94A9-3DB20CF6B71E@.microsoft.com...[vbcol=seagreen]
> Gail
> Thank you for the answer, I checked the Surface area configuration and set
> the option to "Local and Remote connections" and select the option to "use
> both TCP/IP and named Pipes".
> I tried again to register the 2005 SQL server from Management studio of
> another computer. I was able to register/connect only when I selected the
> option "Named Pipes" in Connect properties for Network Protocol. When
> Network
> Protocol option was set to "default" I got Timeout errors.
> Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
> Native client, I was able to view the Databases, but when I tested the
> connection I got a timeout error.
> I can connect to the 2005 server using query analyzer or thro creating an
> ODBC.
> Please advice.
> Thanks again for all your help
> Mahesh
> "Gail Erickson [MS]" wrote:

Connecting to SQL 2005

I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
connect to the server within the same box. When I try to connect to the 2005
SQL server from an other desktop using SQL Server Management studio, I get a
timeout error. Can you please help me to fix this.
This is waht I get when I connect to the SQL server from another computer...
===================================
Cannot connect to CWXPTDVZPT62.
===================================
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding. (.Net SqlClient Data Provider)
--
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
--
Server Name: CWXPTDVZPT62
Error Number: -2
Severity: 11
State: 0
--
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)
at
System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
stateObj, UInt32 error, Boolean freePacket)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
enlistOK)
at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
connectionOptions, Object providerInfo, String newPassword, SqlConnection
owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at
Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()Hi Mahesh,
Starting with the June CTP version, remote access to an instance of SQL
Server 2005 is off by default. You can enable remote access by using the
Surface Area Configuration (SAC) tool.
On the local server:
1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
Configuration Tools | SQL Server Surface Area Configuration
2. From the SAC tool, select Surface Area Configuration for Services and
Connections
3. Under Database Engine, select Remote Connections and then select the
Local and Remote Connections and one of the options under that.
4. Click Apply.
5. You'll need to stop and start the MSSQLSERVER service. You can do that
from the SAC as well. Just click Service under Database Engine and
stop/start the service.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
> connect to the server within the same box. When I try to connect to the
> 2005
> SQL server from an other desktop using SQL Server Management studio, I get
> a
> timeout error. Can you please help me to fix this.
> This is waht I get when I connect to the SQL server from another
> computer...
> ===================================> Cannot connect to CWXPTDVZPT62.
> ===================================> Timeout expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding. (.Net SqlClient Data Provider)
> --
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
> --
> Server Name: CWXPTDVZPT62
> Error Number: -2
> Severity: 11
> State: 0
>
> --
> Program Location:
> at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
> exception, Boolean breakConnection)
> at
> System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
> stateObj)
> at
> System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
> stateObj, UInt32 error, Boolean freePacket)
> at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
> asyncResult, TdsParserStateObject stateObj)
> at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
> bytesExpected)
> at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
> at System.Data.SqlClient.TdsParserStateObject.ReadByte()
> at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
> SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
> bulkCopyHandler, TdsParserStateObject stateObj)
> at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
> enlistOK)
> at
> System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
> owningObject, SqlConnectionString connectionOptions, String newPassword,
> Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
> connectionOptions, Object providerInfo, String newPassword, SqlConnection
> owningObject, Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
> options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection
> owningConnection, DbConnectionPoolGroup poolGroup)
> at
> System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
> outerConnection, DbConnectionFactory connectionFactory)
> at System.Data.SqlClient.SqlConnection.Open()
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo
> ci, IServerType server)
> at
> Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
>|||Gail
Thank you for the answer, I checked the Surface area configuration and set
the option to â'Local and Remote connectionsâ' and select the option to â'use
both TCP/IP and named Pipesâ'.
I tried again to register the 2005 SQL server from Management studio of
another computer. I was able to register/connect only when I selected the
option â'Named Pipesâ' in Connect properties for Network Protocol. When Network
Protocol option was set to â'defaultâ' I got Timeout errors.
Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
Native client, I was able to view the Databases, but when I tested the
connection I got a timeout error.
I can connect to the 2005 server using query analyzer or thro creating an
ODBC.
Please advice.
Thanks again for all your help
Mahesh
"Gail Erickson [MS]" wrote:
> Hi Mahesh,
> Starting with the June CTP version, remote access to an instance of SQL
> Server 2005 is off by default. You can enable remote access by using the
> Surface Area Configuration (SAC) tool.
> On the local server:
> 1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
> Configuration Tools | SQL Server Surface Area Configuration
> 2. From the SAC tool, select Surface Area Configuration for Services and
> Connections
> 3. Under Database Engine, select Remote Connections and then select the
> Local and Remote Connections and one of the options under that.
> 4. Click Apply.
> 5. You'll need to stop and start the MSSQLSERVER service. You can do that
> from the SAC as well. Just click Service under Database Engine and
> stop/start the service.
> --
> Gail Erickson [MS]
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
> news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
> >I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
> > connect to the server within the same box. When I try to connect to the
> > 2005
> > SQL server from an other desktop using SQL Server Management studio, I get
> > a
> > timeout error. Can you please help me to fix this.
> >
> > This is waht I get when I connect to the SQL server from another
> > computer...
> > ===================================> >
> > Cannot connect to CWXPTDVZPT62.
> >
> > ===================================> >
> > Timeout expired. The timeout period elapsed prior to completion of the
> > operation or the server is not responding. (.Net SqlClient Data Provider)
> >
> > --
> > For help, click:
> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
> >
> > --
> > Server Name: CWXPTDVZPT62
> > Error Number: -2
> > Severity: 11
> > State: 0
> >
> >
> > --
> > Program Location:
> >
> > at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
> > exception, Boolean breakConnection)
> > at
> > System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
> > stateObj)
> > at
> > System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
> > stateObj, UInt32 error, Boolean freePacket)
> > at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
> > asyncResult, TdsParserStateObject stateObj)
> > at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
> > bytesExpected)
> > at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
> > at System.Data.SqlClient.TdsParserStateObject.ReadByte()
> > at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
> > SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
> > bulkCopyHandler, TdsParserStateObject stateObj)
> > at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
> > enlistOK)
> > at
> > System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
> > owningObject, SqlConnectionString connectionOptions, String newPassword,
> > Boolean redirectedUserInstance)
> > at
> > System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
> > connectionOptions, Object providerInfo, String newPassword, SqlConnection
> > owningObject, Boolean redirectedUserInstance)
> > at
> > System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
> > options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
> > owningConnection)
> > at
> > System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection
> > owningConnection, DbConnectionPoolGroup poolGroup)
> > at
> > System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
> > owningConnection)
> > at
> > System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
> > outerConnection, DbConnectionFactory connectionFactory)
> > at System.Data.SqlClient.SqlConnection.Open()
> > at
> > Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo
> > ci, IServerType server)
> > at
> > Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
> >
> >
>
>|||Hi Mahesh,
Your follow-up questions are a bit out of area of experience. Please post
your questions to the Setup and DTS newsgroups at this link:
http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005
They should be able to give you some advice.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:8DC49354-F7FC-4979-94A9-3DB20CF6B71E@.microsoft.com...
> Gail
> Thank you for the answer, I checked the Surface area configuration and set
> the option to "Local and Remote connections" and select the option to "use
> both TCP/IP and named Pipes".
> I tried again to register the 2005 SQL server from Management studio of
> another computer. I was able to register/connect only when I selected the
> option "Named Pipes" in Connect properties for Network Protocol. When
> Network
> Protocol option was set to "default" I got Timeout errors.
> Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
> Native client, I was able to view the Databases, but when I tested the
> connection I got a timeout error.
> I can connect to the 2005 server using query analyzer or thro creating an
> ODBC.
> Please advice.
> Thanks again for all your help
> Mahesh
> "Gail Erickson [MS]" wrote:
>> Hi Mahesh,
>> Starting with the June CTP version, remote access to an instance of SQL
>> Server 2005 is off by default. You can enable remote access by using the
>> Surface Area Configuration (SAC) tool.
>> On the local server:
>> 1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
>> Configuration Tools | SQL Server Surface Area Configuration
>> 2. From the SAC tool, select Surface Area Configuration for Services and
>> Connections
>> 3. Under Database Engine, select Remote Connections and then select the
>> Local and Remote Connections and one of the options under that.
>> 4. Click Apply.
>> 5. You'll need to stop and start the MSSQLSERVER service. You can do
>> that
>> from the SAC as well. Just click Service under Database Engine and
>> stop/start the service.
>> --
>> Gail Erickson [MS]
>> SQL Server Documentation Team
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights
>> "Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
>> news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>> >I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able
>> >to
>> > connect to the server within the same box. When I try to connect to the
>> > 2005
>> > SQL server from an other desktop using SQL Server Management studio, I
>> > get
>> > a
>> > timeout error. Can you please help me to fix this.
>> >
>> > This is waht I get when I connect to the SQL server from another
>> > computer...
>> > ===================================>> >
>> > Cannot connect to CWXPTDVZPT62.
>> >
>> > ===================================>> >
>> > Timeout expired. The timeout period elapsed prior to completion of the
>> > operation or the server is not responding. (.Net SqlClient Data
>> > Provider)
>> >
>> > --
>> > For help, click:
>> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
>> >
>> > --
>> > Server Name: CWXPTDVZPT62
>> > Error Number: -2
>> > Severity: 11
>> > State: 0
>> >
>> >
>> > --
>> > Program Location:
>> >
>> > at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
>> > exception, Boolean breakConnection)
>> > at
>> > System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
>> > stateObj)
>> > at
>> > System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
>> > stateObj, UInt32 error, Boolean freePacket)
>> > at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
>> > asyncResult, TdsParserStateObject stateObj)
>> > at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
>> > bytesExpected)
>> > at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
>> > at System.Data.SqlClient.TdsParserStateObject.ReadByte()
>> > at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
>> > SqlCommand cmdHandler, SqlDataReader dataStream,
>> > BulkCopySimpleResultSet
>> > bulkCopyHandler, TdsParserStateObject stateObj)
>> > at
>> > System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
>> > enlistOK)
>> > at
>> > System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
>> > owningObject, SqlConnectionString connectionOptions, String
>> > newPassword,
>> > Boolean redirectedUserInstance)
>> > at
>> > System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
>> > connectionOptions, Object providerInfo, String newPassword,
>> > SqlConnection
>> > owningObject, Boolean redirectedUserInstance)
>> > at
>> > System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
>> > options, Object poolGroupProviderInfo, DbConnectionPool pool,
>> > DbConnection
>> > owningConnection)
>> > at
>> > System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection
>> > owningConnection, DbConnectionPoolGroup poolGroup)
>> > at
>> > System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
>> > owningConnection)
>> > at
>> > System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
>> > outerConnection, DbConnectionFactory connectionFactory)
>> > at System.Data.SqlClient.SqlConnection.Open()
>> > at
>> > Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo
>> > ci, IServerType server)
>> > at
>> > Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
>> >
>> >
>>

Connect to SQL Server from Command Prompt?

I installed SQL Server CTP version and tried to connect from Command Prompt, but failed from either osql or sqlcmd:

osql [/sqlcmd] -H localhost -E

or,

osql [/sqlcmd] -H localhost -U sa -P SAPWD

The error message is:

Named Pipes Provider: Could not open a connection to SQL Server, ...

Please note named pipes are enabled from client protocol configuration.

without Management studio, how can I connect to the server?

Thanks.
PS: I had searched in the forum, but didn't find answer to above question.

-S is the parameter for the instancename e.g.

sqlcmd -S (local) -E

sqlcmd -S (local)\SQL01 -E

For a windows authenticated connection to the default instance on the local

machine you don't need any parameters for sqlcmd e.g

sqlcmd

--

HTH

Jasper Smith (SQL Server MVP)

http://www.sqldbatips.com

I support PASS - the definitive, global

community for SQL Server professionals -

http://www.sqlpass.org

wrote in message

news:f756a7ad-017a-42a5-aa70-0908ad626391@.discussions.microsoft.com...

>I installed SQL Server CTP version and tried to connect from Command

> Prompt, but failed from either osql or sqlcmd:

>

> osql [/sqlcmd] -H localhost -E

>

> or,

>

> osql [/sqlcmd] -H localhost -U sa -P SAPWD

>

> The error message is:

>

> Named Pipes Provider: Could not open a connection to SQL Server, ...

>

> Please note named pipes are enabled from client protocol configuration.

>

> without Management studio, how can I connect to the server?

>

> Thanks.

>

>

> PS: I had searched in the forum, but didn't find answer to above

> question.

>

>

>

>

>|||-S is the parameter for the instancename e.g.

sqlcmd -S (local) -E sqlcmd -S (local)\SQL01 -E

For a windows authenticated connection to the default instance on the local machine you don't need any parameters for sqlcmd e.g

sqlcmd

|||Thanks for the replies.

After a few attempts, I found the following command works:

osql (or sqlcmd) -S .\SQLEXPRESS -E

without instance name, it always timed out.