Showing posts with label experiencing. Show all posts
Showing posts with label experiencing. Show all posts

Friday, March 23, 2012

replication problems sql server to db2

I am experiencing problems replicating (transactional) from SQL Server
2000 sp3 to DB2 v8.2 (running on Red Hat Linux).

I have created an OLE-DB linked server to DB2. The connection connects
successfully in EM and I can query the DB2 tables using the OPENQUERY
function.

I have successfully added the linked server connection as a Subscriber.
I have now set up a Push Subscription to DB2 from one of my
Publications.

My Distribution Agent errors with:
"The process could not connect to Subscriber xxx "

Any suggestions will help, thank youI have no idea myself, but you might get a better response in
microsoft.public.sqlserver.replication.

Simon|||I have no idea myself, but you might get a better response in
microsoft.public.sqlserver.replication.

Simon

Replication Problems from Subscriber to Publisher.

Hi,
I am experiencing some difficulties with DataBase Replication. I have
two SQL 2000 servers running on different machines (The server is
running on Windows 2000 Server, and the other on Window 2000
Professional).
I have created a database with one table. Have then Published this
database, and setup a Subscription. (The Publication is Transactional,
using Immediate updating.)
If I amend/insert/delete any rows/columns at the Publisher, the
changes are immediately propagated to the Subscriber. The problem I'm
having is when the Subscriber makes any changes to the Table, SQL
generates the following error:
Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Could
not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
'SQLOLEDB'.
I have used the Profiler, and determined that the table change
executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
then failing when it try's to execute the following statement:
exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLServer;UID=s a;PWD=;').[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
...
And since I didn't want to re-code the triggers automatically created
by SQL, I'm trying to figure out why the execution of the Remote
Stored
Procedure doesn't work.
Any help is much appreciated.
Thanks in Advance.
Rick 8-)
Two things to check. First, make sure the distributor and/or the publisher
servers have allowed remote proc execution through sp_configure.
Next, make sure your Win 2K Pro installation is running the SQL Server
service accounts under an id that has access to the distributor/publisher or
has the correct sign-in information.
Sincerely,
Anthony Thomas
"Rick Knight" wrote:

> Hi,
> I am experiencing some difficulties with DataBase Replication. I have
> two SQL 2000 servers running on different machines (The server is
> running on Windows 2000 Server, and the other on Window 2000
> Professional).
> I have created a database with one table. Have then Published this
> database, and setup a Subscription. (The Publication is Transactional,
> using Immediate updating.)
> If I amend/insert/delete any rows/columns at the Publisher, the
> changes are immediately propagated to the Subscriber. The problem I'm
> having is when the Subscriber makes any changes to the Table, SQL
> generates the following error:
> Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Could
> not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
> 'SQLOLEDB'.
> I have used the Profiler, and determined that the table change
> executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
> then failing when it try's to execute the following statement:
> exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLServer;UID=s a;PWD=;').[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
> ...
> And since I didn't want to re-code the triggers automatically created
> by SQL, I'm trying to figure out why the execution of the Remote
> Stored
> Procedure doesn't work.
> Any help is much appreciated.
> Thanks in Advance.
> Rick 8-)
>
|||Thanks for the feedback Anthony, But I have check both of these, and
still no luck. Now however the error message is different.
Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB
error trace [OLE/DB Provider 'SQLOLEDB' IUnknow QueryInterface
returned 0x80070005: Access denied.
BTW: Replication from the Publisher to the Subscriber still works okay
though.
Have you any other suggestions?
Thanks in Advance
Rick
"AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message news:<4DCC547D-F875-4F14-8B65-F02CD34B8088@.microsoft.com>...[vbcol=seagreen]
> Two things to check. First, make sure the distributor and/or the publisher
> servers have allowed remote proc execution through sp_configure.
> Next, make sure your Win 2K Pro installation is running the SQL Server
> service accounts under an id that has access to the distributor/publisher or
> has the correct sign-in information.
> Sincerely,
>
> Anthony Thomas
>
> "Rick Knight" wrote:
|||That error message means you've granted the publisher/distributer SQL Agent
account access to the subscriber machine but that the reverse is not true.
In order to do a Pull, the subscriber must have login rights to the
distributer/publisher server.
Sincerely,
Anthony Thomas
"Rick Knight" wrote:

> Thanks for the feedback Anthony, But I have check both of these, and
> still no luck. Now however the error message is different.
> Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB
> error trace [OLE/DB Provider 'SQLOLEDB' IUnknow QueryInterface
> returned 0x80070005: Access denied.
> BTW: Replication from the Publisher to the Subscriber still works okay
> though.
> Have you any other suggestions?
> Thanks in Advance
> Rick
>
> "AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message news:<4DCC547D-F875-4F14-8B65-F02CD34B8088@.microsoft.com>...
>
sql

Replication Problems from Subscriber to Publisher.

Hi,
I am experiencing some difficulties with DataBase Replication. I have
two SQL 2000 servers running on different machines (The server is
running on Windows 2000 Server, and the other on Window 2000
Professional).
I have created a database with one table. Have then Published this
database, and setup a Subscription. (The Publication is Transactional,
using Immediate updating.)
If I amend/insert/delete any rows/columns at the Publisher, the
changes are immediately propagated to the Subscriber. The problem I'm
having is when the Subscriber makes any changes to the Table, SQL
generates the following error:
Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]
Could
not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
'SQLOLEDB'.
I have used the Profiler, and determined that the table change
executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
then failing when it try's to execute the following statement:
exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLSe
rver;UID=sa;PWD=;').
[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
...
And since I didn't want to re-code the triggers automatically created
by SQL, I'm trying to figure out why the execution of the Remote
Stored
Procedure doesn't work.
Any help is much appreciated.
Thanks in Advance.
Rick 8-)Two things to check. First, make sure the distributor and/or the publisher
servers have allowed remote proc execution through sp_configure.
Next, make sure your Win 2K Pro installation is running the SQL Server
service accounts under an id that has access to the distributor/publisher or
has the correct sign-in information.
Sincerely,
Anthony Thomas
"Rick Knight" wrote:

> Hi,
> I am experiencing some difficulties with DataBase Replication. I have
> two SQL 2000 servers running on different machines (The server is
> running on Windows 2000 Server, and the other on Window 2000
> Professional).
> I have created a database with one table. Have then Published this
> database, and setup a Subscription. (The Publication is Transactional,
> using Immediate updating.)
> If I amend/insert/delete any rows/columns at the Publisher, the
> changes are immediately propagated to the Subscriber. The problem I'm
> having is when the Subscriber makes any changes to the Table, SQL
> generates the following error:
> Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Serve
r]Could
> not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
> 'SQLOLEDB'.
> I have used the Profiler, and determined that the table change
> executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
> then failing when it try's to execute the following statement:
> exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLSe
rver;UID=sa;PWD=;'
).[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
> ...
> And since I didn't want to re-code the triggers automatically created
> by SQL, I'm trying to figure out why the execution of the Remote
> Stored
> Procedure doesn't work.
> Any help is much appreciated.
> Thanks in Advance.
> Rick 8-)
>|||Thanks for the feedback Anthony, But I have check both of these, and
still no luck. Now however the error message is different.
Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]
OLE DB
error trace [OLE/DB Provider 'SQLOLEDB' IUnknow QueryInterface
returned 0x80070005: Access denied.
BTW: Replication from the Publisher to the Subscriber still works okay
though.
Have you any other suggestions?
Thanks in Advance
Rick
"AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message news:<4DCC547D-F8
75-4F14-8B65-F02CD34B8088@.microsoft.com>...[vbcol=seagreen]
> Two things to check. First, make sure the distributor and/or the publishe
r
> servers have allowed remote proc execution through sp_configure.
> Next, make sure your Win 2K Pro installation is running the SQL Server
> service accounts under an id that has access to the distributor/publisher
or
> has the correct sign-in information.
> Sincerely,
>
> Anthony Thomas
>
> "Rick Knight" wrote:
>|||That error message means you've granted the publisher/distributer SQL Agent
account access to the subscriber machine but that the reverse is not true.
In order to do a Pull, the subscriber must have login rights to the
distributer/publisher server.
Sincerely,
Anthony Thomas
"Rick Knight" wrote:

> Thanks for the feedback Anthony, But I have check both of these, and
> still no luck. Now however the error message is different.
> Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Serve
r]OLE DB
> error trace [OLE/DB Provider 'SQLOLEDB' IUnknow QueryInterface
> returned 0x80070005: Access denied.
> BTW: Replication from the Publisher to the Subscriber still works okay
> though.
> Have you any other suggestions?
> Thanks in Advance
> Rick
>
> "AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message
news:<4DCC547D-F875-4F14-8B65-F02CD34B8088@.microsoft.com>...
>

Wednesday, March 21, 2012

Replication Problems from Subscriber to Publisher.

Hi,
I am experiencing some difficulties with DataBase Replication. I have
two SQL 2000 servers running on different machines (The server is
running on Windows 2000 Server, and the other on Window 2000
Professional).
I have created a database with one table. Have then Published this
database, and setup a Subscription. (The Publication is Transactional,
using Immediate updating.)
If I amend/insert/delete any rows/columns at the Publisher, the
changes are immediately propagated to the Subscriber. The problem I'm
having is when the Subscriber makes any changes to the Table, SQL
generates the following error:
Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Could
not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
'SQLOLEDB'.
I have used the Profiler, and determined that the table change
executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
then failing when it try's to execute the following statement:
exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLServer;UID=sa;PWD=;').[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
...
And since I didn't want to re-code the triggers automatically created
by SQL, I'm trying to figure out why the execution of the Remote
Stored
Procedure doesn't work.
Any help is much appreciated.
Thanks in Advance.
Rick 8-)Two things to check. First, make sure the distributor and/or the publisher
servers have allowed remote proc execution through sp_configure.
Next, make sure your Win 2K Pro installation is running the SQL Server
service accounts under an id that has access to the distributor/publisher or
has the correct sign-in information.
Sincerely,
Anthony Thomas
"Rick Knight" wrote:
> Hi,
> I am experiencing some difficulties with DataBase Replication. I have
> two SQL 2000 servers running on different machines (The server is
> running on Windows 2000 Server, and the other on Window 2000
> Professional).
> I have created a database with one table. Have then Published this
> database, and setup a Subscription. (The Publication is Transactional,
> using Immediate updating.)
> If I amend/insert/delete any rows/columns at the Publisher, the
> changes are immediately propagated to the Subscriber. The problem I'm
> having is when the Subscriber makes any changes to the Table, SQL
> generates the following error:
> Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Could
> not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
> 'SQLOLEDB'.
> I have used the Profiler, and determined that the table change
> executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
> then failing when it try's to execute the following statement:
> exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLServer;UID=sa;PWD=;').[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
> ...
> And since I didn't want to re-code the triggers automatically created
> by SQL, I'm trying to figure out why the execution of the Remote
> Stored
> Procedure doesn't work.
> Any help is much appreciated.
> Thanks in Advance.
> Rick 8-)
>|||Thanks for the feedback Anthony, But I have check both of these, and
still no luck. Now however the error message is different.
Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB
error trace [OLE/DB Provider 'SQLOLEDB' IUnknow QueryInterface
returned 0x80070005: Access denied.
BTW: Replication from the Publisher to the Subscriber still works okay
though.
Have you any other suggestions?
Thanks in Advance
Rick :)
"AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message news:<4DCC547D-F875-4F14-8B65-F02CD34B8088@.microsoft.com>...
> Two things to check. First, make sure the distributor and/or the publisher
> servers have allowed remote proc execution through sp_configure.
> Next, make sure your Win 2K Pro installation is running the SQL Server
> service accounts under an id that has access to the distributor/publisher or
> has the correct sign-in information.
> Sincerely,
>
> Anthony Thomas
>
> "Rick Knight" wrote:
> > Hi,
> >
> > I am experiencing some difficulties with DataBase Replication. I have
> > two SQL 2000 servers running on different machines (The server is
> > running on Windows 2000 Server, and the other on Window 2000
> > Professional).
> >
> > I have created a database with one table. Have then Published this
> > database, and setup a Subscription. (The Publication is Transactional,
> > using Immediate updating.)
> >
> > If I amend/insert/delete any rows/columns at the Publisher, the
> > changes are immediately propagated to the Subscriber. The problem I'm
> > having is when the Subscriber makes any changes to the Table, SQL
> > generates the following error:
> >
> > Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Could
> > not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
> > 'SQLOLEDB'.
> >
> > I have used the Profiler, and determined that the table change
> > executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
> > then failing when it try's to execute the following statement:
> >
> > exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLServer;UID=sa;PWD=;').[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
> > ...
> >
> > And since I didn't want to re-code the triggers automatically created
> > by SQL, I'm trying to figure out why the execution of the Remote
> > Stored
> > Procedure doesn't work.
> >
> > Any help is much appreciated.
> >
> > Thanks in Advance.
> > Rick 8-)
> >|||That error message means you've granted the publisher/distributer SQL Agent
account access to the subscriber machine but that the reverse is not true.
In order to do a Pull, the subscriber must have login rights to the
distributer/publisher server.
Sincerely,
Anthony Thomas
"Rick Knight" wrote:
> Thanks for the feedback Anthony, But I have check both of these, and
> still no luck. Now however the error message is different.
> Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB
> error trace [OLE/DB Provider 'SQLOLEDB' IUnknow QueryInterface
> returned 0x80070005: Access denied.
> BTW: Replication from the Publisher to the Subscriber still works okay
> though.
> Have you any other suggestions?
> Thanks in Advance
> Rick :)
>
> "AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message news:<4DCC547D-F875-4F14-8B65-F02CD34B8088@.microsoft.com>...
> > Two things to check. First, make sure the distributor and/or the publisher
> > servers have allowed remote proc execution through sp_configure.
> >
> > Next, make sure your Win 2K Pro installation is running the SQL Server
> > service accounts under an id that has access to the distributor/publisher or
> > has the correct sign-in information.
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> > "Rick Knight" wrote:
> >
> > > Hi,
> > >
> > > I am experiencing some difficulties with DataBase Replication. I have
> > > two SQL 2000 servers running on different machines (The server is
> > > running on Windows 2000 Server, and the other on Window 2000
> > > Professional).
> > >
> > > I have created a database with one table. Have then Published this
> > > database, and setup a Subscription. (The Publication is Transactional,
> > > using Immediate updating.)
> > >
> > > If I amend/insert/delete any rows/columns at the Publisher, the
> > > changes are immediately propagated to the Subscriber. The problem I'm
> > > having is when the Subscriber makes any changes to the Table, SQL
> > > generates the following error:
> > >
> > > Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Could
> > > not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
> > > 'SQLOLEDB'.
> > >
> > > I have used the Profiler, and determined that the table change
> > > executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
> > > then failing when it try's to execute the following statement:
> > >
> > > exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLServer;UID=sa;PWD=;').[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
> > > ...
> > >
> > > And since I didn't want to re-code the triggers automatically created
> > > by SQL, I'm trying to figure out why the execution of the Remote
> > > Stored
> > > Procedure doesn't work.
> > >
> > > Any help is much appreciated.
> > >
> > > Thanks in Advance.
> > > Rick 8-)
> > >
>

Replication problems after SP4 upgrade

Hi,
We're experiencing a problem with transaction replication on SP4.
The snapshot is taken without any problems and applies, however, when it
comes to processing the additional transactions which have taken place since
the snaphot, the process starts processing in parrallel and blocks itself.
The process eventually fails and rollbacks.
This used to work fine on SP3a, but not any more... anyone any ideas?
Thanks in advance
Dave
Dave Wall
what do you mean by processing in parallel? Can you log the output to a text
file and post it here.
Follow these step on how to enable logging.
http://support.microsoft.com/default...b;en-us;312292
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Dave Wall" <DaveWall@.discussions.microsoft.com> wrote in message
news:3B4815C4-7438-4C5C-8F81-B9720EB1B0B3@.microsoft.com...
> Hi,
> We're experiencing a problem with transaction replication on SP4.
> The snapshot is taken without any problems and applies, however, when it
> comes to processing the additional transactions which have taken place
since
> the snaphot, the process starts processing in parrallel and blocks itself.
> The process eventually fails and rollbacks.
> This used to work fine on SP3a, but not any more... anyone any ideas?
> Thanks in advance
> Dave
> --
> Dave Wall
|||Hi Dave, it would be great if you can post the [abridged] result of sp_who2
on the distributor\subscriber (or wherever the blocking occurs) as well.
Thanks.
-Raymond
"Dave Wall" wrote:

> Hi,
> We're experiencing a problem with transaction replication on SP4.
> The snapshot is taken without any problems and applies, however, when it
> comes to processing the additional transactions which have taken place since
> the snaphot, the process starts processing in parrallel and blocks itself.
> The process eventually fails and rollbacks.
> This used to work fine on SP3a, but not any more... anyone any ideas?
> Thanks in advance
> Dave
> --
> Dave Wall
|||Hi Raymond,
Got the thing sorted last night. Two things helped. The first was to
increase the minimum query plan threshold for considering paralell execution.
Secondly - we found that our networks team hadn't set the server up with PAE
extensions and so SQL wasn't using all the memory i'd assigned it. Once
these two were changed - replication went through first time.
Looks like a similar problem we had with a another server (see another post)
were processes were blocking themselves. Without the additional memory, IO
went through the roof and the spids started blocking themselves (whilst
waiting for IO)
Sorted the memory, and alls well now.
Thanks
Dave
Dave Wall
"Raymond Mak [MSFT]" wrote:
[vbcol=seagreen]
> Hi Dave, it would be great if you can post the [abridged] result of sp_who2
> on the distributor\subscriber (or wherever the blocking occurs) as well.
> Thanks.
> -Raymond
> "Dave Wall" wrote:
|||Dave,
Am curious which server needed the extra memory. Was it pub, sub, or
dist?
Thanks
Mark Andersen

Wednesday, March 7, 2012

Replication Monitor

experiencing some very odd behavior in Enterprise Manager.
I have a process that performs the following:
1.) Restores a published database from Server A onto Server B. The
databases
are identical and they are both published.
2.) I run a script that then deletes the subscriptions to the
publication on
Server B. I do this via SP_DROPSUBSCRIPTION.
3.) I run a script that then deletes the publication. I do this via
SP_DROPPUBLICATION.
4.) Deletes the distribution database.
5.) Deletes the old jobs.
6.) Creates the publication from pregenerated scripts.
7.) Adds the subscriber.
8.) Adds the subscription.
9.) Generates the snapshot and applies it.
What's happening is that I'm seeing the job name that's assigned to the
distribution job increment by 1 each time this process is run. Also,
I'm seeing ten instances of the publication showing up in the tree view.
When I look in SYSPUBLICATIONS, there is only ONE row!!! Shouldn't
Replication Monitor clean itself up?
Everything appears to be rtunning just fine, transactions being
replicated, etc. I'm just wondering is there something I'm missing in my
steps.
Plus, after two or three months of this, might not look so good having 90
publications showing up in the tree view.
Thanks!
first off run a sp_MSload_replication_status. This can occasionally correct
these problems. Secondly, it looks like your replication metadata is messed
up. It is normal for the publications to increment their names with every
new publication. However, to determine how to fix your error I need to know
which node you are getting the error in?
The Publication node in the replication folder? The Publishers node in the
Replication Monitor folder?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:FE4B9FD8-5948-45AF-A3F8-8F9867CFBC23@.microsoft.com...
> experiencing some very odd behavior in Enterprise Manager.
>
> I have a process that performs the following:
>
> 1.) Restores a published database from Server A onto Server B. The
> databases
> are identical and they are both published.
> 2.) I run a script that then deletes the subscriptions to the
> publication on
> Server B. I do this via SP_DROPSUBSCRIPTION.
> 3.) I run a script that then deletes the publication. I do this via
> SP_DROPPUBLICATION.
> 4.) Deletes the distribution database.
> 5.) Deletes the old jobs.
> 6.) Creates the publication from pregenerated scripts.
> 7.) Adds the subscriber.
> 8.) Adds the subscription.
> 9.) Generates the snapshot and applies it.
>
> What's happening is that I'm seeing the job name that's assigned to the
> distribution job increment by 1 each time this process is run. Also,
> I'm seeing ten instances of the publication showing up in the tree view.
> When I look in SYSPUBLICATIONS, there is only ONE row!!! Shouldn't
> Replication Monitor clean itself up?
> Everything appears to be rtunning just fine, transactions being
> replicated, etc. I'm just wondering is there something I'm missing in my
> steps.
> Plus, after two or three months of this, might not look so good having 90
> publications showing up in the tree view.
>
> Thanks!
>
>
|||Hilary:
I'm seeing this in the publishers node under Replication Monitor...
When would I run the sp_MSload_Replication_Status? I just ran it and it
killed my replication. I'm guessing you don't want to run that proc after
replication has been established...
Thanks!
"Hilary Cotter" wrote:

> first off run a sp_MSload_replication_status. This can occasionally correct
> these problems. Secondly, it looks like your replication metadata is messed
> up. It is normal for the publications to increment their names with every
> new publication. However, to determine how to fix your error I need to know
> which node you are getting the error in?
> The Publication node in the replication folder? The Publishers node in the
> Replication Monitor folder?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:FE4B9FD8-5948-45AF-A3F8-8F9867CFBC23@.microsoft.com...
>
>
|||What do you mean by it "killed" off replication? I should fix transient
errors. Are you saying that some agents are no longer showing up in the
snapshot/distribution/log reader agent folders?
If so, I think this is caused by scripting out replication and running the
same script in a different database without modifying the snapshot, log
reader, or distribution agent names, and without modifying the publication
name. I think you will find that the agents just don't show up, but
everything works fine.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:B69FA4F3-EFA7-40B2-A709-9B08335CE455@.microsoft.com...[vbcol=seagreen]
> Hilary:
> I'm seeing this in the publishers node under Replication Monitor...
> When would I run the sp_MSload_Replication_Status? I just ran it and it
> killed my replication. I'm guessing you don't want to run that proc after
> replication has been established...
> Thanks!
> "Hilary Cotter" wrote:
correct[vbcol=seagreen]
messed[vbcol=seagreen]
every[vbcol=seagreen]
know[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
view.[vbcol=seagreen]
my[vbcol=seagreen]
90[vbcol=seagreen]
|||I stand corrected...everything came back.
But I'm still seeing the multiple publications under the publishers tab of
the replication monitor...
"Hilary Cotter" wrote:

> What do you mean by it "killed" off replication? I should fix transient
> errors. Are you saying that some agents are no longer showing up in the
> snapshot/distribution/log reader agent folders?
> If so, I think this is caused by scripting out replication and running the
> same script in a different database without modifying the snapshot, log
> reader, or distribution agent names, and without modifying the publication
> name. I think you will find that the agents just don't show up, but
> everything works fine.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:B69FA4F3-EFA7-40B2-A709-9B08335CE455@.microsoft.com...
> correct
> messed
> every
> know
> the
> the
> view.
> my
> 90
>
>
|||...also, the scripts that are being used to recreate the replication topology
were generated on the Server B - so the agent names, databases, subscription
names are all correct for that particular server...
"A. Robinson" wrote:
[vbcol=seagreen]
> I stand corrected...everything came back.
> But I'm still seeing the multiple publications under the publishers tab of
> the replication monitor...
> "Hilary Cotter" wrote:

Replication Monitor

I'm experiencing some very odd behavior in Enterprise Manager.

I have a process that performs the following:

1.) Restores a published database from Server A onto Server B. The
databases
are identical and they are both published.
2.) I run a script that then deletes the subscriptions to the
publication on
Server B. I do this via SP_DROPSUBSCRIPTION.
3.) I run a script that then deletes the publication. I do this via
SP_DROPPUBLICATION.
4.) Deletes the distribution database.
5.) Deletes the old jobs.
6.) Creates the publication from pregenerated scripts.
7.) Adds the subscriber.
8.) Adds the subscription.
9.) Generates the snapshot and applies it.

What's happening is that I'm seeing the job name that's assigned to the

distribution job increment by 1 each time this process is run. Also,
I'm
seeing ten instances of the publication showing up in the tree view.

Everything appears to be rtunning just fine, transactions being
replicated,
etc. I'm just wondering is there something I'm missing in my steps.
Plus,
after two or three months of this, might not look so good having 90
publications showing up in the tree view.

Thanks!You might get a better response in
microsoft.public.sqlserver.replication

Simon