Can't connect to SQL Server 2005 Beta 2

I cannot connect to our SQL Server 2005 Beta 2 database server from my
machine. This is the error I get:
"A connection was successfully established with the server, but then an
error occurred during the login process. (provider: TCP Provider, error: 0 -
An existing connection was forcibly closed by the remote host.) (.Net
SqlClient Data Provider)"
Doesn't matter if I'm using Windows Authentication or Sql Server
Authentication.
I'm trying to connect to it with the April CTP management studio and
Business Intelligence Dev Studio.
Thanks,
Jason
Have you added your login to the 2005 server? Sorry for the low-level
question....
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"JasonP" <JasonP@.discussions.microsoft.com> wrote in message
news:AAF608B1-0CD3-4B7E-ABA9-B5CA0D058C6C@.microsoft.com...
> I cannot connect to our SQL Server 2005 Beta 2 database server from my
> machine. This is the error I get:
> "A connection was successfully established with the server, but then an
> error occurred during the login process. (provider: TCP Provider, error:
> 0 -
> An existing connection was forcibly closed by the remote host.) (.Net
> SqlClient Data Provider)"
> Doesn't matter if I'm using Windows Authentication or Sql Server
> Authentication.
> I'm trying to connect to it with the April CTP management studio and
> Business Intelligence Dev Studio.
> Thanks,
> Jason
|||Yes, I created specific users on that server other than sa to see if that
was the problem.
However, I have more information. The database I'm trying to access is a
Sql Server 2005 Beta 2 on Windows Server 2003. If I try to access the server
through another Sql Server Beta 2 client I can login using Sql Server
Authentication.
The machine I'm trying to access it with now currently has the latest Sql
Server 2005 April CTP with VS 2005 Beta 2 on it and cannot access the Beta 2
server.
Has anyone had any problems like this with the April CTP?
Thanks,
Jason
"Kevin3NF" wrote:

> Have you added your login to the 2005 server? Sorry for the low-level
> question....
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> www.experts-exchange.com - experts compete for points to answer your
> questions
>
> "JasonP" <JasonP@.discussions.microsoft.com> wrote in message
> news:AAF608B1-0CD3-4B7E-ABA9-B5CA0D058C6C@.microsoft.com...
>
>
|||Kevin;
I just installed SQL Server 2005 Beta 2 in a virtual pc running Windows
Server 2003 Enterprise Edition, also installed VS 2005 Beta 2 on an XP SP2
machine and can't connect to the SQL Server. I am getting the same error as
you.
Let me know if you got a fix for this.
Thanks,
M. Castellanos
"JasonP" wrote:
[vbcol=seagreen]
> Yes, I created specific users on that server other than sa to see if that
> was the problem.
> However, I have more information. The database I'm trying to access is a
> Sql Server 2005 Beta 2 on Windows Server 2003. If I try to access the server
> through another Sql Server Beta 2 client I can login using Sql Server
> Authentication.
> The machine I'm trying to access it with now currently has the latest Sql
> Server 2005 April CTP with VS 2005 Beta 2 on it and cannot access the Beta 2
> server.
> Has anyone had any problems like this with the April CTP?
> Thanks,
> Jason
>
> "Kevin3NF" wrote:
|||Beta 2 has expired. Since 7/1/2005, you won't be able to connect to it from
a machine that has another framework active. You can still use the tools on
the server itself, but you won't be able to use Help.
You will need to uninstall Beta 2 and install the CTP. This is a big
process which I am struggling with right now. I have been advised that the
entire server should be wiped and rebuilt from scratch. GRRR...
Graeme Martin
"MC" wrote:
[vbcol=seagreen]
> Kevin;
> I just installed SQL Server 2005 Beta 2 in a virtual pc running Windows
> Server 2003 Enterprise Edition, also installed VS 2005 Beta 2 on an XP SP2
> machine and can't connect to the SQL Server. I am getting the same error as
> you.
> Let me know if you got a fix for this.
> Thanks,
> --
> M. Castellanos
>
> "JasonP" wrote:
|||Thanks for the info.
M. Castellanos
"The Oracle" wrote:
[vbcol=seagreen]
> Beta 2 has expired. Since 7/1/2005, you won't be able to connect to it from
> a machine that has another framework active. You can still use the tools on
> the server itself, but you won't be able to use Help.
> You will need to uninstall Beta 2 and install the CTP. This is a big
> process which I am struggling with right now. I have been advised that the
> entire server should be wiped and rebuilt from scratch. GRRR...
> --
> Graeme Martin
>
> "MC" wrote:
|||OK, the process wasn't so bad, and I didn't need to wipe the server. But
there are few helps and 'gotchas' to be aware of.
1. Be sure to uninstall in the correct order. The last two SS items are the
Tools and the Native Client. Last of all is the Framework. Supposedly, you
can just run step 2 (below), and it will preserve many of your preferences.
I wanted a clean uninstall, so I went through Add/Remove Programs and
followed the steps.
2. The CTP has a 'Setup Tools' directory. Run the sqlbuw.exe located in the
Build Uninstall Wizard subdirectory after you have uninstalled everything.
This should clean up any remaining stuff.
3. After you install CTP, check the following info in another post I
recently made:
http://www.microsoft.com/communities...261&sloc=en-us
Good luck! SQL Server is a great product and this new version is worth the
effort.
Graeme Martin
"MC" wrote:
[vbcol=seagreen]
> Thanks for the info.
> --
> M. Castellanos
>
> "The Oracle" wrote:

Can't connect to SQL Server 2005 Beta 2

I cannot connect to our SQL Server 2005 Beta 2 database server from my
machine. This is the error I get:
"A connection was successfully established with the server, but then an
error occurred during the login process. (provider: TCP Provider, error: 0 -
An existing connection was forcibly closed by the remote host.) (.Net
SqlClient Data Provider)"
Doesn't matter if I'm using Windows Authentication or Sql Server
Authentication.
I'm trying to connect to it with the April CTP management studio and
Business Intelligence Dev Studio.
Thanks,
JasonHave you added your login to the 2005 server? Sorry for the low-level
question....
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"JasonP" <JasonP@.discussions.microsoft.com> wrote in message
news:AAF608B1-0CD3-4B7E-ABA9-B5CA0D058C6C@.microsoft.com...
> I cannot connect to our SQL Server 2005 Beta 2 database server from my
> machine. This is the error I get:
> "A connection was successfully established with the server, but then an
> error occurred during the login process. (provider: TCP Provider, error:
> 0 -
> An existing connection was forcibly closed by the remote host.) (.Net
> SqlClient Data Provider)"
> Doesn't matter if I'm using Windows Authentication or Sql Server
> Authentication.
> I'm trying to connect to it with the April CTP management studio and
> Business Intelligence Dev Studio.
> Thanks,
> Jason|||Yes, I created specific users on that server other than sa to see if that
was the problem.
However, I have more information. The database I'm trying to access is a
Sql Server 2005 Beta 2 on Windows Server 2003. If I try to access the serve
r
through another Sql Server Beta 2 client I can login using Sql Server
Authentication.
The machine I'm trying to access it with now currently has the latest Sql
Server 2005 April CTP with VS 2005 Beta 2 on it and cannot access the Beta 2
server.
Has anyone had any problems like this with the April CTP?
Thanks,
Jason
"Kevin3NF" wrote:

> Have you added your login to the 2005 server? Sorry for the low-level
> question....
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> www.experts-exchange.com - experts compete for points to answer your
> questions
>
> "JasonP" <JasonP@.discussions.microsoft.com> wrote in message
> news:AAF608B1-0CD3-4B7E-ABA9-B5CA0D058C6C@.microsoft.com...
>
>|||Jason,
Did you find a solution to your problem then? I am having the same issues,
and looking for an answer.
Could you maybe post your solution, please?
Thanks
Rigalo|||Kevin;
I just installed SQL Server 2005 Beta 2 in a virtual pc running Windows
Server 2003 Enterprise Edition, also installed VS 2005 Beta 2 on an XP SP2
machine and can't connect to the SQL Server. I am getting the same error as
you.
Let me know if you got a fix for this.
Thanks,
M. Castellanos
"JasonP" wrote:
[vbcol=seagreen]
> Yes, I created specific users on that server other than sa to see if that
> was the problem.
> However, I have more information. The database I'm trying to access is a
> Sql Server 2005 Beta 2 on Windows Server 2003. If I try to access the ser
ver
> through another Sql Server Beta 2 client I can login using Sql Server
> Authentication.
> The machine I'm trying to access it with now currently has the latest Sql
> Server 2005 April CTP with VS 2005 Beta 2 on it and cannot access the Beta
2
> server.
> Has anyone had any problems like this with the April CTP?
> Thanks,
> Jason
>
> "Kevin3NF" wrote:
>|||Beta 2 has expired. Since 7/1/2005, you won't be able to connect to it from
a machine that has another framework active. You can still use the tools on
the server itself, but you won't be able to use Help.
You will need to uninstall Beta 2 and install the CTP. This is a big
process which I am struggling with right now. I have been advised that the
entire server should be wiped and rebuilt from scratch. GRRR...
Graeme Martin
"MC" wrote:
[vbcol=seagreen]
> Kevin;
> I just installed SQL Server 2005 Beta 2 in a virtual pc running Windows
> Server 2003 Enterprise Edition, also installed VS 2005 Beta 2 on an XP SP2
> machine and can't connect to the SQL Server. I am getting the same error a
s
> you.
> Let me know if you got a fix for this.
> Thanks,
> --
> M. Castellanos
>
> "JasonP" wrote:
>|||Thanks for the info.
M. Castellanos
"The Oracle" wrote:
[vbcol=seagreen]
> Beta 2 has expired. Since 7/1/2005, you won't be able to connect to it fr
om
> a machine that has another framework active. You can still use the tools
on
> the server itself, but you won't be able to use Help.
> You will need to uninstall Beta 2 and install the CTP. This is a big
> process which I am struggling with right now. I have been advised that th
e
> entire server should be wiped and rebuilt from scratch. GRRR...
> --
> Graeme Martin
>
> "MC" wrote:
>|||OK, the process wasn't so bad, and I didn't need to wipe the server. But
there are few helps and 'gotchas' to be aware of.
1. Be sure to uninstall in the correct order. The last two SS items are the
Tools and the Native Client. Last of all is the Framework. Supposedly, you
can just run step 2 (below), and it will preserve many of your preferences.
I wanted a clean uninstall, so I went through Add/Remove Programs and
followed the steps.
2. The CTP has a 'Setup Tools' directory. Run the sqlbuw.exe located in the
Build Uninstall Wizard subdirectory after you have uninstalled everything.
This should clean up any remaining stuff.
3. After you install CTP, check the following info in another post I
recently made:
http://www.microsoft.com/communitie...3261&sloc=en-us
Good luck! SQL Server is a great product and this new version is worth the
effort.
--
Graeme Martin
"MC" wrote:
[vbcol=seagreen]
> Thanks for the info.
> --
> M. Castellanos
>
> "The Oracle" wrote:
>

Can't connect to SQL 2005

Hi,
I just installed MSDE 2005 (or, rather, whatever it's called now) on my
machine. I'm trying to connect to it using Enterprise Manager, but I
keep getting Unable to connect/connection refused messages.
I've tried giving it my machine name, the word (local), localhost,
127.0.0.1, my machine's IP... nothing. I've also tried all those
permutations using cliconfg.exe, with the same results.
I ran the SQL Manager plug-in, and it shows that SQL Server is indeed
running. Also I tried doing an ODBCPING against it, with the following
errors:
SQLState: 08001 Native Error: 17
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL
Server
does not exist or access denied.
SQLState: 01000 Native Error: 1326
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionOpen (Connect()).
Any recommendations on a next step to try?If you're trying to run the EM for 2000, it won't work. Not supported.
"Scott McNair" <scott.mcnair@.sfmco.takethispartout.com> wrote in message
news:Xns95D7AB2AE2D3Bsfmco@.207.46.248.16...
> Hi,
> I just installed MSDE 2005 (or, rather, whatever it's called now) on my
> machine. I'm trying to connect to it using Enterprise Manager, but I
> keep getting Unable to connect/connection refused messages.
> I've tried giving it my machine name, the word (local), localhost,
> 127.0.0.1, my machine's IP... nothing. I've also tried all those
> permutations using cliconfg.exe, with the same results.
> I ran the SQL Manager plug-in, and it shows that SQL Server is indeed
> running. Also I tried doing an ODBCPING against it, with the following
> errors:
> SQLState: 08001 Native Error: 17
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQ
L Server
> does not exist or access denied.
> SQLState: 01000 Native Error: 1326
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]
> ConnectionOpen (Connect()).
> Any recommendations on a next step to try?|||Derrick Leggett wrote:
> If you're trying to run the EM for 2000, it won't work. Not supported.
>
> "Scott McNair" <scott.mcnair@.sfmco.takethispartout.com> wrote in message
> news:Xns95D7AB2AE2D3Bsfmco@.207.46.248.16...
>
>
>
What about setting up an ODBC System DSN? Shouldn't this be supported
through the SQL Native Client? I get pretty much the same errors when
trying to do that.

Can't connect to SQL 2005

Hi,
I just installed MSDE 2005 (or, rather, whatever it's called now) on my
machine. I'm trying to connect to it using Enterprise Manager, but I
keep getting Unable to connect/connection refused messages.
I've tried giving it my machine name, the word (local), localhost,
127.0.0.1, my machine's IP... nothing. I've also tried all those
permutations using cliconfg.exe, with the same results.
I ran the SQL Manager plug-in, and it shows that SQL Server is indeed
running. Also I tried doing an ODBCPING against it, with the following
errors:
SQLState: 08001 Native Error: 17
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
does not exist or access denied.
SQLState: 01000 Native Error: 1326
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionOpen (Connect()).
Any recommendations on a next step to try?
If you're trying to run the EM for 2000, it won't work. Not supported.
"Scott McNair" <scott.mcnair@.sfmco.takethispartout.com> wrote in message
news:Xns95D7AB2AE2D3Bsfmco@.207.46.248.16...
> Hi,
> I just installed MSDE 2005 (or, rather, whatever it's called now) on my
> machine. I'm trying to connect to it using Enterprise Manager, but I
> keep getting Unable to connect/connection refused messages.
> I've tried giving it my machine name, the word (local), localhost,
> 127.0.0.1, my machine's IP... nothing. I've also tried all those
> permutations using cliconfg.exe, with the same results.
> I ran the SQL Manager plug-in, and it shows that SQL Server is indeed
> running. Also I tried doing an ODBCPING against it, with the following
> errors:
> SQLState: 08001 Native Error: 17
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
> does not exist or access denied.
> SQLState: 01000 Native Error: 1326
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]
> ConnectionOpen (Connect()).
> Any recommendations on a next step to try?
|||Derrick Leggett wrote:
> If you're trying to run the EM for 2000, it won't work. Not supported.
>
> "Scott McNair" <scott.mcnair@.sfmco.takethispartout.com> wrote in message
> news:Xns95D7AB2AE2D3Bsfmco@.207.46.248.16...
>
>
What about setting up an ODBC System DSN? Shouldn't this be supported
through the SQL Native Client? I get pretty much the same errors when
trying to do that.