Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

The Distributer Has not been Installed Correctly - Error 2036 SQL 2008 R2 Expand / Collapse
Author
Message
Posted Monday, January 20, 2014 9:00 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, November 20, 2014 6:38 AM
Points: 30, Visits: 313
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.
Post #1532709
Posted Tuesday, January 21, 2014 7:28 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, November 20, 2014 6:38 AM
Points: 30, Visits: 313
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?
Post #1533058
Posted Tuesday, January 21, 2014 7:43 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 2:52 AM
Points: 49, Visits: 383
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
Post #1533073
Posted Tuesday, January 21, 2014 7:54 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, November 20, 2014 6:38 AM
Points: 30, Visits: 313
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.
Post #1533091
Posted Tuesday, January 21, 2014 8:06 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 2:52 AM
Points: 49, Visits: 383
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?

Post #1533105
Posted Tuesday, January 21, 2014 8:59 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, November 20, 2014 6:38 AM
Points: 30, Visits: 313
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.
Post #1533180
Posted Tuesday, January 21, 2014 9:05 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, November 20, 2014 6:38 AM
Points: 30, Visits: 313
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
Post #1533192
Posted Wednesday, January 22, 2014 7:25 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, November 20, 2014 6:38 AM
Points: 30, Visits: 313
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.
Post #1533623
Posted Wednesday, January 22, 2014 7:46 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 2:52 AM
Points: 49, Visits: 383
Hi,
can you give us more details about your setup, SQL version, instances, user for replication, etc...

Post #1533645
Posted Monday, January 27, 2014 5:11 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, November 20, 2014 6:38 AM
Points: 30, Visits: 313
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.

Post #1534942
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse