Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Clustering / June 2006

Tip: Looking for answers? Try searching our database.

Problems with ArticleID 909968:

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
RedStain - 29 Jun 2006 15:07 GMT
SUMMARY
When I try to add second node to a two node cluster I get this message:
"0x00138f Cluster resource not found"

SETUP
Windows 2003 64-bit R2 // HP Proliant DL380 G4 cluster with MGSA 500 G2
storage // Smart Start 7.4
Documentation I used are:
Doc1(overall document):
http://msmvps.com/blogs/clustering/archive/2004/10/25/16672.aspx
Doc2(network DTC):          http://support.microsoft.com/kb/817064
Doc3(cluster a DTC):
http://support.microsoft.com/default.aspx?scid=kb;en-us;301600
Doc4(Error Message)
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B909968

QUESTION
I get the classic error from this Article (909968). I know the the
workaround says 'Don't worry'  but I don't have a complex SAN as they
suggest, it's only a simple cluster.
I took care on not having both nodes seeing the external array until I was
ready to add second node to newly created cluster.
I have checked 'Disk Management' prior to creating the cluster; the BUS /
LUN and TID were identical, despite this, the document blames the error
message on the LUN and TID being different.

What am I doing wrong? Will this cause a problem in the future when I use
this in mission critical environments.
david@guenthners.com - 30 Jun 2006 03:08 GMT
Simplify the troubleshooting some by shutting down Node 1, and on Node
2 that will not join, stop and set the cluster service to manual.  Then
go to device manager and then show all devices, stop cluster disk
driver. reboot Node 2.

** Make sure Node 1 is powered off the entire time or risk data
corruption on shared disks.

When Node 2 comes back up, go to disk management and verify that you
can see all the disks including the quorum.  If you can see all the
disks from Node 2, this eliminates the hardware presentation of the
disks.  Re-enable the Cluster Disk Driver and set Cluster service to
auto, reboot Node 2.

Post again if this does not help.

Dave
david@guenthners.com - 30 Jun 2006 14:00 GMT
Verify that the network configuration is correct.  For your private
network, simplify that.  Use a cross over cable between nodes,  disable
set network to 10 half duplex, no default gatway. Make sure network
priority of internal network is first via CluAdmin console. Make sure
its internal communications only.  Make sure public nic is set to All
Communications.  Also make sure domain service account for Cluster is
Admin for both nodes....
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.