Jump to content

Sql Server Replication Telsina Vallu Ravalamma... Help Kaval

Spartan

By Spartan
in Old Discussions

 Share

Recommended Posts

Betting Bangarraju Celebrity

Betting Bangarraju

Posted
Posted

SERVER-A,

Named SQL Instance: SERVER-A\AFDBCONNECT

IP: A:B:C:D

 

SERVER-B

Named SQL Instance: SERVER-A\AFDBCONNECT

IP: E:F:G:H

 

Environment:

 

DomainNameResolution ledu..its Workgroup Environment....ie: Server-A does'nt know what is SERVER-B, but Server-A knows who is E:F:G:H.

 

Databases Server-A nunchi Server-B lo replicate cheyaddaniki trying

 

SQL Server Configuration manager INSTANCE\PROTOCOLS lo TCP/IP disable chesi..Named Pipes kuda enabled

 

All SQL ports required are open on both the server  (UDP_1434, sqlservr.exe, sqlserverbrowser.exe)

 

 

SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified   vastundi......

 

2dwc9r8.png

 

 

evarikaina teliste inputs appreciated....

 

Things to check:

1. Make sure your database engine is configured to accept remote connections

• Start > All Programs > SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration
• Click on Surface Area Configuration for Services and Connections
• Select the instance that is having a problem > Database Engine > Remote Connections
• Enable local and remote connections
• Restart instance
 

2. Check the SQL Server service account

• If you are not using a domain account as a service account (for example if you are using NETWORK SERVICE), you may want to switch this first before proceeding
 

3. If you are using a named SQL Server instance, make sure you are using that instance name in your connection strings in your ASweb P.NET application

• Usually the format needed to specify the database server is machinename\instancename
• Check your connection string as well
 

<connectionStrings>

<add name="SampleConnectionString" connectionString="Data Source=machinename\instancename;Initial Catalog=AdventureWorks;Integrated Security=SSPI;Min Pool Size=5;Max Pool Size=60;Connect Timeout=30″ providerName="System.Data.SqlClient"/>

</connectionStrings>
 

4. You may need to create an exception on the firewall for the SQL Server instance and port you are using

• Start > Run > Firewall.cpl
• Click on exceptions tab
• Add the sqlservr.exe (typically located in C:\Program Files (x86)\Microsoft SQL Server\MSSQL.x\MSSQL\Binn, check your installs for the actual folder path), and port (default is 1433)
• Check your connection string as well
 

5. If you are using a named SQL Server instance, make sure you are using that instance name in your connection strings
 

6. Check SQLBrowser; check that it is running. You may also need to create an exception in your firewall for SQLBrowser.
 

7. Check that you have connectivity to the SQL Server. 

Note what you are using to connect: machine name, domain name or IP address? Use this when checking connectivity. For example if you are using myserver
• Start > Run > cmd
•netstat -ano| findstr 1433
•telnet myserver 1433
•ping -a myserver
 

Check what ports are IP addresses are being returned.
 

If you still can’t get any connection, you may want to create a SQL account on the server, a corresponding SQL user on the database in question, and just use this username/password combo in your web application.

  • Replies 51
  • Created
  • Last Reply

Top Posters In This Topic

  • Spartan

    20

  • ravula

    11

  • ZuniorVentiyar

    4

  • Betting Bangarraju

    3

Popular Days

Top Posters In This Topic

Popular Days

Spartan PRODUCER

Spartan

Posted
  • Author
Posted

@Bangarraju.....  avanni fix chesaka a issue arised...

 

now it is resolved man.. :D

Betting Bangarraju Celebrity

Betting Bangarraju

Posted
Posted

@Bangarraju.....  avanni fix chesaka a issue arised...

 

now it is resolved man.. :D

 

Cool. DB ni Test chesav annamaata... brahmilaugh.gif

Spartan PRODUCER

Spartan

Posted
  • Author
Posted

Cool. DB ni Test chesav annamaata... brahmilaugh.gif

 

DB ni test cheyadam endi..  brahmilaugh.gif   ok vidhamga adi kuda jargindi anuko..

Spartan PRODUCER

Spartan

Posted
  • Author
Posted

np: prefix entidi?

 

Protocol Prefix: explicitly specify which protocol you want to use to make connection.

 

Supported protocol prefix in Sql Server includes: “lpc:”, “np:”, “tcp:”, “via:”

Betting Bangarraju Celebrity

Betting Bangarraju

Posted
Posted

DB ni test cheyadam endi..  brahmilaugh.gif   ok vidhamga adi kuda jargindi anuko..

 

Kuch Kuch Kartha Hei.... Kuch Nahi Hotha Hei... Aur Fix Hotha jaathahei... brahmilaugh.gif

fakebabu001 Jr Artist

fakebabu001

Posted
Posted

SERVER-A,

Named SQL Instance: SERVER-A\AFDBCONNECT

IP: A:B:C:D

 

SERVER-B

Named SQL Instance: SERVER-A\AFDBCONNECT

IP: E:F:G:H

 

Environment:

 

DomainNameResolution ledu..its Workgroup Environment....ie: Server-A does'nt know what is SERVER-B, but Server-A knows who is E:F:G:H.

 

Databases Server-A nunchi Server-B lo replicate cheyaddaniki trying

 

SQL Server Configuration manager INSTANCE\PROTOCOLS lo TCP/IP disable chesi..Named Pipes kuda enabled

 

All SQL ports required are open on both the server  (UDP_1434, sqlservr.exe, sqlserverbrowser.exe)

 

 

SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified   vastundi......

 

2dwc9r8.png

 

 

evarikaina teliste inputs appreciated....

 I'm guessing server name or port number thappu ichhi undachhu, below links might help.

 

http://techpint.com/programming/error-26-%E2%80%93-error-locating-serverinstance-specified-sql-server

 

http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx

 

 

 Share
Go to topic listing
×
×
  • Create New...