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 Server

Hi:

I installed SQL Express in one of my Notebook A (XP Pro SP2), I could start writing code with VB6 as it is in local machine (.\Sqlexpress)

At later stage, I used another Notebook B (XP pro SP1). I changed the notebook workgroup with the same name and try to connect to Notebook A with Ethernet Cable using SQLOLEDB to make connection, I had this Error Message

"Test Connection Failed because of an error initialising the provider.[DBNETLIB][Connection Open(Connect()).]SQL Server Does not Exist or Access Denied"

I look thru this forum, I quoted Jens K. Suessmeyer comment

This simply mean that in a network you either will need all users to have their own database OR dedicate a "server" (which can also be a workstation) to host the database as a server attached instance.

So I Presume I could used a PC/Notebook (not a Server) as Database Server?

If I used Windows NT Integrated Security, then I should create user accounts at Notebook A? Or Create User Accounts at SQL Server If i used "Used Specific User Name and Password" to Log in ?

My Intention is If I have 5 PC to log in to Server Automatically whenever they switch on the PC with the VB6 Program executing during start up. It make login to User as transparent as possible.

Thanks

"So I Presume I could used a PC/Notebook (not a Server) as Database Server?"

Yes, indeed you can.

If I used Windows NT Integrated Security, then I should create user accounts at Notebook A? Or Create User Accounts at SQL Server If i used "Used Specific User Name and Password" to Log in ?

If you are in a workgroup the (SQL Server) computers cannot verify the user of another computer as no trust exists between the computers (having the same workgroup name is not a trust). There is a workaround (I would name it hack), to use the same useraccount names and passwords on all computers to logon with Windows Authentication. I would suggest in that case to use SQL Server authentication instead.

"My Intention is If I have 5 PC to log in to Server Automatically whenever they switch on the PC with the VB6 Program executing during start up. It make login to User as transparent as possible."

Use SQL Server logins instead, if you don′t want any user interaction you should use a fixed user name to logon.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.d

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 remote Express instance using SSMS

I have a server running SQL Server 2005 Ent. Ed. SP2 and locally, I can see
the default instance and two SQLExpress instances named 'sqlexpress' and
'officeservers', all withing SSMS, and can connect and manage them.
From my workstation, running SQL 2005 Dev, SP2, I can connect to the default
instance on that server, but cannot connect to the express instances. They
both have TCP/IP protocol enabled, along with "Allow Remote COnnections".
I have done the following:
Made myself a member of the local Admin group
Tried using the sa account to connect
nothing seems to work. What am I missing?
TIA
Todd Chittenden
Is the SQLBrowser Service enabled and started?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:15C51BF6-FF25-435E-B26B-3863344FB81D@.microsoft.com...
>I have a server running SQL Server 2005 Ent. Ed. SP2 and locally, I can see
> the default instance and two SQLExpress instances named 'sqlexpress' and
> 'officeservers', all withing SSMS, and can connect and manage them.
> From my workstation, running SQL 2005 Dev, SP2, I can connect to the
> default
> instance on that server, but cannot connect to the express instances. They
> both have TCP/IP protocol enabled, along with "Allow Remote COnnections".
> I have done the following:
> Made myself a member of the local Admin group
> Tried using the sa account to connect
> nothing seems to work. What am I missing?
> TIA
> --
> Todd Chittenden
>
|||I found it not long after posting the original question:
No, the Browser service was not running. Starting that up enabled me to
connect to it. So that was the answer.
But even before the Enterprise instance was installed, (which includes the
browser service) I was not able to connect. I know I have other machines in
my domain that are running SQL Express. Should I not be able to connect to
them using my SSMS? What do I need to do to make that happen?
I assume that I need membership in the group on the local machine that bears
the SQL Express instance name?
What else? I can't rely on the Browser service in those instances.
Thanks
Todd Chittenden
"Roger Wolter[MSFT]" wrote:

> Is the SQLBrowser Service enabled and started?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:15C51BF6-FF25-435E-B26B-3863344FB81D@.microsoft.com...
>
|||SQL Express by default installs as a named instance. Unless you specify the
TCP/IP port in the connection string, you need the sqlbrowser service to
connect to a named instance.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:F4B981A2-4B9A-443E-855B-D53B89FCE511@.microsoft.com...[vbcol=seagreen]
>I found it not long after posting the original question:
> No, the Browser service was not running. Starting that up enabled me to
> connect to it. So that was the answer.
> But even before the Enterprise instance was installed, (which includes the
> browser service) I was not able to connect. I know I have other machines
> in
> my domain that are running SQL Express. Should I not be able to connect to
> them using my SSMS? What do I need to do to make that happen?
> I assume that I need membership in the group on the local machine that
> bears
> the SQL Express instance name?
> What else? I can't rely on the Browser service in those instances.
> Thanks
> --
> Todd Chittenden
>
> "Roger Wolter[MSFT]" wrote:

Connecting to remote Express instance using SSMS

I have a server running SQL Server 2005 Ent. Ed. SP2 and locally, I can see
the default instance and two SQLExpress instances named 'sqlexpress' and
'officeservers', all withing SSMS, and can connect and manage them.
From my workstation, running SQL 2005 Dev, SP2, I can connect to the default
instance on that server, but cannot connect to the express instances. They
both have TCP/IP protocol enabled, along with "Allow Remote COnnections".
I have done the following:
Made myself a member of the local Admin group
Tried using the sa account to connect
nothing seems to work. What am I missing?
TIA
--
Todd ChittendenIs the SQLBrowser Service enabled and started?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:15C51BF6-FF25-435E-B26B-3863344FB81D@.microsoft.com...
>I have a server running SQL Server 2005 Ent. Ed. SP2 and locally, I can see
> the default instance and two SQLExpress instances named 'sqlexpress' and
> 'officeservers', all withing SSMS, and can connect and manage them.
> From my workstation, running SQL 2005 Dev, SP2, I can connect to the
> default
> instance on that server, but cannot connect to the express instances. They
> both have TCP/IP protocol enabled, along with "Allow Remote COnnections".
> I have done the following:
> Made myself a member of the local Admin group
> Tried using the sa account to connect
> nothing seems to work. What am I missing?
> TIA
> --
> Todd Chittenden
>|||I found it not long after posting the original question:
No, the Browser service was not running. Starting that up enabled me to
connect to it. So that was the answer.
But even before the Enterprise instance was installed, (which includes the
browser service) I was not able to connect. I know I have other machines in
my domain that are running SQL Express. Should I not be able to connect to
them using my SSMS? What do I need to do to make that happen?
I assume that I need membership in the group on the local machine that bears
the SQL Express instance name?
What else? I can't rely on the Browser service in those instances.
Thanks
--
Todd Chittenden
"Roger Wolter[MSFT]" wrote:

> Is the SQLBrowser Service enabled and started?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:15C51BF6-FF25-435E-B26B-3863344FB81D@.microsoft.com...
>|||SQL Express by default installs as a named instance. Unless you specify the
TCP/IP port in the connection string, you need the sqlbrowser service to
connect to a named instance.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:F4B981A2-4B9A-443E-855B-D53B89FCE511@.microsoft.com...[vbcol=seagreen]
>I found it not long after posting the original question:
> No, the Browser service was not running. Starting that up enabled me to
> connect to it. So that was the answer.
> But even before the Enterprise instance was installed, (which includes the
> browser service) I was not able to connect. I know I have other machines
> in
> my domain that are running SQL Express. Should I not be able to connect to
> them using my SSMS? What do I need to do to make that happen?
> I assume that I need membership in the group on the local machine that
> bears
> the SQL Express instance name?
> What else? I can't rely on the Browser service in those instances.
> Thanks
> --
> Todd Chittenden
>
> "Roger Wolter[MSFT]" wrote:
>

connecting to an SQL2005 Server

Hi

I am trying to upgrade a system from SQL 2000 to SQL2005.

I have installed the Server on a PC with Win XP SP2. Using another PC (also Win XP SP2) on the LAN I need to ODBC to the Server.

The Server is NOT the default instance.

I cannot connect via ODBC from the Client PC. This all worked fine with SQL 2000.

As a test I also tried a fresh install of SQL2005 where it was the default instance, this worked fine.

SO the problem is when you have multiple instances.

What do I have to do to sort it out?

Cheers

Eugene

Hi,

What is a error message !? Untill you provide error message we cannot suggest you answer.

Hemantgiri S. Goswami

|||

The error is

Cannot connect to Fred\Fredsql

SQL server does not allow remote connections etc, SQL error 10060

I have used the Surface Area program and Allow remote connections is ticked

Cheers

Eugene

|||Did you had a look in the surface area for this particular instance ? These settings are configured per instance and therefore if you enabled remote connections for the default instance, it does not mean that it is enabled for the named instance as well.

HTH, jens K. Suessmeyer.

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

There are three things that you need to check for...

1) Insure remote connections is enabled for your database instance via the Surface Area Configuration tool for the named instance you are using. By default, SQL Express and DEV SKU has this disabled. Based on the error message posted, this seems to be the issue.

2) Since you are using a non-default (named) instance, this requires that the SQL Browser service to be configured and running properly.

3) Also on Windows XP SP2, you need to insure the firewall exceptions are set up properly. Here is a link with information on how to do this...

http://support.microsoft.com/default.aspx/kb/841249

Hope this helps,

Tom

This posting is provided AS IS with no warranties, and confers no rights.

Connecting to a default installation of MSDE on XP

On PC that has a default installation of MSDE and XP SP2, what ports
need to be open to allow remote connection to the MSDE?
hi,
mark@.sherwood.org.uk wrote:
> On PC that has a default installation of MSDE and XP SP2, what ports
> need to be open to allow remote connection to the MSDE?
a default instance requires TCP/IP 1433 port, while for named instance (with
dynamic port assignement) you have to check the assigned port using the
Server Network Utiliy (svrnetcn.exe) or inspecting the registry, say
HKLM\SOFTWARE\Microsoft\Microsoft SQL
Server\InstanceName\MSSQLServer\SuperSocketNetLib\ Tcp
TcpPort
and of course UDP 1434...
you can close UDP 1434 assigning a static port to the named instance, but
that requires definig server alias on the Client Network Utility
(cliconfg.exe) on each remote client...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I have temporariliy stopped the XP Firewall on the remote PC. Created
an alias in the Client Network Utility on the pc trying to connect to
the MSDE but the registration still fails it shows the following error
message.
SQL Server does not exist or access is denied,
ConnectionOpen(Connect()).
I am a memebr of the sys admin role and I have also tried as the SA
account both display the same error message.
|||hi,
mark@.sherwood.org.uk wrote:
> I have temporariliy stopped the XP Firewall on the remote PC. Created
> an alias in the Client Network Utility on the pc trying to connect to
> the MSDE but the registration still fails it shows the following error
> message.
> SQL Server does not exist or access is denied,
> ConnectionOpen(Connect()).
> I am a memebr of the sys admin role and I have also tried as the SA
> account both display the same error message.
this is a general MDAC message indicatin connection problem(s)... please
have a look at
http://support.microsoft.com/default...06&Product=sql
http://support.microsoft.com/default.aspx?kbid=841249
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Connecting a Cube from Excel 2007

Hi,

i am working with a XP-Client and try to connect to a WinServer2003, (SP2, AS2005) to access an AS2005-cube by Excel 2007. Creating a new connection, i can choose either connect via windows authentification or by entering a user/PW.

The first way (windows authentification) always works fine, but when i try to connect through an sql user, i run on an error at last. The connection works fine, i can select the desired cube but after the last "OK"-Button i get an error message like "Initialization of Data source failed".

the sql user should have admin right on the server.

Do i make sth. wrong?

SQL Server 2005 Analyisis Services Supports only Windows Authentication. (SQL Authentication is only possible if you connect to the SQL Server 2005 Database Engine)

So the username and password you want to enter must be a valid windows nt user with permission on the analysis services database. (check save password otherwise you get errors in excel)

HANNES

Connect to SSAS from SQL Management Studio

I'm trying to connect to an SSAS 2005 cube from my XP SP2 workstation. This is at a client's site & my workstation is not connected to their domain but they have given me a domain account & password that has access to the cube. My colleagues who are also running XP SP2 are able to browse to a UNC path on the SSAS server then when prompted enter the account & password. Then they go into SQL Management Studio to create a connection to the SSAS machine. But I can't locate anything different between our configurations. I'm also running Windows OneCare so I'm not sure if that may be the problem. Can you offer any suggestion please?

The trick with opening UNC share, entering credentials and then connecting to SSAS only works with NTLM authentication. Please make sure you are not on Kerberos. Also, it is important that you document the exact steps you do and exact outcomes (i.e. error messages if any etc) in order for the forum to help you.|||

I wasn't aware of that trick you mentioned. I would suggest one of the following:

1. Create yourself a shortcut with the following path:
C:\WINDOWS\SYSTEM32\RUNAS.EXE /net /user:TheirDomain\UserName "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe"
That will launch Mgmt Studio under the credentials of the right domain account (not the account you've logged onto your laptop). Then you should be able to connect to SSAS on their server.

2. An alternative is if they've got Microsoft VPN, if you VPN to their network, then you don't have to bother with the runas command. (This appears to work when using Microsoft VPN, but not Cisco VPN, for example.)

Connect to SQL Server 2005

I have installed two SQL Server 2005. One on Windows XP SP2 and another on
Windows Server 2003 SP1. I have shut down the firewall on both machine, but
I still failed to coonect each other. Both of them can connect to SQL Server
2000.
Does anyone know what wrong?
Since SQL 2005 is still in beta, you'll want to post this in the Community
Newsgroups:
http://communities.microsoft.com/new...r2005&slcid=us
--Brian
(Please reply to the newsgroups only.)
"Ryan Chen" <sadnut@.163.com> wrote in message
news:OozzaTpuFHA.1132@.TK2MSFTNGP10.phx.gbl...
>I have installed two SQL Server 2005. One on Windows XP SP2 and another on
>Windows Server 2003 SP1. I have shut down the firewall on both machine, but
>I still failed to coonect each other. Both of them can connect to SQL
>Server 2000.
> Does anyone know what wrong?
>
|||Run SQL Server Surface Area Configuration tool and then click on
"Surface Area Configuration for Services and Connections"
Then look under Database Engine, Remote Connection and insure that remote
TCP-IP is enabled.
I always forget to do this when I setup SQL 2005, it's quite annoying that
it defaults to off but this is part of our "surface area off by default as
much as possible" initiative.
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Ryan Chen" <sadnut@.163.com> wrote in message
news:OozzaTpuFHA.1132@.TK2MSFTNGP10.phx.gbl...
>I have installed two SQL Server 2005. One on Windows XP SP2 and another on
>Windows Server 2003 SP1. I have shut down the firewall on both machine, but
>I still failed to coonect each other. Both of them can connect to SQL
>Server 2000.
> Does anyone know what wrong?
>

Connect to SQL Server 2005

I have installed two SQL Server 2005. One on Windows XP SP2 and another on
Windows Server 2003 SP1. I have shut down the firewall on both machine, but
I still failed to coonect each other. Both of them can connect to SQL Server
2000.
Does anyone know what wrong?Since SQL 2005 is still in beta, you'll want to post this in the Community
Newsgroups:
http://communities.microsoft.com/ne...lcid=us

--Brian
(Please reply to the newsgroups only.)
"Ryan Chen" <sadnut@.163.com> wrote in message
news:OozzaTpuFHA.1132@.TK2MSFTNGP10.phx.gbl...
>I have installed two SQL Server 2005. One on Windows XP SP2 and another on
>Windows Server 2003 SP1. I have shut down the firewall on both machine, but
>I still failed to coonect each other. Both of them can connect to SQL
>Server 2000.
> Does anyone know what wrong?
>|||Run SQL Server Surface Area Configuration tool and then click on
"Surface Area Configuration for Services and Connections"
Then look under Database Engine, Remote Connection and insure that remote
TCP-IP is enabled.
I always forget to do this when I setup SQL 2005, it's quite annoying that
it defaults to off but this is part of our "surface area off by default as
much as possible" initiative.
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Ryan Chen" <sadnut@.163.com> wrote in message
news:OozzaTpuFHA.1132@.TK2MSFTNGP10.phx.gbl...
>I have installed two SQL Server 2005. One on Windows XP SP2 and another on
>Windows Server 2003 SP1. I have shut down the firewall on both machine, but
>I still failed to coonect each other. Both of them can connect to SQL
>Server 2000.
> Does anyone know what wrong?
>