Solved

Can't connect to SQL Server 2008 after P2V migration

Posted on 2014-02-24
6
883 Views
Last Modified: 2014-02-24
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!
0
Comment
Question by:data_bits
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 11

Expert Comment

by:David Kroll
ID: 39882539
0
 
LVL 8

Assisted Solution

by:Jeff Perry
Jeff Perry earned 500 total points
ID: 39882551
Have you tried changing the port?

Something seems to have happened during the conversion that is telling SQL that the default port is in use.
0
 
LVL 19

Expert Comment

by:Miguel Angel Perez Muñoz
ID: 39882557
Maybe is bind to older IP?
0
Raise the IQ of Your IT Alerts

From IT major incidents to manufacturing line slowdowns, every business process generates insights that need to reach the people required to take action. You need a platform that integrates with your business tools to create fully enabled DevOps toolchains.

You need xMatters.

 

Author Comment

by:data_bits
ID: 39882663
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?
0
 
LVL 8

Accepted Solution

by:
Jeff Perry earned 500 total points
ID: 39882678
The 10048 error is a port in use error.

Something on the SQL server is already using the port that SQL is trying to start on.
0
 

Author Comment

by:data_bits
ID: 39882743
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.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
Recently we ran in to an issue while running some SQL jobs where we were trying to process the cubes.  We got an error saying failure stating 'NT SERVICE\SQLSERVERAGENT does not have access to Analysis Services. So this is a way to automate that wit…
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question