We are still experiencing problems with the standard sales order
posting process in Axapta v3 SP2. It seems as if the standard
posting routine in Axapta has a memory leak that causes Ax32.exe to
crash with an out of memory error. Has anyone of you experienced
this before and do you have any recommendations for us in this
regard? The details are as follows:
We get the SmartHeap Out of Memory error when trying to import and
post individual sales orders from an external system. The invoices
get imported into Axapta and then posted. This posting happens on a
per sales order basis. (Import 1 sales order from the external
system into the temporary posting tables and then post the sales
order) We suspect that this is due to a memory leak in the Axapta
standard posting process. (Class.SalesFormLetter). For each sales
order that is posted, a certain amount of memory is allocated (as can
be seen in the Windows task manager) and added to the total memory
usage of the Ax32 process. Only a small amount of the added memory is
released after the posting process. This cause the total memory
usage of the Ax32 process to keep growing. (Typical memory leak
behaviour). This causes the SmartHeap Out of Memory error after a
variable amount (about 3500) of sales orders were posted. We have
tracked this down to the SalesFormLetter.post() instruction in
Axapta. The posting is run from a client PC and the error occurs in
both 2 and 3-tier mode.
The standard Axapta posting procedure, in SalesFormLetter.run(), is
called for each sales order imported. (The code causes the memory
leak).
The SmartHeapMemorySizeUp() value has been set.
Do anyone have any suggestions in this regard?
Regards,
SPONSORED LINKS
| Computer part | Programming languages | Microsoft axapta |
| Support exchange |
YAHOO! GROUPS LINKS
- Visit your group "development-axapta" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
