Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Cannot connect to remote DB server from Upgraded SQL Server 2012 Expand / Collapse
Author
Message
Posted Friday, March 29, 2013 9:37 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, May 29, 2013 7:55 AM
Points: 2, Visits: 11
Due to ERP upgrade we're upgrading our SQL Server from 2005 to 2012. Our current DB servers (Access thru Microsoft VM) are as follow:

Production environment: Windows 2003 Server 32-bits, SQL Server 2005 - let call it ‘DBSrvProd’
Test environment: Windows 2003 Server 32-bits, SQL Server 2005 – ‘DBSrvTest’
Upgrade Test environment: Windows 2008 Server R2 64-bits, SQL Server 2012 – ‘DBSrvUpg’

In the Upgrade environemnt’s SSMS we created DB Engine ‘DBSrvUpg’ and we try to connect to our old SQL Server 2005 DB Engine (DBSrvProd and DBSrvTest) so that we can migrate DB to DBSrvUpg, we are able to connect DBSrvTest with no issue at all, however we are not able to connect to 'DBSrvProd'. We are getting the following error:

-----------------------------------------------------------------------
Cannot connect to DBSrvProd.

ADDITIONAL INFORMATION:
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 SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
-----------------------------------------------------------------------------

We have compared all configurations between the Prod and Test environment and it appears to be identical, thus we're puzzle why we can connect to one but not the other. We have checked the following between the two servers:

1. SQL Server Configuration Manager's TCP/IP all appears to be enabled and set to default port: 1433
2. SSMS instance for DBSrvProd and DBSrvTest 'Allow Remote Connections' checked
3. The Firewall Windows service (ipc) are both disabled, when I enabled it and check the properties they both have similar setup

All of the three servers are login with SQL Authencation as 'sa', which belongs to sysadmin server role. Please Help!
Post #1437175
Posted Friday, April 5, 2013 8:07 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 8:38 AM
Points: 4,655, Visits: 11,125
Troubleshoot the obvious first: use portqry to test if the server is reachable from the remote machine. If not, something (firewall) is filtering the traffic.

--
Gianluca Sartori

How to post T-SQL questions
spaghettidba.com
@spaghettidba
Post #1439238
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse