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.
Related
My objective is to use the migration tool in SQL Developer to migrate 2 SQL Server databases to Oracle. I am attempting to connect to a SQL Server database at a remote location using Oracle SQL Developer 4.0.
I have installed jtds.1.3.0.jar per instructions, and get the SQL Server and Sybase tabs in the connection properties window.
I have entered the user, pw, hostname, port, and database name. When I try to Retrieve Database, or connect, I get the error message:
Status : Failure -Test failed: I/O Error: DB server closed connection.
The SQL Server DBA tells me her error logs contain the following error message:
Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgrade your client library. [CLIENT: (my computer's IP address)] Error: 17835, Severity: 20, State: 1.
When I look at SQL Server documentation about this error message, it talks about certificates and SQL Server Connection Manager. Some relevant information to show that I've covered the basics:
Using the same connection parameters, I am able to connect to the SQL Server database using Toad for SQL Server.
Using the same connection parameters, a DBA set up an Oracle Transparent Gateway, and I can connect to the SQL Server database using the gateway and a database link. (As far as I know, neither of these methods required a certificate to connect.)
Both of these use ODBC; SQL Developer uses jdbc with TCP/IP.
The DBA assures me TCP/IP connection is turned on for the SQL Server databases.
I have gone into the XML file where SQL Developer stores the connection string. It has the form jdbc:jtds:sqlserver://sql-xxx-xxx.mw.nos.xxx.com:1433/my_db, which looks correct. I have tweaked it by adding the instance name, but no difference. The database has a default instance name, anyway, so it shouldn't be necessary.
A co-worker has been able to connect to a local SQL Server database on the same machine where SQL Developer was running (both on his laptop).
As a workaround, I am also pursuing the possibility of installing SQL Server on a local workstation, and copying the databases there for processing, but I don't know if I can get approval. If you know another tool for migrating from SQL Server to Oracle, please also let me know.
Thanks in advance.
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
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'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.
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