data_bits
asked on
Can't connect to SQL Server 2008 after P2V migration
Our server was migrated from a physical server to a virtual server and now we can't connect to SQL Server. We keep getting this error:
"A network-related or instance specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that the SQL Server is configured to allow remote connections. (Provider (TCP Provider, error: 0 - Only one usage of each socket address (protocol/network address/port) is permitted.) (Microsoft SQL Server, error 10048)
I checked and TCPIP is enable and the SQL Server process is running.
I can login to the server but I can't connect to SQL Server either using Windows authentication or database authentication.
What is missing here?
TIA!
"A network-related or instance specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that the SQL Server is configured to allow remote connections. (Provider (TCP Provider, error: 0 - Only one usage of each socket address (protocol/network address/port) is permitted.) (Microsoft SQL Server, error 10048)
I checked and TCPIP is enable and the SQL Server process is running.
I can login to the server but I can't connect to SQL Server either using Windows authentication or database authentication.
What is missing here?
TIA!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Maybe is bind to older IP?
ASKER
This just in, apparently it was not migrated to a VM. There are two servers with very similar names, one of which was migrated. This one that we're getting the 10048 error on, was not migrated.
However, it is suspicious that this one started to have problems after the other one was migrated.
Could a duplicate IP# cause this behaviour?
However, it is suspicious that this one started to have problems after the other one was migrated.
Could a duplicate IP# cause this behaviour?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The decision was made to reboot the server since it had been up for a while.
When it came back up, everything was accessible.
Thanks everyone for the input.
When it came back up, everything was accessible.
Thanks everyone for the input.
http://support.microsoft.com/kb/328476