Hello all...
Win2k3 enterprise
SQL 2000
2 nodes
I had 2 instances of SQL installed. I had to run setup to remove clustered
SQL so I could break the disk array and make it larger.
Now, I install instance 1 on node 1 just fine.
But when I run setup on node 2 to install instance 2, it tells me that
instance name already exists.
I thought when I "un-clustered" SQL that both instances would have been
removed. I can see both instance names in C:\program files\Microsoft sql
server\
How do I go about getting rid of the second instance name now, so I can
reinstall it?
Thanks in advance.
Jeff
Hi Jeff,
I would first try to uninstall the second instance the regular way i.e using the setup CD and choosing uninstall (the same way you uninstalled the first instance). If this doesn't work then you will need to manually uninstall
it. For more info, review
HOW TO: Manually Remove SQL Server 2000 Default, Named, or Virtual Instance
http://support.microsoft.com/?kbid=290991
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Thank you Uttam,
I had tried the setup cd and it does not recognize the instance for
uninstall (only when I go to install the instance...go figure). But I did
not find the article you mention, so I will try that.
Jeff
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:RaXEsKppEHA.752@.cpmsftngxa06.phx.gbl...
> Hi Jeff,
> I would first try to uninstall the second instance the regular way i.e
using the setup CD and choosing uninstall (the same way you uninstalled the
first instance). If this doesn't work then you will need to manually
uninstall
> it. For more info, review
> HOW TO: Manually Remove SQL Server 2000 Default, Named, or Virtual
Instance
> http://support.microsoft.com/?kbid=290991
> HTH,
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
Showing posts with label win2k3. Show all posts
Showing posts with label win2k3. Show all posts
Friday, March 30, 2012
Friday, March 9, 2012
Installing SQL Server 2005
Hi,
During the installtion of SQL Server 2005 (Win2k3 SP2) the msxml setup fail. When i try to install manually the msxml i get the error "the system administrator has set policies to prevent this installation". I'm the machine administrator.
Someone can help me?
hi pedrorocha,
i get the same problem on windows xp. i still dont know how to solve this. with all the changes i have made to the registery to try and get this right. i am thankful the registery still works. lol. have you had any luck in finding an answer?
regards,
paul
|||I am getting the same problem, here is the link to a post that has the exact error message and some of the work I have been doing on the problem. (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2078708&SiteID=1&mode=1)
Installing SQL Server 2005
Hi,
During the installtion of SQL Server 2005 (Win2k3 SP2) the msxml setup fail. When i try to install manually the msxml i get the error "the system administrator has set policies to prevent this installation". I'm the machine administrator.
Someone can help me?
hi pedrorocha,
i get the same problem on windows xp. i still dont know how to solve this. with all the changes i have made to the registery to try and get this right. i am thankful the registery still works. lol. have you had any luck in finding an answer?
regards,
paul
|||I am getting the same problem, here is the link to a post that has the exact error message and some of the work I have been doing on the problem. (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2078708&SiteID=1&mode=1)
Installing SQL Server 2005
Hi,
During the installtion of SQL Server 2005 (Win2k3 SP2) the msxml setup fail. When i try to install manually the msxml i get the error "the system administrator has set policies to prevent this installation". I'm the machine administrator.
Someone can help me?
hi pedrorocha,
i get the same problem on windows xp. i still dont know how to solve this. with all the changes i have made to the registery to try and get this right. i am thankful the registery still works. lol. have you had any luck in finding an answer?
regards,
paul
|||I am getting the same problem, here is the link to a post that has the exact error message and some of the work I have been doing on the problem. (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2078708&SiteID=1&mode=1)
Sunday, February 19, 2012
Installing SQL 2000 On active/active cluster
I am trying to install SQL 2000 Ent on a Win2k3 cluster.
I have check both local and domain privlages and they are good.
I have performed MS work around so SQL sp2 and below can be installed on win2k3.
And I keep getting the following error during install...
An error occurred while creating virtual server resources for
clustering.Cluster specific registry entries couldn't be written.
Does anybody have any ideas?Check the privilages for the service account and the Account in which you logged in for Installation has folloing privilages .
Part of Local Admin
In Local Policy
1. Act as part of operating system
2. Log on as service
Make sure in the services :Remote registry service is up|||Privlages are good and remote registry service is running !|||Did you manage to resolve this issue? Did you get any USEFULL help from Microsoft support? Please post a few words of wisdom if so.
We have exactly the same problem and I've been struggling with it for a few weeks. Any help/advice is welcome.
I use SQL 2000 EE SP3 install (i.e with SP3 already included in installation) and still get the same error: "cluster-specific registry could not be written". All the simptoms are the same. I can install single-node virtual server, but if I try to install on both-nodes I've got mentioned message. The same happens if I try add second node to successfully installed single-node virtual server.|||My issue ended up being security on the cluster was to tight.
Once I loosened my security policies it started working fine.
Specifically the registry was being locked down by a Windows 2000 DC which does'nt have all the proper setting that Windows 2003 has.
I eventually upgraded the DC to 2003 to help with this matter.
I have check both local and domain privlages and they are good.
I have performed MS work around so SQL sp2 and below can be installed on win2k3.
And I keep getting the following error during install...
An error occurred while creating virtual server resources for
clustering.Cluster specific registry entries couldn't be written.
Does anybody have any ideas?Check the privilages for the service account and the Account in which you logged in for Installation has folloing privilages .
Part of Local Admin
In Local Policy
1. Act as part of operating system
2. Log on as service
Make sure in the services :Remote registry service is up|||Privlages are good and remote registry service is running !|||Did you manage to resolve this issue? Did you get any USEFULL help from Microsoft support? Please post a few words of wisdom if so.
We have exactly the same problem and I've been struggling with it for a few weeks. Any help/advice is welcome.
I use SQL 2000 EE SP3 install (i.e with SP3 already included in installation) and still get the same error: "cluster-specific registry could not be written". All the simptoms are the same. I can install single-node virtual server, but if I try to install on both-nodes I've got mentioned message. The same happens if I try add second node to successfully installed single-node virtual server.|||My issue ended up being security on the cluster was to tight.
Once I loosened my security policies it started working fine.
Specifically the registry was being locked down by a Windows 2000 DC which does'nt have all the proper setting that Windows 2003 has.
I eventually upgraded the DC to 2003 to help with this matter.
Installing SP4 on New node in cluster on Win2K3
We have a single node cluster using SQL2K EE running on Win2K EE, and this
has been running fine for a year or so. We finally have our new data centre
completed, and the additional hardware installed for us to install the second
node.
1) I installed Cluster services and added the second node to the cluster.
2) Ran COMClust to add DTC as a cluster resource
3) On the Active Node installed SQL2K, and selected advanced options,
Maintain SQL Server . . . .
4) Checked SQL Server resources in Cluster Manager, every thing looks good.
5) Tried to install SP4 from the new passive node - Failed doesn't own
resources in the Cluster
6) Tried installing SP4 from the active node . . . Got a bit further but the
install fails with a 'Setup was unable to complete the operation on all nodes
in the cluster'
At this point I am really stumped Looking at the SQLSP.log file it ends with
16:38:12 Begin SDPassword Dialog
16:38:12 Begin: CheckSAPassword
16:38:12 WARNING : No Blank SA Pwd
16:38:12 End: CheckSAPassword
16:38:12 Begin: SdShowSp3WrngDlg
and searching the net threw up a reference to this
http://support.microsoft.com/kb/815431/] KB article. Although this is not
strictly relevant I am wondering if there is an issue with installing a non
SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
what SP level its at and rejecting it as it doesn't have SP3 Installed.
So then What I did, was to try failing the cluster over so that I could
apply the fix from the new node. While the cluster group fails over, the SQL
group makes and attempt, but then SQL Server fails to start and it all fails
back to the other node.
I then removed SQL Server (from the active node) on the Passive node.
Rebooted the new passive node, and Installed SQL2K SP3a on the new node
successfully. I then tried to install SP4 (From the Active Node), and that
failed with the same error.
Any one have any Ideas?
Regards
Tony
Slipstream sql server sp4 and then try to do the install from the active
node. Also make sure that nobody else is logged onto the active and passive
nodes.
AS
"BC DBA" wrote:
> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data centre
> completed, and the additional hardware installed for us to install the second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but the
> install fails with a 'Setup was unable to complete the operation on all nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the SQL
> group makes and attempt, but then SQL Server fails to start and it all fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony
|||16:38:12 Begin: SdShowSp3WrngDlg
Yes, this is your problem. However, you've indicated that you are running
on Win2K EE, which doesn't exist (only Advanced Server), plus, this security
dialog only presents itself on a Windows Server 2003.
So, let's assume that you are running Windows 2000 Advanced Server on the
active (original) node and Windows Server 2003 EE on the new node.
Your steps through the installation process is correct; however, you will
need to get the new node to the same SP level as the old before the cluster
will successfully move resources to the new node.
There are three issues. The dialog above requires you to apply SP3 or later
before resources will run on new node; however, there is a bug in the SP4
installation package that misreads the new 4 digit Build number 2039 as 203
or 039, both of which are less than the 760 Build for SP3.
You must run service packs from the node that currently owns the cluster
resources, and since you cannot move resources to the new node yet, you must
reapply SP3 on the active (original) node. The installation will detect
that it will be a Binary Only installation to the new node.
Lastly, there is one other security issue in that until the new node has
been updated to SP3, TCP/IP protocol has been disabled. To work around this
issue, on BOTH cluster nodes, you must create NAMED PIPE aliases to the
Virtual SQL Server instance. Since the RTM installation uses this protocol,
this issue does not occur, but it does for any SP installations.
Once SP3 has been applied, you will still not be able to move resources to
new node. You must reapply SP4 plus any additional hot fixes. If you use
AWE, you will definitely want to apply the 2040 HF; moreover, you may want
to consider applying the latest publicly available HF, as it is the most
current build supported, Build 2187.
After this, you should be able to move resources successfully between both
nodes; however, Microsoft only limitedly supports mixed cluster
environments. At this point, you should uninstall the original node from
the cluster, evict the node, and rebuild it as a Windows Server 2003
installation. Then, you will need to follow the procedures above to
reintroduce this node as a clustered member. (As an aside, on Win2K3, you
do not have to run the COMCLUST utility anymore).
One final word of advice, SQL Server 2000 mainstream support expires in
April 2008. You should seriously consider upgrading to SQL Server 2005 as
soon as possible. Moreover, CTP2 for SQL Server 2008 was just released in
this month, with a target EOY 2007 1st QTR 2008 launch expectation, which
means even SS2K5 mainstream support does not have a long expected lifespan.
So, get moving.
Sincerely,
Anthony Thomas
"BC DBA" <BCDBA@.discussions.microsoft.com> wrote in message
news:88FBFA1A-2239-4E19-833F-83A55858ACCC@.microsoft.com...
> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data
centre
> completed, and the additional hardware installed for us to install the
second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks
good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but
the
> install fails with a 'Setup was unable to complete the operation on all
nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends
with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a
non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to
see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the
SQL
> group makes and attempt, but then SQL Server fails to start and it all
fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony
has been running fine for a year or so. We finally have our new data centre
completed, and the additional hardware installed for us to install the second
node.
1) I installed Cluster services and added the second node to the cluster.
2) Ran COMClust to add DTC as a cluster resource
3) On the Active Node installed SQL2K, and selected advanced options,
Maintain SQL Server . . . .
4) Checked SQL Server resources in Cluster Manager, every thing looks good.
5) Tried to install SP4 from the new passive node - Failed doesn't own
resources in the Cluster
6) Tried installing SP4 from the active node . . . Got a bit further but the
install fails with a 'Setup was unable to complete the operation on all nodes
in the cluster'
At this point I am really stumped Looking at the SQLSP.log file it ends with
16:38:12 Begin SDPassword Dialog
16:38:12 Begin: CheckSAPassword
16:38:12 WARNING : No Blank SA Pwd
16:38:12 End: CheckSAPassword
16:38:12 Begin: SdShowSp3WrngDlg
and searching the net threw up a reference to this
http://support.microsoft.com/kb/815431/] KB article. Although this is not
strictly relevant I am wondering if there is an issue with installing a non
SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
what SP level its at and rejecting it as it doesn't have SP3 Installed.
So then What I did, was to try failing the cluster over so that I could
apply the fix from the new node. While the cluster group fails over, the SQL
group makes and attempt, but then SQL Server fails to start and it all fails
back to the other node.
I then removed SQL Server (from the active node) on the Passive node.
Rebooted the new passive node, and Installed SQL2K SP3a on the new node
successfully. I then tried to install SP4 (From the Active Node), and that
failed with the same error.
Any one have any Ideas?
Regards
Tony
Slipstream sql server sp4 and then try to do the install from the active
node. Also make sure that nobody else is logged onto the active and passive
nodes.
AS
"BC DBA" wrote:
> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data centre
> completed, and the additional hardware installed for us to install the second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but the
> install fails with a 'Setup was unable to complete the operation on all nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the SQL
> group makes and attempt, but then SQL Server fails to start and it all fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony
|||16:38:12 Begin: SdShowSp3WrngDlg
Yes, this is your problem. However, you've indicated that you are running
on Win2K EE, which doesn't exist (only Advanced Server), plus, this security
dialog only presents itself on a Windows Server 2003.
So, let's assume that you are running Windows 2000 Advanced Server on the
active (original) node and Windows Server 2003 EE on the new node.
Your steps through the installation process is correct; however, you will
need to get the new node to the same SP level as the old before the cluster
will successfully move resources to the new node.
There are three issues. The dialog above requires you to apply SP3 or later
before resources will run on new node; however, there is a bug in the SP4
installation package that misreads the new 4 digit Build number 2039 as 203
or 039, both of which are less than the 760 Build for SP3.
You must run service packs from the node that currently owns the cluster
resources, and since you cannot move resources to the new node yet, you must
reapply SP3 on the active (original) node. The installation will detect
that it will be a Binary Only installation to the new node.
Lastly, there is one other security issue in that until the new node has
been updated to SP3, TCP/IP protocol has been disabled. To work around this
issue, on BOTH cluster nodes, you must create NAMED PIPE aliases to the
Virtual SQL Server instance. Since the RTM installation uses this protocol,
this issue does not occur, but it does for any SP installations.
Once SP3 has been applied, you will still not be able to move resources to
new node. You must reapply SP4 plus any additional hot fixes. If you use
AWE, you will definitely want to apply the 2040 HF; moreover, you may want
to consider applying the latest publicly available HF, as it is the most
current build supported, Build 2187.
After this, you should be able to move resources successfully between both
nodes; however, Microsoft only limitedly supports mixed cluster
environments. At this point, you should uninstall the original node from
the cluster, evict the node, and rebuild it as a Windows Server 2003
installation. Then, you will need to follow the procedures above to
reintroduce this node as a clustered member. (As an aside, on Win2K3, you
do not have to run the COMCLUST utility anymore).
One final word of advice, SQL Server 2000 mainstream support expires in
April 2008. You should seriously consider upgrading to SQL Server 2005 as
soon as possible. Moreover, CTP2 for SQL Server 2008 was just released in
this month, with a target EOY 2007 1st QTR 2008 launch expectation, which
means even SS2K5 mainstream support does not have a long expected lifespan.
So, get moving.
Sincerely,
Anthony Thomas
"BC DBA" <BCDBA@.discussions.microsoft.com> wrote in message
news:88FBFA1A-2239-4E19-833F-83A55858ACCC@.microsoft.com...
> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data
centre
> completed, and the additional hardware installed for us to install the
second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks
good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but
the
> install fails with a 'Setup was unable to complete the operation on all
nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends
with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a
non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to
see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the
SQL
> group makes and attempt, but then SQL Server fails to start and it all
fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony
installing SP4 for SQL 2000 on a cluster node
Hello,
I recently added a new win2k3 node to an existing SQL cluster and installed
SQL Server 2000. The SQL installation for the new node was performed from
the active node.
I also installed SP4 from the active node. However, I am having SQL
connectivity issues when I fail over to the new node. I noticed that I get
the following event log on the new node. It thinks that SP4 is not installed
although it is. Does anyone know if SP4 should be installed from the passive
node (the new node)? Does it matter which node we run the SP4 installation?
Thank-you,
WG
Event Type:Information
Event Source:MSSQLSERVER/MSDE
Event Category:None
Event ID:1
Date:12/3/2007
Time:3:02:41 PM
User:N/A
Computer:EAGNMNST18C
Description:
You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
Server 2000 Desktop Engine (also called MSDE) that has known security
vulnerabilities when used in conjunction with the Microsoft Windows Server
2003 family. To reduce your computer's vulnerability to certain virus
attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE,
or both have been disabled. To enable these ports, you must install a patch,
or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
http://www.microsoft.com/sql/downloads/default.asp
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Take a look at this page and ensure you followed the right direction.
[url]http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_clu ster[/url]
Ekrem ?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
> Hello,
> I recently added a new win2k3 node to an existing SQL cluster and
> installed
> SQL Server 2000. The SQL installation for the new node was performed from
> the active node.
> I also installed SP4 from the active node. However, I am having SQL
> connectivity issues when I fail over to the new node. I noticed that I
> get
> the following event log on the new node. It thinks that SP4 is not
> installed
> although it is. Does anyone know if SP4 should be installed from the
> passive
> node (the new node)? Does it matter which node we run the SP4
> installation?
> Thank-you,
> WG
> Event Type: Information
> Event Source: MSSQLSERVER/MSDE
> Event Category: None
> Event ID: 1
> Date: 12/3/2007
> Time: 3:02:41 PM
> User: N/A
> Computer: EAGNMNST18C
> Description:
> You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
> Server 2000 Desktop Engine (also called MSDE) that has known security
> vulnerabilities when used in conjunction with the Microsoft Windows Server
> 2003 family. To reduce your computer's vulnerability to certain virus
> attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
> MSDE,
> or both have been disabled. To enable these ports, you must install a
> patch,
> or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
> http://www.microsoft.com/sql/downloads/default.asp
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
|||Thank you!
I actually came across this article and it is helpful.
Could you tell me what is the "database upgrade script"? The article says,
for my scenario, I must run "the databse upgrade script".
Thanks,
WG
"Ekrem ?nsoy" wrote:
> Take a look at this page and ensure you followed the right direction.
> [url]http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_clu ster[/url]
> --
> Ekrem ?nsoy
>
> "Walid" <Walid@.discussions.microsoft.com> wrote in message
> news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
>
|||I believe it must be talking about the upgrading your database scripts that
you used to be using before SP4 is apllied.
Ekrem ?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:AE628F6C-F06F-4DBF-B36D-0D5563B1D110@.microsoft.com...[vbcol=seagreen]
> Thank you!
> I actually came across this article and it is helpful.
> Could you tell me what is the "database upgrade script"? The article
> says,
> for my scenario, I must run "the databse upgrade script".
> Thanks,
> WG
> "Ekrem ?nsoy" wrote:
I recently added a new win2k3 node to an existing SQL cluster and installed
SQL Server 2000. The SQL installation for the new node was performed from
the active node.
I also installed SP4 from the active node. However, I am having SQL
connectivity issues when I fail over to the new node. I noticed that I get
the following event log on the new node. It thinks that SP4 is not installed
although it is. Does anyone know if SP4 should be installed from the passive
node (the new node)? Does it matter which node we run the SP4 installation?
Thank-you,
WG
Event Type:Information
Event Source:MSSQLSERVER/MSDE
Event Category:None
Event ID:1
Date:12/3/2007
Time:3:02:41 PM
User:N/A
Computer:EAGNMNST18C
Description:
You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
Server 2000 Desktop Engine (also called MSDE) that has known security
vulnerabilities when used in conjunction with the Microsoft Windows Server
2003 family. To reduce your computer's vulnerability to certain virus
attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE,
or both have been disabled. To enable these ports, you must install a patch,
or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
http://www.microsoft.com/sql/downloads/default.asp
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Take a look at this page and ensure you followed the right direction.
[url]http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_clu ster[/url]
Ekrem ?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
> Hello,
> I recently added a new win2k3 node to an existing SQL cluster and
> installed
> SQL Server 2000. The SQL installation for the new node was performed from
> the active node.
> I also installed SP4 from the active node. However, I am having SQL
> connectivity issues when I fail over to the new node. I noticed that I
> get
> the following event log on the new node. It thinks that SP4 is not
> installed
> although it is. Does anyone know if SP4 should be installed from the
> passive
> node (the new node)? Does it matter which node we run the SP4
> installation?
> Thank-you,
> WG
> Event Type: Information
> Event Source: MSSQLSERVER/MSDE
> Event Category: None
> Event ID: 1
> Date: 12/3/2007
> Time: 3:02:41 PM
> User: N/A
> Computer: EAGNMNST18C
> Description:
> You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
> Server 2000 Desktop Engine (also called MSDE) that has known security
> vulnerabilities when used in conjunction with the Microsoft Windows Server
> 2003 family. To reduce your computer's vulnerability to certain virus
> attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
> MSDE,
> or both have been disabled. To enable these ports, you must install a
> patch,
> or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
> http://www.microsoft.com/sql/downloads/default.asp
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
|||Thank you!
I actually came across this article and it is helpful.
Could you tell me what is the "database upgrade script"? The article says,
for my scenario, I must run "the databse upgrade script".
Thanks,
WG
"Ekrem ?nsoy" wrote:
> Take a look at this page and ensure you followed the right direction.
> [url]http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_clu ster[/url]
> --
> Ekrem ?nsoy
>
> "Walid" <Walid@.discussions.microsoft.com> wrote in message
> news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
>
|||I believe it must be talking about the upgrading your database scripts that
you used to be using before SP4 is apllied.
Ekrem ?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:AE628F6C-F06F-4DBF-B36D-0D5563B1D110@.microsoft.com...[vbcol=seagreen]
> Thank you!
> I actually came across this article and it is helpful.
> Could you tell me what is the "database upgrade script"? The article
> says,
> for my scenario, I must run "the databse upgrade script".
> Thanks,
> WG
> "Ekrem ?nsoy" wrote:
installing SP4 for SQL 2000 on a cluster node
Hello,
I recently added a new win2k3 node to an existing SQL cluster and installed
SQL Server 2000. The SQL installation for the new node was performed from
the active node.
I also installed SP4 from the active node. However, I am having SQL
connectivity issues when I fail over to the new node. I noticed that I get
the following event log on the new node. It thinks that SP4 is not installe
d
although it is. Does anyone know if SP4 should be installed from the passiv
e
node (the new node)? Does it matter which node we run the SP4 installation?
Thank-you,
WG
Event Type: Information
Event Source: MSSQLSERVER/MSDE
Event Category: None
Event ID: 1
Date: 12/3/2007
Time: 3:02:41 PM
User: N/A
Computer: EAGNMNST18C
Description:
You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
Server 2000 Desktop Engine (also called MSDE) that has known security
vulnerabilities when used in conjunction with the Microsoft Windows Server
2003 family. To reduce your computer's vulnerability to certain virus
attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE
,
or both have been disabled. To enable these ports, you must install a patch
,
or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
http://www.microsoft.com/sql/downloads/default.asp
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.Take a look at this page and ensure you followed the right direction.
http://download.microsoft.com/downl...ailover_cluster
Ekrem ?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
> Hello,
> I recently added a new win2k3 node to an existing SQL cluster and
> installed
> SQL Server 2000. The SQL installation for the new node was performed from
> the active node.
> I also installed SP4 from the active node. However, I am having SQL
> connectivity issues when I fail over to the new node. I noticed that I
> get
> the following event log on the new node. It thinks that SP4 is not
> installed
> although it is. Does anyone know if SP4 should be installed from the
> passive
> node (the new node)? Does it matter which node we run the SP4
> installation?
> Thank-you,
> WG
> Event Type: Information
> Event Source: MSSQLSERVER/MSDE
> Event Category: None
> Event ID: 1
> Date: 12/3/2007
> Time: 3:02:41 PM
> User: N/A
> Computer: EAGNMNST18C
> Description:
> You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
> Server 2000 Desktop Engine (also called MSDE) that has known security
> vulnerabilities when used in conjunction with the Microsoft Windows Server
> 2003 family. To reduce your computer's vulnerability to certain virus
> attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
> MSDE,
> or both have been disabled. To enable these ports, you must install a
> patch,
> or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
> http://www.microsoft.com/sql/downloads/default.asp
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>|||Thank you!
I actually came across this article and it is helpful.
Could you tell me what is the "database upgrade script"? The article says,
for my scenario, I must run "the databse upgrade script".
Thanks,
WG
"Ekrem ?nsoy" wrote:
> Take a look at this page and ensure you followed the right direction.
> http://download.microsoft.com/downl...ailover_cluster
> --
> Ekrem ?nsoy
>
> "Walid" <Walid@.discussions.microsoft.com> wrote in message
> news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
>|||I believe it must be talking about the upgrading your database scripts that
you used to be using before SP4 is apllied.
Ekrem ?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:AE628F6C-F06F-4DBF-B36D-0D5563B1D110@.microsoft.com...[vbcol=seagreen]
> Thank you!
> I actually came across this article and it is helpful.
> Could you tell me what is the "database upgrade script"? The article
> says,
> for my scenario, I must run "the databse upgrade script".
> Thanks,
> WG
> "Ekrem ?nsoy" wrote:
>
I recently added a new win2k3 node to an existing SQL cluster and installed
SQL Server 2000. The SQL installation for the new node was performed from
the active node.
I also installed SP4 from the active node. However, I am having SQL
connectivity issues when I fail over to the new node. I noticed that I get
the following event log on the new node. It thinks that SP4 is not installe
d
although it is. Does anyone know if SP4 should be installed from the passiv
e
node (the new node)? Does it matter which node we run the SP4 installation?
Thank-you,
WG
Event Type: Information
Event Source: MSSQLSERVER/MSDE
Event Category: None
Event ID: 1
Date: 12/3/2007
Time: 3:02:41 PM
User: N/A
Computer: EAGNMNST18C
Description:
You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
Server 2000 Desktop Engine (also called MSDE) that has known security
vulnerabilities when used in conjunction with the Microsoft Windows Server
2003 family. To reduce your computer's vulnerability to certain virus
attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE
,
or both have been disabled. To enable these ports, you must install a patch
,
or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
http://www.microsoft.com/sql/downloads/default.asp
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.Take a look at this page and ensure you followed the right direction.
http://download.microsoft.com/downl...ailover_cluster
Ekrem ?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
> Hello,
> I recently added a new win2k3 node to an existing SQL cluster and
> installed
> SQL Server 2000. The SQL installation for the new node was performed from
> the active node.
> I also installed SP4 from the active node. However, I am having SQL
> connectivity issues when I fail over to the new node. I noticed that I
> get
> the following event log on the new node. It thinks that SP4 is not
> installed
> although it is. Does anyone know if SP4 should be installed from the
> passive
> node (the new node)? Does it matter which node we run the SP4
> installation?
> Thank-you,
> WG
> Event Type: Information
> Event Source: MSSQLSERVER/MSDE
> Event Category: None
> Event ID: 1
> Date: 12/3/2007
> Time: 3:02:41 PM
> User: N/A
> Computer: EAGNMNST18C
> Description:
> You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
> Server 2000 Desktop Engine (also called MSDE) that has known security
> vulnerabilities when used in conjunction with the Microsoft Windows Server
> 2003 family. To reduce your computer's vulnerability to certain virus
> attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
> MSDE,
> or both have been disabled. To enable these ports, you must install a
> patch,
> or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
> http://www.microsoft.com/sql/downloads/default.asp
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>|||Thank you!
I actually came across this article and it is helpful.
Could you tell me what is the "database upgrade script"? The article says,
for my scenario, I must run "the databse upgrade script".
Thanks,
WG
"Ekrem ?nsoy" wrote:
> Take a look at this page and ensure you followed the right direction.
> http://download.microsoft.com/downl...ailover_cluster
> --
> Ekrem ?nsoy
>
> "Walid" <Walid@.discussions.microsoft.com> wrote in message
> news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
>|||I believe it must be talking about the upgrading your database scripts that
you used to be using before SP4 is apllied.
Ekrem ?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:AE628F6C-F06F-4DBF-B36D-0D5563B1D110@.microsoft.com...[vbcol=seagreen]
> Thank you!
> I actually came across this article and it is helpful.
> Could you tell me what is the "database upgrade script"? The article
> says,
> for my scenario, I must run "the databse upgrade script".
> Thanks,
> WG
> "Ekrem ?nsoy" wrote:
>
installing SP4 for SQL 2000 on a cluster node
Hello,
I recently added a new win2k3 node to an existing SQL cluster and installed
SQL Server 2000. The SQL installation for the new node was performed from
the active node.
I also installed SP4 from the active node. However, I am having SQL
connectivity issues when I fail over to the new node. I noticed that I get
the following event log on the new node. It thinks that SP4 is not installed
although it is. Does anyone know if SP4 should be installed from the passive
node (the new node)? Does it matter which node we run the SP4 installation?
Thank-you,
WG
Event Type: Information
Event Source: MSSQLSERVER/MSDE
Event Category: None
Event ID: 1
Date: 12/3/2007
Time: 3:02:41 PM
User: N/A
Computer: EAGNMNST18C
Description:
You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
Server 2000 Desktop Engine (also called MSDE) that has known security
vulnerabilities when used in conjunction with the Microsoft Windows Server
2003 family. To reduce your computer's vulnerability to certain virus
attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE,
or both have been disabled. To enable these ports, you must install a patch,
or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
http://www.microsoft.com/sql/downloads/default.asp
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.Take a look at this page and ensure you followed the right direction.
http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
--
Ekrem Ã?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
> Hello,
> I recently added a new win2k3 node to an existing SQL cluster and
> installed
> SQL Server 2000. The SQL installation for the new node was performed from
> the active node.
> I also installed SP4 from the active node. However, I am having SQL
> connectivity issues when I fail over to the new node. I noticed that I
> get
> the following event log on the new node. It thinks that SP4 is not
> installed
> although it is. Does anyone know if SP4 should be installed from the
> passive
> node (the new node)? Does it matter which node we run the SP4
> installation?
> Thank-you,
> WG
> Event Type: Information
> Event Source: MSSQLSERVER/MSDE
> Event Category: None
> Event ID: 1
> Date: 12/3/2007
> Time: 3:02:41 PM
> User: N/A
> Computer: EAGNMNST18C
> Description:
> You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
> Server 2000 Desktop Engine (also called MSDE) that has known security
> vulnerabilities when used in conjunction with the Microsoft Windows Server
> 2003 family. To reduce your computer's vulnerability to certain virus
> attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
> MSDE,
> or both have been disabled. To enable these ports, you must install a
> patch,
> or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
> http://www.microsoft.com/sql/downloads/default.asp
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>|||Thank you!
I actually came across this article and it is helpful.
Could you tell me what is the "database upgrade script"? The article says,
for my scenario, I must run "the databse upgrade script".
Thanks,
WG
"Ekrem Ã?nsoy" wrote:
> Take a look at this page and ensure you followed the right direction.
> http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
> --
> Ekrem Ã?nsoy
>
> "Walid" <Walid@.discussions.microsoft.com> wrote in message
> news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
> > Hello,
> >
> > I recently added a new win2k3 node to an existing SQL cluster and
> > installed
> > SQL Server 2000. The SQL installation for the new node was performed from
> > the active node.
> > I also installed SP4 from the active node. However, I am having SQL
> > connectivity issues when I fail over to the new node. I noticed that I
> > get
> > the following event log on the new node. It thinks that SP4 is not
> > installed
> > although it is. Does anyone know if SP4 should be installed from the
> > passive
> > node (the new node)? Does it matter which node we run the SP4
> > installation?
> >
> > Thank-you,
> >
> > WG
> >
> > Event Type: Information
> > Event Source: MSSQLSERVER/MSDE
> > Event Category: None
> > Event ID: 1
> > Date: 12/3/2007
> > Time: 3:02:41 PM
> > User: N/A
> > Computer: EAGNMNST18C
> > Description:
> > You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
> > Server 2000 Desktop Engine (also called MSDE) that has known security
> > vulnerabilities when used in conjunction with the Microsoft Windows Server
> > 2003 family. To reduce your computer's vulnerability to certain virus
> > attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
> > MSDE,
> > or both have been disabled. To enable these ports, you must install a
> > patch,
> > or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
> > http://www.microsoft.com/sql/downloads/default.asp
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
>|||I believe it must be talking about the upgrading your database scripts that
you used to be using before SP4 is apllied.
--
Ekrem Ã?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:AE628F6C-F06F-4DBF-B36D-0D5563B1D110@.microsoft.com...
> Thank you!
> I actually came across this article and it is helpful.
> Could you tell me what is the "database upgrade script"? The article
> says,
> for my scenario, I must run "the databse upgrade script".
> Thanks,
> WG
> "Ekrem Ã?nsoy" wrote:
>> Take a look at this page and ensure you followed the right direction.
>> http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
>> --
>> Ekrem Ã?nsoy
>>
>> "Walid" <Walid@.discussions.microsoft.com> wrote in message
>> news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
>> > Hello,
>> >
>> > I recently added a new win2k3 node to an existing SQL cluster and
>> > installed
>> > SQL Server 2000. The SQL installation for the new node was performed
>> > from
>> > the active node.
>> > I also installed SP4 from the active node. However, I am having SQL
>> > connectivity issues when I fail over to the new node. I noticed that I
>> > get
>> > the following event log on the new node. It thinks that SP4 is not
>> > installed
>> > although it is. Does anyone know if SP4 should be installed from the
>> > passive
>> > node (the new node)? Does it matter which node we run the SP4
>> > installation?
>> >
>> > Thank-you,
>> >
>> > WG
>> >
>> > Event Type: Information
>> > Event Source: MSSQLSERVER/MSDE
>> > Event Category: None
>> > Event ID: 1
>> > Date: 12/3/2007
>> > Time: 3:02:41 PM
>> > User: N/A
>> > Computer: EAGNMNST18C
>> > Description:
>> > You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
>> > Server 2000 Desktop Engine (also called MSDE) that has known security
>> > vulnerabilities when used in conjunction with the Microsoft Windows
>> > Server
>> > 2003 family. To reduce your computer's vulnerability to certain virus
>> > attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
>> > MSDE,
>> > or both have been disabled. To enable these ports, you must install a
>> > patch,
>> > or the most recent service pack for Microsoft SQL Server 2000 or MSDE
>> > from
>> > http://www.microsoft.com/sql/downloads/default.asp
>> >
>> > For more information, see Help and Support Center at
>> > http://go.microsoft.com/fwlink/events.asp.
>> >
I recently added a new win2k3 node to an existing SQL cluster and installed
SQL Server 2000. The SQL installation for the new node was performed from
the active node.
I also installed SP4 from the active node. However, I am having SQL
connectivity issues when I fail over to the new node. I noticed that I get
the following event log on the new node. It thinks that SP4 is not installed
although it is. Does anyone know if SP4 should be installed from the passive
node (the new node)? Does it matter which node we run the SP4 installation?
Thank-you,
WG
Event Type: Information
Event Source: MSSQLSERVER/MSDE
Event Category: None
Event ID: 1
Date: 12/3/2007
Time: 3:02:41 PM
User: N/A
Computer: EAGNMNST18C
Description:
You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
Server 2000 Desktop Engine (also called MSDE) that has known security
vulnerabilities when used in conjunction with the Microsoft Windows Server
2003 family. To reduce your computer's vulnerability to certain virus
attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE,
or both have been disabled. To enable these ports, you must install a patch,
or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
http://www.microsoft.com/sql/downloads/default.asp
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.Take a look at this page and ensure you followed the right direction.
http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
--
Ekrem Ã?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
> Hello,
> I recently added a new win2k3 node to an existing SQL cluster and
> installed
> SQL Server 2000. The SQL installation for the new node was performed from
> the active node.
> I also installed SP4 from the active node. However, I am having SQL
> connectivity issues when I fail over to the new node. I noticed that I
> get
> the following event log on the new node. It thinks that SP4 is not
> installed
> although it is. Does anyone know if SP4 should be installed from the
> passive
> node (the new node)? Does it matter which node we run the SP4
> installation?
> Thank-you,
> WG
> Event Type: Information
> Event Source: MSSQLSERVER/MSDE
> Event Category: None
> Event ID: 1
> Date: 12/3/2007
> Time: 3:02:41 PM
> User: N/A
> Computer: EAGNMNST18C
> Description:
> You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
> Server 2000 Desktop Engine (also called MSDE) that has known security
> vulnerabilities when used in conjunction with the Microsoft Windows Server
> 2003 family. To reduce your computer's vulnerability to certain virus
> attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
> MSDE,
> or both have been disabled. To enable these ports, you must install a
> patch,
> or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
> http://www.microsoft.com/sql/downloads/default.asp
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>|||Thank you!
I actually came across this article and it is helpful.
Could you tell me what is the "database upgrade script"? The article says,
for my scenario, I must run "the databse upgrade script".
Thanks,
WG
"Ekrem Ã?nsoy" wrote:
> Take a look at this page and ensure you followed the right direction.
> http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
> --
> Ekrem Ã?nsoy
>
> "Walid" <Walid@.discussions.microsoft.com> wrote in message
> news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
> > Hello,
> >
> > I recently added a new win2k3 node to an existing SQL cluster and
> > installed
> > SQL Server 2000. The SQL installation for the new node was performed from
> > the active node.
> > I also installed SP4 from the active node. However, I am having SQL
> > connectivity issues when I fail over to the new node. I noticed that I
> > get
> > the following event log on the new node. It thinks that SP4 is not
> > installed
> > although it is. Does anyone know if SP4 should be installed from the
> > passive
> > node (the new node)? Does it matter which node we run the SP4
> > installation?
> >
> > Thank-you,
> >
> > WG
> >
> > Event Type: Information
> > Event Source: MSSQLSERVER/MSDE
> > Event Category: None
> > Event ID: 1
> > Date: 12/3/2007
> > Time: 3:02:41 PM
> > User: N/A
> > Computer: EAGNMNST18C
> > Description:
> > You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
> > Server 2000 Desktop Engine (also called MSDE) that has known security
> > vulnerabilities when used in conjunction with the Microsoft Windows Server
> > 2003 family. To reduce your computer's vulnerability to certain virus
> > attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
> > MSDE,
> > or both have been disabled. To enable these ports, you must install a
> > patch,
> > or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
> > http://www.microsoft.com/sql/downloads/default.asp
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
>|||I believe it must be talking about the upgrading your database scripts that
you used to be using before SP4 is apllied.
--
Ekrem Ã?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:AE628F6C-F06F-4DBF-B36D-0D5563B1D110@.microsoft.com...
> Thank you!
> I actually came across this article and it is helpful.
> Could you tell me what is the "database upgrade script"? The article
> says,
> for my scenario, I must run "the databse upgrade script".
> Thanks,
> WG
> "Ekrem Ã?nsoy" wrote:
>> Take a look at this page and ensure you followed the right direction.
>> http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
>> --
>> Ekrem Ã?nsoy
>>
>> "Walid" <Walid@.discussions.microsoft.com> wrote in message
>> news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
>> > Hello,
>> >
>> > I recently added a new win2k3 node to an existing SQL cluster and
>> > installed
>> > SQL Server 2000. The SQL installation for the new node was performed
>> > from
>> > the active node.
>> > I also installed SP4 from the active node. However, I am having SQL
>> > connectivity issues when I fail over to the new node. I noticed that I
>> > get
>> > the following event log on the new node. It thinks that SP4 is not
>> > installed
>> > although it is. Does anyone know if SP4 should be installed from the
>> > passive
>> > node (the new node)? Does it matter which node we run the SP4
>> > installation?
>> >
>> > Thank-you,
>> >
>> > WG
>> >
>> > Event Type: Information
>> > Event Source: MSSQLSERVER/MSDE
>> > Event Category: None
>> > Event ID: 1
>> > Date: 12/3/2007
>> > Time: 3:02:41 PM
>> > User: N/A
>> > Computer: EAGNMNST18C
>> > Description:
>> > You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
>> > Server 2000 Desktop Engine (also called MSDE) that has known security
>> > vulnerabilities when used in conjunction with the Microsoft Windows
>> > Server
>> > 2003 family. To reduce your computer's vulnerability to certain virus
>> > attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
>> > MSDE,
>> > or both have been disabled. To enable these ports, you must install a
>> > patch,
>> > or the most recent service pack for Microsoft SQL Server 2000 or MSDE
>> > from
>> > http://www.microsoft.com/sql/downloads/default.asp
>> >
>> > For more information, see Help and Support Center at
>> > http://go.microsoft.com/fwlink/events.asp.
>> >
Subscribe to:
Posts (Atom)