Replications Server (Delayed Processing)

Yahoo Archive
1
Steps I had to take to fix it

1. Delete context

2. Stop replication server service on SQL server

3. Stop Task Agent

4. Stop Process Server

5. If needed, stop Print server

6. Rename/delete replication logs in the EpicorData folder

7. Start epicor servers/agents up again

8. Start up Replication service on SQL server

9. Recreate context

10. Run a sync

"Zac" Jason Woodward
Network Administrator
Intermountain Electronics, Inc.
O: 877-544-2291
M: 435-820-6515
F: 435-637-9601
www.ie-corp.com

Creating customer confidence through extraordinary service and experienced industry experts.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of adrian.lauchlan
Sent: Monday, March 05, 2012 4:33 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Replications Server (Delayed Processing)



Are you running sonic on any of your other DBs? Sonic can get confused if so and may be affecting your Replication

Regards

Adrian Lauchlan

Inceptum Projects Ltd

Mob 07852 270968

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "kevin.larkin@...<mailto:kevin.larkin@...>" <klarkin@...<mailto:klarkin@...>> wrote:
>
> We have replication server in place with our Progress 905.606a DB being replicated to SQL. I can do a full initialization of approx. 75 tables just fine (About 7hrs). The problem is when users start making transactional changes within the Epicor DB, I receive time-out errors in the replication log. Some data is being replicated but not all. In the Replication management console I see errors, but eventually I get a "Delayed_Processing" or "UNKNOWN" status in the Subscriber making the console useless.
>
> We have had this working for months at a time it but seems very inconsistent long term.
>
> I have cleared the Repl Tables within Epicor, reconfigured Replication completely, re-created SQL DB (Functional) and re-initialized multiple times with the same results.
>
> I have spoken with Epicor many many times on this subject with no luck on a fix.
>
> My questions are:
> "Is anyone using a stable replication server environment?"
> "Is anyone having `Unknown' or `Delayed_Processing' status issues within the replication server management console?"
>
> Any information would be appreciated.
>
> Kevin P. Larkin
> IT Manager
> Ferguson Perforating
>



[Non-text portions of this message have been removed]
2
We have replication server in place with our Progress 905.606a DB being replicated to SQL. I can do a full initialization of approx. 75 tables just fine (About 7hrs). The problem is when users start making transactional changes within the Epicor DB, I receive time-out errors in the replication log. Some data is being replicated but not all. In the Replication management console I see errors, but eventually I get a "Delayed_Processing" or "UNKNOWN" status in the Subscriber making the console useless.

We have had this working for months at a time it but seems very inconsistent long term.

I have cleared the Repl Tables within Epicor, reconfigured Replication completely, re-created SQL DB (Functional) and re-initialized multiple times with the same results.

I have spoken with Epicor many many times on this subject with no luck on a fix.

My questions are:
"Is anyone using a stable replication server environment?"
"Is anyone having `Unknown' or `Delayed_Processing' status issues within the replication server management console?"

Any information would be appreciated.

Kevin P. Larkin
IT Manager
Ferguson Perforating
3
Are you running sonic on any of your other DBs? Sonic can get confused if so and may be affecting your Replication

Regards

Adrian Lauchlan

Inceptum Projects Ltd

Mob 07852 270968


--- In vantage@yahoogroups.com, "kevin.larkin@..." <klarkin@...> wrote:
>
> We have replication server in place with our Progress 905.606a DB being replicated to SQL. I can do a full initialization of approx. 75 tables just fine (About 7hrs). The problem is when users start making transactional changes within the Epicor DB, I receive time-out errors in the replication log. Some data is being replicated but not all. In the Replication management console I see errors, but eventually I get a "Delayed_Processing" or "UNKNOWN" status in the Subscriber making the console useless.
>
> We have had this working for months at a time it but seems very inconsistent long term.
>
> I have cleared the Repl Tables within Epicor, reconfigured Replication completely, re-created SQL DB (Functional) and re-initialized multiple times with the same results.
>
> I have spoken with Epicor many many times on this subject with no luck on a fix.
>
> My questions are:
> "Is anyone using a stable replication server environment?"
> "Is anyone having `Unknown' or `Delayed_Processing' status issues within the replication server management console?"
>
> Any information would be appreciated.
>
> Kevin P. Larkin
> IT Manager
> Ferguson Perforating
>