Friday, June 28, 2013

eConnect Error: Unable to obtain the next note index

A client was using an eConnect load testing tool that I had developed when they encountered this error messsage.

Error Number = 277 
Stored Procedure = taIVTransactionHeaderInsert
Error Description:  Unable to obtain the next note index

And below that was a second error.

Error Number = 3564
Stored Procedure = tasmGetNextNoteIndex
Error Description:  Input parameter contains a NULL parameter

Taking a look at the tasmGetNextNoteIndex procedure in the Dynamics database, I found that the error occurs when either the Company ID or SQL Session ID value is NULL.

A Company ID value would be NULL if the eConnect import was attempting to import into an invalid company database.

So we checked the import configuration file, and sure enough, the database name was incorrect.  It was set to TWO, and the client did not have a TWO database in their test environment.

Once we set the database configuration option to a valid company database, the import ran fine.

Written By Steve Endow

Steve Endow is a Dynamics GP Certified Trainer and Dynamics GP Certified IT Professional in Los Angeles.  He is also the owner of Precipio Services, which provides Dynamics GP integrations, customizations, and automation solutions.

You can also find him on Google+ and Twitter

No comments: