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 (208 reputation)SSC Veteran (208 reputation)SSC Veteran (208 reputation)SSC Veteran (208 reputation)SSC Veteran (208 reputation)SSC Veteran (208 reputation)SSC Veteran (208 reputation)SSC Veteran (208 reputation)

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

Group: General Forum Members
Points: 208 Visits: 351
logged this with microsoft a while ago:

http://connect.microsoft.com/SQLServer/feedback/details/814236/the-distributer-has-not-been-installed-correctly-microsoft-sql-server-error-20036

not sure what the solution is as the replicated machine is clustered using SteelEye Lifekeeper and the network name is the machinename.
Rooster
Rooster
SSC Journeyman
SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)

Group: General Forum Members
Points: 90 Visits: 336
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.
Sue_H
Sue_H
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12962 Visits: 5174
Rooster - Tuesday, June 13, 2017 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.

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




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