PSTL 18.2.5 throws an error at the end of setup in GP 18.3.1245

(0) Share

Report

Posted on by Beat Bucher GP Gee...

28,058 Moderator

Hi All,

I recently run into some weird error messages after adding a few new companies to a customer site which is running GP 18.3.1245.

The latest PSTL module was downloaded already for the previous companies and weirdly enough was showing version discrepancies between some of the older companies and the most recent ones..

This was pulled from the TA00860 table in DYNAMICS system DB.

The error messages I'm getting varies from company to company, in some cases the process for initialisation runs to the end, but throws a grant error (likely), though I've re-run the GRANT.SQL script against those companies..

In other companies, the process fails at 24% and then is stuck there and never completes.

right after when clicking on OK:

I re-installed the 18.2.5 PSTL chunk file and re-run the initializations of the objects in the companies (rebuild procs), but the error would come back anyway.

I'm wondering about that "smChangeAccountIndex2" stored procs that fails every time on some companies and can't get past it.. in some older companies, there is a bunch of SP's that are encrypted and seem to part of the PSTL setup, but with an older creation date.. I'm wondering if there isn't something missing from the most recent PSTL chunk file, and thus not created in the newer companies.. This GP instance was built back in 2020 under GP 18.2 and PSTL 18.2.1

After it got upgraded to GP 18.3, the PSTL was upgraded too, but it looks like that the encrypted SP's never got updated.. and in the new companies, are completely missing..

Thanks for any insights on validating this.

I have the same question (0)

All responses (14)

Answers (1)

Suggested answer

Derek Albaugh on at

Like (0)

Report

RE: PSTL 18.2.5 throws an error at the end of setup in GP 18.3.1245

Looking at my 18.3.1245 system, all of the companies mentioned in TA00860 show as 18.2.5.

That being said, back in late 2019/early 2020, we did have some version errors with PSTL where we put out a 18.2.4 version on 10/10/2019, which was included in the US Year-end update released in mid-November 2019.

I couldn't find any mention of the '1TA_macGrantAllSY' procedure in the first error message you're seeing, in fact, I don't have any objects that contain '1TA' at all, so not sure about those. Those may be custom or third-party?

During the upgrade, GP Utilities actually doesn't do anything with PSTL as far as upgrading, it's all done either the first time you launch PSTL in the company database, or in PSTL when you click the 'Rebuild Procs' button

Is it the company databases that show as 18.2.1 that are having these errors? If so, in one of the companies, can you get into the PSTL window and try the 'Rebuild Procs' option, or does it error before you even get into the PSTL window?

Another option would be to try removing the company record from the TA00860 table and try launching PSTL again.

If none of those work, we usually have scripts to completely remove all PSTL objects from the company database and re-install.

Thanks

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

RE: PSTL 18.2.5 throws an error at the end of setup in GP 18.3.1245

Hi Derek,

Thanks for your reply. The 1TA_macGrantAllSY error only comes up for companies that had previously existed and where PSTL was setup in version 18.2.1.. All other companies that are newly created after the latest GP upgrade and which got PSTL 18.2.5 installed, fail at 24% of initialization with the same error message.. The commonality between those companies is the missing of all the SP's that are encrypted in PSTL (some of the smXXXX SP's and more).

I'm thinking about removing the PSTL 18.2.5 and re-install the previous version 18.2.1 that I still have around and see if that version creates the missing encrypted SP's in the new companies.

I'd be grateful if you could send me the PSTL object removal scripts, since I'm not sure I have them anywhere in my collection..

I also noticed that not all companies are currently in the TA00860 table, and the one that are missing do already have most of the SP's that are encrypted and created by the PSTL setup, so I'm wondering if those aren't somewhat part of another process.. ?

As for the 1TA_macGrantAllSY error message, I ran a SQL trace on a company where PSTL was fully setup and I had re-run the object creation, and this is what I captured towards the end:

use DYNAMICS declare @iStatus int, @O_SQL_Error_State int EXEC @iStatus = taRunProcedure"if exists (select * from sysobjects where id = object_id('dbo.macGrantAll') and sysstat & 0xf = 4) drop procedure dbo.macGrantAll ",'', @O_SQL_Error_State

This is then followed by a whole list of scripts executed against tables & SP's to grant permissions..

use TUCI declare @cStatement varchar(255) declare G_cursor CURSOR for select 'grant execute on ' + convert(varchar(64),name) + ' to DYNGRP' from sysobjects where type = 'P' and name like 'z%TACHANGE%' set nocount on OPEN G_cursor FETCH NEXT FROM G_cursor INTO @cStatement WHILE (@@FETCH_STATUS <> -1) begin EXEC (@cStatement) FETCH NEXT FROM G_cursor INTO @cStatement end DEALLOCATE G_cursor

Apparently, towards the end the end result that is expected is not 0, thus it's throwing the error message.

The 2 last code that was called are on table & SP:

use TUCI grant select,update,insert,delete on gpCustomerException to DYNGRP

use TUCI declare @cStatement varchar(255) declare G_cursor CURSOR for select 'grant execute on ' + convert(varchar(64),name) + ' to DYNGRP' from sysobjects where type = 'P' and name like 'z%gpCustomerException%' set nocount on OPEN G_cursor FETCH NEXT FROM G_cursor INTO @cStatement WHILE (@@FETCH_STATUS <> -1) begin EXEC (@cStatement) FETCH NEXT FROM G_cursor INTO @cStatement end DEALLOCATE G_cursor

Hope that helps..

Was this reply helpful? Yes No
Suggested answer

Derek Albaugh on at

Like (1)

Report

RE: PSTL 18.2.5 throws an error at the end of setup in GP 18.3.1245

To verify....

--newly created company databases fail with PSTL 18.2.5 at 24% initialization and show the same 1TA.... errors.

--existing company databases that had PSTL 18.2.1, also fail with 1TA errors.

For either of these, can you get into the PSTL window and click the 'Rebuild Procs' option or no?

I can't say I've seen these types of issues/errors with PSTL in 18.2/18.3 GP in case volume we've seen up to this point and my own testing, though most of my PSTL testing is probably done with new installs/company databases not an upgraded environment.

The PSTL drop scripts for both system and company databases are here:

/* These Scripts can be used to completely remove all objects associated with the Professional Services Tools Library version 18.2 */

/* There are scripts here for both the company database and system database for Dynamics GP, so verify which scripts you need to run before doing so */

/* Run these against the company databases for Dynamics GP */

DROP TABLE ACColumn

DROP TABLE autotemp

DROP TABLE gp_po_cost

DROP TABLE gpAppEnb

DROP TABLE gpCustomerException

DROP TABLE gpItmCus

DROP TABLE gpUPRCPR

DROP TABLE MinPONum

DROP TABLE TA1099

DROP TABLE TACHANGE

DROP TABLE TAIVRec

DROP TABLE taPMRECALC

DROP TABLE taRMRECALC

DROP TABLE TASCMFG

DROP TABLE WHPSETP

DROP TABLE WHPT001

DROP PROCEDURE amAutoGrant

DROP PROCEDURE APOReconcile

DROP PROCEDURE eeCompanyCopy

DROP PROCEDURE eeCompanyCopyAFA

DROP PROCEDURE eeCompanyCopyBOM

DROP PROCEDURE eeCompanyCopyCmpy

DROP PROCEDURE eeCompanyCopyExPr

DROP PROCEDURE eeCompanyCopyFA

DROP PROCEDURE eeCompanyCopyFinancial

DROP PROCEDURE eeCompanyCopyHR

DROP PROCEDURE eeCompanyCopyIV

DROP PROCEDURE eeCompanyCopyIVC

DROP PROCEDURE eeCompanyCopyMC

DROP PROCEDURE eeCompanyCopyMfg

DROP PROCEDURE eeCompanyCopyMfg2

DROP PROCEDURE eeCompanyCopyMfg3

DROP PROCEDURE eeCompanyCopyMfg4

DROP PROCEDURE eeCompanyCopyPA

DROP PROCEDURE eeCompanyCopyPA2

DROP PROCEDURE eeCompanyCopyPA3

DROP PROCEDURE eeCompanyCopyPA4

DROP PROCEDURE eeCompanyCopyPA5

DROP PROCEDURE eeCompanyCopyPA6

DROP PROCEDURE eeCompanyCopyPA7

DROP PROCEDURE eeCompanyCopyPM

DROP PROCEDURE eeCompanyCopyPOP

DROP PROCEDURE eeCompanyCopyPost

DROP PROCEDURE eeCompanyCopyPR

DROP PROCEDURE eeCompanyCopyPre

DROP PROCEDURE eeCompanyCopyRM

DROP PROCEDURE eeCompanyCopySOP

DROP PROCEDURE ItemSiteCombinerMfg

DROP PROCEDURE ivReconcileSearch

DROP PROCEDURE macGrantAll

DROP PROCEDURE smChangeAccountIndex

DROP PROCEDURE smChangeAccountIndex2

DROP PROCEDURE smChangeAccountIndexCPY

DROP PROCEDURE smChangeAccountIndexMfg

DROP PROCEDURE smChangeVendorMaster

DROP PROCEDURE smCheckbookModify1

DROP PROCEDURE smCustomerChanger1

DROP PROCEDURE smCustomerCombiner1

DROP PROCEDURE smCustomerCombinerProject

DROP PROCEDURE smCustomerNameChange1

DROP PROCEDURE smItemChange1

DROP PROCEDURE smItemDescriptionChange1

DROP PROCEDURE smItemNumberCombiner

DROP PROCEDURE smItemNumberCombiner2

DROP PROCEDURE smItemNumberCombinerMfg

DROP PROCEDURE smItemNumberCombinerService

DROP PROCEDURE smPMSummaryNOINVYTD

DROP PROCEDURE smPMSummaryNOINVYTDLYR

DROP PROCEDURE smRMSummary

DROP PROCEDURE smRMSummaryLYR

DROP PROCEDURE smSalesPersonChange1

DROP PROCEDURE smSiteChange1

DROP PROCEDURE smSiteCombine1

DROP PROCEDURE smTerritoryCombiner1

DROP PROCEDURE smTerritoryModify1

DROP PROCEDURE smVendorChange1

DROP PROCEDURE smVendorNameChange1

DROP PROCEDURE ta1099ModifierProcess

DROP PROCEDURE ta1099ModifierReportOnly

DROP PROCEDURE taAccountIndexCombiner

DROP PROCEDURE TACallCustomerCombine

DROP PROCEDURE TACallItemCombine

DROP PROCEDURE TACallItemSiteCombine

DROP PROCEDURE TACallVendorCombine

DROP PROCEDURE taCustomerCombinerPost

DROP PROCEDURE taCustomerCombinerPre

DROP PROCEDURE taCustomerModifierPost

DROP PROCEDURE taCustomerModifierPre

DROP PROCEDURE TAEmployeeChanger1

DROP PROCEDURE taEmployeeModifierPost

DROP PROCEDURE taEmployeeModifierPre

DROP PROCEDURE taGLModifyAccount

DROP PROCEDURE taItemNumberCombinerPost

DROP PROCEDURE taItemNumberCombinerPre

DROP PROCEDURE taItemNumberModifierPost

DROP PROCEDURE taItemNumberModifierPre

DROP PROCEDURE taItemSiteCombinerPost

DROP PROCEDURE taItemSiteCombinerPre

DROP PROCEDURE taItemSiteModifierPost

DROP PROCEDURE taItemSiteModifierPre

DROP PROCEDURE taPMVendMstrPeriodSum

DROP PROCEDURE taPMVendMstrPeriodSumDetail

DROP PROCEDURE taRMCustMstrPeriodSum

DROP PROCEDURE taRMCustMstrPeriodSumDetail

DROP PROCEDURE taRunProcedure

DROP PROCEDURE taSalesPersonPeriodSum

DROP PROCEDURE taSalesPersonPeriodSumDetail

DROP PROCEDURE taSalesTerrPeriodSum

DROP PROCEDURE taSalesTerrPeriodSumDetail

DROP PROCEDURE taVendorCombinerPost

DROP PROCEDURE taVendorCombinerPre

DROP PROCEDURE taVendorModifierPost

DROP PROCEDURE taVendorModifierPre

DROP PROCEDURE zDP_gp_po_costF_1

DROP PROCEDURE zDP_gp_po_costL_1

DROP PROCEDURE zDP_gp_po_costN_1

DROP PROCEDURE zDP_gp_po_costSD

DROP PROCEDURE zDP_gp_po_costSI

DROP PROCEDURE zDP_gp_po_costSS_1

DROP PROCEDURE zDP_gpAppEnbF_1

DROP PROCEDURE zDP_gpAppEnbL_1

DROP PROCEDURE zDP_gpAppEnbN_1

DROP PROCEDURE zDP_gpAppEnbSD

DROP PROCEDURE zDP_gpAppEnbSI

DROP PROCEDURE zDP_gpAppEnbSS_1

DROP PROCEDURE zDP_gpCustomerExceptionF_1

DROP PROCEDURE zDP_gpCustomerExceptionL_1

DROP PROCEDURE zDP_gpCustomerExceptionN_1

DROP PROCEDURE zDP_gpCustomerExceptionSD

DROP PROCEDURE zDP_gpCustomerExceptionSI

DROP PROCEDURE zDP_gpCustomerExceptionSS_1

DROP PROCEDURE zDP_gpItmCusF_1

DROP PROCEDURE zDP_gpItmCusF_2

DROP PROCEDURE zDP_gpItmCusF_3

DROP PROCEDURE zDP_gpItmCusF_4

DROP PROCEDURE zDP_gpItmCusF_5

DROP PROCEDURE zDP_gpItmCusF_6

DROP PROCEDURE zDP_gpItmCusL_1

DROP PROCEDURE zDP_gpItmCusL_2

DROP PROCEDURE zDP_gpItmCusL_3

DROP PROCEDURE zDP_gpItmCusL_4

DROP PROCEDURE zDP_gpItmCusL_5

DROP PROCEDURE zDP_gpItmCusL_6

DROP PROCEDURE zDP_gpItmCusN_1

DROP PROCEDURE zDP_gpItmCusN_2

DROP PROCEDURE zDP_gpItmCusN_3

DROP PROCEDURE zDP_gpItmCusN_4

DROP PROCEDURE zDP_gpItmCusN_5

DROP PROCEDURE zDP_gpItmCusN_6

DROP PROCEDURE zDP_gpItmCusSD

DROP PROCEDURE zDP_gpItmCusSI

DROP PROCEDURE zDP_gpItmCusSS_1

DROP PROCEDURE zDP_gpItmCusSS_2

DROP PROCEDURE zDP_gpItmCusSS_3

DROP PROCEDURE zDP_gpItmCusSS_4

DROP PROCEDURE zDP_gpItmCusSS_5

DROP PROCEDURE zDP_gpItmCusSS_6

DROP PROCEDURE zDP_gpItmCusUN_3

DROP PROCEDURE zDP_gpItmCusUN_4

DROP PROCEDURE zDP_gpItmCusUN_5

DROP PROCEDURE zDP_gpItmCusUN_6

DROP PROCEDURE zDP_gpUPRCPRF_1

DROP PROCEDURE zDP_gpUPRCPRF_2

DROP PROCEDURE zDP_gpUPRCPRF_3

DROP PROCEDURE zDP_gpUPRCPRF_4

DROP PROCEDURE zDP_gpUPRCPRF_5

DROP PROCEDURE zDP_gpUPRCPRL_1

DROP PROCEDURE zDP_gpUPRCPRL_2

DROP PROCEDURE zDP_gpUPRCPRL_3

DROP PROCEDURE zDP_gpUPRCPRL_4

DROP PROCEDURE zDP_gpUPRCPRL_5

DROP PROCEDURE zDP_gpUPRCPRN_1

DROP PROCEDURE zDP_gpUPRCPRN_2

DROP PROCEDURE zDP_gpUPRCPRN_3

DROP PROCEDURE zDP_gpUPRCPRN_4

DROP PROCEDURE zDP_gpUPRCPRN_5

DROP PROCEDURE zDP_gpUPRCPRSD

DROP PROCEDURE zDP_gpUPRCPRSI

DROP PROCEDURE zDP_gpUPRCPRSS_1

DROP PROCEDURE zDP_gpUPRCPRSS_2

DROP PROCEDURE zDP_gpUPRCPRSS_3

DROP PROCEDURE zDP_gpUPRCPRSS_4

DROP PROCEDURE zDP_gpUPRCPRSS_5

DROP PROCEDURE zDP_gpUPRCPRUN_2

DROP PROCEDURE zDP_gpUPRCPRUN_3

DROP PROCEDURE zDP_gpUPRCPRUN_4

DROP PROCEDURE zDP_gpUPRCPRUN_5

DROP PROCEDURE zDP_MinPONumF_1

DROP PROCEDURE zDP_MinPONumL_1

DROP PROCEDURE zDP_MinPONumN_1

DROP PROCEDURE zDP_MinPONumSD

DROP PROCEDURE zDP_MinPONumSI

DROP PROCEDURE zDP_MinPONumSS_1

DROP PROCEDURE zDP_TA1099F_1

DROP PROCEDURE zDP_TA1099F_2

DROP PROCEDURE zDP_TA1099L_1

DROP PROCEDURE zDP_TA1099L_2

DROP PROCEDURE zDP_TA1099N_1

DROP PROCEDURE zDP_TA1099N_2

DROP PROCEDURE zDP_TA1099SD

DROP PROCEDURE zDP_TA1099SI

DROP PROCEDURE zDP_TA1099SS_1

DROP PROCEDURE zDP_TA1099SS_2

DROP PROCEDURE zDP_TA1099UN_1

DROP PROCEDURE zDP_TACHANGEF_1

DROP PROCEDURE zDP_TACHANGEL_1

DROP PROCEDURE zDP_TACHANGEN_1

DROP PROCEDURE zDP_TACHANGESD

DROP PROCEDURE zDP_TACHANGESI

DROP PROCEDURE zDP_TACHANGESS_1

DROP PROCEDURE zDP_TAIVRecF_1

DROP PROCEDURE zDP_TAIVRecF_2

DROP PROCEDURE zDP_TAIVRecL_1

DROP PROCEDURE zDP_TAIVRecL_2

DROP PROCEDURE zDP_TAIVRecN_1

DROP PROCEDURE zDP_TAIVRecN_2

DROP PROCEDURE zDP_TAIVRecSD

DROP PROCEDURE zDP_TAIVRecSI

DROP PROCEDURE zDP_TAIVRecSS_1

DROP PROCEDURE zDP_TAIVRecSS_2

DROP PROCEDURE zDP_TAIVRecUN_1

DROP PROCEDURE zDP_TASCMFGF_1

DROP PROCEDURE zDP_TASCMFGF_2

DROP PROCEDURE zDP_TASCMFGL_1

DROP PROCEDURE zDP_TASCMFGL_2

DROP PROCEDURE zDP_TASCMFGN_1

DROP PROCEDURE zDP_TASCMFGN_2

DROP PROCEDURE zDP_TASCMFGSD

DROP PROCEDURE zDP_TASCMFGSI

DROP PROCEDURE zDP_TASCMFGSS_1

DROP PROCEDURE zDP_TASCMFGSS_2

DROP PROCEDURE zDP_TASCMFGUN_1

DROP PROCEDURE zDP_WHPSETPF_1

DROP PROCEDURE zDP_WHPSETPL_1

DROP PROCEDURE zDP_WHPSETPN_1

DROP PROCEDURE zDP_WHPSETPSD

DROP PROCEDURE zDP_WHPSETPSI

DROP PROCEDURE zDP_WHPSETPSS_1

DROP PROCEDURE zDP_WHPT001F_1

DROP PROCEDURE zDP_WHPT001F_2

DROP PROCEDURE zDP_WHPT001L_1

DROP PROCEDURE zDP_WHPT001L_2

DROP PROCEDURE zDP_WHPT001N_1

DROP PROCEDURE zDP_WHPT001N_2

DROP PROCEDURE zDP_WHPT001SD

DROP PROCEDURE zDP_WHPT001SI

DROP PROCEDURE zDP_WHPT001SS_1

DROP PROCEDURE zDP_WHPT001SS_2

DROP TRIGGER taAccountInsert

DROP TRIGGER taCustomerAddressInsert

DROP TRIGGER taCustomerInsert

DROP TRIGGER taVendorAddressInsert

DROP TRIGGER taVendorInsert

/* Run these against the system database for Dynamics GP */

Drop Table autotemp

Drop Table gpCustomerPOSetup

Drop Table TA_Map

Drop Table TA0010

Drop Table TA00850

Drop Table TA00860

Drop Table TA60100

Drop Table TANPWD

DROP PROCEDURE amAutoGrant

DROP PROCEDURE macGrantAll

DROP PROCEDURE DROP PROCEDURE smUserWorkCopy1

DROP PROCEDURE TA_ParentInsertAddressPM

DROP PROCEDURE TA_ParentInsertAddressRM

DROP PROCEDURE TA_ParentInsertGL

DROP PROCEDURE TA_ParentInsertPM

DROP PROCEDURE TA_ParentInsertRM

DROP PROCEDURE taRunProcedure

DROP PROCEDURE zDP_gpCustomerPOSetupF_1

DROP PROCEDURE zDP_gpCustomerPOSetupL_1

DROP PROCEDURE zDP_gpCustomerPOSetupN_1

DROP PROCEDURE zDP_gpCustomerPOSetupSD

DROP PROCEDURE zDP_gpCustomerPOSetupSI

DROP PROCEDURE zDP_gpCustomerPOSetupSS_1

DROP PROCEDURE zDP_TA_MapF_1

DROP PROCEDURE zDP_TA_MapL_1

DROP PROCEDURE zDP_TA_MapN_1

DROP PROCEDURE zDP_TA_MapSD

DROP PROCEDURE zDP_TA_MapSI

DROP PROCEDURE zDP_TA_MapSS_1

DROP PROCEDURE zDP_TA0010F_1

DROP PROCEDURE zDP_TA0010L_1

DROP PROCEDURE zDP_TA0010N_1

DROP PROCEDURE zDP_TA0010SD

DROP PROCEDURE zDP_TA0010SI

DROP PROCEDURE zDP_TA0010SS_1

DROP PROCEDURE zDP_TA00850F_1

DROP PROCEDURE zDP_TA00850L_1

DROP PROCEDURE zDP_TA00850N_1

DROP PROCEDURE zDP_TA00850SD

DROP PROCEDURE zDP_TA00850SI

DROP PROCEDURE zDP_TA00850SS_1

DROP PROCEDURE zDP_TA00860F_1

DROP PROCEDURE zDP_TA00860F_2

DROP PROCEDURE zDP_TA00860L_1

DROP PROCEDURE zDP_TA00860L_2

DROP PROCEDURE zDP_TA00860N_1

DROP PROCEDURE zDP_TA00860N_2

DROP PROCEDURE zDP_TA00860SD

DROP PROCEDURE zDP_TA00860SI

DROP PROCEDURE zDP_TA00860SS_1

DROP PROCEDURE zDP_TA00860SS_2

DROP PROCEDURE zDP_TA00860UN_2

DROP PROCEDURE zDP_TA60100F_1

DROP PROCEDURE zDP_TA60100F_2

DROP PROCEDURE zDP_TA60100L_1

DROP PROCEDURE zDP_TA60100L_2

DROP PROCEDURE zDP_TA60100N_1

DROP PROCEDURE zDP_TA60100N_2

DROP PROCEDURE zDP_TA60100SD

DROP PROCEDURE zDP_TA60100SI

DROP PROCEDURE zDP_TA60100SS_1

DROP PROCEDURE zDP_TA60100SS_2

DROP PROCEDURE zDP_TANPWDF_1

DROP PROCEDURE zDP_TANPWDL_1

DROP PROCEDURE zDP_TANPWDN_1

DROP PROCEDURE zDP_TANPWDSD

DROP PROCEDURE zDP_TANPWDSI

DROP PROCEDURE zDP_TANPWDSS_1

On a new 18.3 company database I have, no prior PSTL, it let me initialize PSTL without any issues and showed 18.2.5.

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

RE: PSTL 18.2.5 throws an error at the end of setup in GP 18.3.1245

Thanks Derek for the scripts.

To confirm:

1. yes that fails even when trying to "Rebuild Procs" in PSTL for a failed company setup... always at 24%. It never completes and doesn't get a chance to grant permissions

2. yes the error message about the failed grant comes up always when trying to "Rebuild Procs" in PSTL for companies that had previously PSTL installed. It runs all the way thru the end, before throwing the error.

I'm going to remove the entry for a failing company in TA00860 and remove all the PSTL objects in the company DB only for now and see how it goes.

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

RE: PSTL 18.2.5 throws an error at the end of setup in GP 18.3.1245

Derek,

Tried them all.. first I'd remove all the PSTL objects from a non-working company and re-run the PSTL which would throw the usual error at 24% (object #28 in the run).

What I noticed this time is that there was a hidden pop-up behind the error message which I hadn't seen the previous times..

I tried to clean up all the PSTL objects from the DYNAMICS & the company DB's, installed the previous build 18.2.4, and it would fail exactly at the same place.. always stumbling on that "smChangeAccountIndex2", likely one of the 1st encrypted SP's for PSTL.

I even tried to run thru the add/remove program the re-installation of the PSTL, which then put back vers 18.2.1, which is incompatible with this version of GP.

After I got that removed and replaced as well by 18.2.5 again, it would run when I hit PSTL in GP and it would fail again with the same error as above..

It totally looks like that PSTL is unable to create some encrypted SP's.. I'm wondering if that couldn't be related to some SQL settings.. the server is running SQL 2016 SP2.

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

RE: PSTL 18.2.5 throws an error at the end of setup in GP 18.3.1245

Here is another thing I noticed once the PSTL 18.2.5 was re-installed and the DYNAMICS..TA00860 had been wiped out, I went into various companies.. the old ones would run thru, but throw the pop-up about the grant script..

The newer companies would still all fail at 24%.

From the Scripts you posted here, the system DB script shows in SSMS that some objects are missing:

As well for the company DB script, there are several dozens of objects missing.. even a few zDP_'s at the end that I didn't capture here..

I'm wondering why all those objects are not created and what keeps them from being added to a company DB.. All sessions are executed under the 'sa' account and DYNSA is the owner of the GP companies..

Was this reply helpful? Yes No
Suggested answer

Derek Albaugh on at

Like (0)

Report

RE: PSTL 18.2.5 throws an error at the end of setup in GP 18.3.1245

On my 18.3.1245 environment, I have the 5 TA_Parent.... procedures, taRunProcedure procedure, macGrantAll procedure and smUserWorkCopy1 procedure.

The same on my 18.3.1290 environment.

I'm fairly sure my 18.3.1245 is an upgrade from prior versions of GP 2018, 18.2 and 18.3, but not 100% at what version PSTL was first initialized and/or had procedures rebuilt.

With the encrypted procedures, I don't have scripts readily available either to manually create them.

I'm curious if the 18.3 version of PSTL from this site would resolve the issues you're seeing?

docs.microsoft.com/.../NOAM_PSTL_delta

Thanks

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

RE: PSTL 18.2.5 throws an error at the end of setup in GP 18.3.1245

Derek,

The PSTL download link provided is the same version I'm already using..

I've been checking back to one of my own demo GP 18.3 environment which was setup using PSTL 18.2.5 too and it has all the objects from your list.. with exception of 2 tables in the company DB (TWO)

DROP TABLE WHPSETP

DROP TABLE WHPT001

and the related SP's:

DROP PROCEDURE zDP_WHPSETPF_1

DROP PROCEDURE zDP_WHPSETPL_1

DROP PROCEDURE zDP_WHPSETPN_1

DROP PROCEDURE zDP_WHPSETPSD

DROP PROCEDURE zDP_WHPSETPSI

DROP PROCEDURE zDP_WHPSETPSS_1

DROP PROCEDURE zDP_WHPT001F_1

DROP PROCEDURE zDP_WHPT001F_2

DROP PROCEDURE zDP_WHPT001L_1

DROP PROCEDURE zDP_WHPT001L_2

DROP PROCEDURE zDP_WHPT001N_1

DROP PROCEDURE zDP_WHPT001N_2

DROP PROCEDURE zDP_WHPT001SD

DROP PROCEDURE zDP_WHPT001SI

DROP PROCEDURE zDP_WHPT001SS_1

DROP PROCEDURE zDP_WHPT001SS_2

Maybe those objects belong to a module that isn't installed in GP..

On the DYNAMICS DB side, there is no objects missing from the script list..

for now I can't phantom as why PSTL would not be able to re-create the 'encrypted' SP's in either the System or company DB..

I'll do some more testing on my own 18.3 demo system, not wanting to risk the integrity of the customer setup which is already flaky on that side.

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

RE: PSTL 18.2.5 throws an error at the end of setup in GP 18.3.1245

I just created a new company for another customer (unrelated) that is on GP 18.3.1200 and has PSTL 18.2.5 installed too..

The triggering of the PSTL setup in the new company generated 103 new SP's and 7 new tables in the company DB.

This confirms that the issue is somewhat with the GP setup on that other customer that prevents encrypted objects from being created and causes the PSTL setup to abort.

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

RE: PSTL 18.2.5 throws an error at the end of setup in GP 18.3.1245

I might have a beginning of a hint on the problem.. maybe I'm just wrong. I re-ran the PSTL create objects on a company where it was ok, but still throws the error at the end about the grant macro not found.. and the code 103. It seems to throw this error quite often in the DEXSQL log I captured..

/* Date: 07/14/2021 Time: 12:07:00

SQLSTATE:(37000) Native Err:(103) stmt(160992896):*/

[Microsoft][SQL Server Native Client 11.0][SQL Server]The identifier that starts with 'if exists (select * from dbo.sysobjects where id = Object_id('dbo.taRMCustMstrPeriodSumDetail') and type = 'P') begin drop proc ' is too long. Maximum length is 128.*/

/* Date: 07/14/2021 Time: 12:07:00

stmt(160992896):*/

use CC declare @iStatus int, @O_SQL_Error_State int EXEC @iStatus = taRunProcedure"if exists (select * from dbo.sysobjects where id = Object_id('dbo.taRMCustMstrPeriodSum') and type = 'P') begin drop proc dbo.taRMCustMstrPeriodSum end ",'', @O_SQL_Error_State

/*

/* Date: 07/14/2021 Time: 12:07:00

SQLSTATE:(37000) Native Err:(103) stmt(160992896):*/

[Microsoft][SQL Server Native Client 11.0][SQL Server]The identifier that starts with 'if exists (select * from dbo.sysobjects where id = Object_id('dbo.taRMCustMstrPeriodSum') and type = 'P') begin drop proc dbo.ta' is too long. Maximum length is 128.*/

/*

/* Date: 07/14/2021 Time: 12:07:00

SQLSTATE:(00000) Native Err:(103) stmt(160992896):*/

*/

/* Date: 07/14/2021 Time: 12:06:50

stmt(160992896):*/

use CC declare @iStatus int, @O_SQL_Error_State int EXEC @iStatus = taRunProcedure"if exists (select * from sysobjects where id = object_id('dbo.smCustomerChanger1') and sysstat & 0xf = 4) begin drop procedure dbo.smCustomerChanger1 end ",'', @O_SQL_Error_State

/*

/* Date: 07/14/2021 Time: 12:06:50

SQLSTATE:(37000) Native Err:(103) stmt(160992896):*/

[Microsoft][SQL Server Native Client 11.0][SQL Server]The identifier that starts with 'if exists (select * from sysobjects where id = object_id('dbo.smCustomerChanger1') and sysstat & 0xf = 4) begin drop procedure d' is too long. Maximum length is 128.*/

/*

/* Date: 07/14/2021 Time: 12:06:50

SQLSTATE:(00000) Native Err:(103) stmt(160992896):*/

What is this max length of 128 ?

Was this reply helpful? Yes No