|
Home > Archive > MS SQL Server > November 2005 > SQL 2005 Dev. Management Studio cannot connect to 7.0 servers?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SQL 2005 Dev. Management Studio cannot connect to 7.0 servers?
|
|
| Whitey 2005-11-10, 9:23 am |
| TITLE: Connect to Server
------------------------------
Cannot connect to (servernameremoved).
------------------------------
ADDITIONAL INFORMATION:
This version of Microsoft SQL Server Management Studio can only be used to
connect to SQL Server 2000 and SQL Server 2005 servers. (ConnectionDlg)
------------------------------
BUTTONS:
OK
------------------------------
Our live server is still on 7. And it seems to have uninstalled Enterprise
Manager. C:\Program Files\Microsoft SQL Server\80\Tools\BINN
\SQL Server
Enterprise Manager.MSC is no longer there but most of the other files are,
fantastic, I'm so glad I've upgraded.
Other fun features: It seems to have lost my 20+ database connections
w/logins enterprise manager had and asks me to login again whenever I edit a
stored procedure.
| |
| Corey Bunch 2005-11-10, 9:23 am |
| I'm confused. Do you have a 7.0 instance and a 2005 instance on the
same machine (two instances)? Or did you upgrade in place, and now
only have a 2005 instance? I know it's not the same situation, but I
have both a 2000 instance and a 2005 named instance on the same box,
and all management tools are still there, including Enterprise manager.
Worst case scenario - can't you just stick the 7.0 cd in and reinstall
just enterprise manager?
2005 management studio definitely cannot connect to 7.0 servers -
you're correct.
Whitey wrote:
> TITLE: Connect to Server
> ------------------------------
>
> Cannot connect to (servernameremoved).
>
> ------------------------------
> ADDITIONAL INFORMATION:
>
> This version of Microsoft SQL Server Management Studio can only be used to
> connect to SQL Server 2000 and SQL Server 2005 servers. (ConnectionDlg)
>
> ------------------------------
> BUTTONS:
>
> OK
> ------------------------------
>
> Our live server is still on 7. And it seems to have uninstalled Enterprise
> Manager. C:\Program Files\Microsoft SQL Server\80\Tools\BINN
\SQL Server
> Enterprise Manager.MSC is no longer there but most of the other files are,
> fantastic, I'm so glad I've upgraded.
>
> Other fun features: It seems to have lost my 20+ database connections
> w/logins enterprise manager had and asks me to login again whenever I edit a
> stored procedure.
| |
| Whitey 2005-11-10, 1:23 pm |
| On my local development system, I just installed SQL 2005 Developer Edition,
the servers I connect to are a mix of 7 and 2000, the live SQL server for our
web sites is SQL 7.
I reinstalled SQL 2000 developer, open enterprise manager, and it is telling
me Data Source name not found and no default driver specified. I never used
a DSN for any of these, and ODBC Data Sources does not pull back a list of
drivers when I try to add one.
"Corey Bunch" wrote:
> I'm confused. Do you have a 7.0 instance and a 2005 instance on the
> same machine (two instances)? Or did you upgrade in place, and now
> only have a 2005 instance? I know it's not the same situation, but I
> have both a 2000 instance and a 2005 named instance on the same box,
> and all management tools are still there, including Enterprise manager.
> Worst case scenario - can't you just stick the 7.0 cd in and reinstall
> just enterprise manager?
>
> 2005 management studio definitely cannot connect to 7.0 servers -
> you're correct.
>
>
> Whitey wrote:
>
>
| |
| Whitey 2005-11-10, 8:23 pm |
| I had to fix my drivers this way:
open a command prompt
change directory to c:\windows\system32
type:
odbcconf /f odbcconf.rsp
"Whitey" wrote:
[color=darkred]
> On my local development system, I just installed SQL 2005 Developer Edition,
> the servers I connect to are a mix of 7 and 2000, the live SQL server for our
> web sites is SQL 7.
>
> I reinstalled SQL 2000 developer, open enterprise manager, and it is telling
> me Data Source name not found and no default driver specified. I never used
> a DSN for any of these, and ODBC Data Sources does not pull back a list of
> drivers when I try to add one.
>
> "Corey Bunch" wrote:
>
|
|
|
|
|