"Sue Hoegemeier" wrote:

> That's the error you get when you try to connect to SQL
> Server 7 or earlier with SSMS. Double check the version on
> the other remote server when you connect with Query Analyzer
> using select @@version.
>
> -Sue
>
> On Wed, 26 Jul 2006 10:28:02 -0700, Janet
> <Janet@discussions.microsoft.com> wrote:
>
> >As background - in SSMS, I checked the sql native client connectivity and
> >tcpip is enabled, alias is listed with correct ip and port. Error is:
> >
> >===================================
> >
> >Cannot connect to CASCE.
> >
> >===================================
> >
> >This version of Microsoft SQL Server Management Studio can only be used to
> >connect to SQL Server 2000 and SQL Server 2005 servers. (ConnectionDlg)
> >
> >------------------------------
> >Program Location:
> >
> > at
> >Microsoft.SqlServer.Management.UI.ConnectionDlg.SqlServerType.Microsoft.SqlServer.Management.UI.ConnectionDlg.IConnectionValidator.CheckConnection(IDbConnection conn)
> > at
> >Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.CheckConnection()
> > at
> >Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectorThread()
> >
> >
> >
> >"Sue Hoegemeier" wrote:
> >
> >> What errors do you get?
> >>
> >> -Sue
> >>
> >> On Tue, 25 Jul 2006 06:47:02 -0700, Janet
> >> <Janet@discussions.microsoft.com> wrote:
> >>
> >> >I have a local server I just upgraded to 2005. Everything went well. But, I
> >> >also have a remote sql 2000 server I still need to connect to. Can't seem
> >> >to get the tcp/ip connection to old server to work. Go back to old 2000 tool
> >> >and it works fine, but I'd prefer to stay in one environment and migrate to
> >> >the new tool. Any ideas?
> >>
> >>
>