Setting max buffer size in Ax2009 for AIF

In Dynamics AX 2009 it can happen that a lengthy operation terminates with the following error message in the InfoLog:
Error executing code: Insufficient memory to run script.
A typical example that can result in this error message is when you are running the Reverse Engineering Tool of Dynamics AX 4.0 SP1. Another very common situation is when you are trying to process very large AIF messages with several thousand lines within AX or within an application that uses the Business Connector like the AX BizTalk Adapter.
With Dynamics AX 4.0 a new mechanism was introduced to limit the maximum amount of memory that can be allocated by variables (in X++ code) in a session. This maximum amount is set to 10 MB by default. For some operations like large AIF messages (that are stored in memory during processing) this is however not enough and so the operation is terminated when the maximum amount is reached.
The second part of the error message "Insufficient memory to run script." clearly indicates that this buffer was reached. It is possible to increase the buffer size in the windows registry by changing the following registery enteries


Key name: [HKEY_CURRENT_USER\Software\Microsoft\Dynamics\5.0\Configuration\(configuration name)] Value name: maxbuffersize Value type: REG_SZ Value: (Maximum amount of memory in MB or 0 for no limit)
For Dynamics AOS it is the following registry key Key name: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dynamics Server\5.0\(AOS instance)] Value name: maxbuffersize Value type: REG_SZ Value: (Maximum amount of memory in MB or 0 for no limit)
 This registry entry does, by default, not exist.
 It is recommended not to use value ‘0’ for ‘no limit’.
 After making changes to this registry value, ensure that the Dynamics service and/or client is restarted.

HOW To Do Debugging In AIF

IF we want to do debugging in AIF then follow the following steps.This is for Inbound processing

1.Go to AOT->Classes->AIFInBoundProcessingService
2.Go to method runAsWrapper
3.Comment the following lines in method

// BP deviation documented
// runas(axaptaUserId,
// classnum(AifInboundProcessingService),
// staticmethodstr(AifInboundProcessingService, processAsUser),
// messageIdContainer);


and replace this with the following line

AifInboundProcessingService::processAsUser(messageIdContainer);

4. Make the processAsUser method public from private

public static void runAsWrapper(AifWindowsUser runAsUserId, container messageIdContainer)
{
AifGatewayQueue gatewayQueue;
userId axaptaUserId;
AifMessageId messageId;
int messageIdContainerIdx = 1;
AifMessage errorMessage;
AifInfoLog aifInfoLog;
SysExceptionLog exceptionLog;
;
aifInfoLog = new AifInfoLog();
try
{
// Convert to Axapta UserId
axaptaUserId = AifEndpointUser::getAxaptaUser(runAsUserId).Id;
new RunAsPermission(axaptaUserId).assert();
// BP deviation documented
// runas(axaptaUserId,
// classnum(AifInboundProcessingService),
// staticmethodstr(AifInboundProcessingService, processAsUser),
// messageIdContainer);
AifInboundProcessingService::processAsUser(messageIdContainer);
CodeAccessPermission::revertAssert();

How To Restore Data In AIFSchemaStore Table

AIFSchemaStore table contains the schema information for all the AIF services in AX

If data is deleted from this table or it doesn't contain the proper schema information then we can not configure endpoint action policy

Steps to regenerate data in AIFSchemaStore table:

1.Delete all data from AIFSchemaStore table
2.Delete all the data from AIFDocumentSchema table
3.Click on refresh button on Services form it will regenerate all the data in AIF SchemaStoretable and documentSchema table
4.To verify after refreshing the services check if In AIFAction table all the actions for services is pointing to the classid of corresponding service class.