Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts

Tuesday, March 27, 2012

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!!!Sad

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 Server 2000 on Windows 2003 Server using sql-dmo

Hi
I have a strange problem connecting to a local SQL Server 2000 on a machine
running Windows 2003 Server.
I'm using a plain connection as shown in the code below:
Dim oServer as New SQLDMO.SQLServer
With oServer
.LoginTimeout = -1
.LoginSecure = True 'Use NT Authentication
.AutoReConnect = False
.Connect (strServerName)
End With
I'm connecting through the IP of the machine.
The problem is:
When I have a system32\drivers\etc\hosts entry specified pointing at the
same machine, then I cannot connect to the SQL Server using NT Authenticatio
n.
I can however still connect by using SA user.
Error is:
Runtime error '-2147203052 (80044814)':
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
If I remove the hosts entry I can connect without problems using both NT
authentication and SA user.
It doesn't make any difference about the problem if I'm running NT
authentication mode or mixed mode.
This code having this problem has run without problems on Windows 2000
server, so it is an issue with Windows 2003 server.
Does anyone have a clue to what might cause this problem?
Thanx in advance
/BrianJust a note, if other people should have the same problem.
A temporary work-around is to define the entry in the Hosts entry as an
Alias in
SQL Server - Client Network Utility.
/Brian
"Brian Nielsen" wrote:

> Hi
> I have a strange problem connecting to a local SQL Server 2000 on a machin
e
> running Windows 2003 Server.
> I'm using a plain connection as shown in the code below:
> Dim oServer as New SQLDMO.SQLServer
> With oServer
> .LoginTimeout = -1
> .LoginSecure = True 'Use NT Authentication
> .AutoReConnect = False
> .Connect (strServerName)
> End With
> I'm connecting through the IP of the machine.
> The problem is:
> When I have a system32\drivers\etc\hosts entry specified pointing at the
> same machine, then I cannot connect to the SQL Server using NT Authenticat
ion.
> I can however still connect by using SA user.
> Error is:
> Runtime error '-2147203052 (80044814)':
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> If I remove the hosts entry I can connect without problems using both NT
> authentication and SA user.
> It doesn't make any difference about the problem if I'm running NT
> authentication mode or mixed mode.
> This code having this problem has run without problems on Windows 2000
> server, so it is an issue with Windows 2003 server.
> Does anyone have a clue to what might cause this problem?
> Thanx in advance
> /Brian

connecting to SQL Server 2000

hi all;
I have a SQL server ent. edition installed on windows 2003, I want to
register another SQL server instance installed on windows xp, in my
enterprise manager. When I try to do that i get the following error message.
"SQL server does not exists or access denied."
note that no domain controller is installed on the network.
What is reason, and how can i resolve it?
all ideas would be highly appreciated...
AnsariYou have to verify that :
1. you have nioo network problems , you can test sharing a folder on the XP
machine and access this share from Win2003
2. Verifiy that you have no accounts problems and permissions
3.verify thant services are really started on the xp machine
4. try to register xp server from Win2003 using the IP adresss first second
try with the netbios name .
5. activate the mixed security on the xp machine and try to register with SA
login .
I think that with these 5 tests you should fix the poblem
hch
"Ansari" a écrit :

> hi all;
> I have a SQL server ent. edition installed on windows 2003, I want to
> register another SQL server instance installed on windows xp, in my
> enterprise manager. When I try to do that i get the following error messag
e.
> "SQL server does not exists or access denied."
> note that no domain controller is installed on the network.
> What is reason, and how can i resolve it?
> all ideas would be highly appreciated...
> Ansari
>
>

connecting to SQL Server 2000

hi all;
I have a SQL server ent. edition installed on windows 2003, I want to
register another SQL server instance installed on windows xp, in my
enterprise manager. When I try to do that i get the following error message.
"SQL server does not exists or access denied."
note that no domain controller is installed on the network.
What is reason, and how can i resolve it?
all ideas would be highly appreciated...
Ansari
You have to verify that :
1. you have nioo network problems , you can test sharing a folder on the XP
machine and access this share from Win2003
2. Verifiy that you have no accounts problems and permissions
3.verify thant services are really started on the xp machine
4. try to register xp server from Win2003 using the IP adresss first second
try with the netbios name .
5. activate the mixed security on the xp machine and try to register with SA
login .
I think that with these 5 tests you should fix the poblem
hch
"Ansari" a écrit :

> hi all;
> I have a SQL server ent. edition installed on windows 2003, I want to
> register another SQL server instance installed on windows xp, in my
> enterprise manager. When I try to do that i get the following error message.
> "SQL server does not exists or access denied."
> note that no domain controller is installed on the network.
> What is reason, and how can i resolve it?
> all ideas would be highly appreciated...
> Ansari
>
>
sqlsql

connecting to SQL Server 2000

hi all;
I have a SQL server ent. edition installed on windows 2003, I want to
register another SQL server instance installed on windows xp, in my
enterprise manager. When I try to do that i get the following error message.
"SQL server does not exists or access denied."
note that no domain controller is installed on the network.
What is reason, and how can i resolve it?
all ideas would be highly appreciated...
AnsariYou have to verify that :
1. you have nioo network problems , you can test sharing a folder on the XP
machine and access this share from Win2003
2. Verifiy that you have no accounts problems and permissions
3.verify thant services are really started on the xp machine
4. try to register xp server from Win2003 using the IP adresss first second
try with the netbios name .
5. activate the mixed security on the xp machine and try to register with SA
login .
I think that with these 5 tests you should fix the poblem
hch
"Ansari" a écrit :
> hi all;
> I have a SQL server ent. edition installed on windows 2003, I want to
> register another SQL server instance installed on windows xp, in my
> enterprise manager. When I try to do that i get the following error message.
> "SQL server does not exists or access denied."
> note that no domain controller is installed on the network.
> What is reason, and how can i resolve it?
> all ideas would be highly appreciated...
> Ansari
>
>

connecting to sql server (within windows domain) through linux?

Hi,

I'm planning to develop a small intranet to provide our organization
with documents online. I've decided to do this using jsp/servlets
using a tomcat server. For an operating system, I have chosen red hat
linux. However, I'd like to keep a small database on a sql server as
a datasource. However, this sql server is already part of our
organization's windows domain. I suspect I'll need to configure samba
so that other terminals on the windows domain will be able to reach
the intranet. What's the best manner in which to connect my linux
servlets to this sql server database? I suspect this may be
difficult, considering the sql server exists within a windows domain,
but as a beginner, what do I know. Perhaps someone could point me in
the right direction.Hi

You can use the JDBC driver to communicate with your SQL Server and use SQL
Server authentication to access the server. Samba is not needed at all this
may be a way to connect to an access database but SQL Server is a completely
different product.

John
"Dan" <danhicks333@.gmail.com> wrote in message
news:b03c5d2b.0409111105.18d75023@.posting.google.c om...
> Hi,
> I'm planning to develop a small intranet to provide our organization
> with documents online. I've decided to do this using jsp/servlets
> using a tomcat server. For an operating system, I have chosen red hat
> linux. However, I'd like to keep a small database on a sql server as
> a datasource. However, this sql server is already part of our
> organization's windows domain. I suspect I'll need to configure samba
> so that other terminals on the windows domain will be able to reach
> the intranet. What's the best manner in which to connect my linux
> servlets to this sql server database? I suspect this may be
> difficult, considering the sql server exists within a windows domain,
> but as a beginner, what do I know.Perhapssomeonecouldpointmein
> the right direction.|||Dan (danhicks333@.gmail.com) writes:
> I'm planning to develop a small intranet to provide our organization
> with documents online. I've decided to do this using jsp/servlets
> using a tomcat server. For an operating system, I have chosen red hat
> linux. However, I'd like to keep a small database on a sql server as
> a datasource. However, this sql server is already part of our
> organization's windows domain. I suspect I'll need to configure samba
> so that other terminals on the windows domain will be able to reach
> the intranet. What's the best manner in which to connect my linux
> servlets to this sql server database? I suspect this may be
> difficult, considering the sql server exists within a windows domain,
> but as a beginner, what do I know. Perhaps someone could point me in
> the right direction.

I have never connected to SQL Server from Unix myself, but I happen to
maintain a page which summarizes the various options. Look at:
http://www.sommarskog.se/mssqlperl/unix.html

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||The SQL server I want to connect to does not have a public IP address.
I connect to this server from my other web server (part of the
windows domain)using the server name (treadstonesql). My thinking was
that if samba is configured correctly, I could connect to it the same
way my web server does. Does this help?

"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:<414352bf$0$4664$afc38c87@.news.easynet.co.uk>...
> Hi
> You can use the JDBC driver to communicate with your SQL Server and use SQL
> Server authentication to access the server. Samba is not needed at all this
> may be a way to connect to an access database but SQL Server is a completely
> different product.
> John
> "Dan" <danhicks333@.gmail.com> wrote in message
> news:b03c5d2b.0409111105.18d75023@.posting.google.c om...
> > Hi,
> > I'm planning to develop a small intranet to provide our organization
> > with documents online. I've decided to do this using jsp/servlets
> > using a tomcat server. For an operating system, I have chosen red hat
> > linux. However, I'd like to keep a small database on a sql server as
> > a datasource. However, this sql server is already part of our
> > organization's windows domain. I suspect I'll need to configure samba
> > so that other terminals on the windows domain will be able to reach
> > the intranet. What's the best manner in which to connect my linux
> > servlets to this sql server database? I suspect this may be
> > difficult, considering the sql server exists within a windows domain,
> > but as a beginner, what do I know.Perhapssomeonecouldpointmein
> > the right direction.|||Hi

The IPaddress does not have to be a public one (in fact it would be better
if it wasn't) The IP Address can be used when connecting instead of using a
lookup, you will need to set up the firewall rules so that you can talk on
the right ports (not necessarily the default ones!) between the two
machines.

I would not expect your second web server to be part of the internal domain,
this may mean that your whole domain is compromised if the web server is
compromised.

John

"Dan" <danhicks333@.gmail.com> wrote in message
news:b03c5d2b.0409120659.618cc1ae@.posting.google.c om...
> The SQL server I want to connect to does not have a public IP address.
> I connect to this server from my other web server (part of the
> windows domain)using the server name (treadstonesql). My thinking was
> that if samba is configured correctly, I could connect to it the same
> way my web server does. Does this help?
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:<414352bf$0$4664$afc38c87@.news.easynet.co.uk>...
> > Hi
> > You can use the JDBC driver to communicate with your SQL Server and use
SQL
> > Server authentication to access the server. Samba is not needed at all
this
> > may be a way to connect to an access database but SQL Server is a
completely
> > different product.
> > John
> > "Dan" <danhicks333@.gmail.com> wrote in message
> > news:b03c5d2b.0409111105.18d75023@.posting.google.c om...
> > > Hi,
> > > > I'm planning to develop a small intranet to provide our organization
> > > with documents online. I've decided to do this using jsp/servlets
> > > using a tomcat server. For an operating system, I have chosen red hat
> > > linux. However, I'd like to keep a small database on a sql server as
> > > a datasource. However, this sql server is already part of our
> > > organization's windows domain. I suspect I'll need to configure samba
> > > so that other terminals on the windows domain will be able to reach
> > > the intranet. What's the best manner in which to connect my linux
> > > servlets to this sql server database? I suspect this may be
> > > difficult, considering the sql server exists within a windows domain,
> > > but as a beginner, what do I know.Perhapssomeonecouldpointmein
> > > the right direction.

Connecting To SQL Server

Hi,

I have a problem in logging in to an SQL Server database engine. I can log in to the engine with Windows authentication method. The problem is, when I create a page with an SqlDataConnection control, the page can not connect to the database engine eventhough I select "Use Windows Authentication" when configuring the SqlDataConnection. What should I do?

Best regards,

Haris

This article explains how to connect to SQL Server using Windows authentication.

http://msdn2.microsoft.com/en-us/library/ms998292.aspx

|||

Is the steps in the article that you mentioned also applicable on SQL Server 2005?

|||

Hi haris101,

Yes. It is applicable on sql2005.

The problem is, when I create a page with an SqlDataConnection control, the page can not connect to the database engine eventhough I select "Use Windows Authentication" when configuring the SqlDataConnection

what is your error message when your connection fails? also, did you get the error from visual web developper or IIS?

If you are getting the error from IIS (which i thin is the most case), make sure you have granted ASPNET (if using win xp) or NETWORK SERVICE (if using win 2003 server) the proper access permission. As to how to grant permission to a specific account, you can check the link tsm gave you . thanks

Sunday, March 25, 2012

Connecting to sql from Delphi 5

I try to connect (locally) to SQLServer Express from Delphi5. On my developer computer, which has Windows XP, SQLServer 2000, VisualStudio2005 (and with that, SQLExpress 2005), it is no problem. However, when I transfer my program and the database to other computers with Windows 2000/WindowsServer2003 and a more recent standalone-version of SQLExpress, I get error messages like:

'Db-Library error 10004: No connection possible: SQL Server not available or not existing'

It does not matter which protocols I activate at the Server or whether the Server Browser service is running or not.

Does anybody have an idea how this might be fixed? Or whether it is a problem of the operating system?

Didi you try making a connecting without any Delphi tools like sqlcmd.exe at the command prompt ?

HTH, Jens K. Suessemeyer.

http://www.sqlserver2005.de
|||

Yes, all MS SQL 2005 tools work.

Meanwhile I found a solution myself: Everything works fine, if I install SQL Server 2000 additionally -- the client suffices. I don't like talking to a new 2005 database via an old 2000 client library, but at least it works.

Thanks very much for helping.

Lucia Lehr

Connecting to SQL across Non-Trusted Domains

The problem I am having is this :
SQL Servers in a non -trusted Windows 2000 Domain (Test domain) do not show
as being alive in Enterprise Manager unless you map a drive to a server in t
he non-trusted domain.
Has anyone seem this problem before? Not sure whether this is related to Act
ive Directory.
Also all our SQL Instances use specific port numbers.
Thanks
CPNZSounds like the Agent polling is not able to contact the other servers
unless you map a drive allowing your server
to communicate with the others. This is more of a problem with disjoined
domains that SQL Server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||You can do the following.
Your SQL Server instances must be running as a LOCAL or Domain account. If
you configure a LOCAL account on the server you are trying to connect to
with the same username and password it will log in using this account.
Barry McAuslin
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"CPNZ" <anonymous@.discussions.microsoft.com> wrote in message
news:72C261EE-AB91-45D1-BA20-EE1F805E3FD0@.microsoft.com...
> The problem I am having is this :
> SQL Servers in a non -trusted Windows 2000 Domain (Test domain) do not
show as being alive in Enterprise Manager unless you map a drive to a server
in the non-trusted domain.
> Has anyone seem this problem before? Not sure whether this is related to
Active Directory.
> Also all our SQL Instances use specific port numbers.
> Thanks
> CPNZ|||Okay. We have clients using Enterprise Manager, and they used to be able to
connect accross these domains using SQL authentication.
Kevin could there be an Active Directory issue stopping these services being
seen accross the domains? My server people say nothing has changed in AD,
but you never know. Also could you give a little more info on the Polling A
gent.
Thanks
Clint|||Hi Clint,
The SQL Server state polling is controlled in Enterprise Manager.
Go to the server you registered. Then Select from the menu, Tools ,
Options.
By default we poll servers every 10 seconds.
Check to see if you're clients connect using Named Pipes or TCP/IP sockets.
You'll be unable to connect to a remote server in an untrusted domain
using Named Pipes. Use the SQL Client network utility to specify tcp/ip as
the protocol to connect to the remote server.
Hope this helps.
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connecting to SQL across Non-Trusted Domains

The problem I am having is this :
SQL Servers in a non -trusted Windows 2000 Domain (Test domain) do not show
as being alive in Enterprise Manager unless you map a drive to a server in t
he non-trusted domain.
Has anyone seem this problem before? Not sure whether this is related to Act
ive Directory.
Also all our SQL Instances use specific port numbers.
ThanksClint,
That's called "working as designed" I'm afraif - it's expecting there to be
an underlying NT authentication.

> The problem I am having is this :
> SQL Servers in a non -trusted Windows 2000 Domain (Test domain) do not sho
w as being alive in Enterprise Manager unless you map a drive to a server in
the non-trusted domain.
> Has anyone seem this problem before? Not sure whether this is related to A
ctive Directory.
> Also all our SQL Instances use specific port numbers.
> Thanks
>
Neil Pike MVP/MCSE. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvfor...p?SRV=MSDevApps
(faqxxx.zip in lib 7)
or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq

Thursday, March 22, 2012

Connecting to SQL 2005 server on Windows 2003

Hope this is on the correct forum, if not could the admins move please.

Im running Win XP SP2 Pro + All updates, Visual Studio .Net 2005 and SQL 2005. SQL is running on Win 2003 server. When i try to create a connection on the WinXP system using ODBC i get the following error:

Connection Failed:
SQLSTATE: '01000'
SQL Server Error: 233
[Microsoft] [ODBC SQL server driver][DBNETLIB]Connection open (PreLoginHandshake())
Connection failed:
SQLState: '08001'
SQL Server error: 11
[Microsoft] [ODBC SQL server driver][DBNETLIB]General Network error. Chcek your network documentation.

Ive searched about the error but nothing seems to work - can anyone help to resolve please?

Thanks in advance.

1) Are you making remote connection? If you have SQL 2005 installed on your XP client box, can you try Management studio to connect to remote server? what error you see?

2) Did you install SQL Express 2005 and make remote connection?If so, check this blog:

http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx

But I do not think this is the case.

3) more GNE error troubleshooting blog:

http://blogs.msdn.com/sql_protocols/archive/2006/04/12/574608.aspx

Might give you some clue.

Summary, to fix your problem, please:

check our anouncement posted by Nan Tu, provided the answer to the questions for troubleshootin connectivity issue.

Thanks!

Ming.

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()
>> >
>> >
>>

Connecting to SQL

I have a problem in connecting to an SQL database on a server from laptop
computers. The users can access it from a desktop with same windows login as
they use on their laptop but all I get when they try on the laptop is an
error message saying connection failure. All machines are running XP and we
cannot find any differences in the setup.
If anyone has any advise or can point me in the right direction I would be
greatful.
TIA
Rob
Hi Rob,
Do you use sqlserver authentication or windows authentication on the
sqlserver ?
Ton
"Rob Fenn" <robfenn.mp@.nospamntlworld.com> wrote in message
news:OGxRj9rtEHA.2664@.TK2MSFTNGP12.phx.gbl...
> I have a problem in connecting to an SQL database on a server from laptop
> computers. The users can access it from a desktop with same windows login
as
> they use on their laptop but all I get when they try on the laptop is an
> error message saying connection failure. All machines are running XP and
we
> cannot find any differences in the setup.
> If anyone has any advise or can point me in the right direction I would be
> greatful.
> TIA
> Rob
>
>
|||windows authentication. Although this has been partly resolved. The laptops
have been assigned fixed IP addresses which has allowed them to connect.
However I would ideally prefer a different workaround as fixed IP addresses
are not ideal.
Thanks
"Ton" <t.leer@.wanadoo.nl> wrote in message
news:4176ad6b$0$30709$18b6e80@.news.wanadoo.nl...
> Hi Rob,
> Do you use sqlserver authentication or windows authentication on the
> sqlserver ?
> Ton
> "Rob Fenn" <robfenn.mp@.nospamntlworld.com> wrote in message
> news:OGxRj9rtEHA.2664@.TK2MSFTNGP12.phx.gbl...
> as
> we
>
|||This is a DNS issue and is not really related to SQL Server.
Michael Otey
"Rob Fenn" <robfenn.mp@.nospamntlworld.com> wrote in message
news:O1Ljfq4tEHA.2316@.TK2MSFTNGP12.phx.gbl...
> windows authentication. Although this has been partly resolved. The
laptops
> have been assigned fixed IP addresses which has allowed them to connect.
> However I would ideally prefer a different workaround as fixed IP
addresses[vbcol=seagreen]
> are not ideal.
> Thanks
> "Ton" <t.leer@.wanadoo.nl> wrote in message
> news:4176ad6b$0$30709$18b6e80@.news.wanadoo.nl...
laptop[vbcol=seagreen]
login[vbcol=seagreen]
an[vbcol=seagreen]
and
>

Connecting to SQL

I have a problem in connecting to an SQL database on a server from laptop
computers. The users can access it from a desktop with same windows login as
they use on their laptop but all I get when they try on the laptop is an
error message saying connection failure. All machines are running XP and we
cannot find any differences in the setup.
If anyone has any advise or can point me in the right direction I would be
greatful.
TIA
RobHi Rob,
Do you use sqlserver authentication or windows authentication on the
sqlserver ?
Ton
"Rob Fenn" <robfenn.mp@.nospamntlworld.com> wrote in message
news:OGxRj9rtEHA.2664@.TK2MSFTNGP12.phx.gbl...
> I have a problem in connecting to an SQL database on a server from laptop
> computers. The users can access it from a desktop with same windows login
as
> they use on their laptop but all I get when they try on the laptop is an
> error message saying connection failure. All machines are running XP and
we
> cannot find any differences in the setup.
> If anyone has any advise or can point me in the right direction I would be
> greatful.
> TIA
> Rob
>
>|||windows authentication. Although this has been partly resolved. The laptops
have been assigned fixed IP addresses which has allowed them to connect.
However I would ideally prefer a different workaround as fixed IP addresses
are not ideal.
Thanks
"Ton" <t.leer@.wanadoo.nl> wrote in message
news:4176ad6b$0$30709$18b6e80@.news.wanadoo.nl...
> Hi Rob,
> Do you use sqlserver authentication or windows authentication on the
> sqlserver ?
> Ton
> "Rob Fenn" <robfenn.mp@.nospamntlworld.com> wrote in message
> news:OGxRj9rtEHA.2664@.TK2MSFTNGP12.phx.gbl...
> as
> we
>|||This is a DNS issue and is not really related to SQL Server.
Michael Otey
"Rob Fenn" <robfenn.mp@.nospamntlworld.com> wrote in message
news:O1Ljfq4tEHA.2316@.TK2MSFTNGP12.phx.gbl...
> windows authentication. Although this has been partly resolved. The
laptops
> have been assigned fixed IP addresses which has allowed them to connect.
> However I would ideally prefer a different workaround as fixed IP
addresses
> are not ideal.
> Thanks
> "Ton" <t.leer@.wanadoo.nl> wrote in message
> news:4176ad6b$0$30709$18b6e80@.news.wanadoo.nl...
laptop[vbcol=seagreen]
login[vbcol=seagreen]
an[vbcol=seagreen]
and[vbcol=seagreen]
>

Connecting to Reporting Services Server failed!!!

SQL Server 2005 and SSRS 2005 is curently installed on the same box. The OS is Windows 2003 (S) enterprise edition.

When I connect to the Reporting Services Server using the Sql Server Management studio I get the following error message

The request failed with HTTP status 407: Proxy Authentication Required.

(Microsoft.sqlserver.Management.UI.RSClient)

rsAccessDenied

I am tring to connect using the Windows Admin id. I would like to get an answer from this form.

-Aza

Any body to help here

-Nitu

Tuesday, March 20, 2012

Connecting to Oracle from Windows 64bit IA server

I am trying to pull data from an Oracle 9i database to my SQL Server 2005 sp1 database on Windows 2003 64bit Itanium server. Each time I try to use the import wizard, select the Microsoft OLE DB driver for Oracle, I get an error message telling me that the Oracle client tools are not installed. This happened after I had already installed the 9i tools, tested the connection using TNSPING and confirmed the tnsnames file was correct. So, I uninstalled the 9i tools and then installed the 10g client tools. Tested everything after the install and then tried the import again selecting the MS OLE DB driver for Oracle. I again got the error message that the Oracle tools were not installed.

has anyone ran into this problem and if so, were you able to fix it?

It seems that there is an with how Oracle parses the Program Files (x86) directory. Has anyone heard of this?|||

This is a known Oracle bug, with plenty of information about the issue here -

Connecting to Oracle on 64-bit (x64) machine - MSDN Forums
(http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=159581&SiteID=1)

sqlsql

Connecting to ODBC Connections with Report Services

I have just migrated from SQL 2000 to SQL 2005 and in the process upgraded to new hardware. I am now running SQL2005 (64 Bit) on Windows 2003 R2 (64 Bit). The problem is that when i deploy some reports to the new server that use ODBC to connect to the data, reporting services is erroring with :

Data source name not found and no default driver specified

The ODBC connections are set up exactly the same on the old server and the new server. Is it because it is looking for a 64 bit ODBC driver and not the 32 Bit one I have installed. If i go into the SysWOW64 and run the odbcad32.exe i can see the drivers and the connection. The connection test works fine from here.

Thanks

Has anyone got any ideas on this ?|||Did you find a resolution? I have the same problem.|||I am waiting for a company called Openlink to get back to me they are currently developing some drivers|||Thanks. My client is switching to 32-bit software to resolve this. Good luck.|||

Did anyone get this resolved? I am having the same problem. I fear I may have to revert back to the 32-Bit OS.

Any advice or suggestion are welcomed.

Thanks,

Andy

Connecting to ODBC Connections with Report Services

I have just migrated from SQL 2000 to SQL 2005 and in the process upgraded to new hardware. I am now running SQL2005 (64 Bit) on Windows 2003 R2 (64 Bit). The problem is that when i deploy some reports to the new server that use ODBC to connect to the data, reporting services is erroring with :

Data source name not found and no default driver specified

The ODBC connections are set up exactly the same on the old server and the new server. Is it because it is looking for a 64 bit ODBC driver and not the 32 Bit one I have installed. If i go into the SysWOW64 and run the odbcad32.exe i can see the drivers and the connection. The connection test works fine from here.

Thanks

Has anyone got any ideas on this ?|||Did you find a resolution? I have the same problem.|||I am waiting for a company called Openlink to get back to me they are currently developing some drivers|||Thanks. My client is switching to 32-bit software to resolve this. Good luck.|||

Did anyone get this resolved? I am having the same problem. I fear I may have to revert back to the 32-Bit OS.

Any advice or suggestion are welcomed.

Thanks,

Andy