Problem when running MRP

Yahoo Archive
1
Until we unchecked "run finite scheduling" on process MRP, we had intermittent lockups as well. If you need finite scheduling, turn it off on MRP and run it. We also found running with only 1 process for MRP and scheduling worked better. I would appear that sometimes the threads didn't communicate well together and one would get locked out.

After running MRP without finite, run Calculate Global Scheduling Order, then Global Scheduling. This combination works every time for us.

Tim

--- In vantage@yahoogroups.com, "Nick" <nick@...> wrote:
>
> So we are hoping to go live finally on Jan 3rd, we have Epicor 9.05.606
>
> One of the last things, processing MRP without error.
>
> Our latest issue, when running MRP, it hangs about 30 minutes into the
> process.
>
> Server Log says:
> 40001: [Microsoft][SQL Server Native Client 10.0][SQL Server]Transaction
> (Process ID 58) was deadlocked on lock resources with another process and
> has been chosen as the deadlock victim.
>
> Ran a SQL Trace, and its locking on the JobNum Index.
>
> Any thoughts on where to go from here?
>
> Already put a call into support, but its been a while and they just played
> the transfer game with me and now they seem to be closed for the day.
>
> Thanks
>
2
So we are hoping to go live finally on Jan 3rd, we have Epicor 9.05.606

One of the last things, processing MRP without error.

Our latest issue, when running MRP, it hangs about 30 minutes into the
process.

Server Log says:
40001: [Microsoft][SQL Server Native Client 10.0][SQL Server]Transaction
(Process ID 58) was deadlocked on lock resources with another process and
has been chosen as the deadlock victim.

Ran a SQL Trace, and its locking on the JobNum Index.

Any thoughts on where to go from here?

Already put a call into support, but its been a while and they just played
the transfer game with me and now they seem to be closed for the day.

Thanks
3
Nick,
Make sure that you don't have any jobs out there whether forecast or firm that do not have a start date and required date as far as scheduling goes. You can see this either in planners workbench or in the Job status maintenance. I have seen where this has deadlocked the MRP process. Also if you use the DMR module, make sure there are no jobs there that are causing the conflict. If need be you can call me.
Â
Michael Brown
Master Scheduler
D&S Manufacturing
mbrown@...
715-284-5376 Ext. 344
www.dsmfg.com


________________________________
From: Nick <nick@...>
To: vantage@yahoogroups.com
Sent: Thursday, December 8, 2011 5:57 PM
Subject: [Vantage] Problem when running MRP


Â
So we are hoping to go live finally on Jan 3rd, we have Epicor 9.05.606

One of the last things, processing MRP without error.

Our latest issue, when running MRP, it hangs about 30 minutes into the
process.

Server Log says:
40001: [Microsoft][SQL Server Native Client 10.0][SQL Server]Transaction
(Process ID 58) was deadlocked on lock resources with another process and
has been chosen as the deadlock victim.

Ran a SQL Trace, and its locking on the JobNum Index.

Any thoughts on where to go from here?

Already put a call into support, but its been a while and they just played
the transfer game with me and now they seem to be closed for the day.

Thanks



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