Showing posts with label distributor. Show all posts
Showing posts with label distributor. Show all posts

Tuesday, March 27, 2012

Can not generate snapshot (SQl Server 2005 Transactional Repl )

Hi,

This is my first try at implementing transactional replication (Sql Server 2005). My Publisher and Distributor are on different instances of SQL. I am receiving the following error during execution of setp 2 in snapshot agent:

2005-09-15 19:09:48.39 Connecting to Distributor 'WLN-SQL2005DEV\WDC_DIST'
2005-09-15 19:09:48.61 The replication agent had encountered an exception.
2005-09-15 19:09:48.61 Source: Replication
2005-09-15 19:09:48.61 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentException
2005-09-15 19:09:48.61 Exception Message: The snapshot could not be generated because the publisher is inactive.
2005-09-15 19:09:48.61 Message Code: 54057

Can anyone help me out with this?

Thank you,

NickCan you elaborate how you got into this situation?

To fix the problem, you can call the following stored procedure:

sp_changedistpublisher 'YOUR-PUBLISHER-NAME', 'active', 'true'
|||I just got into that situation. I am not sure exactly how I got there but it occured after one or more instances of removing the distibutor, publisher and subscriber and trying to recreate them.

Can not generate snapshot (SQl Server 2005 Transactional Repl )

Hi,

This is my first try at implementing transactional replication (Sql Server 2005). My Publisher and Distributor are on different instances of SQL. I am receiving the following error during execution of setp 2 in snapshot agent:

2005-09-15 19:09:48.39 Connecting to Distributor 'WLN-SQL2005DEV\WDC_DIST'
2005-09-15 19:09:48.61 The replication agent had encountered an exception.
2005-09-15 19:09:48.61 Source: Replication
2005-09-15 19:09:48.61 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentException
2005-09-15 19:09:48.61 Exception Message: The snapshot could not be generated because the publisher is inactive.
2005-09-15 19:09:48.61 Message Code: 54057

Can anyone help me out with this?

Thank you,

NickCan you elaborate how you got into this situation?

To fix the problem, you can call the following stored procedure:

sp_changedistpublisher 'YOUR-PUBLISHER-NAME', 'active', 'true'
|||I just got into that situation. I am not sure exactly how I got there but it occured after one or more instances of removing the distibutor, publisher and subscriber and trying to recreate them.

Sunday, March 25, 2012

Can not create my Publisher

Hi,
I install Sql server 2000 on a server named JMI_SQL
After Installation we decide to rename the server JMI_SQL for SQL2007
I create a Distributor on the server SQLDIST2007
Once my distibutor created i try to create my Publisher on SQL2007 and I
receive this message
Error 18482 Could not connec to server SqlDIST2007 because JMI_SQL is not
defined as a remote Server
In the Wizard when I was creating my Publisher I select SQl2007 as Publisher
and the wizard is looking for JMI_SQL which the old name of the server
I try those commands in sql query analyser to get some information
select @.@.servername Show JMI_SQL
SELECT srvname, srvid
FROM sysservers
Show this
ADAMM_DB1
BESERVER_DB2
CATALOG_DB3
JMI_SQL0
repl_distributor 4
In the tables master.sysservers I try to Change manually all the JMI_SQL for
SQL2007 Sql server dont let me change it
Is there a way that I can change the JMI_SQL for SQL2007 in the sysservers
table
I would like to avoid to uninstall and reinstall Sql Server 2000
Before trying to do something I would like to have an advise from
experimented person on how to do that.
Thanks in advance and have a nice day!
Hi Gav,
Thanks a lot for the information
I appreciate very much !
Have a nice day
"Gav" wrote:

> Using Query Analyzer, execute the following:
> Use master
> go
> sp_dropserver 'JMI_SQL', droplogins
> go
> sp_addserver 'SQL2007', LOCAL
> go
> After you have done this make sure you restart the SQL service or restart
> your computer (whichever you fancy!) and that should do it
> Regards
> Gav
> "GC" <GC@.discussions.microsoft.com> wrote in message
> news:65162A3C-16DB-43C1-884D-601056BEFAF8@.microsoft.com...
>
>
sql

Thursday, March 22, 2012

Can not connect to distributor because distributor_admin is not defined as remote login

Hello everyone,
We set up replication yesterday and it runs beautifully ... once. After
the first replication, we get the following error whenever we try to
access any of the replication admin screens, with the exception of the
"disable replication" screen:
Error 18483: Could not connect to server XXXX because
'distributor_admin' is not defined as a remote login at the server.
Our setup consists of two SQL Server machines, a primary server which
acts as a publisher and a secondary which acts as both distributor and
subscriber. Replication setup works great, as does the initial snapshot
copy. The transaction agent works perfectly as well.
The error goes away if I disable publishing on both machines and set it
up again, but then it breaks as soon as I complete the initial
replication.
Any help? This has everyone here stumped.
Thanks!!
Sorry - posted this to the wrong group. Please ignore.
rich@.adgooroo.com wrote:
> Hello everyone,
> We set up replication yesterday and it runs beautifully ... once. After
> the first replication, we get the following error whenever we try to
> access any of the replication admin screens, with the exception of the
> "disable replication" screen:
> Error 18483: Could not connect to server XXXX because
> 'distributor_admin' is not defined as a remote login at the server.
> Our setup consists of two SQL Server machines, a primary server which
> acts as a publisher and a secondary which acts as both distributor and
> subscriber. Replication setup works great, as does the initial snapshot
> copy. The transaction agent works perfectly as well.
> The error goes away if I disable publishing on both machines and set it
> up again, but then it breaks as soon as I complete the initial
> replication.
> Any help? This has everyone here stumped.
> Thanks!!