Jump to content

Sql Server Replication Telsina Vallu Ravalamma... Help Kaval


Recommended Posts

Posted

try this

 

Try this, open Windows Firewall>Advanced setting. Find the SQL Server Rule (it may have a custom name). Right-Click and go to properties, then Programs and Services Tab. If Programs-This program is selected, you should browse for the proper version of sqlserver.exe.

 

example C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\Sqlservr.exe.

  • Replies 51
  • Created
  • Last Reply

Top Posters In This Topic

  • Spartan

    20

  • ravula

    11

  • ZuniorVentiyar

    4

  • Betting Bangarraju

    3

Top Posters In This Topic

Posted

try this

 

Try this, open Windows Firewall>Advanced setting. Find the SQL Server Rule (it may have a custom name). Right-Click and go to properties, then Programs and Services Tab. If Programs-This program is selected, you should browse for the proper version of sqlserver.exe.

 

 

rule leka pothe create one

xeifdj.jpg  both inbound and outbound rules lo..... sqlservr.exe and sqlbrowser.exe, related version ve added...

Posted

do this man

 

go to SSMS: EXEC xp_readerrorlog
And look for the line with "SQL server listening on...", probably the port isn't 1433

Posted

do this man

 

go to SSMS: EXEC xp_readerrorlog
And look for the line with "SQL server listening on...", probably the port isn't 1433

 

default ports are UDP 1434, TCP 1433.....OPEN

 

Dynamic TCP's on both : TCP 49301 on A, and TCP 49311 on B ---> OPEN 

 

 

thanks for checking man.....may be i will try out again tomorrow.....

 

incase any more input..please post it here..

Posted

at what stage are you getting that error?

could you brief us like what have you done till now regarding replication

when did you get that error?

Posted

do this

Create a TCP/IP alias on publisher server with same name as susbcriber server\ instance with correct port.

Make sure that when you run select @@servername on subscriber it returns you the correct server name

Another thing to remember

Alias names can be case sensitive

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....

In general when you r replicating or clustering two instances they always tend to take hostnames instead of ips. Check wht Server A is refering to i.e servb ip or hostname. If it is hostname try to change it to ip...if you can change then add serverb hostname and ip in server a's host.conf file.

Posted

Issue resolved,

 

nenu Named Pipes protocol enable chesa, kaani SQL instance ki mundu "np:" ani prefix add cheyadam maricha..

 

it resolved the issue. 

 

thanks everyone for helping out....

×
×
  • Create New...