SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


The Distributer Has not been Installed Correctly - Error 2036 SQL 2008 R2


The Distributer Has not been Installed Correctly - Error 2036 SQL 2008 R2

Author
Message
rajaster
rajaster
SSC Veteran
SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)

Group: General Forum Members
Points: 234 Visits: 351
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.
rajaster
rajaster
SSC Veteran
SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)

Group: General Forum Members
Points: 234 Visits: 351
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?
Andreas Kreuzberg
Andreas Kreuzberg
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1107 Visits: 1038
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
rajaster
rajaster
SSC Veteran
SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)

Group: General Forum Members
Points: 234 Visits: 351
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.
Andreas Kreuzberg
Andreas Kreuzberg
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1107 Visits: 1038
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?
rajaster
rajaster
SSC Veteran
SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)

Group: General Forum Members
Points: 234 Visits: 351
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.
rajaster
rajaster
SSC Veteran
SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)

Group: General Forum Members
Points: 234 Visits: 351
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
rajaster
rajaster
SSC Veteran
SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)

Group: General Forum Members
Points: 234 Visits: 351
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.
Andreas Kreuzberg
Andreas Kreuzberg
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1107 Visits: 1038
Hi,
can you give us more details about your setup, SQL version, instances, user for replication, etc...
rajaster
rajaster
SSC Veteran
SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)SSC Veteran (234 reputation)

Group: General Forum Members
Points: 234 Visits: 351
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search