Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I'm trying to create a sql server 2008 R2 cluster.

I've got two windows machines running server 2008 that are clustered and have all passed the validation tests etc.

I'm now going through the "Install a sql server failover cluster" wizard and am on the "Instance Configuration" page.

This is a brand new machine with nothing but windows and .net3.5 installed. I've given it a sql server network name, named the instance differently, the instance ID is the same as the instance name.

Hit next and I get the following error

[Error Message]
The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid.'

[Details]
Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException: The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the Clustered SQL instance due to the following error: 'The network address is invalid.'

Has anyone seen this before and found a solution? I've tried google and came up with sites saying it was a bug with the installer and to tweak the registry which sounded dodgy.

If you need any more information I'll provide anything you ask for, I wasn't sure what would be useful.

Thank you

share|improve this question

migrated from stackoverflow.com Sep 2 '11 at 21:15

This question came from our site for professional and enthusiast programmers.

    
I've found the fix. social.msdn.microsoft.com/Forums/uk-UA/sqlsetupandupgrade/… uninstall VMware tools, install SQL Server 2008 in clustered mode, then reinstall vmware tools. Something in VMware tools seems to be causing the problem. –  Blootac Aug 31 '11 at 13:43

1 Answer 1

up vote 1 down vote accepted

I've found the fix. http://social.msdn.microsoft.com/Forums/uk-UA/sqlsetupandupgrade/thread/d96afca2-9cb7-4a5c-b8a9-9ee2d3fedef1

Here is a workaround for this issue that appears under the following conditions; VMware ESX 4 Update 1 SQL Server 2008 slipstreamed with SP1 Windows Server 2008 R2

You will need to use E1000 network adapters (as the drivers are included in windows), uninstall VMware tools, install SQL Server 2008 in clustered mode, then reinstall vmware tools. Something in VMware tools seems to be causing the problem.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.