Today I worked with a customer who was receiving this error message when posting batches:
Illegal address for field 'TPEInitialize' in script '[Not Found]'. Script terminated.
We also saw:
Transaction not completed at initiating scripts exist, implicitly rolled back.
I've seen the first error a few times before, but didn't know the cause, other than that it is some type of internal Dynamics GP / Dexterity error. This customer was seeing the error when trying to post batches using the Distributed Process Server.
Today, after working with the customer for over an hour, we found the cause of the problem in the customer's environment. The customer has numerous complex Dynamics GP customizations--when attempting to save and post a batch in Dynamics GP with a particular GP login, we saw that some permission errors occurred. The permissions were related to custom tables and the GP login didn't have sufficient access to those tables. Those errors caused all sorts of failures and problems in the GP client.
Once we fixed the permission settings, we were able to save and post batches in GP, and then the batches posted successfully in DPS.
The error messages are pretty generic, so there may be other causes besides security, but if you run into them, try performing all of the steps of the process manually in GP with the same GP login.
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.
No comments:
Post a Comment