SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 Old Forums
 CLOSED - SQL Server 2005/Yukon
 2005 modifies 2000
 Forum Locked
 Printer Friendly
Author Previous Topic Topic Next Topic  

SamC
White Water Yakist

USA
3467 Posts

Posted - 04/20/2006 :  20:24:38  Show Profile
I ran into repeatable problems installing 2005 on my testing server which had SQL 2000 running. DTS jobs which contained ActiveX scripts would fail. Recreating the jobs did no good.

Taking a peek at the file activity, it looks like SQL 2000 DTS is trying to find sqlResourceLoader.dll in the 2005 installation, and unsuccessfully. It's installed, but it isn't pathed correctly somehow.

Have other problems been reported with 2000 behaving badly after 2005 was installed?

jen
Flowing Fount of Yak Knowledge

Sweden
4110 Posts

Posted - 04/20/2006 :  23:18:08  Show Profile  Send jen a Yahoo! Message
yes...

it seems that some objects are overwritten by 2005 upon installation, i thought i did it differently

i wasn't able to connect to 2000, good thing it's development, so i had to uninstall both and reinstall 2000

also for clients, it does the same thing... so i'm avoiding having both on same machine, which is really a pain coz if i wanted to connect to 2005, i need to do it on the server, unless they'll issue me another workstation



--------------------
keeping it simple...
Go to Top of Page

eyechart
Flowing Fount of Yak Knowledge

USA
3575 Posts

Posted - 04/20/2006 :  23:31:26  Show Profile
I am running into issue with runing SQL2k5 on a cluster that also has SQL 2000 instances. I have an open ticket with microsoft to try and resolve it.

I'm starting to think that SQL 2005 sucks..



-ec
Go to Top of Page

SamC
White Water Yakist

USA
3467 Posts

Posted - 04/21/2006 :  00:14:29  Show Profile
quote:
Originally posted by jen

i wasn't able to connect to 2000, good thing it's development, so i had to uninstall both and reinstall 2000

also for clients, it does the same thing... so i'm avoiding having both on same machine, which is really a pain coz if i wanted to connect to 2005, i need to do it on the server, unless they'll issue me another workstation

I've got 'em both running on a testing server. I set 2005 to listen on port 1434, and connect using:

servername/SQL2005,1434

Both EM and SSMS work from my client workstation now.

It was h3ll getting there though.
Go to Top of Page

SamC
White Water Yakist

USA
3467 Posts

Posted - 04/21/2006 :  00:15:41  Show Profile
quote:
Originally posted by jen

it seems that some objects are overwritten by 2005 upon installation

Anything specific?
Go to Top of Page

SamC
White Water Yakist

USA
3467 Posts

Posted - 04/21/2006 :  00:16:09  Show Profile
quote:
Originally posted by eyechart

I am running into issue
What kind of issue?
Go to Top of Page

jen
Flowing Fount of Yak Knowledge

Sweden
4110 Posts

Posted - 04/21/2006 :  00:17:00  Show Profile  Send jen a Yahoo! Message
i guess it's expected to be that way, assuming it's a relatively 'new' product and not much on the forums...

it's ok if we start from scratch, no dependencies and all but when the manager starts pressuring you to give the go signal for the migration, well that sucks...



--------------------
keeping it simple...
Go to Top of Page

SamC
White Water Yakist

USA
3467 Posts

Posted - 04/21/2006 :  08:31:00  Show Profile
quote:
Originally posted by jen

it's ok if we start from scratch, no dependencies and all but when the manager starts pressuring you to give the go signal for the migration, well that sucks...

This may be an opportunity to request a separate server for the migration effort.
Go to Top of Page

jen
Flowing Fount of Yak Knowledge

Sweden
4110 Posts

Posted - 04/21/2006 :  10:16:56  Show Profile  Send jen a Yahoo! Message
Hi Sam,

can you share what hell you went through?

i'm still in hell though,
it's really weird, i was able to get it going for several days enough to test migrating objects from 2000 to 2005 but after the weekend (yes, it fell on friday or probably sat or sun ), keep getting connection error and had to go back to (local)\instance_name, until now...

for clients, vaguely, it says fatal error or something relative to that... i'll post the error once i've reinstalled and encounter it again

as for server, they are happy to purchase but if i don't smooth out the process then i'm

--------------------
keeping it simple...
Go to Top of Page

SamC
White Water Yakist

USA
3467 Posts

Posted - 04/21/2006 :  10:30:17  Show Profile
2005 modifies 2000's DTS scheduling. I found SQL 2000 will break unless 2000 Server Agent is STOPPED during 2005 installation.

At this time, I have no problems found running 2000 side by side with 2005. I have backups running in both, DTS tasks in 2000, and I am working on developing SSIS tasks for 2005 to replace the 2000 email task. (Anybody know how to email a recordset of email returned from a stored proc using SSIS?)

I hope to build confidence to cut over production in the next week or two.

I found no way to remotely connect to both 2000 and 2005 on the same port 1433 (even when specifying the instance). Instead, visit the 2005 configuration manager, Network Configuration, Protocols, Properties of TCP/IP, IP Addresses (Tab).

Set the last item "IP All" to port 1434 and set your intended IP address to 1434 also. I've no idea why both settings are required. Be sure to restart the 2005 service to make the change active. Check that your server firewall isn't blocking by telneting to IP:1434.

If you can connect locally with SSMS using a SQL username/password, that only verifies the u/p pair, not the TCP/IP as SSMS is using a memory connection locally.

When you login remotely, login using hostname\instancename,1434 in the SSMS login dialogue.

Now that it's working, I don't experience any problems, but when a login error occurs, there's not much information as to why. Keep plugging away at it.

And I'd be very interested in any specifics of any SQL server-side errors you encounter. I haven't seen any after resolving the installation and setup problems.

Sam
Go to Top of Page

eyechart
Flowing Fount of Yak Knowledge

USA
3575 Posts

Posted - 04/22/2006 :  15:16:11  Show Profile
quote:
Originally posted by SamC

quote:
Originally posted by eyechart

I am running into issue
What kind of issue?



the issue is that I cannot start our SQL 2000 up from the cluster any longer. I can start it from the services panel. connection through shared memory work, but not named pipes or tcp.

the only thing that changed recently is the addition of the recent security hotfixes (we did not add the mdac fix) and teh installation of SQL 2005 on another virtual host in the cluster.

everything worked after the security hotfixes (for certain), but the wheels have fallen off after trying to install SQL2K5 on this thing. the system is an HP DL385 64 bit running x64 windows, SQL 2000 32bit w/SP4 and a current hotfix.

this is is a test instance, so no real harm, but it is a little frustrating..


-ec
Go to Top of Page

eyechart
Flowing Fount of Yak Knowledge

USA
3575 Posts

Posted - 04/22/2006 :  17:48:51  Show Profile
quote:
Originally posted by eyechart

quote:
Originally posted by SamC

quote:
Originally posted by eyechart

I am running into issue
What kind of issue?



the issue is that I cannot start our SQL 2000 up from the cluster any longer. I can start it from the services panel. connection through shared memory work, but not named pipes or tcp.

the only thing that changed recently is the addition of the recent security hotfixes (we did not add the mdac fix) and teh installation of SQL 2005 on another virtual host in the cluster.

everything worked after the security hotfixes (for certain), but the wheels have fallen off after trying to install SQL2K5 on this thing. the system is an HP DL385 64 bit running x64 windows, SQL 2000 32bit w/SP4 and a current hotfix.

this is is a test instance, so no real harm, but it is a little frustrating..


-ec



I now have 2 separate tickets opened with microsoft. bottom line is, that SQL 2K5 kills your SQL2K clustered virtual hosts. There is no recovery at this point.



-ec
Go to Top of Page

eyechart
Flowing Fount of Yak Knowledge

USA
3575 Posts

Posted - 04/23/2006 :  00:27:35  Show Profile
I will post more details of the problems we are facing with SQL 2005 and SQL 2000 on the same cluster in this thread http://sqlteam.com/forums/topic.asp?TOPIC_ID=65096



-ec
Go to Top of Page

rony
Starting Member

Israel
2 Posts

Posted - 05/16/2006 :  01:36:50  Show Profile
Hi,
I have a question ,
can i install sql 2005 on a server with sql 2000 but with w2k server ?


Regards ,Rony
Go to Top of Page

mr_mist
Grunnio

United Kingdom
1870 Posts

Posted - 05/16/2006 :  04:12:41  Show Profile  Visit mr_mist's Homepage
quote:
Originally posted by SamC


I found no way to remotely connect to both 2000 and 2005 on the same port 1433 (even when specifying the instance).


I'm not sure why you would expect to be able to do this. Different apps can't share the same recieving port. One or t'other will have to be listening on a different port.

-------
Moo. :)
Go to Top of Page

rony
Starting Member

Israel
2 Posts

Posted - 05/16/2006 :  04:41:08  Show Profile
if i understand , it can be done .
by what SamC wrote .
and by what microsoft wrote http://msdn2.microsoft.com/en-us/library/ms181087.aspx
"Side-by-Side Installation with SQL Server 2000"
please correct me if i wrong .

Regards ,Rony
Go to Top of Page

mr_mist
Grunnio

United Kingdom
1870 Posts

Posted - 05/16/2006 :  05:36:33  Show Profile  Visit mr_mist's Homepage
AIUI, the SQL Browser does not mean that two instances share the same port. It means that the browser service listens for incoming connections and then redirects them to the correct port for each instance. The instances themselves would be dynamically or statically assigned to different port numbers as normal.

-------
Moo. :)
Go to Top of Page

SamC
White Water Yakist

USA
3467 Posts

Posted - 05/16/2006 :  07:41:23  Show Profile
quote:
Originally posted by SamC

I've got 'em both running on a testing server. I set 2005 to listen on port 1434, and connect using:

servername/SQL2005,1434

Both EM and SSMS work from my client workstation now.
Go to Top of Page
  Previous Topic Topic Next Topic  
 Forum Locked
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.12 seconds. Powered By: Snitz Forums 2000