Riddle me This Batman!

Yahoo Archive
1
Check to see if you are trying to schedule an Inactive resource - or there simply are not any scheduling blocks available large enough - or you are scheduling an OP into multiple finite resources that have calendars that result in no net capacity available.



________________________________
From: Jonathan Lang <lsbestinc@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Thursday, March 15, 2012 10:58 AM
Subject: Re: [Vantage] Re: Riddle me This Batman!


Â
Karen! Haha, I knew you'd be the one to answer. Will check to see if that's the issue.

________________________________
From: Karen Schoenung <kschoenung@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Thursday, March 15, 2012 9:57 AM
Subject: RE: [Vantage] Re: Riddle me This Batman!


Â
I know we used to have issues with no date shown as scheduled on a job that caused havoc (8.03.409c). Run a query to see if you have any of those?

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Rob Bucek
Sent: Thursday, March 15, 2012 9:53 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Riddle me This Batman!

God I love poetry, but since he sucked up his vast pride and asked for help...

The only time weve seen behavior even similar to what you've described is when there was a corrupt dmr record associated with a job, its only happened twice in 4 years.. it would be a long shot if that was your issue,

(somehow I needed to end it so I could tie into tissue)

Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-0590
FAX: (715)284-4084
[Description: cid:1.234354861@...<mailto:1.234354861%40web65412.mail.ac4.yahoo.com>]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of noles1andgators2
Sent: Thursday, March 15, 2012 9:42 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: Riddle me This Batman!

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>, Jonathan Lang <lsbestinc@...<mailto:lsbestinc@...>> wrote:
>
> Okay, so I have an issue that has completely baffled me and that takes a lot.
> From the common user, you've got a prob,
> This thing you say with user and job.
> Robin's advise is grab a tissue,
> And hope somebody can resolve your issue.
>
> Version:
> 8.03.409A
>
> Problem:
> Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
>
> Problem doesn't happen with every job just a select few every great once in a while.
>
>
> Description:
> We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
>
> IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
>
> Any ideas?
>
> Jonathan
>
>
> [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]

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




[Non-text portions of this message have been removed]
2
Okay, so I have an issue that has completely baffled me and that takes a lot.


Version:
8.03.409A

Problem:
Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.

Problem doesn't happen with every job just a select few every great once in a while.


Description:
We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.

IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.

Any ideas?

Jonathan


[Non-text portions of this message have been removed]
3
--- In vantage@yahoogroups.com, Jonathan Lang <lsbestinc@...> wrote:
>
> Okay, so I have an issue that has completely baffled me and that takes a lot.
> From the common user, you've got a prob,
> This thing you say with user and job.
> Robin's advise is grab a tissue,
> And hope somebody can resolve your issue.
>
> Version:
> 8.03.409A
>
> Problem:
> Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
>
> Problem doesn't happen with every job just a select few every great once in a while.
>
>
> Description:
> We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
>
> IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
>
> Any ideas?
>
> Jonathan
>
>
> [Non-text portions of this message have been removed]
>
4
God I love poetry, but since he sucked up his vast pride and asked for help...

The only time weve seen behavior even similar to what you've described is when there was a corrupt dmr record associated with a job, its only happened twice in 4 years.. it would be a long shot if that was your issue,

(somehow I needed to end it so I could tie into tissue)

Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-0590
FAX: (715)284-4084
[Description: cid:1.234354861@...]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of noles1andgators2
Sent: Thursday, March 15, 2012 9:42 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Riddle me This Batman!




--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Jonathan Lang <lsbestinc@...> wrote:
>
> Okay, so I have an issue that has completely baffled me and that takes a lot.
> From the common user, you've got a prob,
> This thing you say with user and job.
> Robin's advise is grab a tissue,
> And hope somebody can resolve your issue.
>
> Version:
> 8.03.409A
>
> Problem:
> Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
>
> Problem doesn't happen with every job just a select few every great once in a while.
>
>
> Description:
> We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
>
> IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
>
> Any ideas?
>
> Jonathan
>
>
> [Non-text portions of this message have been removed]
>



[Non-text portions of this message have been removed]
5
I know we used to have issues with no date shown as scheduled on a job that caused havoc (8.03.409c). Run a query to see if you have any of those?

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Rob Bucek
Sent: Thursday, March 15, 2012 9:53 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Riddle me This Batman!



God I love poetry, but since he sucked up his vast pride and asked for help...

The only time weve seen behavior even similar to what you've described is when there was a corrupt dmr record associated with a job, its only happened twice in 4 years.. it would be a long shot if that was your issue,

(somehow I needed to end it so I could tie into tissue)

Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-0590
FAX: (715)284-4084
[Description: cid:1.234354861@...<mailto:1.234354861%40web65412.mail.ac4.yahoo.com>]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of noles1andgators2
Sent: Thursday, March 15, 2012 9:42 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: Riddle me This Batman!

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>, Jonathan Lang <lsbestinc@...<mailto:lsbestinc@...>> wrote:
>
> Okay, so I have an issue that has completely baffled me and that takes a lot.
> From the common user, you've got a prob,
> This thing you say with user and job.
> Robin's advise is grab a tissue,
> And hope somebody can resolve your issue.
>
> Version:
> 8.03.409A
>
> Problem:
> Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
>
> Problem doesn't happen with every job just a select few every great once in a while.
>
>
> Description:
> We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
>
> IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
>
> Any ideas?
>
> Jonathan
>
>
> [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
Karen! Haha, I knew you'd be the one to answer. Will check to see if that's the issue.



________________________________
From: Karen Schoenung <kschoenung@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Thursday, March 15, 2012 9:57 AM
Subject: RE: [Vantage] Re: Riddle me This Batman!


Â
I know we used to have issues with no date shown as scheduled on a job that caused havoc (8.03.409c). Run a query to see if you have any of those?

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Rob Bucek
Sent: Thursday, March 15, 2012 9:53 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Riddle me This Batman!

God I love poetry, but since he sucked up his vast pride and asked for help...

The only time weve seen behavior even similar to what you've described is when there was a corrupt dmr record associated with a job, its only happened twice in 4 years.. it would be a long shot if that was your issue,

(somehow I needed to end it so I could tie into tissue)

Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-0590
FAX: (715)284-4084
[Description: cid:1.234354861@...<mailto:1.234354861%40web65412.mail.ac4.yahoo.com>]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of noles1andgators2
Sent: Thursday, March 15, 2012 9:42 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: Riddle me This Batman!

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>, Jonathan Lang <lsbestinc@...<mailto:lsbestinc@...>> wrote:
>
> Okay, so I have an issue that has completely baffled me and that takes a lot.
> From the common user, you've got a prob,
> This thing you say with user and job.
> Robin's advise is grab a tissue,
> And hope somebody can resolve your issue.
>
> Version:
> 8.03.409A
>
> Problem:
> Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
>
> Problem doesn't happen with every job just a select few every great once in a while.
>
>
> Description:
> We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
>
> IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
>
> Any ideas?
>
> Jonathan
>
>
> [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]




[Non-text portions of this message have been removed]
7
Not sure if it's the same problem, but when we went to 9.04 we had problems where MES would lock up randomly causing the same problem. After the lockup/crash then the user couldn't log clock back into the job.

Epicor at the time told us to run conversion program 8920 which fixed the stuck jobs and ended the labor activities that we otherwise couldn't end.

So, I would maybe ask Epicor if that exists in 8.03 or if that would fix it. If you have a test environment you could try it in there I guess.

We're on 9.05 now and haven't had that problem since.

--- In vantage@yahoogroups.com, Jonathan Lang <lsbestinc@...> wrote:
>
> Okay, so I have an issue that has completely baffled me and that takes a lot.
>
>
> Version:
> 8.03.409A
>
> Problem:
> Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
>
> Problem doesn't happen with every job just a select few every great once in a while.
>
>
> Description:
> We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
>
> IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
>
> Any ideas?
>
> Jonathan
>
>
> [Non-text portions of this message have been removed]
>
8
I should note, my comments below only fix the resulting issue of not being able to clock out a stuck job, it doesn't fix the problem of them happening in the first place.

--- In vantage@yahoogroups.com, "pbparker" <scrumbus@...> wrote:
>
> Not sure if it's the same problem, but when we went to 9.04 we had problems where MES would lock up randomly causing the same problem. After the lockup/crash then the user couldn't log clock back into the job.
>
> Epicor at the time told us to run conversion program 8920 which fixed the stuck jobs and ended the labor activities that we otherwise couldn't end.
>
> So, I would maybe ask Epicor if that exists in 8.03 or if that would fix it. If you have a test environment you could try it in there I guess.
>
> We're on 9.05 now and haven't had that problem since.
>
> --- In vantage@yahoogroups.com, Jonathan Lang <lsbestinc@> wrote:
> >
> > Okay, so I have an issue that has completely baffled me and that takes a lot.
> >
> >
> > Version:
> > 8.03.409A
> >
> > Problem:
> > Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
> >
> > Problem doesn't happen with every job just a select few every great once in a while.
> >
> >
> > Description:
> > We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
> >
> > IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
> >
> > Any ideas?
> >
> > Jonathan
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
9
Rob,


You're heartless bro! A man comes on knees and I get, "Grab a tissue!" LOL! After all the help I provide for this forum I get, "Grab a tissue." Just heartless! And the DMR is fine. No corruption.


Okay, Karen, no go. It has all the required date fields. I do have it unlocked and I did change the date to the actual Start date. StartDate was set in the future and they're working on it now, but that shouldn't lock the job up. I dunno, I guess I can chalk this up to 'Ghost in the Machine." It would just be nice to know why this happens.

Jonathan



________________________________
From: Jonathan Lang <lsbestinc@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Thursday, March 15, 2012 9:58 AM
Subject: Re: [Vantage] Re: Riddle me This Batman!


Â
Karen! Haha, I knew you'd be the one to answer. Will check to see if that's the issue.

________________________________
From: Karen Schoenung <kschoenung@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Thursday, March 15, 2012 9:57 AM
Subject: RE: [Vantage] Re: Riddle me This Batman!


Â
I know we used to have issues with no date shown as scheduled on a job that caused havoc (8.03.409c). Run a query to see if you have any of those?

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Rob Bucek
Sent: Thursday, March 15, 2012 9:53 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Riddle me This Batman!

God I love poetry, but since he sucked up his vast pride and asked for help...

The only time weve seen behavior even similar to what you've described is when there was a corrupt dmr record associated with a job, its only happened twice in 4 years.. it would be a long shot if that was your issue,

(somehow I needed to end it so I could tie into tissue)

Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-0590
FAX: (715)284-4084
[Description: cid:1.234354861@...<mailto:1.234354861%40web65412.mail.ac4.yahoo.com>]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of noles1andgators2
Sent: Thursday, March 15, 2012 9:42 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: Riddle me This Batman!

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>, Jonathan Lang <lsbestinc@...<mailto:lsbestinc@...>> wrote:
>
> Okay, so I have an issue that has completely baffled me and that takes a lot.
> From the common user, you've got a prob,
> This thing you say with user and job.
> Robin's advise is grab a tissue,
> And hope somebody can resolve your issue.
>
> Version:
> 8.03.409A
>
> Problem:
> Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
>
> Problem doesn't happen with every job just a select few every great once in a while.
>
>
> Description:
> We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
>
> IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
>
> Any ideas?
>
> Jonathan
>
>
> [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]

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




[Non-text portions of this message have been removed]
10
Haha… I didn’t write the tissue poem, I like poems, but am incapable of artistic expression, I hope you find a solution..

Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-0590
FAX: (715)284-4084
[Description: cid:1.234354861@...]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Jonathan Lang
Sent: Thursday, March 15, 2012 10:08 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Re: Riddle me This Batman!



Rob,

You're heartless bro! A man comes on knees and I get, "Grab a tissue!" LOL! After all the help I provide for this forum I get, "Grab a tissue." Just heartless! And the DMR is fine. No corruption.

Okay, Karen, no go. It has all the required date fields. I do have it unlocked and I did change the date to the actual Start date. StartDate was set in the future and they're working on it now, but that shouldn't lock the job up. I dunno, I guess I can chalk this up to 'Ghost in the Machine." It would just be nice to know why this happens.

Jonathan

________________________________
From: Jonathan Lang <lsbestinc@...<mailto:lsbestinc%40yahoo.com>>
To: "vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>" <vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>>
Sent: Thursday, March 15, 2012 9:58 AM
Subject: Re: [Vantage] Re: Riddle me This Batman!



Karen! Haha, I knew you'd be the one to answer. Will check to see if that's the issue.

________________________________
From: Karen Schoenung <kschoenung@...<mailto:kschoenung%40fisher-barton.com>>
To: "vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>" <vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>>
Sent: Thursday, March 15, 2012 9:57 AM
Subject: RE: [Vantage] Re: Riddle me This Batman!


I know we used to have issues with no date shown as scheduled on a job that caused havoc (8.03.409c). Run a query to see if you have any of those?

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of Rob Bucek
Sent: Thursday, March 15, 2012 9:53 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Re: Riddle me This Batman!

God I love poetry, but since he sucked up his vast pride and asked for help...

The only time weve seen behavior even similar to what you've described is when there was a corrupt dmr record associated with a job, its only happened twice in 4 years.. it would be a long shot if that was your issue,

(somehow I needed to end it so I could tie into tissue)

Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-0590
FAX: (715)284-4084
[Description: cid:1.234354861@...<mailto:1.234354861%40web65412.mail.ac4.yahoo.com><mailto:1.234354861%40web65412.mail.ac4.yahoo.com>]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>] On Behalf Of noles1andgators2
Sent: Thursday, March 15, 2012 9:42 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: Riddle me This Batman!

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>, Jonathan Lang <lsbestinc@...<mailto:lsbestinc@...>> wrote:
>
> Okay, so I have an issue that has completely baffled me and that takes a lot.
> From the common user, you've got a prob,
> This thing you say with user and job.
> Robin's advise is grab a tissue,
> And hope somebody can resolve your issue.
>
> Version:
> 8.03.409A
>
> Problem:
> Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
>
> Problem doesn't happen with every job just a select few every great once in a while.
>
>
> Description:
> We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
>
> IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
>
> Any ideas?
>
> Jonathan
>
>
> [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]

[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]
11
You need to run conversion 8920 "End Activity on Labor Detail Transactions", (Admin Tools ->Run Conversion Programs), Enter Company, Enter Emp Num, get details, change Active from "Yes" to "No", don't forget to update your labor details in labor entry for this transaction.



--- In vantage@yahoogroups.com, "pbparker" <scrumbus@...> wrote:
>
> I should note, my comments below only fix the resulting issue of not being able to clock out a stuck job, it doesn't fix the problem of them happening in the first place.
>
> --- In vantage@yahoogroups.com, "pbparker" <scrumbus@> wrote:
> >
> > Not sure if it's the same problem, but when we went to 9.04 we had problems where MES would lock up randomly causing the same problem. After the lockup/crash then the user couldn't log clock back into the job.
> >
> > Epicor at the time told us to run conversion program 8920 which fixed the stuck jobs and ended the labor activities that we otherwise couldn't end.
> >
> > So, I would maybe ask Epicor if that exists in 8.03 or if that would fix it. If you have a test environment you could try it in there I guess.
> >
> > We're on 9.05 now and haven't had that problem since.
> >
> > --- In vantage@yahoogroups.com, Jonathan Lang <lsbestinc@> wrote:
> > >
> > > Okay, so I have an issue that has completely baffled me and that takes a lot.
> > >
> > >
> > > Version:
> > > 8.03.409A
> > >
> > > Problem:
> > > Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
> > >
> > > Problem doesn't happen with every job just a select few every great once in a while.
> > >
> > >
> > > Description:
> > > We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
> > >
> > > IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
> > >
> > > Any ideas?
> > >
> > > Jonathan
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
12
Yes, but as I explained in my original e-mail, I run that to unlock the user, but Thanks Jeremey.


________________________________
From: jeremeyhavrilla <havrilla@...>
To: vantage@yahoogroups.com
Sent: Thursday, March 15, 2012 10:15 AM
Subject: [Vantage] Re: Riddle me This Batman!


Â
You need to run conversion 8920 "End Activity on Labor Detail Transactions", (Admin Tools ->Run Conversion Programs), Enter Company, Enter Emp Num, get details, change Active from "Yes" to "No", don't forget to update your labor details in labor entry for this transaction.

--- In vantage@yahoogroups.com, "pbparker" <scrumbus@...> wrote:
>
> I should note, my comments below only fix the resulting issue of not being able to clock out a stuck job, it doesn't fix the problem of them happening in the first place.
>
> --- In vantage@yahoogroups.com, "pbparker" <scrumbus@> wrote:
> >
> > Not sure if it's the same problem, but when we went to 9.04 we had problems where MES would lock up randomly causing the same problem. After the lockup/crash then the user couldn't log clock back into the job.
> >
> > Epicor at the time told us to run conversion program 8920 which fixed the stuck jobs and ended the labor activities that we otherwise couldn't end.
> >
> > So, I would maybe ask Epicor if that exists in 8.03 or if that would fix it. If you have a test environment you could try it in there I guess.
> >
> > We're on 9.05 now and haven't had that problem since.
> >
> > --- In vantage@yahoogroups.com, Jonathan Lang <lsbestinc@> wrote:
> > >
> > > Okay, so I have an issue that has completely baffled me and that takes a lot.
> > >
> > >
> > > Version:
> > > 8.03.409A
> > >
> > > Problem:
> > > Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
> > >
> > > Problem doesn't happen with every job just a select few every great once in a while.
> > >
> > >
> > > Description:
> > > We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
> > >
> > > IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
> > >
> > > Any ideas?
> > >
> > > Jonathan
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>




[Non-text portions of this message have been removed]
13
We have a similar problem once in a while and it is always tied to the LadorDtl.ResourceGrpId being blank. Apparently when the job is setup they are missing that entry every so often. We just add the ResourceGrpId to the record and the operator can clock out.

Thanks,
Ed
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Jonathan Lang
Sent: Thursday, March 15, 2012 10:25 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Re: Riddle me This Batman!



Yes, but as I explained in my original e-mail, I run that to unlock the user, but Thanks Jeremey.

________________________________
From: jeremeyhavrilla <havrilla@...<mailto:havrilla%40gmail.com>>
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Sent: Thursday, March 15, 2012 10:15 AM
Subject: [Vantage] Re: Riddle me This Batman!



You need to run conversion 8920 "End Activity on Labor Detail Transactions", (Admin Tools ->Run Conversion Programs), Enter Company, Enter Emp Num, get details, change Active from "Yes" to "No", don't forget to update your labor details in labor entry for this transaction.

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "pbparker" <scrumbus@...<mailto:scrumbus@...>> wrote:
>
> I should note, my comments below only fix the resulting issue of not being able to clock out a stuck job, it doesn't fix the problem of them happening in the first place.
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "pbparker" <scrumbus@> wrote:
> >
> > Not sure if it's the same problem, but when we went to 9.04 we had problems where MES would lock up randomly causing the same problem. After the lockup/crash then the user couldn't log clock back into the job.
> >
> > Epicor at the time told us to run conversion program 8920 which fixed the stuck jobs and ended the labor activities that we otherwise couldn't end.
> >
> > So, I would maybe ask Epicor if that exists in 8.03 or if that would fix it. If you have a test environment you could try it in there I guess.
> >
> > We're on 9.05 now and haven't had that problem since.
> >
> > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Jonathan Lang <lsbestinc@> wrote:
> > >
> > > Okay, so I have an issue that has completely baffled me and that takes a lot.
> > >
> > >
> > > Version:
> > > 8.03.409A
> > >
> > > Problem:
> > > Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
> > >
> > > Problem doesn't happen with every job just a select few every great once in a while.
> > >
> > >
> > > Description:
> > > We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
> > >
> > > IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
> > >
> > > Any ideas?
> > >
> > > Jonathan
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>

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


________________________________
The information contained in this message is intended solely for the individual to whom it is specifically and originally addressed. This message and its contents may contain confidential or privileged information. If you are not the intended recipient, you are hereby notified that any disclosure or distribution, or taking any action in reliance on the contents of this information, is strictly prohibited.
We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses.

This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.

Thank you.


[Non-text portions of this message have been removed]
14
Interesting, the same thing has happened to us in 8.03.405.

Always has the same user involved somewhere on the job whether he's the one who locked the job up or not. Anyone who tries to access the job after that will have Epicor lock up completely on them. The job stays locked for about a half hour, then it can be worked on normally again. I haven't been able to see any problems with any of the jobs and it doesn't happen on every job he works on, but I've wondered whether there isn't something corrupt in his Shop Employee record.

Labor detail and header records not usually locked so script doesn't help.

Twice, I found a second MES application running on the (hidden) taskbar with a disconnect error and the job freed up after I closed it.

--- In vantage@yahoogroups.com, Jonathan Lang <lsbestinc@...> wrote:
>
> Okay, so I have an issue that has completely baffled me and that takes a lot.
>
>
> Version:
> 8.03.409A
>
> Problem:
> Job locks up User and anyone who logs into the Job. This also includes Payroll when they log into the User to correct his hours.
>
> Problem doesn't happen with every job just a select few every great once in a while.
>
>
> Description:
> We have a user that we will call 917. He is a machine operator. 917 starts a job and works in the job. The job locks up his MES session. When he closes MES and re logs back into the system the Job has him locked out and he can't perform any functions within MES.
>
> IT, that's me, then runs a couple scripts to end the labor detail and labor header. Unfortunately this doesn't cure the issue only allows 917 to log back into the system and work as long as he doesn't log back into the runaway job.
>
> Any ideas?
>
> Jonathan
>
>
> [Non-text portions of this message have been removed]
>