Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32). Unknown failure (com.boomi.connector.api.ConnectorException)

Document created by Nikita_nandakumar on Jan 15, 2015Last modified by dave_lesshafft on Mar 1, 2016
Version 2Show Document
  • View in full screen mode
This error usually occurs on the Microsoft Dynamics GP (Great Plains) connector.Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32) means that something that you are drawing information from in your stored procedure is more than 32 nested levels deep.
Please check the following:

 

1) Check to see if there has been some recent changes in the database.
2) Check the settings at the database level.You could use the nested triggers option to control whether a trigger can cascade.
3) Identify the table causing the error.Verify if there is a duplicate trigger inside the table.

 

Deleting the duplicate trigger will stop generating the error on the connector.

 

For additional information :

 

http://www.mssqltips.com/sqlservertip/1713/maximum-stored-procedure-function-trigger-or-view-nesting-level-exceeded-limit-32/

 

http://blogs.msdn.com/b/developingfordynamicsgp/archive/2012/05/03/sql-error-maximum-stored-procedure-function-trigger-or-view-nesting-level-exceeded-limit-32.aspx

 

http://www.windows-tech.info/15/5adf8b5edc53054a.php

Attachments

    Outcomes