› Target system integrations › Microsoft Dynamics › Dynamics AX 2012 › Introduction › Troubleshooting

Troubleshooting

Check these issues when troubleshooting the Dynamics AX 2012 integration.

"Error executing code: Insufficient memory to run script."

If you receive the message above in Dynamics AX 2012, you can try increasing the Dynamics AX maxbuffersize in the Windows registry to solve this issue.

To change the value of maxbuffersize:

  1. In Windows, click Start, click Run, type "regedit" in the Open box, and then click OK.
  2. Navigate to maxbuffersize (default location: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dynamics Server\6.0\01\Original (installed configuration)).

    If you are not running the Original (installed configuration), make the change in the active configuration, which can be for example, \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dynamics Server\6.0\01\PRODUCTION P1

    If maxbuffersize does not exist, create it as a string (REG_SZ).

    maxbuffersize
  3. Increase the value of maxbuffersize. We recommend at least 200, which means 200 MB.
  4. Restart AOS.
  5. Recompile the Tungsten AP Essentials integration project.
    1. Press  Ctrl  +  D  to open AOT and click the Project button.
      Click the Project button
    2. Expand the Shared node and double-click RsoIntegration to open the project.
    3. Select Compile (Build menu) to compile the project.
      Compile the project

"Cannot create a record in RsoLogTable (RsoLogTable). The SQL database has issued an error."

If you receive the message above in Dynamics AX 2012, you can try synchronizing the data dictionary in Dynamics AX to solve this issue.

Infolog

To synchronize the data dictionary:

  1. Press Ctrl + D  to open AOT.
  2. Right-click Data Dictionary and select Synchronize.
    Synchronize the data dictionary

Document management directory does not exist

An error message that the "Document management directory does not exist" can appear in:

Three issues can cause this error message:

  • The directory does not exist in Dynamics AX. Make sure that the folder that is specified in the Archive directory setting exists.
Archive directory setting
  • AOS cannot access the directory. If the Archive directory is located on a different computer than the AOS service, you must share the folder and reference its shared path.
Archive directory setting
  • The integration user does not have access to the directory. Make sure that the user that performs the integration has read/write access to the folder that is specified in the Archive directory setting in Dynamics AX (Document management parameters dialog).

You can specify the integration user in two different places:

  • The Tungsten AP Essentials configuration wizard.
  • The Tungsten AP Essentials Windows service.