Does anyone used recently the PSTL utility to apply changes to GL accounts in GP2010?
I have the error coming on screen when trying to use the PSTL tool to change GL Accounts from one segment to another... Renaming accounts (non-existant destination) seems to work fine, but Accounts that need to be merged with an existing account poses a serious issue and can't be converted. I've tried both avenues (file import or direct input) and none of them work.... I looked at the GL00100 table and can't find custom triggers aside of the one put in place by the PSTL (starting with ta... ). I also see 3 triggers starting with glp... and that covers the inset, delete and update actions. They do look like coming from GP, but I couldn't say for sure. They have a date of creation quite recent (when the last YE Tax update was applied)... but they seem to have been there for a while.
I did run also a DEX trace log, but the last statement that is called before the error is a stored procs... : zDP_SY02100SS_1 and then right after an SP declare : BEGIN DECLARE @stored_proc_name char(28) DECLARE @retstat int DECLARE @param5 int set nocount on SELECT @stored_proc_name = 'FTI.dbo.smChangeAccountIndex' EXEC @retstat = @stored_proc_name '2274', '2435', 2274, 2435, @param5 OUT SELECT @retstat, @param5 set nocount on END
after which I get the SQL nested error message :
/* Date: 03/06/2013 Time: 13:39:42
SQLSTATE:(37000) Native Err:(217) stmt(13379536):*/
[Microsoft][SQL Server Native Client 10.0][SQL Server]Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32).*/
Any ideas where to start look for ?