Multicompany stuck records in E9

I have always got the same response as you. They send me the Clear IM table script to run. I asked if I should just run this script on a SQL job schedule but they didn't recommend that.

We have never been able to get MultiCompany to run consistently without it completely stopping at some point.


From: "ben.johnson@... [vantage]" <vantage@yahoogroups.com>
To: vantage@yahoogroups.com
Sent: Wednesday, April 15, 2015 10:59 AM
Subject: [Vantage] Multicompany stuck records in E9



Hello,

We're running Epicor version 9.05.701 with a  SQL database and we've had problems with records being held up in the IntQueIn table after our Multicompany Direct process runs.

We've been working with Epicor on this but so far the only solution they've been able to come up with as a "fix" in a IM table clear. These records come through the logs as "Registration errors" without any further information than that.

What we've tried:

* Restarting the appservers in their proper order
* Going into the integrated table work bench and trying to re-validate the stuck records
* Switching multicompany from continuous processing to interval schedule
* Running the process entirely on a manual setting
* A combination of the above

Few things we've learned:
* Restoring to a test database cleared out a lot of records but there approximately 7/8 AP Inv records that refuse to move
* We've been unable to find a way to set the multicompany log file to a "verbose" or equivalent setting
* Doing manual MC-Direct runs still doesn't clear out these records in live despite it not running into another scheduled process
* The integration table is getting backed up with records because it is unable to process what is already in there
* Epicor and our financial department are unable to determine if the fault lies with the data yet the former is proposing an IMTable clear fix which is simply not an option for us

Has anyone encountered similar issues with this process and is there a way to more effectively debug this issue? Epicor's standard operating procedure seems to be to wipe out the data already in there and hope it works next time but we'd like to know why this is happening in the first place.

Ben




Hello,


We're running Epicor version 9.05.701 with a  SQL database and we've had problems with records being held up in the IntQueIn table after our Multicompany Direct process runs.


We've been working with Epicor on this but so far the only solution they've been able to come up with as a "fix" in a IM table clear. These records come through the logs as "Registration errors" without any further information than that.


What we've tried:


* Restarting the appservers in their proper order

* Going into the integrated table work bench and trying to re-validate the stuck records

* Switching multicompany from continuous processing to interval schedule

* Running the process entirely on a manual setting

* A combination of the above


Few things we've learned:

* Restoring to a test database cleared out a lot of records but there approximately 7/8 AP Inv records that refuse to move

* We've been unable to find a way to set the multicompany log file to a "verbose" or equivalent setting

* Doing manual MC-Direct runs still doesn't clear out these records in live despite it not running into another scheduled process

* The integration table is getting backed up with records because it is unable to process what is already in there

* Epicor and our financial department are unable to determine if the fault lies with the data yet the former is proposing an IMTable clear fix which is simply not an option for us


Has anyone encountered similar issues with this process and is there a way to more effectively debug this issue? Epicor's standard operating procedure seems to be to wipe out the data already in there and hope it works next time but we'd like to know why this is happening in the first place.


Ben