Finance | Project Operations, Human Resources, ...

PSTL account combiner error

(0) Share

Report

Posted on by JBurgess

Using GP 18.4 and PSTL 18.2.5

When rebuilding the procs in PSTL, I get an error:

Eventually the rebuild finishes and you can run the account combiner, but it fails with this error:

I've verified that the stored procedure does not exist in the database.

It doesn't appear that I can script out that sproc from another company as it appears to be locked/encrypted.

I've grabbed the latest download for PSTL 18.2.5 and dropped the CNK into the root directory to rebuild the dictionary, but same errors.

Any insigh/help with this would be appreciated!

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Suggested answer

Derek Albaugh Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Against the company database, do you see the procedure present?

select * from sysobjects where name = 'taAccountIndexCombiner'

If not, then the 'Rebuild Procs' button in PSTL would be the next step, which should drop and re-create the procedures used.

I tested deleting my proc and using the Rebuild Procs and it put it back.

Otherwise, you may need to manually remove PSTL from the company database and re-add it back in.

Thanks

Was this reply helpful? Yes No
JBurgess 74 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the suggestion here.

I ran the script you provided and confirmed that the proc is not in the company database.

I run the rebuild procs button in that database, but that is the original issue and presents the errors above, it does not put the proc back. It seems like the process hangs for a bit at around 24% finished if that helps troubleshooting.

Do you have a recommendation to remove PSTL from just the one company database? This client has multiple companies, and those all appear to be working as intended.

Was this reply helpful? Yes No
Suggested answer

Derek Albaugh Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Close out of Dynamics GP again for all users on a machine that GP is installed onto.

2. In Control Panel > Programs and Features, uninstall PSTL from Dynamics GP.

3. In this GP's directory, verify the TAUTIL.DIC file is gone and then in the Dynamics.set file, we also shouldn't see the following:

1838
Technical Service Tools

:C:Program Files (x86)/Microsoft Dynamics/GP/TAUTIL.dic
:C:Program Files (x86)/Microsoft Dynamics/GP/Data/F1838.DIC
:C:Program Files (x86)/Microsoft Dynamics/GP/Data/R1838.DIC

4. Here is a text file which has scripts to remove PSTL objects from both the GP company and system databases. Run them at least against the GP system database and the one company database you're testing PSTL on.

Drop-PSTL-Objects-GP-18_5F00_x.txt

5. Reinstall PSTL via Control Panel > Programs and Features again and see if this doesn't help resolve the missing stored procedure.

Thanks

Was this reply helpful? Yes No
JBurgess 74 on at

Like (0)

Report
Copy link

Link copied!

Derek, I followed the instructions above.

I uninstalled via control panel and confirmed the dictionary was removed and not in the DYNAMICS.SET file.

I then ran the Drop scripts against the company and then DYNAMICS.

After that, I re-added PSTL via the GP install.

When loading PSTL for the first time I experienced the same issue as before.

Something else to note, is that it seems to hang at this point for a few seconds before moving on:

I checked the event viewer logs to see if anything might have shown up there, but I don't see any errors or warnings related to GP.

Thanks again for your continued help in resolving this.

Was this reply helpful? Yes No
Suggested answer

Derek Albaugh Microsoft Employee on at

Like (2)

Report
Copy link

Link copied!

I'm curious if you once had Analytical Accounting installed in the company(s) seeing this DBMS 8101/2TA_Account_Changer error, and then not upgraded AA to the current GP version you're on?

I ask because we've seen this error caused by tables that have Account Index data in them, but they're at the wrong structure for the GP version you're on.

Similar to GP upgrades, if it sees AAG tables at all, it expects them to be upgraded to the current version, otherwise it'll cause errors.

If you did have AAG installed but it isn't used and hasn't been updated to the current GP version you're on, you can remove it via this article and scripts:

learn.microsoft.com/.../remove-analytical-accounting-from-computer-with-dynamics-gp-installed

Thanks

Was this reply helpful? Yes No
Suggested answer

JBurgess 74 on at

Like (2)

Report
Copy link

Link copied!

Derek, using the remove AA scripts worked. The client does not use AA, and it does appear that those tables existed from a previous install. Once I ran the scripts the rebuild procs process went through with no issues, and I was able to use the account combiner as intended. Thank you for your help!

Was this reply helpful? Yes No
Suggested answer

Derek Albaugh Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I'm glad it worked. Thanks for the confirmation, have a great day.

Was this reply helpful? Yes No