Updated · Originally published
Lately while upgrading a GP client to the latest GP release (build 18.2. 1060) from GP 2015, there was an error that we encountered when trying to launch PSTL:
We searched and found a new 18.2.4 version of the PSTL tool on the that was released in October, but installing that available build did not end fixing the problem. The solution we found was to run the following command in SQL Server Management Studio (first ensure you have a database backup):
DELETE DYNAMICS..TA00860
Once running the above script, we had no issues introducing the PSTL utility within GP and rebuilding the Stored Procs. Our goal is this will assist others if you have established that you are using the right PSTL build and are continuing to receive the above error.
If you are still having a problem with this error, please contact Crestwood Support at [email protected]. We would love to help you!
Nice article!