Installing sql: node

Showing posts with label node. Show all posts

Friday, March 30, 2012

Instance wil not come online

2 out of 4 instances on my 3 node cluster wil not come online on one off
the clusternodes, unless I add an alias (which I removed after
installing sp3). The application eventlog complains about not being able
to connect to the instance. I can connect to the instance remotely, but
apparently the clusterservice can not. I can not find any differences in
the registry of files. Reinstalling sql did not help. Any ideas?
Hans
Hans de Bruin wrote:
> 2 out of 4 instances on my 3 node cluster wil not come online on one off
> the clusternodes, unless I add an alias (which I removed after
> installing sp3). The application eventlog complains about not being able
> to connect to the instance. I can connect to the instance remotely, but
> apparently the clusterservice can not. I can not find any differences in
> the registry of files. Reinstalling sql did not help. Any ideas?
>
udp 1434 isn't always responding. So when the is no entry in
hkey-local_machine\software\mssqlserverclient\..\lastco nnect on my
workstation osql wil not connect. All nodes and instances report to be
8.00.818 (sp3 + latest hotfix). accoording to netstat al de nodes are
listening to udp 0.0.0.0:1434. Could W2k3 still be blocking 1434 or is
there a problem with registering the instance with the udp thing?
Hans
|||Hans de Bruin wrote:
> Hans de Bruin wrote:
>
> udp 1434 isn't always responding. So when the is no entry in
> hkey-local_machine\software\mssqlserverclient\..\lastco nnect on my
> workstation osql wil not connect. All nodes and instances report to be
> 8.00.818 (sp3 + latest hotfix). accoording to netstat al de nodes are
> listening to udp 0.0.0.0:1434. Could W2k3 still be blocking 1434 or is
> there a problem with registering the instance with the udp thing?
>
hmm, on ether node:
clear the node of all sql instances:
clear the registry on the client.
fail over one sql instance to the node.
connect to the instance: success
fail over a second instance to the node
connect to the second instance: timout on udp 1434
clear the registry on the client.
connect to the fisrt instance again: success
move the fist instance to an other node.
connect to the fisrt second again: success
So I am only able to connect to the fist activated instance on a node
useing udp 1434. Where did I go wrong?
Hans
|||Hans,
I have seen a similar problem to yours in one of our clusters.
Can you post the errors in the eventlog.
Thanks,
PK
Message posted via http://www.sqlmonster.com
|||PK via SQLMonster.com wrote:
> Hans,
> I have seen a similar problem to yours in one of our clusters.
> Can you post the errors in the eventlog.
> Thanks,
> PK
>
It looks like this one:
http://groups.google.nl/groups?threa...GP11.phx. gbl
My instances were running without local admin rights. After I
fixed this, udp1434 was behaving normally, and I could remove the
alias on the clusternodes.
I want to run some of the instances without local admin rights so I can
give developers sysadmin rights on their instance without giving them
access to the whole system.
Hans
|||Hans de Bruin wrote:
> PK via SQLMonster.com wrote:
>
> It looks like this one:
> http://groups.google.nl/groups?threa...GP11.phx. gbl
oops try this one:
http://groups.google.nl/groups?threa...0a% 40phx.gbl

>
> My instances were running without local admin rights. After I
> fixed this, udp1434 was behaving normally, and I could remove the
> alias on the clusternodes.
> I want to run some of the instances without local admin rights so I can
> give developers sysadmin rights on their instance without giving them
> access to the whole system.
>
|||Hans de Bruin wrote:
> 2 out of 4 instances on my 3 node cluster wil not come online on one off
> the clusternodes, unless I add an alias (which I removed after
> installing sp3). The application eventlog complains about not being able
> to connect to the instance. I can connect to the instance remotely, but
> apparently the clusterservice can not. I can not find any differences in
> the registry of files. Reinstalling sql did not help. Any ideas?
>
Apparently what happens is this:
- i1 come online the node as non admin and takes hold of udp 1434
- the MSCS tries to connect to the i1 and requests for the portnumber.
- i1 looks in its own the reqistry and finds the port number.
- MSCS gets an anwser an connects. i1 is online.
- i2 tries to come online on the node as either admin or non admin.
- the MSCS tries to connect to the i2 and requests for the portnumber.
- i1 tries to looks in i2's reqistry and gets an access denied.
- MSCS does not get any anwser and makes interesing calls to wins and
dns, fails to figure out the portnumer or pipename and fails i2
- i3 tries to come online on the node as either admin or non admin.
- the MSCS tries to connect to the i3 and requests for the portnumber.
- i1 tries to looks in i3's reqistry and gets an access denied.
- MSCS does not get any anwser and makes interesing calls to wins and
dns, fails to figure out the portnumer or pipename and fails i3
...
conclussion:
When running multiple sql instances (clustered or not) sql needs to run
as an local admin or system account or you need to hack the registry
permissions to let udp 1434 work, or or you need create an alias on the
server and the clients so sqlserveragent and the clients can connect.
Hans

Monday, March 26, 2012

Installing SQL205 in a cluster with mount points

I am struggling with an installation of SQL2005 on Windows Server 2003 SP1. I
am trying to set up a 2 node cluster with a single instance of sql2005. I
need to use mount points so I create a shared disk for the mount points and 2
disks which are mounted in there. The shared disk is called M: and the other
disks have names (DB and Logs). There will be more in due course but I
thought I would start with 2.
The install proceeds okay until it gets to the point where I have to choose
a cluster group to put it in. I have created one with M: in it plus the two
mounted disks. However, when I select that one it insists in making M: the
destination for the data files and, of course there is not enough space there
for them. It seems to be completed incapable of using the mount points. In
fact ir doesn't see them at all.
Does anyone know how to fix this or is it just not possible to use mount
points with SQL2005 in a cluster despite what the documentation says
Hi Colin,
This link has information about special mount point considerations
http://msdn2.microsoft.com/en-us/library/ms189910.aspx.
Regards
Antonio Soto
Solid Quality Leaning
http://www.solidqualitylearning.com
DISCLAIMER:
Anything written in this message represents solely the point of view of the
sender. This message does not imply endorsement from Solid Quality Learning,
and it does not represent the point of view of Solid Quality Learning or any
other person, company or institution mentioned in this message
"Colin Bruce" <ColinBruce@.discussions.microsoft.com> escribi en el mensaje
news:2DA833EE-D6B1-4D53-8E2B-4374B73F7F03@.microsoft.com...
>I am struggling with an installation of SQL2005 on Windows Server 2003 SP1.
>I
> am trying to set up a 2 node cluster with a single instance of sql2005. I
> need to use mount points so I create a shared disk for the mount points
> and 2
> disks which are mounted in there. The shared disk is called M: and the
> other
> disks have names (DB and Logs). There will be more in due course but I
> thought I would start with 2.
> The install proceeds okay until it gets to the point where I have to
> choose
> a cluster group to put it in. I have created one with M: in it plus the
> two
> mounted disks. However, when I select that one it insists in making M: the
> destination for the data files and, of course there is not enough space
> there
> for them. It seems to be completed incapable of using the mount points. In
> fact ir doesn't see them at all.
> Does anyone know how to fix this or is it just not possible to use mount
> points with SQL2005 in a cluster despite what the documentation says
|||Dear Antonio,
Thanks for the info. The bit that is mssing from that document - at least I
cannot find it is how big the base drive has to be. As far as I can see what
is not mentioned is that the SQL 2005 installation will put some files in the
base drive. Most of the installation goes somewhere such as C:\Program
Files\... but some files are put in the shared drive which is acting as the
base drive. I have tried creating the base drive with about 50 GB and SQL
2005 then installs. I don't know how much will go in there for different
installation choices but I am now trying a 30GB base drive to see if that is
big enough.
Anyway, to summarise, the base drive isn't just for mount points as the
document suggests but also holds quite a few installation files which I guess
need to be shared between the cluster nodes.
Best wishes...
Colin
"Antonio Soto" wrote:

> Hi Colin,
> This link has information about special mount point considerations
> http://msdn2.microsoft.com/en-us/library/ms189910.aspx.
> Regards
> Antonio Soto
> Solid Quality Leaning
> http://www.solidqualitylearning.com
> DISCLAIMER:
> Anything written in this message represents solely the point of view of the
> sender. This message does not imply endorsement from Solid Quality Learning,
> and it does not represent the point of view of Solid Quality Learning or any
> other person, company or institution mentioned in this message
>
> "Colin Bruce" <ColinBruce@.discussions.microsoft.com> escribió en el mensaje
> news:2DA833EE-D6B1-4D53-8E2B-4374B73F7F03@.microsoft.com...
>
>

Installing SqL SP2 on sql 2005 clustered

Hi,

I have installed sql sp2 after finished core installation. I thought that it would deploys to node 2 as well (I did it on node 1) but when i tried to shutdown node 1 the clusters will be on node2, I could not to use MS management studio that including sp2 on node2. Why? What should I do?

Please answers me asap.

Appreciate everyone to come in help.

Thank you very much.

You have to install SP2 on each node of the cluster.

It does not 'automagically' install on additional nodes after you install it on one node.

Monday, March 19, 2012

Installing SQL Server 2005 Developer Edition 64-bit extended on Windows 2003 SP2 cluster

Hello

I've installed Windows 2003 SP2 in a stand-alone cluster (will be adding a second node later). I'm now installing SQL Server 2005 Developer Edition 64-bit extended and would like to have the "Create a SQL Server Failover Cluster" box to not be grayed out. Even when I check the "SQL Server Database Services" box, it still has the cluster box grayed out.

Any idea's?

TIA!

Have you created and configured the cluster service (MSCS)?|||This is resolved. As per usual, SQL 2005 seems to install with more success when you copy the cabs local to the machine, and then run setup (versus over the network).thank anyways Arnie.

Sunday, February 19, 2012

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

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.
>> >

INstalling sp3a on second node

I have a active/passive cluster with W2K Adv. and SQL 2000.
I was having the issue with setting up SQL on the second node. I fixed issue by installing directly onto the second node. But their is no option with the sp3a to install onto the second node locally. The same issue that happened with trying to remote inst
all with the primary node. The install failed because of a timeout issue. Error 121. All of my settings and correct accounts are setup. The person who told me to install directly on the second node to
install SQL stated that this was actually a known problem. What is the fix for the service packs if you cannot install remotely? It looks like sp3a installed correctly because when I ran query analyzer the version that showed up was sp3a. Any comments wou
ld be appreciated.
Thanks,
dcaldwell
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
There is no 'first node' and 'second node' concept in SQL 2000 clustering.
All nodes are equal. The only difference is what node is currently hosting
the instance. Adding and removing nodes is a different process and is well
documented in BOL. It sounds like you built the cluster on a single node or
applied the service pack with one node offline. Normal installation of SQL
Service packs will update all nodes at the same time if it is run from teh
node currently hosting the instance. If you need to reapply a service pack
to update binaries on a newly added or replaced node, you must run the
Service Pack from the 'new' node while hte SQL instance is hosted on an
'old' node. This is documented in the Service Pack readme file.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:%23%23T55iTgEHA.3272@.TK2MSFTNGP11.phx.gbl...
> I have a active/passive cluster with W2K Adv. and SQL 2000.
> I was having the issue with setting up SQL on the second node. I fixed
issue by installing directly onto the second node. But their is no option
with the sp3a to install onto the second node locally. The same issue that
happened with trying to remote install with the primary node. The install
failed because of a timeout issue. Error 121. All of my settings and correct
accounts are setup. The person who told me to install directly on the second
node to
> install SQL stated that this was actually a known problem. What is the fix
for the service packs if you cannot install remotely? It looks like sp3a
installed correctly because when I ran query analyzer the version that
showed up was sp3a. Any comments would be appreciated.
> Thanks,
> dcaldwell
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
|||What do you mean by "I fixed issue by installing directly onto the second
node. "
Did you install a local, non-clustered installation on the second node?
Perhaps now is a time to uninstall that local copy, and reinstall back as a
virtual SQL Server. You can find a clustering installation white paper at:
http://www.microsoft.com/technet/pro.../failclus.mspx
Chris Skorlinski
Microsoft SQL Server Support
Please reply directly to the thread with any updates.
This posting is provided "as is" with no warranties and confers no rights.

Friday, March 30, 2012

Instance wil not come online

Monday, March 26, 2012

Installing SQL205 in a cluster with mount points

Installing SqL SP2 on sql 2005 clustered

Monday, March 19, 2012

Installing SQL Server 2005 Developer Edition 64-bit extended on Windows 2003 SP2 cluster

Sunday, February 19, 2012

Installing SP4 on New node in cluster on Win2K3

installing SP4 for SQL 2000 on a cluster node

installing SP4 for SQL 2000 on a cluster node

installing SP4 for SQL 2000 on a cluster node

INstalling sp3a on second node

Installing sql

Blog Archive

About Me