Error 7201: Could not execute procedure on remote server "repl_distributor' because SQL Server is not configured for remote access.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: SniperX (anonymous_at_discussions.microsoft.com)
Date: 03/16/04 

Date: Tue, 16 Mar 2004 15:31:08 -0800

I have a replication issue between SQLSERVER1 and SQLSERVER2. SQLSERVER1 is the distributor in a remote distributor replication configuration. SQLSERVER2 is the publisher. The log reader has been showing errors all morning. When I try to start the Log Reader Agent it looks like it is processing transactions, but then fails. The agent details just show "The step did not generate any output. The step failed."

I cannot manage the subscriptions from the distributor either. If I try to create a new publication or delete an old one I get:

Error 7201: Could not execute procedure on remote server "repl_distributor'
because SQL Server is not configured for remote access. Ask your system
administrator to reconfigure SQL Server to allow remote access.

I am not finding much in BOL or on Microsoft's KB. Any suggestions?

Thanks,

SniperX

Relevant Pages

  • Re: cannot delete publication
    ... Named Pipes Provider: No process is on the other end of the pipe. ... We lost our distributor and I reinstall SQL Server in Distributor ... Now I am not able to delete publication and subscription from publisher ...
    (microsoft.public.sqlserver.replication)
  • Error 7201: Could not execute procedure on remote server "repl_distributor because SQL Server i
    ... I cannot manage the subscriptions from the distributor either. ... If I try to create a new publication or delete an old one I get: ... administrator to reconfigure SQL Server to allow remote access. ...
    (microsoft.public.sqlserver.replication)
  • Re: Replace SQL view on merge
    ... not a different distributor - in fact this is not possible to another ... publication from the same publisher. ... Paul Ibison SQL Server MVP, ...
    (microsoft.public.sqlserver.replication)
  • Re: Transactional replication
    ... The publication will exist only on the publisher. ... The snapshot folder will be defined on the distributor or you can use an ... Paul Ibison SQL Server MVP, ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication Monitor didnt work because different collations
    ... Looking for a SQL Server replication book? ... SQL 2005 filtered merge replication. ... We changed collations to match the server collation and Replication ... After this change we started all publication snapshots. ...
    (microsoft.public.sqlserver.replication)