v8.03.406A Labor Entry "Save" Lock-Up

Yahoo Archive
1
We're on Progress here, so I'm not sure our problems will interrelate.
But Epicor seems to think it might be a locking issue, too, since
they've sent me a "Locks Logger" routine to run.

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of hessd3
Sent: Tuesday, March 03, 2009 10:15 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: v8.03.406A Labor Entry "Save" Lock-Up



It only happens occasionally and we average 15 users so it's not to
big a deal. A lot of hanging issues clear up themselves after a few
hours so that is what makes me think it's usually a user locking some
table and they finally close the window. A note that we are using MS
SQL 2005 for the db if it helps.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Ari
Footlik" <ari@...> wrote:
>
> That would be catastrophically bad...
>
> ________________________________
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
> Of hessd3
> Sent: Tuesday, March 03, 2009 8:35 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: v8.03.406A Labor Entry "Save" Lock-Up
>
>
>
> We have similar issues where a client seems to randomly hang and then
> the user has to kill the Vantage client to get out of it. If you can
> reproduce it again after killing the client, it appears to be someone
> is locking a table in the database. I have to get all the users to
> close all windows until they are at the main Vantage window. That
> usually fixes the repeatable hanging. Check for an open print preview
> window that a user left unattended. I don't have any proof, but
> everytime someone repeatedly gets hung, I find an open print preview
> window on another user's workstation.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> , "Ari
> Footlik" <ari@> wrote:
> >
> > In our 8.03.406A implementation, it seems that making any changes in
> > "Labor Entry" (not MES) results in the client hanging. Has anyone
> > experienced this and found a fix?
> >
> > Thank you.
> > --Ari
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>






[Non-text portions of this message have been removed]
2
In our 8.03.406A implementation, it seems that making any changes in
"Labor Entry" (not MES) results in the client hanging. Has anyone
experienced this and found a fix?

Thank you.
--Ari


[Non-text portions of this message have been removed]
3
Possibly resolved - I deleted all the personalizations that were
associated with the "Labor Entry" program and that seems to have fixed
the issue.

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Ari Footlik
Sent: Tuesday, March 03, 2009 8:10 AM
To: vantage@yahoogroups.com
Subject: [Vantage] v8.03.406A Labor Entry "Save" Lock-Up



In our 8.03.406A implementation, it seems that making any changes in
"Labor Entry" (not MES) results in the client hanging. Has anyone
experienced this and found a fix?

Thank you.
--Ari

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






[Non-text portions of this message have been removed]
4
We have similar issues where a client seems to randomly hang and then
the user has to kill the Vantage client to get out of it. If you can
reproduce it again after killing the client, it appears to be someone
is locking a table in the database. I have to get all the users to
close all windows until they are at the main Vantage window. That
usually fixes the repeatable hanging. Check for an open print preview
window that a user left unattended. I don't have any proof, but
everytime someone repeatedly gets hung, I find an open print preview
window on another user's workstation.


--- In vantage@yahoogroups.com, "Ari Footlik" <ari@...> wrote:
>
> In our 8.03.406A implementation, it seems that making any changes in
> "Labor Entry" (not MES) results in the client hanging. Has anyone
> experienced this and found a fix?
>
> Thank you.
> --Ari
>
>
> [Non-text portions of this message have been removed]
>
5
Nope - the personalizations issue wasn't it...

--Ari

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Ari Footlik
Sent: Tuesday, March 03, 2009 8:28 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] v8.03.406A Labor Entry "Save" Lock-Up



Possibly resolved - I deleted all the personalizations that were
associated with the "Labor Entry" program and that seems to have fixed
the issue.

________________________________

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
Of Ari Footlik
Sent: Tuesday, March 03, 2009 8:10 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] v8.03.406A Labor Entry "Save" Lock-Up

In our 8.03.406A implementation, it seems that making any changes in
"Labor Entry" (not MES) results in the client hanging. Has anyone
experienced this and found a fix?

Thank you.
--Ari

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

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






[Non-text portions of this message have been removed]
6
That would be catastrophically bad...

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of hessd3
Sent: Tuesday, March 03, 2009 8:35 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: v8.03.406A Labor Entry "Save" Lock-Up



We have similar issues where a client seems to randomly hang and then
the user has to kill the Vantage client to get out of it. If you can
reproduce it again after killing the client, it appears to be someone
is locking a table in the database. I have to get all the users to
close all windows until they are at the main Vantage window. That
usually fixes the repeatable hanging. Check for an open print preview
window that a user left unattended. I don't have any proof, but
everytime someone repeatedly gets hung, I find an open print preview
window on another user's workstation.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Ari
Footlik" <ari@...> wrote:
>
> In our 8.03.406A implementation, it seems that making any changes in
> "Labor Entry" (not MES) results in the client hanging. Has anyone
> experienced this and found a fix?
>
> Thank you.
> --Ari
>
>
> [Non-text portions of this message have been removed]
>






[Non-text portions of this message have been removed]
7
It only happens occasionally and we average 15 users so it's not to
big a deal. A lot of hanging issues clear up themselves after a few
hours so that is what makes me think it's usually a user locking some
table and they finally close the window. A note that we are using MS
SQL 2005 for the db if it helps.

--- In vantage@yahoogroups.com, "Ari Footlik" <ari@...> wrote:
>
> That would be catastrophically bad...
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of hessd3
> Sent: Tuesday, March 03, 2009 8:35 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: v8.03.406A Labor Entry "Save" Lock-Up
>
>
>
> We have similar issues where a client seems to randomly hang and then
> the user has to kill the Vantage client to get out of it. If you can
> reproduce it again after killing the client, it appears to be someone
> is locking a table in the database. I have to get all the users to
> close all windows until they are at the main Vantage window. That
> usually fixes the repeatable hanging. Check for an open print preview
> window that a user left unattended. I don't have any proof, but
> everytime someone repeatedly gets hung, I find an open print preview
> window on another user's workstation.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Ari
> Footlik" <ari@> wrote:
> >
> > In our 8.03.406A implementation, it seems that making any changes in
> > "Labor Entry" (not MES) results in the client hanging. Has anyone
> > experienced this and found a fix?
> >
> > Thank you.
> > --Ari
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>