Question

Heads UP! 2022.1.8 and a recurring MRP Issue

  • 28 July 2022
  • 2 replies
  • 83 views

Userlevel 1

It seems that 2022.1.8 has (re)introduced an issue with MRP running and saying that the App server does not match in Kinetic and what is on the Server. We just upgraded to 2022.1.9 because of a fix with Lot selection on Inventory transactions and have done a provisional MRP test before we release the system for UAT and we are getting the following error -

 

15:01:23 Beginning of Update of PartPlant.PartRunMRP
15:01:25 End of Update of PartPlant.PartRunMRP
15:01:25 Starting sub-processes
15:01:25 Exception has been thrown by the target of an invocation.
15:01:25 -> Verify that the Appserver URL in the System Agent is the same as the URL in the Epicor Administration Console - Connection Properties
15:01:25 Exception has been thrown by the target of an invocation.
15:01:25 -> Verify that the Appserver URL in the System Agent is the same as the URL in the Epicor Administration Console - Connection Properties
15:01:28 Scheduling Jobs...
15:01:28 Erp.Internal.MR.MRPCancelledException: Cancelling from MrpExp mrp
   at Erp.Internal.MR.MrpExp.mrp(Boolean p_net, String p_plist, Nullable`1 p_cutoff, String p_reqtype, Nullable`1 MRP_DEBUG_ON, String ipPartList, String ipPartClassList, String ipProdGrupList, List`1 ttMrpProcRows, List`1 ttMrpQueueRows) in C:\_releases\ERP\ERP11.2.100.0\Source\Server\Internal\MR\MrpExp\MrpExp.cs:line 2349
   at Erp.Internal.MR.MrpExp.main_block(List`1 ttMrpProcRows, List`1 ttMrpQueueRows) in C:\_releases\ERP\ERP11.2.100.0\Source\Server\Internal\MR\MrpExp\MrpExp.cs:line 1867
   at Erp.Internal.MR.MrpExp.RunProcess(Int64 instanceTaskNum, String outputFileName) in C:\_releases\ERP\ERP11.2.100.0\Source\Server\Internal\MR\MrpExp\MrpExp.cs:line 824

 

The MRP stops after a few seconds and actually is marked as complete in the system monitor. 

We have spoken with Chris Coogan at EPICOR who confirms that this is a known bug but looking on Epicare it could be a re-occurrence of an issue that was raised in May 2021!


2 replies

Userlevel 1

We ran into this issue back in April of this year on version 2022.1.1. They had to apply a fix (ERP-40914) to our server to correct it, and they also opened problem PRB0249226, which I see is still in Accepted status without any Resolution or Fixed in Release noted.

Userlevel 1

We ran into this issue back in April of this year on version 2022.1.1. They had to apply a fix (ERP-40914) to our server to correct it, and they also opened problem PRB0249226, which I see is still in Accepted status without any Resolution or Fixed in Release noted.

We just found your problem on epicare and sent that to our PM to look into. Strange that you saw it on 2022.1.1 and we have been fine up unto 2022.1.5.

Reply