January 20, 2014 at 9:00 am
Hello,
Hoping some one can advise, I am receiving the Error "The Distributer has not been installed correct(Microsoft SQL Server, Error: 20036", when I am trying to script the Replication Publication. What I don't understand is that I was able to do this when I set up the publication and when I check the publication via replication monitor it is running correctly.
The Publication and distributer are running on separate servers and I can script the distributer and replication jobs without any problems on the distribution server, I can also script another publication on another Server without any problems.
Can anyone help me on this please, as there is nothing specified anywhere else and the Microsoft website has drawn a blank.
January 21, 2014 at 7:28 am
The second problem, when I go to test the connection of the linked server call repl_distributor which is setup by the distributer it is failing to connect properly ie Server 'repl_distributor' is not configured for DATA ACCESS.(Mircrosoft SQL Server: 7411). Data Access is enable and I can browse through the catalog yet I still recieve this error?, I think its this that's causing my scripting error?
Can anyone help?
January 21, 2014 at 7:43 am
Hi,
please check if there is a wrong DISTRIBUTOR connected:
sp_get_distributor
I had the same error a few days before, i don't know how, but my "Distributor" was something else, but not an sql-server.
If there is the wrong distributor in your result, i can give you the query to drop and create the right distributor
Regards,
Andreas
January 21, 2014 at 7:54 am
Hi Andreas, Thanks for the post, I ran the proc mentioned and it returns the name of the distribution server on the publisher, on the distribution server every thing is marked enabled(1) and again it contains the correct name for the distribution server.
January 21, 2014 at 8:06 am
Hi,
could you please check all servernames of publisher, distributor and subscriber:
SELECT @@SERVERNAME
how do you connect to the server, local with SSMS or remote from distributor. Are there everywhere the same version of sql installed?
January 21, 2014 at 8:59 am
I think my problem is linked to the linked server DATA ACCESS, if we can get to the bottom of that then it should work as the generate scripts tries to query procs on the distribtion database on the distribution server Although in users and logins i've yet to find the elusive remote login account called distributor_admin under security logins and users.
January 21, 2014 at 9:05 am
Hi Andreas,
I've checked the Servernames they are all correct. We do use aliases on our clustered environments etc but that shouldn't cause this problem as replication is working correctly. It's just the script tasks and the linked servers I'm seeing problems with.
Thanks
Raj
January 22, 2014 at 7:25 am
I setup replication on a test server with the same settings as live and found no error generating the scripts but did find that the link server error also occurred there which means the link servers do not need to have data access available and the error occurs there also which means its probably a Microsoft bug.
January 22, 2014 at 7:46 am
Hi,
can you give us more details about your setup, SQL version, instances, user for replication, etc...
January 27, 2014 at 5:11 am
SQL version is 10.50.4279 for the publisher
The distributer is 10.50.4000.
The SQL Database that is replicated is running in SQL 2000 Compatibility Mode and was upgraded recently from SQL 2000(replication was rebuilt). I was able to script the task after rebuilding the replication but its suddenly stopped working in between the replication rebuild(last month) and now.
I'm not sure if theres anything else I can add.
I did use sp_removedbreplication to cleanup replication tables before the migration.
March 25, 2014 at 10:50 am
Hi Can some one assist,
I managed to find a few spare mins today looking into this problem.
I zoned in that the problem is relating to the sp_helpqreader_agent SP, and is the problem SP as it returns null for the @loc_distribdb which it retrieves from the CONVERT(sysname, SERVERPROPERTY('ServerName')) .
When I run @@Servername is showing correctly my alias name, but when I run the serverproperty statement above i recieve the actual SERVERNAME\ALIAS, which seems wrong and like its a bug. I've trawled around to find a solution but have not yet found a solution.
Is there any way around this so the name is displayed correctly?
April 1, 2014 at 8:13 am
logged this with microsoft a while ago:
not sure what the solution is as the replicated machine is clustered using SteelEye Lifekeeper and the network name is the machinename.
June 13, 2017 at 2:14 pm
If you have a remote distributor setup it must also be set as a publisher. Not having this set will produce error 20036.
The Workaround:
To get around the problem, you will have to mark the distribution server as a publisher as well. But you don't have to publish any articles from the distribution server's databases.
To mark the distributor as a publisher, follow these steps in SQL Server Management Studio (SSMS):
- Connect to the replication distribution server
- Right click on the "Replication" node in the server tree
- Select "Distributor Properties..." from the popup menu
- Click on the "Publishers" page in the left hand side pane
- Tick the check box against the name of the distribution server
- Click "OK", and provide any other requested information
The same can be performed from the query window of SSMS, using a system stored procedure called, sp_adddistpublisher. For more information about the parameters required by this procedure, see SQL Server 2005 Books Online.
June 13, 2017 at 3:21 pm
Rooster - Tuesday, June 13, 2017 2:14 PMIf you have a remote distributor setup it must also be set as a publisher. Not having this set will produce error 20036.The Workaround:
To get around the problem, you will have to mark the distribution server as a publisher as well. But you don't have to publish any articles from the distribution server's databases.To mark the distributor as a publisher, follow these steps in SQL Server Management Studio (SSMS):
- Connect to the replication distribution server
- Right click on the "Replication" node in the server tree
- Select "Distributor Properties..." from the popup menu
- Click on the "Publishers" page in the left hand side pane
- Tick the check box against the name of the distribution server
- Click "OK", and provide any other requested informationThe same can be performed from the query window of SSMS, using a system stored procedure called, sp_adddistpublisher. For more information about the parameters required by this procedure, see SQL Server 2005 Books Online.
Looks like the workaround steps, comments (even formatting) are quoted directly from this site:
SQL Server 2005 Replication Error : The Distributor has not been installed correctly
As he explains on his site and as it's explained in the connect item above for the issue, it's a bug with sys.sp_MSrepl_getdistributorinfo. If you read the connect comments, it doesn't appear to be an issue with all versions.
Sue
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply