February 18, 2013 at 3:47 am
If people on the Internet are not able to help within the timescale you want, then the best thing is to open a Support Case with Microsoft. SQL people know a bit about setting up clustering at an OS level, but Microsoft has experts in this area.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
February 18, 2013 at 9:25 am
EdVassie (2/18/2013)
the best thing is to open a Support Case with Microsoft.
or hire a consultant to troubleshoot the system for you, which would likely be a lot cheaper than calling Microsoft 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 20, 2013 at 2:15 am
Perry Whittle (2/18/2013)
EdVassie (2/18/2013)
the best thing is to open a Support Case with Microsoft.or hire a consultant to troubleshoot the system for you, which would likely be a lot cheaper than calling Microsoft 😉
I solved it on my own. It's even cheaper! YEAH!
This error perplexed me :
[NODE] Node 2: New join with n1: stage: 'Authenticate Initial Connection'
00000f7c.000009ac::2013/02/18-12:06:33.886 ERR 000007fe:fe0f9e5d( ERROR_MOD_NOT_FOUND(126) )
00000f7c.000009ac::2013/02/18-12:06:33.886 ERR 00000000:01ebf050( ERROR_MOD_NOT_FOUND(126) )
00000f7c.000009ac::2013/02/18-12:06:33.886 ERR 00000000:003e0350( ERROR_MOD_NOT_FOUND(126) )
00000f7c.000009ac::2013/02/18-12:06:33.886 ERR 00000000:ff53c050( ERROR_MOD_NOT_FOUND(126) )
00000f7c.000009ac::2013/02/18-12:06:33.886 INFO [NODE] Node 2: New join with n1: stage: 'Authorize Initial Connection' status HrError(0x8009030c) reason: '[SV] Authorization failed'
The Problem was that the RSA-Machinekey 4f692a7dc1b824e1f679f93fadd08a3b_6adaa04c-870a-4415-a11a-3cadf31e62e0 was unaccessible, allthough the Domain-User-Account running the Cluster Service was even owner. I added rights for the local admin (just for fun) and it worked! At this point I'll give up the search for a logical explanation, just stating, that you should never trust a microsoft error message. 99% of the microsoft error messages you could overwrite with : permission problem :D!
Thank you very much for all your efforts and help!
PS: If you run into permission problems, get familiar with process monitor :P!
Greetz
Query Shepherd
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply