Author |
Message
|
parsar |
Posted: Tue Nov 07, 2006 10:30 pm Post subject: FMC01014E - The PEA for USERID.FMCGRP is not available |
|
|
Novice
Joined: 08 Dec 2005 Posts: 22
|
Hi
we recently have migrated from PEA to UPES.
i.e, we have used the PEA earlier to start the work items but now we have migrated to UPES to start the work items. But in production we had lot of work items that were created using PEA. The FMCDB had the PEAs defined for the work items and now we have changed the definition of the work items to use UPES here after.
Now, when we have imported the FDL , it didnt update the existing definitions of the work items in the FMC.PROCESS_TEMPL instead it created a new row for each process definition. Why is this happening? Is it not supposed to update the existing records?
Now the problem is :
If we create the work items afresh, then we do not have any problem and we are able to work the work items and we get the process instance start XML messages in the UPES queue. But if we try to start the work items that were created earlier(before the UPES version of the FDL was imported) , then the work item goes into an error state(128) saying "The PEA for USERID.FMCGRP is not available". This error is obvious since we have removed the code chunk which starts the PEA (programExecutionAgentStartUp() ). But we are force restarting the erroneous work items in the code and are able to close the work item after performing the business process. So, how serious is this error and what needs to be done to get rid of this problem, since we have around 50000+ such work items. I am actually not able to figure out whats happening behind the scenes. Why the existing work items are using the UPES and why are they complaining about non-existence of the PEA?
An urgent suggestion and help is highly appreciated since we have the code already in production!!
Thanks a lot in advance |
|
Back to top |
|
 |
jmac |
Posted: Wed Nov 08, 2006 6:14 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
If I understand what you are saying correctly, then what you are seeing is exactly how MQWF is supposed to perform. In-flight instances will use the existing template, and thus need the PEA, newly created instances will use the UPES. _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
parsar |
Posted: Wed Nov 08, 2006 9:27 am Post subject: |
|
|
Novice
Joined: 08 Dec 2005 Posts: 22
|
Thanks JMac for the reply.
But the whole thing is running without show stoppers.
Just that we see this error in the fmcautil -> system log for each user who attempts to start his work items.
So what should be done now? can this error be ignored?
Please suggest. Thanks again. |
|
Back to top |
|
 |
jmac |
Posted: Wed Nov 08, 2006 9:35 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
You obviously replaced a fat client with a thin client. Are the old activities being displayed properly in your new client when you run them? If so I think you can safely ignore the message. _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
parsar |
Posted: Wed Nov 08, 2006 2:27 pm Post subject: |
|
|
Novice
Joined: 08 Dec 2005 Posts: 22
|
Yes John ,
The old work items working fine except for this error message.
But I am curious to know how the work items are executing properly even if I am not starting the PEA for any user or for any work item.
Its obvious that there is no PEA started, what is being used to execute the work items. There is neither PEA nor UPES for those old work items.
Thanks for the clarification John. |
|
Back to top |
|
 |
jmac |
Posted: Wed Nov 08, 2006 2:45 pm Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
I assume your thin client is able to locate the proper executable. Without knowing what your client looks like it is not easy to tell. _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
|