intermittent replication issue

Hello,

I currently run a nightly replication from a windows server 2003 machine with sql server 2000 sp3 to a windows 2003 server machine with sql server 2005 sp1. I run a snapshot replication as merge is not supported from 2000 to 2005.

2 out 5 snapshots weekly fail with the following error:

2006-08-09 17:00:06.97 Message Code: 10054
2006-08-09 17:00:06.97
2006-08-09 17:00:06.97 [0%] The replication agent had encountered an exception.
2006-08-09 17:00:06.97 Source: Replication
2006-08-09 17:00:06.97 Exception Type: Microsoft.SqlServer.Replication.ConnectionFailureException
2006-08-09 17:00:06.97 Exception Message: TCP Provider: An existing connection was forcibly closed by the remote host.

I have setup the sql server 2005 agent service to automatic with a 'log on as' domain admin account. The sql server agent on the 2000 machine uses the local system account.

Does anyone know what i can try to fix this?

thks

geoff

Is this the snapshot agent or the distribution agent that's failing?|||

regardless, it's some kind of a security or network problem you're having. Check this similar post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=187500&SiteID=1.

sql

Interesting Transactional Replication issue

Hello,

We have moved from SQL 2000 to SQL 2005 for our main server, and our reporting server, which uses transactional replication.

Now, in SQL 2000 when I originally setup replication, it replicated all of the table indexes.

I have recreated the publications in SQL 2005, but they are no longer there. Do you have any idea what would cause some of our table indexes to be missing?

What can be done to ensure this doesn't happen?

Thank you.

Justin, the default article schema options when creating a transactional publication through the SQL2005 workbench is to not replicate any non-clustered indexes (unique key constraints, clustered index, and primary key are replicated though). Is it possible that the indexes that you are missing at the subscriber are simply non-clustered indexes? Hope that helps.

-Raymond

|||Thanks for the reply. You're correct in that they are non-clustered indexes. How would I modify replication to include these secondary indexes?
|||

Hi Justin,

You can use sp_changearticle to enable the NonClusteredIndexes (0x40) schema option, or you can change the 'Copy non-clustered indexes' option to true on the article property sheet (right-click publication node->properties->select Articles on left plane->Click Article Properties button.

Hope that helps,

-Raymond

interesting error message

Hi,
I keep geeting this error message in one of my servers.
Replication: agent failed.: Unable to expand message 17055 [-1073724769]
18265 Log backed up: Database: mine, creation date(time):
2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number of
dump devices: 1, device informa... ..
There is no replication configured on the server. The backup job is also
successful. What is this message about?
I don't know, but if it's really from August 11 of last year, are you sure
it's still relevant?
On 3/2/05 8:45 PM, in article
545CADDF-C5EF-48A2-967F-A4246D13D306@.microsoft.com, "Bharath"
<Bharath@.discussions.microsoft.com> wrote:

> Hi,
> I keep geeting this error message in one of my servers.
> Replication: agent failed.: Unable to expand message 17055 [-1073724769]
> 18265 Log backed up: Database: mine, creation date(time):
> 2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number of
> dump devices: 1, device informa... ..
>
> There is no replication configured on the server. The backup job is also
> successful. What is this message about?
|||Aaron,
It is relevant - I think the message is of Aug 11 - because the db was
created on Aug 11th 2004 - but it is a current message only.
"Aaron [SQL Server MVP]" wrote:

> I don't know, but if it's really from August 11 of last year, are you sure
> it's still relevant?
>
> On 3/2/05 8:45 PM, in article
> 545CADDF-C5EF-48A2-967F-A4246D13D306@.microsoft.com, "Bharath"
> <Bharath@.discussions.microsoft.com> wrote:
>
>

interesting error message

Hi,
I keep geeting this error message in one of my servers.
Replication: agent failed.: Unable to expand message 17055 [-1073724769]
18265 Log backed up: Database: mine, creation date(time):
2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number of
dump devices: 1, device informa... ..
There is no replication configured on the server. The backup job is also
successful. What is this message about?I don't know, but if it's really from August 11 of last year, are you sure
it's still relevant?
On 3/2/05 8:45 PM, in article
545CADDF-C5EF-48A2-967F-A4246D13D306@.microsoft.com, "Bharath"
<Bharath@.discussions.microsoft.com> wrote:
> Hi,
> I keep geeting this error message in one of my servers.
> Replication: agent failed.: Unable to expand message 17055 [-1073724769]
> 18265 Log backed up: Database: mine, creation date(time):
> 2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number of
> dump devices: 1, device informa... ..
>
> There is no replication configured on the server. The backup job is also
> successful. What is this message about?|||Aaron,
It is relevant - I think the message is of Aug 11 - because the db was
created on Aug 11th 2004 - but it is a current message only.
"Aaron [SQL Server MVP]" wrote:
> I don't know, but if it's really from August 11 of last year, are you sure
> it's still relevant?
>
> On 3/2/05 8:45 PM, in article
> 545CADDF-C5EF-48A2-967F-A4246D13D306@.microsoft.com, "Bharath"
> <Bharath@.discussions.microsoft.com> wrote:
> > Hi,
> >
> > I keep geeting this error message in one of my servers.
> >
> > Replication: agent failed.: Unable to expand message 17055 [-1073724769]
> > 18265 Log backed up: Database: mine, creation date(time):
> > 2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number of
> > dump devices: 1, device informa... ..
> >
> >
> > There is no replication configured on the server. The backup job is also
> > successful. What is this message about?
>

interesting error message

Hi,
I keep geeting this error message in one of my servers.
Replication: agent failed.: Unable to expand message 17055 [-1073724769]
18265 Log backed up: Database: mine, creation date(time):
2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number of
dump devices: 1, device informa... ..
There is no replication configured on the server. The backup job is also
successful. What is this message about?I don't know, but if it's really from August 11 of last year, are you sure
it's still relevant?
On 3/2/05 8:45 PM, in article
545CADDF-C5EF-48A2-967F-A4246D13D306@.microsoft.com, "Bharath"
<Bharath@.discussions.microsoft.com> wrote:

> Hi,
> I keep geeting this error message in one of my servers.
> Replication: agent failed.: Unable to expand message 17055 [-107372476
9]
> 18265 Log backed up: Database: mine, creation date(time):
> 2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number
of
> dump devices: 1, device informa... ..
>
> There is no replication configured on the server. The backup job is also
> successful. What is this message about?|||Aaron,
It is relevant - I think the message is of Aug 11 - because the db was
created on Aug 11th 2004 - but it is a current message only.
"Aaron [SQL Server MVP]" wrote:

> I don't know, but if it's really from August 11 of last year, are you sure
> it's still relevant?
>
> On 3/2/05 8:45 PM, in article
> 545CADDF-C5EF-48A2-967F-A4246D13D306@.microsoft.com, "Bharath"
> <Bharath@.discussions.microsoft.com> wrote:
>
>