Re: Windows 2003 cluster trust issue during install?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi again,


FYI I just did a comlete patch check on both NODE1 and NODE2 from MS site.
It found a few minor one, however at this point they are up to date and we
are still in the same situation.

Scott

"scott" wrote:

Hi,


Geoff, that was the same link I mentioned in one of my replies. The issue
is that after the system checks both nodes, it finds 8+ issues on NODE1,
which is the system that failed an now back in the MS CLUSTER, and will not
allow me to go past by clicking next. However, if NODE1 isn't apart of the
MS CLUSTER, then MS SQL tells me it's unavailable to remove.

Catch '22'!!! Can it be removed outside of add/remove? If so, however??

Scott




********
On the Welcome page, click Next.
The System Configuration Checker scans your computer's existing
configuration.

After the System Configuration Checker finishes its scan, click Next.
*********


"Geoff N. Hiten" wrote:

Follow this link in Books On-Line:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/fe20dca9-a4c1-4d32-813d-42f1782dfdd3.htm

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP


"scott" <scott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6506FBE3-10BF-40ED-A774-B1A57A48EF92@xxxxxxxxxxxxxxxx
Hi Geoff,

Do you have any ideas as to how to remove a node from a clustered SQL
2005
Enterprise?

I can't find anything in the newgroups or KB on this issue?




"scott" wrote:

Hi,

I followed the instructions to remove a node from an SQL install (which
can
be found at http://msdn2.microsoft.com/en-us/library/ms191545.aspx). On
the
screen labeled "Cluster Node configuartion", I found that the node in
question (NODE1) was in the "Unavailable Nodes" area and the last node
was in
the "Required Nodes". So I was unable to remove anything.

However, to answer the remainded of your questions:
1. I was logged into the system as Administrator.
2. Yes, the service is running on both servers.
3. Yes, NODE1 (the failed machine) has been put back in the cluster and
is
working fine.

Question: How can I remove NODE1 from the SQL install if the system will
not allow me to using the KB.? How do we proceed from here?

Scott




"Geoff N. Hiten" wrote:

This looks like SQL 2005, but confirmation would be nice.

If you are to this point, you need to have removed Node1 from the
cluster
and the domain, then re-added the rebuilt node. You also need to have
removed Node1 from the SQL install, otherwise it will still try and
update
the old node, which no longer exists.

Finally, you need to make sure the installer account is an admin on all
nodes and that the task scheduler is running on all nodes.

These are just some semi-generic guesses. Without more details, I
really
can't dig in any further.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP



"scott" <scott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3430A0D1-BA63-4221-9AB5-8172DF92BD11@xxxxxxxxxxxxxxxx
We had a problem with one of our servers which is apart of a cluster
(
NODE1
). It required reloading and now we're back to installing SQL. When
we're
on NODE2, its partner, and try to install SQL, it complains about
NODE1
(see
logfile). However, when we try to load SQL from NODE1 the same
errors now
appear on NODE2. What's up???

Is there a trust problem? Permissions?



System Configuration Check

- NODE2 - WMI Service Requirement (Success)
Messages
* WMI Service Requirement

* Check Passed


- NODE2 - MSXML Requirement (Success)
Messages
* MSXML Requirement

* Check Passed


- NODE2 - Operating System Minimum Level Requirement (Success)
Messages
* Operating System Minimum Level Requirement

* Check Passed


- NODE2 - Operating System Service Pack Level Requirement. (Success)
Messages
* Operating System Service Pack Level Requirement.

* Check Passed


- NODE2 - SQL Server Edition Operating System Compatibility (Success)
Messages
* SQL Server Edition Operating System Compatibility

* Check Passed


- NODE2 - Minimum Hardware Requirement (Success)
Messages
* Minimum Hardware Requirement

* Check Passed


- NODE2 - IIS Feature Requirement (Success)
Messages
* IIS Feature Requirement

* Check Passed


- NODE2 - Pending Reboot Requirement (Success)
Messages
* Pending Reboot Requirement

* Check Passed


- NODE2 - Performance Monitor Counter Requirement (Success)
Messages
* Performance Monitor Counter Requirement

* Check Passed


- NODE2 - Default Installation Path Permission Requirement (Success)
Messages
* Default Installation Path Permission Requirement

* Check Passed


- NODE2 - Internet Explorer Requirement (Success)
Messages
* Internet Explorer Requirement

* Check Passed


- NODE2 - COM Plus Catalog Requirement (Success)
Messages
* COM Plus Catalog Requirement

* Check Passed


- NODE2 - ASP.Net Version Registration Requirement (Success)
Messages
* ASP.Net Version Registration Requirement

* Check Passed


- NODE2 - Minimum MDAC Version Requirement (Success)
Messages
* Minimum MDAC Version Requirement

* Check Passed


- NODE1 - WMI Service Requirement (Error)
Messages
* WMI Service Requirement

* Unable to process the check.


- NODE1 - MSXML Requirement (Success)
Messages
* MSXML Requirement

* Check Passed


- NODE1 - Operating System Minimum Level Requirement (Error)
Messages
* Operating System Minimum Level Requirement

* Unable to process the check.


- NODE1 - Operating System Service Pack Level Requirement. (Error)
Messages
* Operating System Service Pack Level Requirement.

* Unable to process the check.


- NODE1 - SQL Server Edition Operating System Compatibility (Warning)
Messages
* SQL Server Edition Operating System Compatibility

* Unable to process the check.


- NODE1 - Minimum Hardware Requirement (Error)
Messages
* Minimum Hardware Requirement

* Unable to process the check.


- NODE1 - IIS Feature Requirement (Warning)
Messages
* IIS Feature Requirement

* Unable to process the check.


- NODE1 - Administrative Shares Requirement (Error)
Messages
* Administrative Shares Requirement

* Unable to process the check.


- NODE1 - Pending Reboot Requirement (Error)
Messages
* Pending Reboot Requirement

* Unable to process the check.


- NODE1 - Performance Monitor Counter Requirement (Error)
Messages
* Performance Monitor Counter Requirement

* Unable to process the check.


- NODE1 - Default Installation Path Permission Requirement (Warning)
Messages
* Default Installation Path Permission Requirement

* Unable to process the check.


- NODE1 - Internet Explorer Requirement (Warning)
Messages
.

Relevant Pages

  • Re: Windows 2003 cluster trust issue during install?
    ... I followed the instructions to remove a node from an SQL install (which can ... How can I remove NODE1 from the SQL install if the system will ... Operating System Service Pack Level Requirement. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Windows 2003 cluster trust issue during install?
    ... Geoff, that was the same link I mentioned in one of my replies. ... is that after the system checks both nodes, it finds 8+ issues on NODE1, ... then MS SQL tells me it's unavailable to remove. ... How can I remove NODE1 from the SQL install if the system will ...
    (microsoft.public.sqlserver.clustering)
  • Re: Windows 2003 cluster trust issue during install?
    ... you start from add/remove programs to do cluster ... This is different than with SQL 2000. ... FYI I just did a comlete patch check on both NODE1 and NODE2 from MS site. ... How can I remove NODE1 from the SQL install if the system ...
    (microsoft.public.sqlserver.clustering)
  • Cluster and XACT_E_TMNOTAVAILABLE error
    ... SQL Version is 8.00.904.The cluster is ... Yesterday we made a manual failover from Node1 to Node2 ... Cluster Group failover I made the SQL Group failover, ...
    (microsoft.public.sqlserver.clustering)
  • Re: Windows 2003 cluster trust issue during install?
    ... I followed the instructions to remove a node from an SQL install (which can ... How can I remove NODE1 from the SQL install if the system will ... Operating System Service Pack Level Requirement. ...
    (microsoft.public.sqlserver.clustering)