Windows Failover Cluster - Create Cluster Wizard: error occurred while creating the cluster ...
Did the new image of black hole confirm the general theory of relativity?
Working around an AWS network ACL rule limit
If I can make up priors, why can't I make up posteriors?
Statistical model of ligand substitution
Can smartphones with the same camera sensor have different image quality?
Direct Experience of Meditation
Area of a 2D convex hull
Cold is to Refrigerator as warm is to?
Autumning in love
I'm thinking of a number
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
New Order #5: where Fibonacci and Beatty meet at Wythoff
How to colour the US map with Yellow, Green, Red and Blue to minimize the number of states with the colour of Green
Can a monk deflect thrown melee weapons?
Array/tabular for long multiplication
Why does tar appear to skip file contents when output file is /dev/null?
Blender game recording at the wrong time
Mortgage adviser recommends a longer term than necessary combined with overpayments
Typeface like Times New Roman but with "tied" percent sign
What do you call a plan that's an alternative plan in case your initial plan fails?
What's the difference between (size_t)-1 and ~0?
What would be Julian Assange's expected punishment, on the current English criminal law?
Is above average number of years spent on PhD considered a red flag in future academia or industry positions?
Unexpected result with right shift after bitwise negation
Windows Failover Cluster - Create Cluster Wizard: error occurred while creating the cluster
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!SQL 2008 R2 Active/Active/Passive Cluster Does Not Allow Linked Servers Both WaysWindows 2008R2 two node failover cluster creation failsFailover Cluster Migration Wizard (SQL Install Portion)Windows Cluster An error was encountered while determining shared storageWindows Failover Cluster - Trying to create MSDTC Role - AD Permissions issues?Creating a failover cluster of 2 VMsExchange 2013 DAG Cluster Unable to add second severfailover cluster creation ErrorWindows Cluster Communication IssuesCluster Fails when Enabling Storage Spaces Direct Server 2016
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have 2 identical Windows Server 2008 R2 servers which I am trying to setup a failover cluster on.
The "Validate a Configuration" passes, but the actual creation process produces an error:
An error occurred while creating the cluster.
An error occurred creating cluster 'newcluster'.
This operation returned because the timeout period expired
Anybody know how to fix this?
Thanks!
Edit #1:
Create Cluster
Cluster: NEWCLUSTER
Node: server1.domain.local
Node: server2.domain.local
IP Address: 10.10.10.101
Started 12/11/2014 11:35:21 AM
Completed 12/11/2014 11:38:25 AM
Beginning to configure the cluster NEWCLUSTER.
Initializing Cluster NEWCLUSTER.
Validating cluster state on node server1.domain.local.
Searching the domain for computer object 'NEWCLUSTER'.
Creating a new computer object for 'NEWCLUSTER' in the domain.
Configuring computer object 'NEWCLUSTER' as cluster name object.
Validating installation of the Network FT Driver on node server1.domain.local.
Validating installation of the Cluster Disk Driver on node server1.domain.local.
Configuring Cluster Service on node server1.domain.local.
Validating installation of the Network FT Driver on node server2.domain.local.
Validating installation of the Cluster Disk Driver on node server2.domain.local.
Configuring Cluster Service on node server2.domain.local.
Waiting for notification that Cluster service on node server1.domain.local has started.
Forming cluster 'clusterrr'.
Unable to successfully cleanup.
To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
An error occurred while creating the cluster.
An error occurred creating cluster 'NEWCLUSTER'.
This operation returned because the timeout period expired
windows-server-2008-r2 windows-server-2012-r2 cluster failover failovercluster
edited May 24 '16 at 20:56
Ty H.
15818
asked Dec 10 '14 at 18:00
mradaritmradarit
1115
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have 2 identical Windows Server 2008 R2 servers which I am trying to setup a failover cluster on.
The "Validate a Configuration" passes, but the actual creation process produces an error:
An error occurred while creating the cluster.
An error occurred creating cluster 'newcluster'.
This operation returned because the timeout period expired
Anybody know how to fix this?
Thanks!
Edit #1:
Create Cluster
Cluster: NEWCLUSTER
Node: server1.domain.local
Node: server2.domain.local
IP Address: 10.10.10.101
Started 12/11/2014 11:35:21 AM
Completed 12/11/2014 11:38:25 AM
Beginning to configure the cluster NEWCLUSTER.
Initializing Cluster NEWCLUSTER.
Validating cluster state on node server1.domain.local.
Searching the domain for computer object 'NEWCLUSTER'.
Creating a new computer object for 'NEWCLUSTER' in the domain.
Configuring computer object 'NEWCLUSTER' as cluster name object.
Validating installation of the Network FT Driver on node server1.domain.local.
Validating installation of the Cluster Disk Driver on node server1.domain.local.
Configuring Cluster Service on node server1.domain.local.
Validating installation of the Network FT Driver on node server2.domain.local.
Validating installation of the Cluster Disk Driver on node server2.domain.local.
Configuring Cluster Service on node server2.domain.local.
Waiting for notification that Cluster service on node server1.domain.local has started.
Forming cluster 'clusterrr'.
Unable to successfully cleanup.
To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
An error occurred while creating the cluster.
An error occurred creating cluster 'NEWCLUSTER'.
This operation returned because the timeout period expired
windows-server-2008-r2 windows-server-2012-r2 cluster failover failovercluster
edited May 24 '16 at 20:56
Ty H.
15818
asked Dec 10 '14 at 18:00
mradaritmradarit
1115
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Can you post the cluster log ? so that we can check duplicate account that may have the same name as any of the nodes in the cluster, if so probably we need to remove those duplicate accounts. Also Please confirm you have given both nodes every permission.
– vembutech
Dec 10 '14 at 20:47
Please see edit #1. Both nodes have permissions and cluster is being created using a domain administrator account.
– mradarit
Dec 11 '14 at 16:47
I my case with similar error while trying to create a cluster on HP servers the problem was solved by installing latest NIC driver downloaded from HP support site or even from NIC vendor's [Broadcom or Intel] site.
– Sergey
Dec 16 '14 at 20:03
The validate stage may "pass" but it can pass conditionally. Was it all green? Or were there any yellow warning flags?
– Colyn1337
Dec 17 '14 at 18:19
I am having this problem right now in Windows Server 2012 R2, The "forming cluster" message appears for 2 minutes before the cluster create wizard fails and rolls back. The log is exactly the same as OP's log. Did anybody ever figure this out?
– Ty H.
May 24 '16 at 20:18
add a comment |
I have 2 identical Windows Server 2008 R2 servers which I am trying to setup a failover cluster on.
The "Validate a Configuration" passes, but the actual creation process produces an error:
An error occurred while creating the cluster.
An error occurred creating cluster 'newcluster'.
This operation returned because the timeout period expired
Anybody know how to fix this?
Thanks!
Edit #1:
Create Cluster
Cluster: NEWCLUSTER
Node: server1.domain.local
Node: server2.domain.local
IP Address: 10.10.10.101
Started 12/11/2014 11:35:21 AM
Completed 12/11/2014 11:38:25 AM
Beginning to configure the cluster NEWCLUSTER.
Initializing Cluster NEWCLUSTER.
Validating cluster state on node server1.domain.local.
Searching the domain for computer object 'NEWCLUSTER'.
Creating a new computer object for 'NEWCLUSTER' in the domain.
Configuring computer object 'NEWCLUSTER' as cluster name object.
Validating installation of the Network FT Driver on node server1.domain.local.
Validating installation of the Cluster Disk Driver on node server1.domain.local.
Configuring Cluster Service on node server1.domain.local.
Validating installation of the Network FT Driver on node server2.domain.local.
Validating installation of the Cluster Disk Driver on node server2.domain.local.
Configuring Cluster Service on node server2.domain.local.
Waiting for notification that Cluster service on node server1.domain.local has started.
Forming cluster 'clusterrr'.
Unable to successfully cleanup.
To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
An error occurred while creating the cluster.
An error occurred creating cluster 'NEWCLUSTER'.
This operation returned because the timeout period expired
windows-server-2008-r2 windows-server-2012-r2 cluster failover failovercluster
edited May 24 '16 at 20:56
Ty H.
15818
asked Dec 10 '14 at 18:00
mradaritmradarit
1115
I have 2 identical Windows Server 2008 R2 servers which I am trying to setup a failover cluster on.
The "Validate a Configuration" passes, but the actual creation process produces an error:
An error occurred while creating the cluster.
An error occurred creating cluster 'newcluster'.
This operation returned because the timeout period expired
Anybody know how to fix this?
Thanks!
Edit #1:
Create Cluster
Cluster: NEWCLUSTER
Node: server1.domain.local
Node: server2.domain.local
IP Address: 10.10.10.101
Started 12/11/2014 11:35:21 AM
Completed 12/11/2014 11:38:25 AM
Beginning to configure the cluster NEWCLUSTER.
Initializing Cluster NEWCLUSTER.
Validating cluster state on node server1.domain.local.
Searching the domain for computer object 'NEWCLUSTER'.
Creating a new computer object for 'NEWCLUSTER' in the domain.
Configuring computer object 'NEWCLUSTER' as cluster name object.
Validating installation of the Network FT Driver on node server1.domain.local.
Validating installation of the Cluster Disk Driver on node server1.domain.local.
Configuring Cluster Service on node server1.domain.local.
Validating installation of the Network FT Driver on node server2.domain.local.
Validating installation of the Cluster Disk Driver on node server2.domain.local.
Configuring Cluster Service on node server2.domain.local.
Waiting for notification that Cluster service on node server1.domain.local has started.
Forming cluster 'clusterrr'.
Unable to successfully cleanup.
To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
An error occurred while creating the cluster.
An error occurred creating cluster 'NEWCLUSTER'.
This operation returned because the timeout period expired
windows-server-2008-r2 windows-server-2012-r2 cluster failover failovercluster
windows-server-2008-r2 windows-server-2012-r2 cluster failover failovercluster
edited May 24 '16 at 20:56
Ty H.
15818
asked Dec 10 '14 at 18:00
mradaritmradarit
1115
edited May 24 '16 at 20:56
Ty H.
15818
asked Dec 10 '14 at 18:00
mradaritmradarit
1115
edited May 24 '16 at 20:56
Ty H.
15818
edited May 24 '16 at 20:56
Ty H.
15818
edited May 24 '16 at 20:56
Ty H.
15818
15818
asked Dec 10 '14 at 18:00
mradaritmradarit
1115
asked Dec 10 '14 at 18:00
mradaritmradarit
1115
asked Dec 10 '14 at 18:00
mradaritmradarit
1115
1115
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Can you post the cluster log ? so that we can check duplicate account that may have the same name as any of the nodes in the cluster, if so probably we need to remove those duplicate accounts. Also Please confirm you have given both nodes every permission.
– vembutech
Dec 10 '14 at 20:47
Please see edit #1. Both nodes have permissions and cluster is being created using a domain administrator account.
– mradarit
Dec 11 '14 at 16:47
I my case with similar error while trying to create a cluster on HP servers the problem was solved by installing latest NIC driver downloaded from HP support site or even from NIC vendor's [Broadcom or Intel] site.
– Sergey
Dec 16 '14 at 20:03
The validate stage may "pass" but it can pass conditionally. Was it all green? Or were there any yellow warning flags?
– Colyn1337
Dec 17 '14 at 18:19
I am having this problem right now in Windows Server 2012 R2, The "forming cluster" message appears for 2 minutes before the cluster create wizard fails and rolls back. The log is exactly the same as OP's log. Did anybody ever figure this out?
– Ty H.
May 24 '16 at 20:18
add a comment |
Can you post the cluster log ? so that we can check duplicate account that may have the same name as any of the nodes in the cluster, if so probably we need to remove those duplicate accounts. Also Please confirm you have given both nodes every permission.
– vembutech
Dec 10 '14 at 20:47
Please see edit #1. Both nodes have permissions and cluster is being created using a domain administrator account.
– mradarit
Dec 11 '14 at 16:47
I my case with similar error while trying to create a cluster on HP servers the problem was solved by installing latest NIC driver downloaded from HP support site or even from NIC vendor's [Broadcom or Intel] site.
– Sergey
Dec 16 '14 at 20:03
The validate stage may "pass" but it can pass conditionally. Was it all green? Or were there any yellow warning flags?
– Colyn1337
Dec 17 '14 at 18:19
I am having this problem right now in Windows Server 2012 R2, The "forming cluster" message appears for 2 minutes before the cluster create wizard fails and rolls back. The log is exactly the same as OP's log. Did anybody ever figure this out?
– Ty H.
May 24 '16 at 20:18
Can you post the cluster log ? so that we can check duplicate account that may have the same name as any of the nodes in the cluster, if so probably we need to remove those duplicate accounts. Also Please confirm you have given both nodes every permission.
– vembutech
Dec 10 '14 at 20:47
Can you post the cluster log ? so that we can check duplicate account that may have the same name as any of the nodes in the cluster, if so probably we need to remove those duplicate accounts. Also Please confirm you have given both nodes every permission.
– vembutech
Dec 10 '14 at 20:47
Please see edit #1. Both nodes have permissions and cluster is being created using a domain administrator account.
– mradarit
Dec 11 '14 at 16:47
Please see edit #1. Both nodes have permissions and cluster is being created using a domain administrator account.
– mradarit
Dec 11 '14 at 16:47
I my case with similar error while trying to create a cluster on HP servers the problem was solved by installing latest NIC driver downloaded from HP support site or even from NIC vendor's [Broadcom or Intel] site.
– Sergey
Dec 16 '14 at 20:03
I my case with similar error while trying to create a cluster on HP servers the problem was solved by installing latest NIC driver downloaded from HP support site or even from NIC vendor's [Broadcom or Intel] site.
– Sergey
Dec 16 '14 at 20:03
The validate stage may "pass" but it can pass conditionally. Was it all green? Or were there any yellow warning flags?
– Colyn1337
Dec 17 '14 at 18:19
The validate stage may "pass" but it can pass conditionally. Was it all green? Or were there any yellow warning flags?
– Colyn1337
Dec 17 '14 at 18:19
I am having this problem right now in Windows Server 2012 R2, The "forming cluster" message appears for 2 minutes before the cluster create wizard fails and rolls back. The log is exactly the same as OP's log. Did anybody ever figure this out?
– Ty H.
May 24 '16 at 20:18
I am having this problem right now in Windows Server 2012 R2, The "forming cluster" message appears for 2 minutes before the cluster create wizard fails and rolls back. The log is exactly the same as OP's log. Did anybody ever figure this out?
– Ty H.
May 24 '16 at 20:18
add a comment |
1 Answer
1
active
oldest
votes
I would also advise to check for duplicate Service Principal Names (SPNs) in your domain. In our case, we received the error because the SPN for the cluster had somehow already been registered to a different server.
Run the following command to find all duplicate SPNs in your domain:
SETSPN -X
If any of your SQL nodes, or Windows Cluster Name, or SQL Cluster Name is seen in the output, you'll need to remove the duplicate SPNs. For example:
HOST/SQLCLUSTER1 is registered on these accounts:
CN=APPSERVER04,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
CN=SQLCLUSTER1,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
MSServerClusterMgmtAPI/SQLCLUSTER1 is registered on these accounts:
CN=SQLCLUSTER1,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
CN=APPSERVER04,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
Delete the SPNs from the old server (preferably on a domain controller - you likely need to be a domain administrator to modify SPNs). In this example, SQLCLUSTER1 is the name we want to use for the current cluster we are trying to create, but oddly, some SPNs for the account are registered on an old server, APPSERVER04. Run these commands to remove them:
setspn -D HOST/SQLCLUSTER1 CORPAPPSERVER04$
setspn -D MSServerClusterMgmtAPI/SQLCLUSTER1 CORPAPPSERVER04$
edited Aug 24 '16 at 0:10
techraf
3,34981735
answered Aug 23 '16 at 19:45
MarkMark
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f650616%2fwindows-failover-cluster-create-cluster-wizard-error-occurred-while-creating%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I would also advise to check for duplicate Service Principal Names (SPNs) in your domain. In our case, we received the error because the SPN for the cluster had somehow already been registered to a different server.
Run the following command to find all duplicate SPNs in your domain:
SETSPN -X
If any of your SQL nodes, or Windows Cluster Name, or SQL Cluster Name is seen in the output, you'll need to remove the duplicate SPNs. For example:
HOST/SQLCLUSTER1 is registered on these accounts:
CN=APPSERVER04,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
CN=SQLCLUSTER1,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
MSServerClusterMgmtAPI/SQLCLUSTER1 is registered on these accounts:
CN=SQLCLUSTER1,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
CN=APPSERVER04,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
Delete the SPNs from the old server (preferably on a domain controller - you likely need to be a domain administrator to modify SPNs). In this example, SQLCLUSTER1 is the name we want to use for the current cluster we are trying to create, but oddly, some SPNs for the account are registered on an old server, APPSERVER04. Run these commands to remove them:
setspn -D HOST/SQLCLUSTER1 CORPAPPSERVER04$
setspn -D MSServerClusterMgmtAPI/SQLCLUSTER1 CORPAPPSERVER04$
edited Aug 24 '16 at 0:10
techraf
3,34981735
answered Aug 23 '16 at 19:45
MarkMark
1
add a comment |
I would also advise to check for duplicate Service Principal Names (SPNs) in your domain. In our case, we received the error because the SPN for the cluster had somehow already been registered to a different server.
Run the following command to find all duplicate SPNs in your domain:
SETSPN -X
If any of your SQL nodes, or Windows Cluster Name, or SQL Cluster Name is seen in the output, you'll need to remove the duplicate SPNs. For example:
HOST/SQLCLUSTER1 is registered on these accounts:
CN=APPSERVER04,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
CN=SQLCLUSTER1,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
MSServerClusterMgmtAPI/SQLCLUSTER1 is registered on these accounts:
CN=SQLCLUSTER1,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
CN=APPSERVER04,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
Delete the SPNs from the old server (preferably on a domain controller - you likely need to be a domain administrator to modify SPNs). In this example, SQLCLUSTER1 is the name we want to use for the current cluster we are trying to create, but oddly, some SPNs for the account are registered on an old server, APPSERVER04. Run these commands to remove them:
setspn -D HOST/SQLCLUSTER1 CORPAPPSERVER04$
setspn -D MSServerClusterMgmtAPI/SQLCLUSTER1 CORPAPPSERVER04$
edited Aug 24 '16 at 0:10
techraf
3,34981735
answered Aug 23 '16 at 19:45
MarkMark
1
add a comment |
I would also advise to check for duplicate Service Principal Names (SPNs) in your domain. In our case, we received the error because the SPN for the cluster had somehow already been registered to a different server.
Run the following command to find all duplicate SPNs in your domain:
SETSPN -X
If any of your SQL nodes, or Windows Cluster Name, or SQL Cluster Name is seen in the output, you'll need to remove the duplicate SPNs. For example:
HOST/SQLCLUSTER1 is registered on these accounts:
CN=APPSERVER04,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
CN=SQLCLUSTER1,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
MSServerClusterMgmtAPI/SQLCLUSTER1 is registered on these accounts:
CN=SQLCLUSTER1,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
CN=APPSERVER04,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
Delete the SPNs from the old server (preferably on a domain controller - you likely need to be a domain administrator to modify SPNs). In this example, SQLCLUSTER1 is the name we want to use for the current cluster we are trying to create, but oddly, some SPNs for the account are registered on an old server, APPSERVER04. Run these commands to remove them:
setspn -D HOST/SQLCLUSTER1 CORPAPPSERVER04$
setspn -D MSServerClusterMgmtAPI/SQLCLUSTER1 CORPAPPSERVER04$
edited Aug 24 '16 at 0:10
techraf
3,34981735
answered Aug 23 '16 at 19:45
MarkMark
1
I would also advise to check for duplicate Service Principal Names (SPNs) in your domain. In our case, we received the error because the SPN for the cluster had somehow already been registered to a different server.
Run the following command to find all duplicate SPNs in your domain:
SETSPN -X
If any of your SQL nodes, or Windows Cluster Name, or SQL Cluster Name is seen in the output, you'll need to remove the duplicate SPNs. For example:
HOST/SQLCLUSTER1 is registered on these accounts:
CN=APPSERVER04,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
CN=SQLCLUSTER1,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
MSServerClusterMgmtAPI/SQLCLUSTER1 is registered on these accounts:
CN=SQLCLUSTER1,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
CN=APPSERVER04,OU=Servers,OU=SQL,OU=usa,DC=corp,DC=company,DC=net
Delete the SPNs from the old server (preferably on a domain controller - you likely need to be a domain administrator to modify SPNs). In this example, SQLCLUSTER1 is the name we want to use for the current cluster we are trying to create, but oddly, some SPNs for the account are registered on an old server, APPSERVER04. Run these commands to remove them:
setspn -D HOST/SQLCLUSTER1 CORPAPPSERVER04$
setspn -D MSServerClusterMgmtAPI/SQLCLUSTER1 CORPAPPSERVER04$
edited Aug 24 '16 at 0:10
techraf
3,34981735
answered Aug 23 '16 at 19:45
MarkMark
1
edited Aug 24 '16 at 0:10
techraf
3,34981735
edited Aug 24 '16 at 0:10
techraf
3,34981735
edited Aug 24 '16 at 0:10
techraf
3,34981735
3,34981735
answered Aug 23 '16 at 19:45
MarkMark
1
answered Aug 23 '16 at 19:45
MarkMark
1
answered Aug 23 '16 at 19:45
MarkMark
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f650616%2fwindows-failover-cluster-create-cluster-wizard-error-occurred-while-creating%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you post the cluster log ? so that we can check duplicate account that may have the same name as any of the nodes in the cluster, if so probably we need to remove those duplicate accounts. Also Please confirm you have given both nodes every permission.
– vembutech
Dec 10 '14 at 20:47
Please see edit #1. Both nodes have permissions and cluster is being created using a domain administrator account.
– mradarit
Dec 11 '14 at 16:47
I my case with similar error while trying to create a cluster on HP servers the problem was solved by installing latest NIC driver downloaded from HP support site or even from NIC vendor's [Broadcom or Intel] site.
– Sergey
Dec 16 '14 at 20:03
The validate stage may "pass" but it can pass conditionally. Was it all green? Or were there any yellow warning flags?
– Colyn1337
Dec 17 '14 at 18:19
I am having this problem right now in Windows Server 2012 R2, The "forming cluster" message appears for 2 minutes before the cluster create wizard fails and rolls back. The log is exactly the same as OP's log. Did anybody ever figure this out?
– Ty H.
May 24 '16 at 20:18