Sage MAS 90 and 200 Sage MAS 500 blogs Product Feedback Support Training
Reply
Contributor
mjohnstone
Posts: 16
Registered: 08-03-2009
0

Error 80 AR

AR I was going to do the Period End and I received the following message:

 

Error 80……..Invalid Key, definition and or name

O/S Error……Invalid Class String (err/ret=2/0)

Program…….AR_Customer Credit Card_Bus.PVC

Statement….329

Class……….AR_CustomerCreditCard_bus

Method……..ClearCreditCard

 

I have never used anything with “Credit Card” for any of my companies!!  I went into Utilities, Clear Credit Card – and it tells me that I am not authorized – so got no where.

Super Contributor
Posts: 1,462
Registered: 11-03-2008
0

Re: Error 80 AR

What version are you on?

Sage MAS Partner
LuAnnKlann
Posts: 13
Registered: 02-19-2010
0

Re: Error 80 AR

I had a pesky Error 80, referingto the same credit card file you got when trying to convert data from 4.2 to 4.4.  I think it is the product update 2.  I redid the migration on a 4.4, with NO updates, and the data converted.  Now, if only the enhancements would convert!  What version are you on?  Which updates?

Sage MAS Partner
TomTarget
Posts: 1,752
Registered: 11-02-2008
0

Re: Error 80 AR

Take a look at knowledgebase resolution id 522971.   This may be it.

Thomas H. Rogers, C.P.A.
Target System Technology, Inc. - Spokane, WA -
The best solution often comes not from answering the question asked, but understanding WHY the question was asked.
Sage MAS 90 Customer
tfischbeck
Posts: 1
Registered: 09-24-2010
0

Re: Error 80 AR

I am experiencing the same issue.  Has anyone found a resolution?

 

Version 4.30.0.18

 

Error #80:  Invalid key definition, number or name

Program  AR_CustomerCreditCard_bus.pvc

Line  329

 

 

Sage MAS Partner
TomTarget
Posts: 1,752
Registered: 11-02-2008
0

Re: Error 80 AR

[ Edited ]

I'm betting your recently installed service update 18 for 4.3?

 

That and either product update #1 or #2 for 4.4 do some updates for credit card compliance.

 

Did you look at the aforementioned knowledgebase article?  I believe you have to get the proper rights before you have any hope of getting further.

 

Also see this post

 

http://community.sagemas.com/t5/Technical-and-Installation/4-30-Service-Update-18-Issues/m-p/25596#M...

Thomas H. Rogers, C.P.A.
Target System Technology, Inc. - Spokane, WA -
The best solution often comes not from answering the question asked, but understanding WHY the question was asked.
Super Contributor
rmikolainis
Posts: 1,252
Registered: 10-29-2008
0

Re: Error 80 AR


TomTarget wrote:

Take a look at knowledgebase resolution id 522971.   This may be it.


Here is Resolution ID 522971 for you just in case:

 

Subject:

"The credit card conversion process was interrupted.  You do not have sufficient rights to perform this task.  See your system administrator." when trying to Activate or Convert data after installing SU18 for version 4.30 or PU1 for version 4.40.  There are new options in Role Maintenance that are unselected by default after installing Service Update 18 for v. 4.30 and Product Update 1 for v. 4.40.

Possible Resolution:

  1. Go to Library Master / Main Role Maintenance / tab 2 - Security Events and select "Allow Access to Credit Card Encryption in Company Maintenance" and Accept.
  2. Try activating or converting the data again.
Sage MAS Partner
soaman
Posts: 14
Registered: 12-19-2008
0

Re: Error 80 AR

I'm a little late to the party.....but this issue just came up.  They updated to 4.3.18 and now can't close AR.  After changing the security the close process now gets Error 80 for AR_TRANSACTIONPAYMENTHISTORY.  I'm out of ideas.  You got any?

Sage MAS Partner
TomTarget
Posts: 1,752
Registered: 11-02-2008
0

Re: Error 80 AR

Hopefully your backup is good.   There was a reported problem with this way back then.   The problem was not always readily noticable immediately after conversion,  some clients were going two weeks or more before they discovered the problem.  : (

 

I've avoided  the problem since  by doing rebuild key files before jumping between 17 and 18.   Seems to keep the problem from happening.  I believe the cause is something to do with damaged indexes in the pre-conversion data.

 

I don't recall if Sage came up with a fix if it was not caught immediately.   Might want to call tech support on this if you don't have a good backup.

Thomas H. Rogers, C.P.A.
Target System Technology, Inc. - Spokane, WA -
The best solution often comes not from answering the question asked, but understanding WHY the question was asked.