SQL Server 2014/16 transaction replication - sql-server

I have a sql 2012 publisher(transaction) database. This publisher is good and working with other instance. When I try to create a subscriber from a sql 2016 named instance with a static PORT I'm having problem. I have created alias on both instances. Restarted SQL. I can use this alias from ssms from either server and works.
When I create and add subscription instance it would not take the named instance with port. It takes only default\named not default\named,1234. not even alias. If I add server sp_addserver for either alias or default\named,1234 it says already exist. I also see error "Replication requires the actual server name to make a connection."
If I use default\named it will create subscription but it will keep retrying. distibutor to subscriber job will keep retrying. I see messages like "A network-related or instance-specific error has occurred while establishing a connection to SQL Server"
Please help.

Sometimes, this error has been observed on a server that had been renamed after the original installation of SQL Server, and where the SQL Server configuration function ‘##SERVERNAME’ still returned the original name of the server.
Can you run the below command and see if that's the same name you are giving in subscription as well?
select ##SERVERNAME
If you see mismatch you can change it using
sp_addserver 'real-server-name', LOCAL

Related

Unable to connect to another connection in SSAS Tabular

I have a very weird issue with SSAS Tabular connecting to a SQL Server source database. I've spent almost the entire day on this, and searched online in various ways to find a helpful answer, but none of the suggestions solved this mysterious problem for me.
It used to work fine, but I tried various connection settings (Windows vs SQL authentication, and different impersonation modes), but now I no longer can get it to work (even if I revert back to the previous bim file in source control).
When I process a table from the WORKSPACE database (through SSMS), it works. But when I process a table from the DEPLOYED database (still through SSMS), it does NOT work.
The connection I am using is:
-SQL Server Native Client 11.0
-Windows Authentication
-Impersonation mode of a Windows account (which has the appropriate permissions)
The source database is in a SQL Server database located on a different server (but in the same network).
I have searched everywhere online, but didn't find anything that could help me.
I have tried changing the connection driver (OLE DB Provider for SQL Server), and I have restarted the SSAS Tabular service.
The full error message I get when trying to process a table on the deployed database is:
Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error: Login timeout expired; HYT00; A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [5]. ; 08001.
A connection could not be made to the data source with the Name of 'DataWarehouse'.
'.
In fact, after I tried a second time to restart the SSAS Tabular service, the error message I get after attempting to process a table is slightly different:
Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.; 08001; SSL Provider: The requested security package does not exist
; 08001; Client unable to establish connection; 08001; Encryption not supported on the client.; 08001.
A connection could not be made to the data source with the Name of 'DataWarehouse'.
'.
According to your description, it seems to be related to connection problem. You need to check whether corresponding SQL server service and SSAS Service is running(check server which contains "DataWarehouse" is running and can be connected). You could go to "SQL Server Configuration Manager " to restart them.
In addition, you also need to make sure your current windows credential can access this database(if you use window credential). And check whether this server enable remote connect.
Zoe

Add remote subscriber SQL Server

I am getting this error:
SQL Server replication requires the actual server name to make a connection to the server. Specify the actual server name, 'Bla'. (Replication.Utilities)
I am aware of this:
http://www.cryer.co.uk/brian/sqlserver/replication_requires_actual_server_name.htm
and I have applied it. Unfortunately, the error persists. How can I add a remote subscribers with either an IP or DNS name?
PS:
This seems to help.
Turns out I had to do this:
Create aliases publisher side as described here
As my publisher is sql server 2012 and my subscriber sql server 2014 I had to use SSMS 2014 publisher side as described here.

Wrong SERVER NAME in SQL Server 2012

First, I started the SQL Server Browser in SQL Server Configuration Manager, because it was stopped. No problem to that, done. Next I started the SQL Server Agent, but there was an error:
"The request failed or the service did not respond in a timely fashion. . .".
I also fixed that in SQL Server Instance name properties. Then I successfully started the SQL Server Agent. Then, I tried to go and put the server name in SQL Server 2012..
BUT THERE'S STILL AN ERROR! I don't know what to do any more. The server name is default. MSSQLSERVER I tried to put MSSQLSERVER, PCNAME\MSSQLSERVER... error is still there. what should I do?
The MSSQLSERVER service is the default, un-named instance - which means you can connect to it using a server/instance name of:
.
(local)
localhost
pcname
The point is: it's the unnamed instance, so you don't have to specify any instance name like MSSQLSERVER at all

I cannot add new publication for snapshot replication

i'm gonna create a snapshot replication on sql server 2008 R2 database instance, but when on Replication Node, on Local publications , i'm using new publication sub menu, i get this error Message :
New Publication Wizard
SQL Server is unable to connect to server '192.168.1.7'.
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1&EvtSrc=Microsoft.SqlServer.Management.UI.PubWizardErrorSR&EvtID=CantConnect&LinkId=20476
ADDITIONAL INFORMATION:
SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, 'SHAHEDINSTDB02'. (Replication.Utilities)
when i use computer name for connecting to sql server, after connecting, i get this error message again,
could you please he;p me?
You may have an instance name too like SharedDBServer\DB02. You will have to use that full name. If SQL browser isn't running, create a sql alias to define the port it will need to connect with.

SQL Server Replication connection error

After I renamed my PC, I couldn't create new paublications, for database replication in SQL Server 2005.
I receive un error "SQL Server replication requires the actual server name to make connection to the server."
When I returned my old PC name, the problem solved. How could I make use of replication after renaming the PC?
The SQL Service itself still thinks it has the old server name, and since it has the habit of referring to itself in the third person, this causes problems when the underlying server name has changed. You need to take the following steps to correct it:
Run "Select ##ServerName" to verify the servername - it should be the old name.
sp_dropserver ‘OLDSERVERNAME’
sp_addserver ‘NEWSERVERNAME’, local
Restart both the SQL Service and the Agent Service
Run step 1 again to confirm that the server name is now correct

Resources