Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Accpac 5.6 PU3 post-install issue

Status
Not open for further replies.

ramam1

Programmer
Mar 20, 2009
226
US
Hi,
I applied 5.6 PU3 last night and it seems to have gone well aside from one snag. Whenever some folks open the AR -> AR-Customers -> Customer module they get five pop-up erors in a row after whcih everything works right. It only happens to some users, it does not matter which workstation they use - both the ADMIN account and my regular user account (which is admin for everything) do not get the error pop-ups.

The five eror message are nearly identical.. the first one is:
Error Code: 5
Collection Class: ACCPACCustCtls
Property: (get) Item
Argument: vntIndexKey = "afecARCUSccexp"
Invalid Procedure call or argument

The next four are identical other than the Argument which is: afeARCUSccname afeARCUSccnumber afeARCUScctype afecBKCCTYPEdesc.

These all look like reading CC info is failing. We don't use any CC stuff in accpac but I noticed that PU3 brings with it a new payment capability so I'm wondering if that's related.

Any ideas?
thanks
ram

Workstations are all XP SP 3. Users run as limited accounts. SS2k8-R2.
 
It looks like the issue relates to profile customization. The users that have this issue have in common a UI customization that hides the listed fields. When I view the customized profiles via Admin->UI Profile Maintenance I see those fields listed as hidden for the affected profiles; when I open the actual AR Customers module and try to File->Customize those fields do not show-up so I can't clean them out.
Looks like this may be an Accpac PU3 bug. It's a bit of a nuisance to our users so I went DB diving to fix it up. Seems like running the following statements fixed it. Note that the relevant table exists in both SYS and DAT so if you share a Company DB across several companies it's all or none.

Here is the fix that worked for me - I strongly advise you DO NOT USE IT. This is what I did against one of my test environments to test it - I then ran data integrity check and got no complaints so I'm going live.

use T2DAT;
delete from CSUICST where CTRLTOHIDE like '%bkcc%' and PGMVER='56a';
delete from CSUICST where CTRLTOHIDE like '%ARCUScc%' and PGMVER='56a';

use T2SYS;
delete from CSUICST where CTRLTOHIDE like '%bkcc%' and PGMVER='56a';
delete from CSUICST where CTRLTOHIDE like '%ARCUScc%' and PGMVER='56a';

 
Might not be a bug so much as an oversight. I would say that the UI profile should be more graceful with this type of condition. It can happened when upgrading versions as well.
 
Oversight is a fair characterization, but I couldn't leave it as it was.
A simpler workaround would be to create a new profile group, customize it, switch the users over, and delete the old group.
In any case next person will find this page and not have to figure it out.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top