Help. Labor Entry causing the client and AppServer to hang

Yahoo Archive
1
We have exactly the same problem on Vantage 8.03.406. Logged a call with Epicor in June 2010 and it is still open.....

--- In vantage@yahoogroups.com, "markbetts66" <markbetts66@...> wrote:
>
> Hi,
>
> When posting labor against a particular assembly within a job its causing the both the client + AppServer to hang and high CPU usage on the SQL server.
>
> Has anyone else had this issue? Or any ideas what may be causing it?
>
> Thanks,
> Mark.
>
2
Hi,

When posting labor against a particular assembly within a job its causing the both the client + AppServer to hang and high CPU usage on the SQL server.

Has anyone else had this issue? Or any ideas what may be causing it?

Thanks,
Mark.
3
What version are you on?

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of markbetts66
Sent: Monday, March 07, 2011 11:30 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Help. Labor Entry causing the client and AppServer to hang



Hi,

When posting labor against a particular assembly within a job its causing the both the client + AppServer to hang and high CPU usage on the SQL server.

Has anyone else had this issue? Or any ideas what may be causing it?

Thanks,
Mark.



[Non-text portions of this message have been removed]
4
Hi,

408B SQL

--- In vantage@yahoogroups.com, Karen Schoenung <kschoenung@...> wrote:
>
> What version are you on?
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of markbetts66
> Sent: Monday, March 07, 2011 11:30 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Help. Labor Entry causing the client and AppServer to hang
>
>
>
> Hi,
>
> When posting labor against a particular assembly within a job its causing the both the client + AppServer to hang and high CPU usage on the SQL server.
>
> Has anyone else had this issue? Or any ideas what may be causing it?
>
> Thanks,
> Mark.
>
>
>
> [Non-text portions of this message have been removed]
>
5
Do you have any custom code that touches the Labor tables?

I've seen Epicor hang a number of times when it finds malformed records. Try
viewing the record with a query and compare it to a good one.

On Mon, Mar 7, 2011 at 1:59 PM, markbetts66 <markbetts66@...> wrote:

>
>
> Hi,
>
> 408B SQL
>
>
> --- In vantage@yahoogroups.com, Karen Schoenung <kschoenung@...> wrote:
> >
> > What version are you on?
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of markbetts66
> > Sent: Monday, March 07, 2011 11:30 AM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Help. Labor Entry causing the client and AppServer to
> hang
> >
> >
> >
> > Hi,
> >
> > When posting labor against a particular assembly within a job its causing
> the both the client + AppServer to hang and high CPU usage on the SQL
> server.
> >
> > Has anyone else had this issue? Or any ideas what may be causing it?
> >
> > Thanks,
> > Mark.
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>


[Non-text portions of this message have been removed]
6
We are on 8.03.409C SQL

We have seen jobs with no schedule date shown (although they were scheduled). I know this caused MRP to hang and may also have caused some labor issues...We have a process to reschedule those jobs (a BAQ finds those without a date).

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of markbetts66
Sent: Monday, March 07, 2011 1:00 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Help. Labor Entry causing the client and AppServer to hang



Hi,

408B SQL

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Karen Schoenung <kschoenung@...> wrote:
>
> What version are you on?
>
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of markbetts66
> Sent: Monday, March 07, 2011 11:30 AM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Help. Labor Entry causing the client and AppServer to hang
>
>
>
> Hi,
>
> When posting labor against a particular assembly within a job its causing the both the client + AppServer to hang and high CPU usage on the SQL server.
>
> Has anyone else had this issue? Or any ideas what may be causing it?
>
> Thanks,
> Mark.
>
>
>
> [Non-text portions of this message have been removed]
>



[Non-text portions of this message have been removed]
7
Hi,

The labor entry screen is Vanilla as it comes. Will try comparing the offending assembly record against the good ones, thanks.



--- In vantage@yahoogroups.com, Waffqle <waffqle@...> wrote:
>
> Do you have any custom code that touches the Labor tables?
>
> I've seen Epicor hang a number of times when it finds malformed records. Try
> viewing the record with a query and compare it to a good one.
>
> On Mon, Mar 7, 2011 at 1:59 PM, markbetts66 <markbetts66@...> wrote:
>
> >
> >
> > Hi,
> >
> > 408B SQL
> >
> >
> > --- In vantage@yahoogroups.com, Karen Schoenung <kschoenung@> wrote:
> > >
> > > What version are you on?
> > >
> > > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> > Of markbetts66
> > > Sent: Monday, March 07, 2011 11:30 AM
> > > To: vantage@yahoogroups.com
> > > Subject: [Vantage] Help. Labor Entry causing the client and AppServer to
> > hang
> > >
> > >
> > >
> > > Hi,
> > >
> > > When posting labor against a particular assembly within a job its causing
> > the both the client + AppServer to hang and high CPU usage on the SQL
> > server.
> > >
> > > Has anyone else had this issue? Or any ideas what may be causing it?
> > >
> > > Thanks,
> > > Mark.
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
8
Mark;

You touched a nerve.
We struggled with this issue since 8.03.408 and it was listed in the patch list twice that I know of as having been fixed. I also got (3) one-off fixes that did not work. It comes and goes, with no rhyme or reason. We replaced swittches, computers, re-schduled jobs etc. and would be good for a while but it would always come back.
We had three weeks of crashing (4) times a day last month and pleaded with Epicor to send out an expert. What came next was a miracle.
We got a "One-Off" fix that corrects this known issue, and it worked!
We have not had a single crash in two weeks! Not even a flutter.

Contact support and reference:

Fix is in SCR 67017 where you replace the "Write.r" for for JobOper trigger.

I hope helps you as much as it did our company!

Regards,
George Hicks


--- In vantage@yahoogroups.com, "markbetts66" <markbetts66@...> wrote:
>
> Hi,
>
> When posting labor against a particular assembly within a job its causing the both the client + AppServer to hang and high CPU usage on the SQL server.
>
> Has anyone else had this issue? Or any ideas what may be causing it?
>
> Thanks,
> Mark.
>
9
Thanks George,

We have contacted Epicor and requested the SCR.


--- In vantage@yahoogroups.com, "pcivantage" <vantagegroup@...> wrote:
>
> Mark;
>
> You touched a nerve.
> We struggled with this issue since 8.03.408 and it was listed in the patch list twice that I know of as having been fixed. I also got (3) one-off fixes that did not work. It comes and goes, with no rhyme or reason. We replaced swittches, computers, re-schduled jobs etc. and would be good for a while but it would always come back.
> We had three weeks of crashing (4) times a day last month and pleaded with Epicor to send out an expert. What came next was a miracle.
> We got a "One-Off" fix that corrects this known issue, and it worked!
> We have not had a single crash in two weeks! Not even a flutter.
>
> Contact support and reference:
>
> Fix is in SCR 67017 where you replace the "Write.r" for for JobOper trigger.
>
> I hope helps you as much as it did our company!
>
> Regards,
> George Hicks
>
>
> --- In vantage@yahoogroups.com, "markbetts66" <markbetts66@> wrote:
> >
> > Hi,
> >
> > When posting labor against a particular assembly within a job its causing the both the client + AppServer to hang and high CPU usage on the SQL server.
> >
> > Has anyone else had this issue? Or any ideas what may be causing it?
> >
> > Thanks,
> > Mark.
> >
>